SNMP Troubleshooting Guide
1) Please check the snmp agent is running in problematic remote server or not.
2) if it is running then execute the snmpwalk.bat / snmpwalk.sh
This snmpwalk is used to check if the connectivity and the Discovery of the SNMP
Server is possible from the Applications Manager installed
server. This standalone program is a excerpt of the same process we use
to add the SNMP Server monitor. The usage to run this file is as below
Via command prompt go to AppManager/bin/troubleshooting directory and execute the SNMPwalk file with the usage below.
Usage : snmpwalk.bat [version] [community] [port] [hostname / Ip] [Manufacturer]
[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
[timeout] Timeout value. By default 5 seconds
[Manufacturer] Hardware manufacturer DELL/HP
This will initiate the process to discover the SNMP Server and on success will also fetch the data for the default attributes monitored and shown as the output. From this you will be able to find If discovery is possible, If data is returned for all attributes or not. In case there is any issue for an attribute data it'll be shown as null. This infers that the data is not available in that server and has to be checked on the SNMP running server.
For more info or assistance do send us the output of the above command for analysis along with Support Information File.
Via command prompt go to AppManager/bin/troubleshooting directory and execute the SNMPwalk file with the usage below.
Usage : snmpwalk.bat [version] [community] [port] [hostname / Ip] [Manufacturer]
[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
[timeout] Timeout value. By default 5 seconds
[Manufacturer] Hardware manufacturer DELL/HP
This will initiate the process to discover the SNMP Server and on success will also fetch the data for the default attributes monitored and shown as the output. From this you will be able to find If discovery is possible, If data is returned for all attributes or not. In case there is any issue for an attribute data it'll be shown as null. This infers that the data is not available in that server and has to be checked on the SNMP running server.
For more info or assistance do send us the output of the above command for analysis along with Support Information File.
New to ADSelfService Plus?
Related Articles
Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below 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 the help ...APM Insight - Agents Troubleshooting and Compatibility Guide
To optimize performance and troubleshooting, Please provide the following details related to the respective agents and cross-verify compatibility from the provided help pages. Java Agent Application Server & Version : __________________ [Eg. Apache ...SNMP is installed in the server and SNMP request is getting timed out
Make sure whether SNMP is installed and running in the server. Also refer here in case you are not able to view monitored data. If SNMP is running and the SNMP request is still getting timed out, follow the below troubleshooting steps : Check ...PHP Monitor Troubleshooting
PHP Monitor Errors and Troubleshooting Guide Check if the phpstats.php file in the webserver's document root. Ensure there is no modifications done in phpstats.php file Check if the correct PHP path is given. Retry with the "SSL is enabled" option ...Troubleshooting WinRM errors
This KB serves as a guide for troubleshooting errors when using the WinRM mode of data collection. First, ensure that all the following conditions are met: Refer to the below link and check if all the WinRM prerequisites have been completed properly ...