OrionNPM 9.1SP3
Looking for a little help here.
We are in the process of changing to snmpv3, and after a code upgrade on a Cisco switch, the snmp-server engineid changed on the switch automatically, and as a result the snmpv3 userid's md5 hash was invalid.
A sniffer trace shows the switch responds with snmp reports of usmStatsUnknownUserNames and usmStatsUnknownEngineIDs when polled by OrionNPM
As a result we were not not getting alerts (software version change) or stats.
Looking in NPM monitor the device shows up, as it responds to ping, but it was just by luck I found we were not gathering stats.
What I am interested in is a way to determine via alerting that the we can't poll data via snmp from the device.
Any help is greatly appreciated.
