Preview Tool

Cisco Bug: CSCuo06668 - PI: Multiple issues with Nexus 1000v devices when SNMPv3 is used

Last Modified

Oct 04, 2016

Products (1)

  • Cisco Prime Infrastructure

Known Affected Releases

1.3(0.20) 1.4(1.45) 2.0(0.0.294)

Description (partial)

All Nexus 1000v devices are using following engine ID 800000090302000c000000 in addition we don't have any possibility to change engine ID value manually (bug: CSCtl49904).

When SNMPv3 protocol is used and, PI will be confused to which device is speaking (because of the duplicated engine ID's) and will start setting wrong values for msgAuthoritativeEngineBoots / msgAuthoritativeEngineTime fields in SNMPv3 packets.

This issue breaks RFC 3414 synchronization and device is replaying with reports (usmStatsNotInTimeWindows) instead of normal get-responses.

Because of that communication by SNMPv3 protocol is broken - Nexus 1000v devices becomes unreachable, we can see gaps on the graphs etc.

SNMPv3, Nexus 1000v devices with NX-OS up to 4.2(1)SV2(2.2).
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.