SNMPv3 test fails when adding and/or editing nodes in the SolarWinds Platform Website

This article provides brief information and steps to resolve the issue when the SNMPV3 test fails when adding or editing nodes in the SolarWinds Platform website. 

The device is responding to SNMPv3 request with some Context Name, which is not been sent by SolarWinds NPM. Therefore, when the information is returned under SNMPV3 packet its been rejected by the SolarWinds Platform .
 

SNMPv3 Username: testuser
SNMPv3 Authentication Method: SHA1
SNMPv3 Authentication Password: test1234ro
 
SNMPv3 Privacy / Encryption Method: DES56
SNMPv3 Privacy / Encryption Password: test1234ro

Note

The SNMP test will fail if the values of these OID(s) are not returned. Ensure you can see these OID(s) when running an SNMP walk.

• 1.3.6.1.2.1.1.1 - sysDescr
• 1.3.6.1.2.1.1.2 - sysObjectID
• 1.3.6.1.2.1.1.3 - sysUpTime

Run SolarWinds SNMP Walk for the node, and if you can access all of these OID(s), increase the SNMP timeout value to 10000 ms, and test SNMP on the Web Console again:

1. In the SolarWinds Platform Web Console, go to Settings > Polling Settings.
2. On the Polling Settings page, Under Network, look for SNMP TIMEOUT.
3. Change the value of SNMP TIMEOUT to 10000 ms.
4. Click Submit to save the changes.

Resolution 1:

Either the Context name must be configured on the device and then fed into the SolarWinds Platform NPM SNMPv3, or the issue must be corrected by the device's Vendor.

Resolution 2:

Remove the Context from the actual device. Refer to Troubleshoot an SNMP Node/SNMP Test Failed result . 

Resolution 3:

Scenario: Another device already added to the SolarWinds Platform via SNMPv3 and the customer is insisting it is identically configured with the affected node.

1. Check CollectorService.log and look for this similar error:

ERROR DataPreProcessing - Processing result: PollerResultWrapper: PollerType=N.Uptime.SNMP.Generic, NetObject=N:13 ErrorCode=79F2, ErrorMessage=Error 31218 - SNMPv3 - Wrong Digests - The authentication digest did not match to the expected result, possible incorrect key/password.

If  the device is configured using Authentication-Key, it's entirely possible that the wrong one is on the affected device. Create a separate SNMPv3 account and assign that to the node and see if that works. 

2. If the same issue, provide Support with screenshots on how both working and non-working devices are configured to check on the device model (JUNOS), authentication setup, and if SNMP is set up to use MAC Address for engine-id. See the sample image below:



3. Implement SNMPv3 via 'authentication-password' instead of 'authentication-key'. It will be converted automatically to 'authentication-key' by using engine-id.

Resolution 4:

Verify the following has the same Method and Password from a working similar Node:

• SNMPv3 Authentication
• SNMPv3 Privacy / Encryption