cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
666
Views
0
Helpful
3
Replies

Multiple MPLS providers

parknfly2060
Level 1
Level 1

Hell all,

We are in the process of switching MPLS providers.  At this time we have most locations migrated.  However, we still have a couple on the old MPLS provider network.  All MPLS routers in our data center and remote locations are managed by the providers and we have no access to them.  However, we are using a Cisco 3550 switch to do our internal routing. 

Since we have migrated some of our sites over, we have begun having issues with remote sites finding servers in our data center or to be able to ping back to our data center.  It seems that network traffic is getting confused due to the 2 vendor routers.  I've been told that in order to have multiple routers on the same network, they should be weighted.  Since I can't get into them, does anyone have a suggestion on how to eliminate the issue of remote sites not able to access servers or unable to ping back to our data center?  They radomly seem to loose the ability, but soon will come back.

The 3550 is managed by us and is located behind the 2 vendor provided routers.  I have changed the routes for the migrated sites to point to the new MPLS router IP (.254) and maintained the existing route for the old router IP (.1).

3 Replies 3

vmiller
Level 7
Level 7

What does the routing table look like at the last layer 3 device you can manage at the remotes?

I'm suspecting that you are getting a default advertised from both providers.

The easiest fix would be on a device that you manage would be to modify the routes to prefer your new provider over

your old.

192.168.0.1 is existing vendor router

192.168.0.254 is new vendor router

Here is what is in the config for routes:

ip default-gateway 192.168.0.13

ip classless

ip route 0.0.0.0 0.0.0.0 192.168.0.13

ip route 192.168.8.0 255.255.255.0 192.168.0.13

ip route 192.168.9.0 255.255.255.0 192.168.0.13

ip route 192.168.10.0 255.255.255.0 192.168.0.13

ip route 192.168.40.0 255.255.255.0 192.168.0.1

ip route 192.168.41.0 255.255.255.0 192.168.0.254

ip route 192.168.42.0 255.255.255.0 192.168.0.254

ip route 192.168.43.0 255.255.255.0 192.168.0.254

ip route 192.168.44.0 255.255.255.0 192.168.0.254

ip route 192.168.45.0 255.255.255.0 192.168.0.254

ip route 192.168.46.0 255.255.255.0 192.168.0.254

ip route 192.168.47.0 255.255.255.0 192.168.0.254

ip route 192.168.48.0 255.255.255.0 192.168.0.254

ip route 192.168.49.0 255.255.255.0 192.168.0.254

ip route 192.168.50.0 255.255.255.0 192.168.0.254

ip route 192.168.51.0 255.255.255.0 192.168.0.254

ip route 192.168.52.0 255.255.255.0 192.168.0.254

ip route 192.168.53.0 255.255.255.0 192.168.0.254

ip route 192.168.54.0 255.255.255.0 192.168.0.254

ip route 192.168.55.0 255.255.255.0 192.168.0.1

ip route 192.168.56.0 255.255.255.0 192.168.0.1

ip route 192.168.57.0 255.255.255.0 192.168.0.1

ip route 192.168.58.0 255.255.255.0 192.168.0.1

ip route 192.168.59.0 255.255.255.0 192.168.0.1

ip route 192.168.60.0 255.255.255.0 192.168.0.1

ip route 192.168.61.0 255.255.255.0 192.168.0.254

ip route 192.168.62.0 255.255.255.0 192.168.0.254

ip route 192.168.63.0 255.255.255.0 192.168.0.1

ip route 192.168.100.0 255.255.255.0 192.168.0.13

ip route 192.168.105.0 255.255.255.0 192.168.0.1

Here is the result of show ip route:

Gateway of last resort is 192.168.0.13 to network 0.0.0.0

S 192.168.46.0/24 via 192.168.0.254

S 192.168.63.0/24 via 192.168.0.1

S 192.168.62.0/24 via 192.168.0.254

S 192.168.47.0/24 via 192.168.0.254

S 192.168.44.0/24 via 192.168.0.254

S 192.168.61.0/24 via 192.168.0.254

S 192.168.105.0/24 via 192.168.0.1

S 192.168.60.0/24 via 192.168.0.1

S 192.168.45.0/24 via 192.168.0.254

S 192.168.42.0/24 via 192.168.0.254

S 192.168.59.0/24 via 192.168.0.1

S 192.168.8.0/24 via 192.168.0.13

S 192.168.58.0/24 via 192.168.0.1

S 192.168.43.0/24 via 192.168.0.254

S 192.168.9.0/24 via 192.168.0.13

S 192.168.10.0/24 via 192.168.0.13

S 192.168.40.0/24 via 192.168.0.1

S 192.168.57.0/24 via 192.168.0.1

S 172.17.6.80 via 192.168.0.13

S 192.168.56.0/24 via 192.168.0.1

S 192.168.41.0/24 via 192.168.0.254

S 192.168.55.0/24 via 192.168.0.1

C 192.168.4.0/24 is directly connected, Vlan4

S 192.168.54.0/24 via 192.168.0.254

C 192.168.5.0/24 is directly connected, Vlan5

C 192.168.6.0/24 is directly connected, Vlan6

S 192.168.53.0/24 via 192.168.0.254

C 192.168.7.0/24 is directly connected, Vlan7

S 192.168.52.0/24 via 192.168.0.254

S 192.168.51.0/24 via 192.168.0.254

C 192.168.0.0/24 is directly connected, Vlan1

S 192.168.50.0/24 via 192.168.0.254

C 192.168.2.0/24 is directly connected, Vlan2

S 192.168.49.0/24 via 192.168.0.254

S 192.168.100.0/24 via 192.168.0.13

S 192.168.48.0/24 via 192.168.0.254

S* 0.0.0.0/0 via 192.168.0.13

Thanks,

Garry Fincher

Systems Engineer

Park 'N Fly

Office: (404) 364-8138

Cel: (404) 578-0154

2060 Mt. Paran Road, NW

Atlanta, GA 30327

Why are some of your routes pointing to the existing mpls router at .1,& the default gateway at .13?

Is .13 connected to the the orginal provider ?

Review Cisco Networking products for a $25 gift card