[c-nsp] NPE-400/12.2(18)S3, TFIB not populated from mBGP

[Tomas Daniska]

Hi folks,

we have an issue with TFIB not being populated from BGP VPN prefices on
a NPE400-based PE.

The tag arrives correctly via BGP:

router#sh ip bgp vpn vrf <X> labels 
   Network          Next Hop      In label/Out label
   172.17.1.0/24    x.x.x.x   nolabel/172

but it's not populated into this VRF's TFIB:

router#sh tag forwarding-table vrf <X>
Local  Outgoing    Prefix              Bytes tag  Outgoing   Next Hop

tag    tag or VC   or Tunnel Id        switched   interface



and thus CEF adjacencies also are not built so tags would be imposed...


router#sh ip cef vrf <X> 172.17.1.0 
172.17.1.0/24, version 794, epoch 0, per-destination sharing
0 packets, 0 bytes
  Flow: AS 0, mask 24
  tag information set, all rewrites inheritted
    local tag: assigned-when-resolved-later
  via x.x.x.x, 0 dependencies, recursive
    next hop y.y.y.y, GigabitEthernet2/0.45 via x.x.x.x/32
    valid adjacency
  Recursive load sharing using x.x.x.x/32.

At the same time, other VRFs on the box are working OK. The issue
appears intermittenly and so far we were not able to correlate the
appearances to any common denominator (we suspect this occurs usually
after some flaps, but have not confirmed that yet). Withdraw/readvertise
usually helps.




Searching the bug tool for 12.2(18)S3 the closest DDTSs I came to were
ee83549, ee63825 and eb68673 but in my oppiniom their symptoms do not
match the situation.

Does this ring a bell to anyone? Oli? Dennis? :)


Thanks! 

(please keep the Cc: address when replying)



--
 
Tomas Daniska
systems engineer

Tronet, a.s.
Plynarenska 5, 829 75 Bratislava, Slovakia
tel: +421 2 58224111, fax: +421 2 58224199
 
Nobody ever got rich by telling the American public that what they had
was good enough and that they really didn't need anything better!
-- Bob Atkins