[c-nsp] vs route leaking into globasl on the samer box

[Jeff Kell]

You can insert statics to an L3 interface with a next-hop of a second
router (very kludgy and inefficient, but required for the reason you
discovered).

You can use a FWSM or external box to handle the route [leak].

You can loop a cable between global and the target VRF.

You can do "VRF Selection using Policy-Based Routing" (Google that on
site:cisco.com) where you define an SVI that exists in multiple VRFs
and/or global, and you use policy-based routing to select the forwarding
table to be used in lookups for traffic received on that interface.  IOS
will insert the interface as a connected route in each of the included
VRFs.  We use this to land VPN traffic... (VPN box defaults to route to
the global address of the selector interface, and policy-routes based on
the source address of the incoming VPN traffic)

Jeff



On 1/2/2012 5:43 AM, Arne Larsen / Region Nordjylland wrote:
> Hi all.
>
> Can someone give me a hint about route leaking.
> I would like to leak a vrf network into the global routing table.
> I'm using a 6500-vss environment. The vrf network is a vlan directly on the vss.
> When I try to leak it into the global routing I get an error that next hop is the router it self.
> Is there a way to get around this.
>
> Happy new year to all.
>
> /Arne
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/