Well... so it works in 12.4.4 but not 12.4.24 as configured. I had wanted to use the global instead of specifying an interface. I don't remember the train of thought for that right now as the config has been in place for over a year.
I also wanted to avoid putting any static routes in the Customer VRFs and instead use MPBGP to import the routes from vrf VOIP. So that I could maintain all of the routes to be shared in a single table. --Karl Karl Putland Senior Engineer *SimpleSignal* Anywhere: 303-242-8608 <http://www.simplesignal.com/explainer_video.php> On Tue, Oct 8, 2013 at 3:47 PM, Peter Rathlev <[email protected]> wrote: > On Tue, 2013-10-08 at 12:15 -0600, Karl Putland wrote: > > So I have a working MPBGP VRF-Lite configuration that does what I > > expect on 12.4.4. When I upgrade to 12.4.24 or 12.4.20 or 12.4.22 it > > stops returning traffic from the customer VRFs and CEF drops packets > > with Unresolved Route. 12.4.15 is the last 12.4 that seems to work. > > 15.2.4 also appears to work. I'm hoping that someone can help shed > > some light on this. I've been searching release notes for a couple of > > days and I'm coming up empty. > > Maybe related to the 172.1.119.177 next hop being unreachable in VRF > "E701" since Gi0/1 is in global routing and the most specific covering > route is 0.0.0.0/0 -> drop? > > For VPN routes that require a next-hop you can just use the target > address itself. Something like this: > > ip route vrf E701 172.1.119.177 255.255.255.255 Gi0/1 172.1.119.177 > ip route vrf E701 172.1.119.178 255.255.255.255 Gi0/1 172.1.119.178 > > -- > Peter > > > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
