[c-nsp] RIB-failure(2) - next-hop mismatch - In VRF context
Adam Vitkovsky
adam.vitkovsky at swan.sk
Tue May 7 04:30:50 EDT 2013
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
We tried changing the RT and it didn't work, we also tried advertising the
route from a different PE(NH) which obviously did the trick.
We did not clear the process or rebooted the router to rule out memory
issues or table allocation problems.
And obviously there are plenty of other routes with the same NH in this VRF
and they are all fine.
adam
More information about the cisco-nsp
mailing list