SNMPv2 Request Not Working

Attempting to poll a device using SNMPv2. Target host documentation has been reviewed and seems very straightforward. When testing the SNMPv2 connection from the GUI I get the standard and not very informative yellow banner "test failed"

When I run a SNMP Walk from the polling server to the target I get a few errors but a file does produce with over 1074 OID's. I cannot determine what portion of the SNMPv2 query is failing

The IP address and community string have been blocked out intentionally.

Find more posts tagged with

snmpv2

snmpwalk

161

Polling

31005

Accepted answers

nick_scott

I contacted support, level one tech informed me that the MIB being used is a private MIB. I Kicked the ball back over to the server side!

All comments

rschroeder

If you're configuring a server to be discovered via snmp-v2, review these videos to see if you may be missing something basic:

No matter what you're working on, as long as you have your edge device configured to use the same string as your Orion product, snmp should work.

Configuring SNMPv2 and SNMPv3 for Solarwinds Products

snmp-v3 is preferred today, for its security, and you should strongly consider using it instead of v2.

d09h

Sounds like things are working as well as they are going to, and it seems SNMP communication is succesful given the 1070+ OIDs that respond. I've seen this behavior before. Perhaps something to do with SysObjectID? It can give the false impression that SNMP is not working. Is the Vendor / Machine Type detected?

In my case, I was able to successfully poll via Universal Device Poller even though testing SNMP via web always failed. Certain models from certain vendors were just weird (luckily not very often).

May want/ need to do this if Vendor / Machine Type not detected :

Configure Vendor/Machine type when Orion is unable to detect it - SolarWinds Worldwide, LLC. Help and Support

You may find that an SNMP walk from outside of SolarWinds app behaves similarly. I did, anyway.

nick_scott

I was hoping someone had seen the error in the SNMPwalk before. I cant add the device without proper SNMP verification.

d09h

I have seen that error before. It is possible to add as ICMP or external node and then make necessary changes in the database. Regardless, you can prove what is or isn't happening with packet capture or logs. I would be remiss if I didn't urge being careful if editing the database, but it is pretty straightforward.

Seems the error has been seen from another direction: Hardware Monitoring not working on HP ProLiant / HP ProLiant gets Hardware Polling failed: Error 31040 or 31005

nick_scott

I contacted support, level one tech informed me that the MIB being used is a private MIB. I Kicked the ball back over to the server side!

nick_scott

SLW support advised that this particular device is providing a private MIB as everything is starting with 1.3.6.1.4 and not 1.3.6.1.2. Here is a response from the vendor pointed at SLW.

"It sounds like you are having an issue implementing the VPLEX
MIB file with your currently available SNMP server. This MIB file is the only file
available from a VPLEX standpoint. The only recommendation I can provide at
this point is you work with your SNMP vendor to determine why this MIB file is
not importing properly. As long as the server is running SNMPv2c, this file
should import without any issues."

anil.singh

Either you can check, if there is a problem with the host or snmpwalk.exe in solarwinds.

Try snmp walk from any linux system. (SNMP package must be installed on that system), wc to count the number of OID's.

~]# snmpwalk -v2c -c "community string" "target machine IP address" system > snmp_result.txt

~]# wc -l snmp_result.txt