MPLS network - local routing problem

macwhizard

I'm having something strange going on my MPLS network, which is under testing. MPLS is provided by an ISP.

Site A
LAN - 10.0.3.0/24
WAN GW - 10.1.1.2/30

static route - 0.0.0.0 0.0.0.0 10.1.1.2


Site B
LAN - 10.0.4.0/24
WAN GW - 10.2.10.2/30

static route - 0.0.0.0 0.0.0.0 10.2.10.2

Site C
LAN - 10.0.10.0/24
WAN GW - 10.200.216.57/30

static route - 10.0.4.0 255.255.255.0 10.200.216.57
static route - 10.0.3.0 255.255.255.0 10.200.216.57


Ok, From site C I'm able to ping A & B, but not vice-versa unless I put 0.0.0.0 0.0.0.0 10.0.216.57 in site C router!!!!
It won't even ping my router LAN IP.

where have i gone wrong ? Any explanation for this ?. Been ripping my hair on this.

pcgizzmo

To get it to work I think your going to need to do the same things to A and B as you did to C. You have static routes to A and B on C but not static routes to B and C on A or B.

You have default routes that say if the router doesn't know what the address is to send it out your GW but from there it doesn't know what to do with it on A or B In the routes on C you actually put the destination network in the IP so the router has something to match up to.

Also you shouldn't have to use static routes on your MPLS network is your provider not using something such as BGP? You should work with them on this as static routes aren't the best option especially if you are growing your network at any time in the future.

lsud00d

Wild guess since I'm not a network admin (haven't started CCNA studies yet but I know a little bit) but you set static default routes on site A and B but not C? Would the below work to address your problem?

Site A
10.0.4.0 255.255.255.0 10.1.1.2
10.0.10.0 255.255.255.0 10.1.1.2

Site B
10.0.3.0 255.255.255.0 10.2.10.2
10.0.10.0 255.255.255.0 10.2.10.2

networker050184

What kind of MPLS service and hand off are you getting?

macwhizard

@pcgizzmo & lsud00d
****************
I have tried giving static route to 10.0.10.0 on A & B with relavent GW ip's. It is not working.

Not sure if ISP is using BGP.

@networker050184
***************
It is not root/hub MPLS type, kinda point-multipoint.

The thing I don't understand is, how come A & B are able to reach C LAN network, when 0.0.0.0 0.0.0.0 10.0.216.57 is given in C router and not otherwise ?.

When 0.0.0.0 is not set on C, the traceroute from A & B stops at their relevant gateways, and when enabled it reaches LAN of C. I think I'm missing something important here.

networker050184

How are you testing the pings? Are you pinging from the router A/B to C? By default the router will use the outgoing interface address, which I'm assuming is in the 10.1.1.0/30 or 10.2.10.0/30 range. So since site C doesn't have a default route it has no way to reach these two ranges. Try doing an extended ping using the LAN addresses as the source.

macwhizard

I'm pinging from A/B router to a PC in C LAN. Not sure these non-cisco(A & boxes support extended ping, also wonder if this issue happens due to these devices.

I have added the following in router C

ip route 10.0.4.0 255.255.255.0 10.200.216.57
ip route 10.0.3.0 255.255.255.0 10.200.216.57
ip route 10.1.1.0 255.255.255.252 10.200.216.57
ip route 10.2.10.0 255.255.255.252 10.200.216.57

even so A & B can't ping inside C without the default route ( 0.0.0.0 0.0.0.0 10.0.216.57 ). Another interesting fact is i'm able to ping GW & router wan interfaces of A & B with the last 2 routes in place from C.

The thing is i'm planning to have internet access from site C, in that case I can't put a default route to the MPLS.

networker050184

You shouldn't need a default route there as long as you have specific routes for everything you are pinging from. Obviously the next hop router knows how to get back if it works with the default. You are just missing something or its a host firewall issue etc.

Another thing some people do is route all RFC 1918 space (and any internally reached public addressing) towards the inside MPLS then a default route to the internet. That's more of a lazy catch all way to do it, but it works.