Collecting an SNMP Walk/Dump
KB1238 - Jul 26, 2018
Type: Troubleshooting
Description: How to collect an SNMP walk or dump when requested by the Sentry Support Team.
Additional Keywords: Troubleshooting, SNMP, Dump, Walk
Introduction
To be able to reproduce your issue, the Sentry Support Team may ask you to provide an SNMP dump of your system. The SNMP dump can be obtained by either using the diagnosis tool installed with Sentry KMs or the snmpwalk utility.
This article explains how to run both utilities.
Procedure
Using the Sentry KMs Diagnosis Tool
The diagnosis tool
To collect an SNMP walk/dump using this diagnosis tool, run the java -jar <jar file name>
command:
java -jar MS_HW_matsya-module-snmpclient.jar -v1|-v2 [-host:<hostname>] [-community:<community>] [-retryIntervals:<retryIntervals>] <action>
java -jar MS_HW_matsya-module-snmpclient.jar -v3 [-host:<hostname>] [-authType:<none|MD5|SHA> -username:<username> -password:<password>] [-privType:<none|DES|AES> -privpassword:<privpassword>] [-contextName:<contextName>] [-retryIntervals:<retryIntervals>] <action>````
Where <action> can be:
-get:<OID>
-getNext:<OID>
-walk:<OID>```
and <retryIntervals> is a comma-separated list of retry intervals in milliseconds. Default is: 500,1000,2000,5000,5000.
Example
To collect an SNMP walk/dump for Hardware Sentry for a device supporting SNMP v2, we ran the following command:
java -jar MS_HW_matsya-module-snmpclient.jar -v2 -host:fermat-cmdb -community:public -walk:1.3.6.1.4
and obtained the following result:
Result:
1.3.6.1.4.1.77.1.1.1.0 ASN_OCTET_STR 6
1.3.6.1.4.1.77.1.1.2.0 ASN_OCTET_STR 3
1.3.6.1.4.1.77.1.1.3.0 ASN_OCTET_STR 03 00 00 00
1.3.6.1.4.1.77.1.1.4.0 ASN_INTEGER 1529917342
1.3.6.1.4.1.77.1.1.5.0 COUNTER 17867
1.3.6.1.4.1.77.1.1.6.0 COUNTER 0
1.3.6.1.4.1.77.1.1.7.0 COUNTER 0
1.3.6.1.4.1.77.1.2.1.0 ASN_OCTET_STR
1.3.6.1.4.1.77.1.2.2.0 ASN_INTEGER 65
1.3.6.1.4.1.77.1.2.3.1.1.5.80.111.119.101.114 ASN_OCTET_STR Power
1.3.6.1.4.1.77.1.2.3.1.1.6.83.101.114.118.101.114 ASN_OCTET_STR Server
1.3.6.1.4.1.77.1.2.3.1.1.6.84.104.101.109.101.115 ASN_OCTET_STR Themes
1.3.6.1.4.1.77.1.2.3.1.1.8.78.101.116.108.111.103.111.110 ASN_OCTET_STR Netlogon
1.3.6.1.4.1.77.1.2.3.1.1.9.73.80.32.72.101.108.112.101.114 ASN_OCTET_STR IP Helper
1.3.6.1.4.1.77.1.2.3.1.1.10.68.78.83.32.67.108.105.101.110.116 ASN_OCTET_STR DNS Client
1.3.6.1.4.1.77.1.2.3.1.1.11.68.72.67.80.32.67.108.105.101.110.116 ASN_OCTET_STR DHCP Client
1.3.6.1.4.1.77.1.2.3.1.1.11.87.111.114.107.115.116.97.116.105.111.110 ASN_OCTET_STR Workstation
....
For a device supporting SNMP v3, we ran this command:
java -jar MS_HW_matsya-module-snmpclient.jar -v3 -host:cisco-san-07 -authType:MD5 -username:admin -password:xxxxxxx -walk:1.3.6.1.4
Using Net-SNMP's snmpwalk Utility
To collect an SNMP walk/dump using the snmpwalk utility, run the following command:
snmpwalk -t 600 -OnteU -v2c -c <community_string> <hostname> 1.3.6.1.2 > out.snmpwalk
snmpwalk -t 600 -OnteU -v2c -c <community_string> <hostname> 1.3.6.1.3 >> out.snmpwalk
snmpwalk -t 600 -OnteU -v2c -c <community_string> <hostname> 1.3.6.1.4 >> out.snmpwalk
where <community_string>
and <hostname>
should be replaced with the appropriate values.
For a device supporting SNMP v3, run the following command:
snmpwalk -v3 -u [SNMPv3 user] -A [password] -l [set-security-level] deviceIP <OID> .
Example:
snmpwalk -v3 -u admin -l authNoPriv -a MD5 -A "xxxxxx" cisco-san-07 1.3.6.1.4
Related Topics
- All SNMP-based Connectors Fail for one Hour before Reactivating
- Hardware Monitoring: Monitoring Servers Using SNMP
- Hardware Monitoring: SNMP-based connectors test fails with errno: 100 on Linux
- Monitoring HP Blade Chassis Virtual Connect with Hardware Sentry
- Monitoring HP Blade Systems with Hardware Sentry
- SNMP 'get_next' fails on Network adapter on HP ProLiant Servers
- SNMP-Based Connectors Stopped Working
- SSH-Based Connectors Stopped Working
- Troubleshooting Missed Events
- Troubleshooting WMI-Based Connectors
- Unable to Monitor Hardware Using SNMP-based Connectors with PATROL Agent v.9.5.00.02
- WBEM-Based Connectors Stopped Working