Hi Bob and Edward,It was me! I mentioned it. You can run a tunnel between two loopback on the router, and make each endpoint in a different VRF, and run a routing protocol over the tunnel. e.g. int loo 99ip vrf Aip address 1.1.1.1 255.255.255.255 int loo 100ip vrf Bip address 1.1.1.2 255.255.255.255 ip vrf Ard 1:1route-target both 1:1 ip vrf Brd 1:1route-target both 1:2 int tunnel 1ip vrf for Aip address 2.2.2.1 255.255.255.0tunnel source loo 99tunnel dest 1.1.1.2 int tunnel 2ip vrf for Bip address 2.2.2.2 255.255.255.0tunnel source loo 100tunnel dest 1.1.1.1 router ripno autovers 2 address-family ipv4 vrf Ano autonet 2.0.0.0 address-family ipv4 vrf Bno autonet 2.0.0.0 The BGP method is much more elegant though. IMHO.> From: [email protected] > Date: Fri, 5 Oct 2012 16:31:15 -0400 > To: [email protected] > CC: [email protected] > Subject: Re: [OSL | CCIE_RS] EIGRP VRF issue > > Probably need to use MP BGP and leak routes from one VRF to the other > that way. You can selectively redistribute using route-maps in BGP, or > I've also done it using import-maps or export-maps and setting > specific RTs for the routes to be leaked. > > I've heard of another way too (someone was just asking about this on > OSL a couple weeks ago) but not remembering it. > > Bob > -- > Sent from my iPhone, please excuse any typos. > > On Oct 5, 2012, at 1:50 PM, "Bodnar, Edward" <[email protected]> wrote: > > > They are not in the vrf. But question I am asking myself is this how to I > > advertise the connected routes out both VRF's? I can only put the > > interface in one VRF. > > > > -----Original Message----- > > From: Bob McCouch [mailto:[email protected]] > > Sent: Friday, October 05, 2012 1:47 PM > > To: Bodnar, Edward > > Cc: [email protected] > > Subject: Re: [OSL | CCIE_RS] EIGRP VRF issue > > > > I was wondering that. How about the connected routes? If the interface > > isn't in the VRF, the connected route wouldn't be either, it would be > > in the global. Do the connected routes show under 'sh ip route VRF > > blah'? > > > > Bob > > -- > > Sent from my iPhone, please excuse any typos. > > > > On Oct 5, 2012, at 1:36 PM, "Bodnar, Edward" <[email protected]> > > wrote: > > > >> Interesting I figured part of this out. My static routes did not have a > >> valid next hop so they were missing my fa1/0 int was not configured :( > >> .... Still need to figure out the connected route part. Gotta be > >> something simple. > >> > >> > >> > >> -----Original Message----- > >> From: Bob McCouch [mailto:[email protected]] > >> Sent: Friday, October 05, 2012 1:10 PM > >> To: Bodnar, Edward > >> Cc: [email protected] > >> Subject: Re: [OSL | CCIE_RS] EIGRP VRF issue > >> > >> Seems like a dumb thing to ask, but the connected interfaces and > >> static routes are in that VRF, not the global routing table, right? > >> > >> And you're setting a seed metric through a "default-metric" statement, > >> specifying on the redistribution line, or setting with a route-map, > >> right? > >> > >> Bob > >> -- > >> Sent from my iPhone, please excuse any typos. > >> > >> On Oct 5, 2012, at 12:47 PM, "Bodnar, Edward" <[email protected]> > >> wrote: > >> > >>> Question to all . Working in my lab and playing with VRF's and > >>> redistribution. I am having an issue with redistributing connected or > >>> static into my EIGRP VRF. I get an eigrp neighbor relationship with > >>> downstream devices. I can see routes if there not connected or static. > >>> Just those 2 key words not working, Not showing up in eigrp top table so > >>> the issue is there just not getting into eigrp at all. > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> Config attached. : > >>> > >>> > >>> > >>> router eigrp 100 > >>> > >>> redistribute connected > >>> > >>> no auto-summary > >>> > >>> ! > >>> > >>> address-family ipv4 vrf NEX2 > >>> > >>> redistribute connected metric 1000 100 255 1 1500 > >>> > >>> redistribute static metric 1000 100 255 1 1500 > >>> > >>> network 123.123.123.0 0.0.0.255 > >>> > >>> network 0.0.0.0 > >>> > >>> no auto-summary > >>> > >>> autonomous-system 100 > >>> > >>> exit-address-family > >>> > >>> ! > >>> > >>> address-family ipv4 vrf NEX1 > >>> > >>> redistribute connected metric 1000 100 255 1 1500 > >>> > >>> redistribute static metric 1000 100 255 1 1500 > >>> > >>> network 123.123.123.0 0.0.0.255 > >>> > >>> network 177.177.177.0 0.0.0.255 > >>> > >>> network 0.0.0.0 > >>> > >>> no auto-summary > >>> > >>> autonomous-system 100 > >>> > >>> exit-address-family > >>> > >>> _______________________________________________ > >>> For more information regarding industry leading CCIE Lab training, please > >>> visit www.ipexpert.com > >>> > >>> Are you a CCNP or CCIE and looking for a job? Check out > >>> www.PlatinumPlacement.com > >>> > >>> http://onlinestudylist.com/mailman/listinfo/ccie_rs > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com > > http://onlinestudylist.com/mailman/listinfo/ccie_rs _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com http://onlinestudylist.com/mailman/listinfo/ccie_rs
