Preview Tool

Cisco Bug: CSCul22062 - RNH tracking dissapears after VDC OTV reload or join-interface flap

Last Modified

Feb 01, 2017

Products (7)

  • Cisco Nexus 7000 Series Switches
  • Cisco Nexus 7000 10-Slot Switch
  • Cisco Nexus 7000 4-Slot Switch
  • Cisco Nexus 7000 18-Slot Switch
  • Cisco Nexus 7700 18-Slot Switch
  • Cisco Nexus 7000 9-Slot Switch
  • Cisco Nexus 7700 10-Slot Switch

Known Affected Releases


Description (partial)

Convergence time for the OTV is highly impacted due to lacking RNH tracking.<br><br>

Following command prints out empty output and RNH tracking doesn't happen between pair of VDC OTV.<br><br>

h13-n7k-01-w2-otv# sh otv isis track-adjacency-nexthop<br>
OTV-IS-IS process: default<br><br>

Output of the command should look like this:<br>
h13-n7k-01-w2-otv(config-if)# sh otv isis track<br>
OTV-IS-IS process: default<br>
    OTV-ISIS adjs for nexthop:, VRF: default<br>
       Hostname: 0026.980d.8e42, Overlay: Overlay1<br><br>

Reload VDC OTV:<br>
- Symptoms are very deterministic. RNH tracking never recovers on the reloaded VDC but works fine on the 2nd VDC OTV from the pair.<br><br>

Join-interface flap on the VDC OTV:<br>
- Sometimes it happens sometimes not. Shut/no shut join-interface on the VDC OTV.  RNH tracking never recovers on the VDC were join-interface was flapped but works fine on the 2nd VDC OTV from the pair.<br><br>
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.