Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > ipMonitor > Troubleshoot SNMP communication from ipMonitor

Troubleshoot SNMP communication from ipMonitor

Table of contents
Created by Chris Foley, last modified by Karen Valdellon on Apr 27, 2017

Views: 85 Votes: 0 Revisions: 8

Overview

This article provides steps to verify if SNMP communication is successfully established between ipMonitor and the target system when you encounter the following:

  • ipMonitor discovery is finding very little to no resources.
  • You lost authentication or communication with half of the monitors.
  • You are getting false alerts.

Environment

  • All ipMonitor versions
  • All Windows versions

Steps

You can test SNMP connectivity from ipMonitor by requesting SysUptime from the remote system as this is supported by all SNMP-enabled systems. 

  1. On the ipMonitor web interface, click Devices > All Managed Devices.
  2. Click any device.
  3. Click Add > Add New Monitor.
  4. In the left-hand pane, click SNMP.
  5. In the right-hand pane, click Custom SNMP (Wizard), and check if the address and the SNMP community name of the system you want to monitor are correct.
  6. Click Next.


If this fails to provide SysUptime from the system, look at the following information:

  • Verify if the SNMP service is installed and running on the target system.
  • Verify that the SNMP community name you specified within the monitor matches the SNMP community name accepted by the target SNMP agent. The SNMP community is case-sensitive.
  • The SNMP agent on the target system has a list of systems that it will accept SNMP packets from. Verify that the ipMonitor system is on this list.
    Note: See Install and configure SNMP services for more information.
  • If something is blocking communication on port 161 over UDP, verify the configurations of any firewall which may exist between the ipMonitor system and the target system, including any firewall applications installed on these systems.

 

 

Last modified
19:18, 26 Apr 2017

Tags

Classifications

Public