Troubleshooting steps for Server Hardware Health Monitoring

Troubleshooting steps for Server Hardware Health Monitoring

1. SNMP Mode of monitoring:

Monitoring Dell hardware status:
Monitoring HP hardware status:
Determine if SNMP responds to the OID properly. Below are the correct OID's for each vendor:

For HP:
For Dell:

Using snmpwalk to troubleshoot:
To determine if the remote server responds to the correct OID, you can use the MIB browser free tool from ManageEngine, which can be downloaded from Additionally, you can use other third-party tools capable of making SNMP requests."

Verify Applications Manager is able to collect hardware status by the below steps. Via command prompt go to AppManagerHome/bin/troubleshooting directory and execute the SNMPwalk file with the usage below.

Usage : snmpwalk.bat/sh [version] [community] [port] [hostname / Ip] [hardware]

[version]            =      version of SNMP agent v1 / v2. By default v1
[community]      =      community string. By default public
[port]                  =      remote SNMP agent port number. By default 161
[hostname/Ip]    =      hostname or Ip address of machine where SNMP agent is running
[hardware ]        =      hardware manufacturer. Supported options are DELL or HP (optional)

Example: snmpwalk.bat   v1 public 161 server1 DELL >> snmpwalk.txt

This will verify whether the Applications Manager is able to collect the hardware metrics of  DELL servers. Send the snmpwalk.txt file to along with the support information file from Applications Manager.

2. WMI mode of monitoring:

The following conditions must be met before you can proceed to troubleshoot WMI nodes:
  • The node has successfully been added via WMI.
  • WMI is working properly on the remote server.
  • HP System Insight Manager (SIM v6.2 or higher is recommended) is installed on the remote server and running.
  • Dell OpenManage Server Administrator is installed on the remote server and running.

Using wbemtest.exe to troubleshoot WMI:

1. Open wbemtest.exe, usually located at C:\Windows\System32\wbem\wbemtest.exe
2. From the Applications Manager server, open wbemtest.exe and click Connect.
3. In the Namespace field enter:
      For HP: \\RemoteServerIpAddress\root\HPQ
      For Dell: \\RemoteServerIpAddress\root\cimv2\Dell
4. Click Connect.

6. Once connected, click Query. The Query dialog appears.
7. Run a Query for specific information.

Select Manufacturer, Model, SerialNumber from CIM_Chassis

If the test was not successful, re-install Hardware Monitoring Agent software on the remote server or contact the Hardware Vendor.
If the test was successful and still not able to get the Hardware details in the Applications Manager web console, then follow the below steps.

1. Go to AppManagerHome\working\conf\application\scripts\ folder in command prompt and execute the below script:
If hardware manufacturer is HP:
cscript wmiDataCollector.vbs <RemoteHost> <UserName> <Password> ..\HPHardwareDataCollector.xml > hwinfo.txt
If hardware manufacturer is DELL:
cscript wmiDataCollector.vbs <RemoteHost> <UserName> <Password> ..\DELLHardwareDataCollector.xml > hwinfo.txt

cscript wmiDataCollector.vbs apmtest test test123 ..\DELLHardwareDataCollector.xml > hwinfo.txt
cscript wmiDataCollector.vbs localhost ..\DELLHardwareDataCollector.xml > hwinfo.txt
2. Send the hwinfo.txt file to along with the support information file from Applications Manager.
3. Enter administrator credentials.

          • Related Articles

          • Ceph storage monitoring troubleshooting steps

            Ceph Storage Monitoring: By default Ceph monitor added via ssh. so ssh should be work if the customer want to monitor the Ceph storage for the server. Supported Ceph Storage Version : >= v0.66 Command used to collected all performance data :  ceph -s ...
          • IIS Server monitor - Troubleshooting steps

            Troubleshooting guide for adding an IIS Server monitor Troubleshooting 'No data available' error for IIS Server performance metrics (IIS Websites and Application Pools statistics)
          • Troubleshooting Bad Request and Internal Server error

            Bad Request & Internal Server error When the server of URL cannot understand the request it has received it responds with a Bad request or a malformed syntax error message. If there is an error in processing the request received by the server, it ...
          • Troubleshooting SSL Handshake Error

            SSL Handshake Error SSL Handshake error occurs when a secure connection cannot be established to the URL added for monitoring. Common reasons for it are wrong SSL protocol version, incompatible ciphers, and invalid/missing client-side certificate.  ...
          • Troubleshooting URL Monitor

            Here are few of the common errors you may come across in URL monitor, we have mentioned the steps you can follow to troubleshoot them.   General troubleshooting for URL monitor Ensure that the URL is accessible from the server in which Applications ...