[c-nsp] Aggregate label not generated

[Peter Rathlev]

Well, AFAIK "default-information originate" is needed to advertise
defaults also in VRFs. But if PE1 and PE2 are the same HW/SW that
shouldn't be the case here, i.e. 0.0.0.0/1 doesn't seem to be considered
a "default".

If I understand it correctly, for a label to be assigned by the router
the prefix needs to exist in the RIB "on itself". If the route from PE1,
and not the locally generated route, is installed in the RIB, and the
route uses Default-IP-Routing-Table as next hop via a
Loopback-to-Loopback LSP (L3VPN) you won't have a local label.

The route from PE1 is preferred since BGP admin distance is less than
the 250 assigned to the static.

Regards,
Peter


On Thu, 2008-06-19 at 03:00 +1200, Pshem Kowalczyk wrote:
> Hi,
> 
> First I would like to make sure that the stuff we're trying to do is
> actually doable and it should work :-)
> I'm not sure if default-originate would help within a vrf.
> 
> kind regards
> Pshem
> 
> 2008/6/19 David Prall <dcp at dcptech.com>:
> > 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
> >
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/