You could also use a GRE tunnel for the connection as well. Jeff is right that this topic keeps coming up every so often. I wonder why Cisco won't just make this easier for people.
---------------------------------------------- Luan Nguyen Chesapeake NetCraftsmen, LLC. http://www.netcraftsmen.net ---------------------------------------------- -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ivan Pepelnjak Sent: Tuesday, June 16, 2009 1:24 PM To: 'Clue Store'; [email protected] Subject: Re: [c-nsp] Global Route Leaking on same PE 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. > -----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/
