Preview Tool

Cisco Bug: CSCvi21956 - PI 3.3 Inventory displays an invalid Reachability status for devices using AES-256 as priv type

Last Modified

Oct 21, 2019

Products (1)

  • Cisco Prime Infrastructure

Known Affected Releases

3.3 3.3(0.0) 3.3(1)

Description (partial)

Reachability status is invalid in PI 3.3 for devices using AES-192 & AES-256 as SNMP V3 priv type although credential verification & Inventory collection are being successful.

PI 3.3.0 or PI 3.3 Device Pack 1
Add a device using AES 192 & AES-256 as SNMP V3 privacy type, Reachability shows up as "Ping Reachable/SNMP Unreachable"

Related Community Discussions

Prime Infrastructure 3.1 snmpv3 issues
In the device rediscovery process I'm experiencing inconsistent snmp collection results.  At one time or another 22 devices (3750,3850,4500 switches and 2900 and ASR1001 routers) have been successfully discovered/rediscovered by the PI, only to later fail snmp collection with no changes in the PI snmp discovery settings or device configuration, (with ping and CLI/SSH being successful)   Here is a representative sample of the device configuration   snmp-server engineID local 123456789012 snmp-server ...
Latest activity: Apr 12, 2018
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.