[c-nsp] Aggregate label not generated

Peter Rathlev peter at rathlev.dk
Thu Jun 19 03:24:48 EDT 2008


On Thu, 2008-06-19 at 16:38 +1200, Pshem Kowalczyk wrote:
> 2008/6/19 Peter Rathlev <peter at rathlev.dk>:
> > 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.
> 
> The question here is why is there no label on PE1 at all? It has a
> locally connected interface that gets into bgp using a network
> statement - it should generate a label for it. Unless I'm completely
> wrong here ...

Oh, now I see. I mixed up completely things when reading the original
mail. :-)

I hope I'm not being too dense here, but why doesn't PE2 show the static
route, and instead shows the one learned from BGP? And the destination
that PE2 sees wouldn't happen to be PE1 would it? Who generated the {16}
label that PE2 has as outgoing via Te2/2?

Also, a specific "show mpls for vrf X <prefix>" doesn't show the
aggregate label on our PEs. Without specifying the prefix it shows just
the aggregate label. Specifying connected prefixes gives nothing and
specifying remote prefixes gives the expected result:

HOR-CORE-1#show ip route vrf dcdriftc 10.83.8.0 255.255.255.0
Routing entry for 10.83.8.0/24
  Known via "connected", distance 0, metric 0 (connected, via interface)
  Advertised by bgp 65432
  Routing Descriptor Blocks:
  * directly connected, via Vlan108
      Route metric is 0, traffic share count is 1

HOR-CORE-1#show ip route vrf dcdriftc 10.83.69.0 255.255.255.0
Routing entry for 10.83.69.0/24
  Known via "bgp 65432", distance 200, metric 0, type internal
  Last update from 10.85.248.4 1w0d ago
  Routing Descriptor Blocks:
  * 10.85.248.4 (Default-IP-Routing-Table), from 10.85.248.4, 1w0d ago
      Route metric is 0, traffic share count is 1
      AS Hops 0

HOR-CORE-1#show mpls forwarding-table vrf dcdriftc 10.83.8.0 24    
Local  Outgoing    Prefix           Bytes tag  Outgoing   Next Hop    
tag    tag or VC   or Tunnel Id     switched   interface              
HOR-CORE-1#show mpls forwarding-table vrf dcdriftc 10.83.69.0 24
Local  Outgoing    Prefix           Bytes tag  Outgoing   Next Hop    
tag    tag or VC   or Tunnel Id     switched   interface              
None   17          10.83.69.0/24  0          Te6/5      10.85.250.14 
HOR-CORE-1#show mpls forwarding-table vrf dcdriftc              
Local  Outgoing    Prefix           Bytes tag  Outgoing   Next Hop    
tag    tag or VC   or Tunnel Id     switched   interface              
32     Aggregate   vrf:dcdriftc   687698517                          
HOR-CORE-1#

Regards,
Peter




More information about the cisco-nsp mailing list