[c-nsp] L3VPN works, but not default route

[Aaron]

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:peter at rathlev.dk] 
Sent: Tuesday, April 17, 2012 8:32 PM
To: aaron1 at gvtc.com
Cc: Cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] L3VPN works, but not default route

On Tue, 2012-04-17 at 20:06 -0400, aaron1 at gvtc.com 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