article Troubleshooting Network Device Issues with snmpwalk

This article explains how to use the snmpwalk command line tool (Linux) or the iReasoning MIB Browser (Windows) to explore which SNMP OIDs are provided from a specific network device.  This output is helpful when troubleshooting why a network device is failing to add into up.time.

If there is an issue adding a Network Device element to up.time, it is possible to review the OID's available on the network device by using the snmpwalk command line tool available on most Linux installs or by using the Windows GUI tool, iReasoning MIB Browser.

It is possible to identify if there are any OID's missing that up.time requires for monitoring the Network Device.  A list of the OID's used by up.time is available in the Configuration and Performance Metrics for Network Devices article.

Snmpwalk and iReasoning MIB Browser can be installed on any server that has network access to the network device that will be analyzed but it is helpful to install on the up.time Monitoring Station server to also test the SNMP connectivity between the Monitoring Station and the network device.

Net-SNMP's snmpwalk
  • If snmpwalk is not already installed, use the Operating System's package management tool (e.g. yast or yum) to install it or download it from http://www.net-snmp.org/download.html.
  • Run the following command to list all of the OID's available from the network device where <community string> is the proper SNMP community string set on the network device and <hostname> is the hostname or IP address of the device:
    • snmpwalk -v 2c -c <community string> <hostname> .1.3
  • Review the output to make sure all of the OID's that up.time requires are present.

 

iReasoning MIB Browser
  • Download the application at http://www.ireasoning.com/downloadmibbrowserlicense.shtml and install on the Windows-based up.time Monitoring Station server.
  • Open the MIB Browser application and in the tool bar, enter "10.6.10.5" in the Address field.
  • Click the Advanced... button to enter the community string.
  • From the Operations drop down, select Walk, then click Go.
  • Review the output to make sure all of the OID's that up.time requires are present.

Further Documentation
 

Related Articles


Configuration and Performance Metrics for Network Devices

RatingViews
article

By: uptime Support | Date Created: 9-10-2012 | Last Modified: 3-6-2014 | Index: 586

  4676

Troubleshooting WMI with WMIDIAG

RatingViews
article

The WMIDIAG tool runs a diagnostic test against a system's WMI configuration and working status, reports any errors, and explains the configuration settings.After running the tool, review the...

By: uptime Support | Date Created: 2-11-2012 | Last Modified: 7-25-2013 | Index: 576

  4524

Troubleshooting time discrepancies

RatingViews
article

This solution may be useful if you observe time discrepancies such as the Duration status column for a service showing +364 days when you are sure that figure is not accurate. This discrepancy may...

By: uptime Support | Date Created: 7-9-2011 | Last Modified: 8-25-2011 | Index: 540

  2372

How do I add a server or device to up.time?

RatingViews
article

To add systems or network devices, do the following: NOTE: If you are adding a system for full up.time monitoring the up.time agent must be installed on the target server before it is added to...

By: uptime Support | Date Created: 12-31-1969 | Last Modified: 8-26-2011 | Index: 332

  4970

Active Directory / LDAP Authentication Troubleshooting

RatingViews
article

This solution may apply to AD or LDAP authentication failures when using the fully qualified domain name (FQDN) to configure up.time authentication methods. The FQDN may be required but this...

By: uptime Support | Date Created: 9-28-2011 | Last Modified: 9-29-2011 | Index: 566

  3891

User Comments



No comments have been posted.

Copyright © 2021 IDERA, Inc.   Legal   Privacy Statement