[c-nsp] RIB-failure(2) - next-hop mismatch - In VRF context

[Adam Vitkovsky]

Hi Oli,

It's legacy 7206VXR (NPE-G2) 12.4(12.2r)T.  
And actually there's only this single 10.100.2.0/28 route coming from the
10.101.1.2 NH. 

#show ip route 10.101.1.2
Routing entry for 10.101.1.2/32
  Known via "isis", distance 115, metric 30, type level-1
  Redistributing via isis
  Last update from 10.101.2.11 on GigabitEthernet0/1, 7w0d ago
  Routing Descriptor Blocks:
  * 10.101.2.11, from 10.101.1.2, via GigabitEthernet0/1
      Route metric is 30, traffic share count is 1

#show ip route vrf voice1 10.101.1.2
Routing entry for 10.101.1.0/24
  Known via "connected", distance 0, metric 0 (connected, via interface)
  Redistributing via bgp 65512
  Advertised by bgp 65512
  Routing Descriptor Blocks:
  * directly connected, via GigabitEthernet0/2.1106
      Route metric is 0, traffic share count is 1

#show ip route vrf voice1 10.100.2.0
% Subnet not in table

adam

-----Original Message-----
From: Oliver Boehmer (oboehmer) [mailto:oboehmer at cisco.com] 
Sent: Tuesday, May 07, 2013 11:38 AM
To: Adam Vitkovsky; cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] RIB-failure(2) - next-hop mismatch - In VRF context



On 07/05/2013 10:30, "Adam Vitkovsky" <adam.vitkovsky at swan.sk> wrote:

>Hi folks,
>
>I'd like to ask what is the meaning of "RIB-failure(2) - next-hop 
>mismatch"
>- in context of a VRF table please
>
>#sh ip b vpnv4 vrf voice1 10.100.2.0
>BGP routing table entry for 16160:402:10.100.2.0/28, version 22965354
>Paths: (1 available, best #1, table voice1, RIB-failure(2) - next-hop
>mismatch)
>  Advertised to update-groups:
>        9
>  Local, imported path from 16160:454:10.100.2.0/28
>    10.101.1.2 (metric 30) from 10.101.1.2 (10.101.1.2)
>      Origin incomplete, metric 0, localpref 100, valid, internal, best
>      Extended Community: RT:16160:45400 RT:16160:50001
>      mpls labels in/out nolabel/667
>
>#sh ip b vpnv4 vrf voice1 rib-failure
>Network            Next Hop                      RIB-failure   RIB-NH
>Matches
>Route Distinguisher: 16160:402 (default for vrf voice1)
>10.100.2.0/28      10.101.1.2          Admin distance >= 255
>n/a

which version do you run? Can you share

show ip route 10.101.1.2
show ip route vrf voice1 10.101.1.2
show ip route vrf voice1 10.100.2.0


and you are seeing more BGP VRF routes installed with next-hop 10.101.1.2?

there is CSCsi11807 which shares the same problem signature, but can't tell
without more details.

	oli