Guest

Preview Tool

Cisco Bug: CSCus89661 - N7k not learning forwarding adjacency entry

Last Modified

May 18, 2018

Products (1)

  • Cisco Nexus 7000 Series Switches

Known Affected Releases

6.2(8)E1

Description (partial)

Symptom:
After adding a static route with no valid next hop, 0.0.0.0 is added as next hop. The ip route, ip arp, and ip adjacency (all in software) for directly connected hosts in the vlan specified in the ip route statement will all be correct, but in some instances the FIB adjacency in hardware (show forwarding adjacency) may show unresolved. This may cause packet loss to hosts in the specified vlan.

Conditions:
1) Must have 2 ip route statements using a vlan. One with and one without a NH specified. 

Example:
ip route 50.50.50.0/31 Vlan50 1.50.0.2
ip route 50.50.50.0/31 Vlan50
Bug details contain sensitive information and therefore require a Cisco.com 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.