SNMPv3 discovery fails or only creates Pingable
Article ID: 4317
Updated On:
Products
Issue/Introduction
Discovery of device, using an SNMP v3 profile, only responds to ICMP
Discovering a device using SNMPv3 fails, no device is discovered and polled.
Discovering a device using SNMPv3 fails, only creates a Pingable item.
When we enable "Detailed SNMP Logging by IP" via the <DA_Host>:<Port>/dcdebug page and reproduce the Discovery attempt we see the following.
Dec 07 16:42:57.312: Enabling SNMP logging
Dec 07 16:43:28.750: Send SNMP request [Initial Q position: 0 / Delay: 0 ms], Q Size: 0: GETNEXT[{contextEngineID=80:00:07:c7:03:d4:c1:9e:11:ca:40, contextName=}, requestID=65, errorStatus=0, errorIndex=50, VBS[1.3.6.1.2.1.1.3 = Null]]
Dec 07 16:43:37.752: No SNMP response for evRequest: GETNEXT[{contextEngineID=80:00:07:c7:03:d4:c1:9e:11:ca:40, contextName=}, requestID=65, errorStatus=0, errorIndex=50, VBS[1.3.6.1.2.1.1.3 = Null]]
Environment
All supported DX NetOps Performance Management releases
Cause
The username and/or password values set in the SNMP Profile used by the Discovery run are incorrect.
Resolution
The OID returned by the failed Discovery attempt is defined as:
usmStatsWrongDigests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The total number of packets received by the SNMP engine which were dropped because they didn't contain the expected digest value."
What this is really telling us is that we've used the wrong user name, auth password or priv password in the SNMPv3 Profile used.
Validate the SNMPv3 Credentials in use work using the sapwalk2 or snmpwalk commands.
Edit the SNMP Profile and retype the values ensuring the correct syntax is used to match required credentials.
Additional Information
How to use sapwalk to get a mib dump file
https://knowledge.broadcom.com/external/article/48972/
How to SNMPWalk2 a v3 device
Feedback
