Cisco Bug: CSCuo06610 - PI: Prime Infrastructure does not check for duplicate SNMP engine IDs
May 07, 2020
- Cisco Prime Infrastructure
Known Affected Releases
1.3(0.20) 1.4(0.45) 2.0(0.0.294)
Symptom: When SNMPv3 protocol is used and some of devices have duplicated SNMP engine ID values, PI will be confused to which device is speaking 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 - some of devices becomes unreachable, we can see gaps on the graphs etc. PI should check for engine ID duplicates. Conditions: SNMPv3, multiple devices with same snmp engineID value.
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases