SAM monitors hardware by polling nodes and utilizing the Hardware Monitoring Agent software provided by the hardware manufacturer. SAM can monitor hardware from VMware hosts, HP ProLiant, Dell PowerEdge, and the IBM X-Series using this software. Hardware monitoring is achieved by polling via SNMP or WMI, depending upon the node. For SNMP and WMI nodes, hardware monitoring must be enabled manually through SAM's web console.
If you run a scheduled Network Sonar Discovery of your existing servers, SAM will automatically collect any servers that support hardware health information the next time the discovery runs.
Note: Only SAM administrators can enable hardware health monitoring.
Hardware Prerequisite Checklist
If the following conditions cannot be met, the Hardware Health resources will not be displayed. To monitor hardware in SAM, the following must be true:
- The monitored node must be HP Proliant, Dell PoweEdge, IBM X-Series, HP C7000, HP C3000, or Dell M1000e.
- The node must be monitored using one of the following protocols:
- ICMP nodes are allowed for VMWare when the Poll for VMware option is selected.
- The Hardware Monitoring Agent software, (provided by the vendor), is installed on the remote server. This applies for both SNMP and WMI.
- For VMware, the minimum requirements are as follows: ESX server version 3.5, 4.0, 4.1, ESXi version 5.0, vCenter version 4.0, 4.1, 5.0.
The following systems have been verified to work properly with SAM's hardware monitoring features.
Note: Other systems may work as well.
- Dell PowerEdge M610, R210, R610, R710, R900, 1950, 2850, 2950, 2970, 6850
- HP ProLiant DL320 G4, DL360 G3, DL360 G4, DL380 G4, DL380 G6, ML570 G3
- IBM IBM System x3550, System x3550 M2, System x3550 M3, System x3650, System x3650 M2, System x3650 M3, x3850, eServer 306m
- HP C7000, HP C3000
- Dell M1000e.
Note: IBM's ServeRAID Manager software must be installed on IBM X-Series servers for storage hardware health information to be displayed in SolarWinds SAM. HP’s WBEM providers are required for HP servers polled via WMI.
Hardware Troubleshooting Flowchart
Troubleshooting an SNMP Node
The most common issue customers face is that hardware information is not available via SNMP because the Hardware Monitoring Agent software was installed before SNMP was installed. This means MIBs were never installed and/or configured correctly. The easiest solution is to uninstall and then re-install the Hardware Monitoring Agent software after installing SNMP on the server. If this is not the case, follow the troubleshooting steps as outlined below:
- Verify the node was successfully added using SNMP.
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: 22.214.171.124.126.96.36.199.188.8.131.52
For Dell: 184.108.40.206.4.1.674.10892.1.300.10.1.8.1
For IBM: 220.127.116.11.18.104.22.168.22.214.171.124.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.
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 will be used in this demonstration.
- Start SNMPWalk.exe and type in the IP address of the remote server and the community string for SNMP.
- Click Scan.
- After completing the scan, save the SNMP walk in a text file.
- 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.
Troubleshooting a WMI Node
The following conditions must be met before you can proceed troubleshooting WMI nodes:
- The node has successfully been added via WMI.
- WMI is working properly on the remote server.
- The Hardware Monitoring Agent software is installed on the remote server and running.
Using Wbemtest.exe to troubleshoot WMI:
- Open wbemtest.exe, usually located at C:\Windows\System32\wbem\wbemtest.exe.
- Connect from the problematic node (either the SAM server or the additional poller server) to the remote server using wbemtest.exe.
- Click Connect.
- In the Namespace field enter:
For IBM and HP enter: \\RemoteServerIpAddress\root
For Dell enter: \\RemoteServerIpAddress\root\cimv2
5. Enter Administrator credentials
6. Click Connect.
7. Once connected, click Query… from the main screen. The Query dialog appears.
8. Enter: select * from __Namespace
Replace Namespace with the following:
- For HP nodes, replace Namespace with HPQ
- For Dell nodes replace Namespace with Dell
- For IBM nodes replace Namespace with IBMSD
9. If the proper Namespace is found, connect to this Namespace.
- \\RemoteServerIpAddress\root\IBMSD for IBM.
- \\RemoteServerIpAddress\root\HPQ for HP.
- \\RemoteServerIpAddress\root\cimv2\Dell for Dell.
10. Run a Query for specific information.
Select Manufacturer, Model, Serial Number from CIM Chassis
- If the test was not successful, re-install the platform or Hardware Monitoring on the remote server with the latest release.
Troubleshooting a VMWare Node
VMWare nodes can be polled for Hardware information either through the vCenter or directly by using the CIM protocol. Polling through the vCenter uses VMWare's native API interface. Polling the ESX server directly uses the CIM protocol to get Hardware information.
To determine if a node is polled through the vCenter or directly:
- From the web console, navigate to Settings > Virtualization Settings
- Listed will be table of all the currently polled VMWare nodes. This table contains the Polling Through column. Note: This column may be hidden. If the column is hidden, unhide it by clicking the dropdown menu of an adjacent column and check the Polling Through option:
- Use the illustration below to determine how your VMWare is being polled.