Troubleshooting steps for Server Hardware Health Monitoring
1. SNMP Mode of monitoring:
Monitoring Dell hardware status:
- Dell OpenManage Server Administrator and make sure SNMP agent is enabled
- Installation steps: http://www.dell.com/downloads/global/power/ps2q06-20050112-Lou-OE.pdf
Monitoring HP hardware status:
- HP System Insight Manager (SIM v6.2 or higher is recommended) and make sure SNMP agent is enabled
- Installation steps: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04771934
Determine if SNMP responds to the OID properly. Below are the correct OID's 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
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 http://www.manageengine.com/products/mibbrowser-free-tool/download.html. 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
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 appmanager-support@manageengine.com 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
Example:
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 appmanager-support@manageengine.com along with the support information file from Applications Manager.
3. Enter administrator credentials.
New to ADSelfService Plus?
Related Articles
Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the below steps for troubleshooting. Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer this help ...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 ...Troubleshooting Bad Request and Internal Server error
When a server responds with a Bad Request (400) or Internal Server Error (500), It typically indicates issues with how the request is being made or processed. The reasons for these errors can vary, but the most common causes are Incorrectly formatted ...Monitoring HAProxy - Configuring the HAProxy Stats page
To effectively monitor an HAProxy instance, you can enable and access the HAProxy stats page, which provides real-time metrics about HAProxy's performance. Steps to Enable HAProxy Stats: Open the HAProxy Configuration File: The HAProxy configuration ...gMSA troubleshooting steps
Troubleshooting Guide for GMSA account issues in Applications Manager This guide provides step-by-step instructions to resolve authentication issues when using a Group Managed Service Account (gMSA) with ManageEngine Applications Manager for SQL ...