[c-nsp] route table lookup on leaking between vrfs

[Oliver Boehmer (oboehmer)]

Pshem Kowalczyk <> wrote on Wednesday, December 12, 2007 1:03 AM:

> Hi All,
> 
> 
> We have a setup with two vrfs (on 6500, sup720). Only some routes
> (aggregates) are imported from vrf Internal to vrf Servers. Some of
> the routes in 'Internal' are available through external eBGP peerings,
> some - through connected networks. Vrf servers spans a few different
> boxes.
> 
> And now the problem.
> 
> In vrf servers I have a route for 192.168.0.0/16, in vrf Internal
> there is that route as well as a bunch of /24 for more specific
> prefixes (received from different ebgp peers then the original /16,
> but those don't get leaked into vrf Servers). When I do a trace from
> one of the servers to anything in those /24 it always chooses the next
> hop for the /16.
> 
> In non-vrf situation I would use next-hop-self before advertising the
> /16 to all the other peers, that would force the lookup on the router
> that knows about the /24s. Is there a way to do this lookup when the
> routes are leaked between vrfs?

No, this is not possible unless you are creating an aggregate on a PE
somewhere (which would set the next-hop accordingly and allocate an
aggregate label to do the 2nd lookup). Why don't you just import the /24
into the Server vrf as well? you could use communities to tag them and
not advertise them beyond the PEs if you worry about it.

	oli