Preview Tool

Cisco Bug: CSCvs44324 - ADJMGR and FIB Next Hop Interface are not consistent

Last Modified

Aug 28, 2020

Products (1)

  • Cisco Nexus 9000 Series Switches

Known Affected Releases


Description (partial)

As there is no specific route to the destination, so the next hop is following the default route but the next-hop rewrite is incorrect. Following a looping of ARP replies we can see that the Software adjacency table and the HW BCM Next Hop are out of sync:

slot  1
IPv4 adjacency information

next_hop:  rewrite_info:0000.5e00.013c   interface:Vlan3097 (Phy 0x1a004e00) <==== actual forwarding port

Eth1/40         436227584  (0x1a004e00)    <====converted the HEX back to port number

* 3097     0000.5e00.013c   dynamic  0         F      F    Po10 <======MAC learning port

There is no specific route in the routing table, it is using the default route for the data traffic
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.