References > Troubleshooting > Troubleshooting Hardware Health > Troubleshooting an SNMP Node

SNMP monitored node not returning hardware information

Error: SNMP monitored nodes may not return hardware health data if the software was installed improperly. You must install SNMP software prior to installing or deploying an Agent to the node. If you install the Agent first, you will encounter installation and configuration issues with MIBs.

Resolution: Uninstall the Hardware Monitoring Agent software, install SNMP, then reinstall the Agent on the node. Review the Hardware Health resources for updated health data for the node. If you continue to encounter issues, you may need to review the following troubleshooting sections to verify the node and check OIDs.

Verify the node was successfully added using SNMP

Use the following steps to verify the monitored node has an SNMP polling method.

  1. Verify the polling method on the Node Details page.
  2. Verify the Hardware Monitoring Agent software is installed on the remote server and running.
  3. Determine if SNMP responds for the proper OID. Below are the correct OIDS for each vendor:
    • For HP:1.3.6.1.4.1.232.2.2.2.1.0
    • For Dell:1.3.6.1.4.1.674.10892.1.300.10.1.8.1
    • For IBM:1.3.6.1.4.1.2.6.159.1.1.60.3.1

To determine if the remote server responds to the correct OID, you can use the MIB browser from SolarWinds Engineer’s Toolset, which can be downloaded from http://www.solarwinds.com/downloads/. Additionally, you can use other applications capable of making SNMP requests.

Check OIDs using SNMPWalk.exe

If you do not have a tool for checking OIDs on the remote server, you can create an SNMP walk by using the SNMPWalk.exe installed with SAM, normally located at C:\Program Files (x86)\SolarWinds\Orion\SnmpWalk.exe. SNMPWalk.exe is used in this demonstration.

  1. Start SNMPWalk.exe  and type in the IP address of the remote server and the community string for SNMP.
  2. Click Scan then save the SNMP walk in a text file.
  3. Open the text file and manually search for the OIDs.

If the Remote Server does not respond on this OID, the Hardware Monitoring Agent software may not be properly configured. Check to see if the Hardware Monitoring Agent software has imported the correct MIBs as outlined in the following table.

HP

Dell

IBM

CPQSTDEQ-MIB

MIB-Dell-10892

IBM-SYSTEM-HEALTH-MIB

CPQSINFO-MIB

StorageManagement-MIB

IBM-SYSTEM-ASSETID-MIB

CPQIDA-MIB

 

IBM-SYSTEM-LMSENSOR-MIB

CPQHLTH-MIB

 

IBM-SYSTEM-MEMORY-MIB

CPQSTSYS-MIB

 

IBM-SYSTEM-POWER-MIB

CPQIDE-MIB

 

IBM-SYSTEM-PROCESSOR-MIB

 

 

IBM-SYSTEM-RAID-MIB

 

 

ADAPTEC-UNIVERSAL-STORAGE-MIB