[c-nsp] How not to redistribute statics into VRFs/BGP

David Freedman david.freedman at uk.clara.net
Mon Mar 30 13:28:25 EDT 2009


>ip route vrf Chmbr-General 0.0.0.0 0.0.0.0 10.120.24.2 ! This is an ASA
>on the 'LAN' for this site
>ip route vrf Chmbr-General 10.0.0.0 255.0.0.0 Serial0/1/0.310

Right, got you so far

>So I remove the static route pointing to 10.120.24.2 and point it to the
>remote MPLS spoke, 10.120.24.2.

You mean 10.120.112.2? 

>ip route vrf Chmbr-General 0.0.0.0 0.0.0.0 10.120.112.2 ! This is a
>different FW at a remote MPLS spoke
>ip route vrf Chmbr-General 10.0.0.0 255.0.0.0 Serial0/1/0.310

So both 10.120.24.2 and 10.120.112.2 are at the remote site?
any chance you can knock up a small ascii diagram else it gets a bit confusing.

>Traceroutes after the change show that it is using the main egress route
>going out the US, which is a gateway of last resort being propagated via
>BGP/VRF. 

US? 

How are you tracerouting? using "traceroute vrf Chmbr-General x.x.x.x" command?

Also worth noting that since you are doing what is called "recursive" routing here
(i.e point default at something which is also pointed at an interface) your traffic
will always go via Serial0/1/0.310 and onto your MPLS provider , anything past this
you have no direct influence over (usually) and hence you will need to have them change the
way the default is advertised into their VRF as well.

Does this make sense?

Dave.



More information about the cisco-nsp mailing list