Ivan Pepelnjak wrote:
The last time I've seen discussion on this topic, you had to have an
external back-to-back connection between a VRF interface and a global
interface.
I maybe wrong, but seems this was related to resolving the CEF adjacency
to a physical interface ?
I understand that you could then use the ip route vrf command, adding
the interface in the ip route statement.
-----Original Message-----
From: Clue Store [mailto:[email protected]]
Sent: Tuesday, June 16, 2009 4:18 PM
To: [email protected]
Subject: [c-nsp] Global Route Leaking on same PE
Hi All,
Looked through the archives but couldn't find anything about
this specific issue. I'm trying to leak a route from the
global table on a PE to an iterface that is on the same PE
but I get the folowwing when I try to just point it to a loopback.....
ip route vrf test 64.193.x.x 255.255.255.248 192.168.222.1
global %Invalid next hop address (it's this router)
Also tried to point it to just the interface and it says vpn
routes have to be pointed to next-hop addresses. Anyone have
some clue how to get this to work where the traffic never
leaves the same PE and makes a look around the network??
TIA
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
