There was discussion about bogon filters and the 0.0.0.0/24 not being advertised unless the default-information originate command was entered in BGP. I'm wondering if this is the same issue. If so open a case and have a bugid filed, unless of course there already is one.
David -- http://dcp.dcptech.com > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Pshem > Kowalczyk > Sent: Wednesday, June 18, 2008 10:32 AM > To: cisco-nsp > Subject: [c-nsp] Aggregate label not generated > > Hi, > > We have a L3VPN with quite a few routes (in ranges of 40k+). So far > all PEs that had to carry that were 6500, but soon we'll be adding a > few smaller ones (28xx) for remote sites. They don't need to know the > 'optimal' path to the destination, it's enough if the CEs hanging of > them can talk to other CEs in the same VPN. In order to do that we > decided to create aggregate label for 'pseudo-default' on the 6500s: > > ip route vrf custXXXX 0.0.0.0 128.0.0.0 Null0 250 > ip route vrf custXXXX 128.0.0.0 128.0.0.0 Null0 250 > > router bgp 7657 > address-family ipv4 vrf custXXXX > network 0.0.0.0 mask 128.0.0.0 > network 128.0.0.0 mask 128.0.0.0 > > > however, that didn't do what we wanted. We've configured that on 2 > PEs, and the results were as following: > > PE1: > #sh mpls forwarding-table vrf custXXXX 0.0.0.0 1 > Local Outgoing Prefix Bytes tag Outgoing Next Hop > tag tag or VC or Tunnel Id switched interface > > #sh ip route vrf custXXXX 0.0.0.0 128.0.0.0 > Routing entry for 0.0.0.0/1, supernet > Known via "static", distance 250, metric 0 (connected) > Advertised by bgp xyz > Routing Descriptor Blocks: > * directly connected, via Null0 > Route metric is 0, traffic share count is 1 > > > and PE2: > #sh mpls forwarding-table vrf custXXXX 0.0.0.0 1 > Local Outgoing Prefix Bytes tag Outgoing Next Hop > tag tag or VC or Tunnel Id switched interface > None 16 0.0.0.0/1 0 Te2/2 172.16.1.98 > > #sh ip route vrf custXXXX 0.0.0.0 128.0.0.0 > Routing entry for 0.0.0.0/1, supernet > Known via "bgp xyz", distance 200, metric 0, type internal > Redistributing via ospf 1 > Advertised by bgp xyz (self originated) > Last update from 172.16.31.239 00:04:47 ago > Routing Descriptor Blocks: > * 172.16.31.239 (Default-IP-Routing-Table), from > 172.16.31.239, 00:04:47 ago > Route metric is 0, traffic share count is 1 > AS Hops 0 > > > Any ideas why that didn't generate a label on PE1? > > kind regards > Pshem > _______________________________________________ > 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/
