Thanks folks, 4.0.1 on a couple 4.1.2 on all the others
What is selective vrf download used for and why do you bring that up? I was trying to avoid doing anything in the ipv4 address families within the pe's. up to this point I'm able to simply take in vrf specific routes (connected, ospf) and simply put them into vpvn4 af's on pe's and it works. The only thing that isn't working is the default route coming from the pe. I see in the pe (closest to ce that is injecting ospf routes) ospf IA and E2 routes and this *DO* get redis'd over to the other side with the following....i didn't have to match internal or external... ? seems to be working for all except default route. (under bgp) vrf one rd 10.101.0.1:1 address-family ipv4 unicast redistribute ospf 1 -----Original Message----- From: Jason Lixfeld [mailto:[email protected]] Sent: Tuesday, April 17, 2012 10:37 PM To: Aaron Cc: Peter Rathlev; [email protected] Subject: Re: [c-nsp] L3VPN works, but not default route What version of XR is running on those 9ks? If it's 4.2.0, you might be hitting the SVD 'feature'. 'show svd role' http://www.cisco.com/en/US/docs/routers/asr9000/software/asr9k_r4.2/routing/ command/reference/b_routing_cr42asr9k_chapter_01.html#wp1470915078 -- Sent from my mobile device On 2012-04-17, at 11:25 PM, "Aaron" <[email protected]> wrote: > Do I need default info-orig in this configuration within the pe's in order for this to work? I think it's the default info-orig in the original ce that causes the 0/0 route to show up at the first pe, do I need default info-orig in the pe somewhere to make this 0/0 route make it across the l2vpn? > > > Pe closest to ce.... > > RP/0/RSP0/CPU0: 9k#show bgp vpnv4 unicast vrf one 0.0.0.0 Tue Apr 17 > 21:18:36.588 CST % Network not in table > > RP/0/RSP0/CPU0:9k#sh route vrf one 0.0.0.0 Tue Apr 17 21:18:50.441 CST > > Routing entry for 0.0.0.0/0 > Known via "ospf 1", distance 110, metric 1, candidate default path > Tag 12345, type extern 2 Installed Apr 17 16:12:48.181 for 05:06:02 > Routing Descriptor Blocks > 1.2.3.4, from 1.1.1.1, via TenGigE0/1/0/0 > Route metric is 1 > No advertising protos. > > Pe on other side of l2vpn.... (I'm only doing directly connected > connectivity here on this side) (ce on this side CAN ping remote ce's > specific route destinations, just not seeing default route in this pe > side) > > RP/0/RSP0/CPU0:otherpe-9k#show bgp vpnv4 unicast vrf one 0.0.0.0 Tue > Apr 17 21:21:30.280 CST % Network not in table > > RP/0/RSP0/CPU0:otherpe-9k#sh route vrf one summa Tue Apr 17 > 21:21:31.156 CST > > Route Source Routes Backup Deleted Memory (bytes) > local 1 0 0 136 > connected 1 0 0 136 > dagr 0 0 0 0 > bgp 64512 496 0 0 67456 > Total 498 0 0 67728 > > > > > -----Original Message----- > From: Peter Rathlev [mailto:[email protected]] > Sent: Tuesday, April 17, 2012 8:32 PM > To: [email protected] > Cc: [email protected] > Subject: Re: [c-nsp] L3VPN works, but not default route > > On Tue, 2012-04-17 at 20:06 -0400, [email protected] wrote: >> So, again, i see the default route learned via ospf on ce-pe >> advertisements in the pe vrf on one side of the cloud....then i redis >> ospf into mp-ibgp and i see all of my ospf routes (about 490 routes >> total) advertised over the mpls core to the other pe on the other >> side of the cloud .... the only route that doesn't make it over is >> 0/0 >> > What does "show ip bgp vpnv4 vrf NAME 0.0.0.0" say on both the PE closest to the originating CE and the PE in the other end? What does "show ip route vrf NAME 0.0.0.0" say on the remote PE? > > Is the default supposed to be redistributed to OSPF also on the remote PE? If so, do you have "default-information originate" on the OSPF process on this remote PE? > > -- > Peter > > > > _______________________________________________ > 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/
