Troubleshoot hardware health monitoring on SNMP nodes

This section focuses on Dell, HP, HPE ProLiant, and IBM devices. See the SolarWinds Platform Administrator Guide for tips on monitoring Cisco UCS or Nutanix clusters.

To monitor hardware health for devices in SAM, you can either enable hardware health monitoring for individual nodes, or use the Discovery process to:

1. Automatically scan for nodes that meet hardware health monitoring requirements,
2. Deploy SolarWinds Platform agents that act as hardware health sensors, and
3. Enable hardware health monitoring across multiple nodes automatically.

Hardware health statistics are typically polled through SNMP from a MIB tree on devices that are represented as nodes in the SolarWinds Platform Web Console. If an SNMP-monitored node does not return data as expected, verify that it is properly configured for SNMP:

• Open default port 161 on the node.
• For SNMPv1 or SNMPv2c nodes, confirm that the device community string was added to the SolarWinds Platform. The default value is Public.
• For SNMPv3 nodes, review these Success Center articles:
  • SNMPv3 configuration and troubleshooting in SolarWinds Platform
  • SNMPv3 prerequisites and checks
• For Cisco devices, verify that the correct MIB is selected.

If SolarWinds Platform agents were deployed to a node before it was configured to use SNMP, you may encounter installation and configuration issues with MIBs. Use the Manage Agents page to remove related agents, configure the node for SNMP, and then redeploy agents to the node, or run Discovery again.

If a node was originally configured for SNMP and then you want to use the SolarWinds Platform agent on the node for Asset Inventory or Hardware Health monitoring, see Configure SNMP for SolarWinds Platform agents on Linux/Unix and AIX systems in SAM.

Modify SNMP agents to monitoring on HPE and Dell Linux systems

To support hardware health monitoring on HPE and Dell target systems running Linux, modify the SNMP agent required for NETSNMP.

HPE systems

The HPE SNMP Agents (hp-snmp-agents) is a collection of SNMP protocol-based agents and tools which enables monitoring of fans, power supplies, temperature sensors, and other management events via SNMP. It also provides Foundation and Server agents, Storage Subsystem agents, Network Subsystem agents, the SNMP Dynamically Loaded Module, and the web support applications.

For reference, see HPE SNMP Agents for Red Hat Enterprise Linux 7 Server.

HPE GEN10 Server and host-based SNMP are no longer supported.

Dell systems

Install Dell OpenManage Server Administrator (DOMSA) on the Linux system and enable the following List Resources options on the Node Details view:

• Hardware Health
• Asset Inventory

For reference, see:

• How to configure OMSA/SNMP on Linux (Dell systems)
• Dell Service Tag on Servers running Linux (THWACK)

Verify a node was added using SNMP

To verify that a monitored node uses SNMP for polling:

1. Navigate to the Node Details view and examine the Polling Method.

   

2. Navigate to the Manage Agents page to verify that an SolarWinds Platform agent was deployed.
3. Confirm that the node responds with a proper OID by using either:
   • The MIB Browser in SolarWinds Engineer’s Toolset (ETS), or
   • Another application that can make SNMP requests.

OIDS for vendors include:

• HP: 1.3.6.1.4.1.232.2.2.2.1.0
• Dell: 1.3.6.1.4.1.674.10892.1.300.10.1.8.1
• IBM: 1.3.6.1.4.1.2.6.159.1.1.60.3.1

Check OIDs with the SolarWinds SNMP Walk tool

To troubleshoot connection issues, you can use the vendor-specific OIDs listed above in the SolarWinds SNMP Walk tool, is available in the following default directory on the SolarWinds Platform server: C:\Program Files (x86)\SolarWinds\Orion\SnmpWalk.exe.

For an overview, watch Collect MIB walk data using the SolarWinds SNMP Walk Tool. You can also use this tool to resolve memory, CPU, or volume issues for nodes.

If the tool does not respond for a vendor-specific OID on a node, check the SolarWinds Platform agent configuration.

When the scan finishes, save the resulting text file and open it. It should include the MIBs outlined here:

Dell	HP	IBM
MIB-Dell-10892	CPQSTDEQ-MIB	IBM-SYSTEM-HEALTH-MIB
StorageManagement-MIB	CPQSINFO-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