Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > ipMonitor > ipMonitor - Knowledgebase Articles > Troubleshoot SNMP trap monitors in ipMonitor

Troubleshoot SNMP trap monitors in ipMonitor

Updated November 6, 2018

Overview

This article describes how to troubleshoot SNMP trap monitors.

Environment

All ipMonitor versions

Steps

Setting up ipMonitor to listen for SNMP traps is a two-step process:

  1. Set up trap listening.
  2. Set up trap filters.

Set up trap listening

SNMP trap listening is disabled by default to ensure that ipMonitor properly co-exists with your existing network management software.

To enable the SNMP trap listener:

  1. Launch the ipMonitor configuration program from the ipMonitor program group.
  2. Select Communications > Web Server Ports.
  3. In the SNMP Trap Listener section, specify a listening IP Address and Port (UDP) for all SNMP trap QA monitors and ensure the Enabled checkbox is checked. Any agent you configure to send traps to ipMonitor must use this same IP address and port combination.

Resolve SNMP Trap Listener conflicts

When you enable the Windows SNMP Trap Service on the ipMonitor host computer, it can conflict with ipMonitor's SNMP Trap Listener (depending on configuration parameters). Normally, the Windows SNMP Trap Service is configured to listen on IP Address 0.0.0.0 Port 162 (it is configured to listen for all inbound Traps on Port 162). ipMonitor also uses the same default settings for its SNMP Trap Listener. Because only one SNMP trap listener can be bound to port 162 at a time, a conflict occurs.

To resolve this issue, disable the Windows SNMP Trap Service from the Windows Control Panel/Services interface. Normally, this won't present any problems unless you installed ipMonitor on that same host machine as another SNMP solution that requires use of the Windows SNMP Trap Service.

Alternatively, modify the ipMonitor's SNMP port to an unused port. You will also need to modify the outbound port for any SNMP agents that send traps to ipMonitor.

Set up trap filters

You can set up trap filters by configuring an SNMP trap monitor with filters for specific values.  Send one SNMP trap from the problem device and then open the snmptrap.log file located at \ipmonitor\logs. This log includes the following SNMP traps: 

  • Accepted: Its values matched the criteria of one or more SNMP Trap Monitors
  • Refused: Its values did not match the criteria of any of the SNMP Trap Monitors

Locate the trap that was sent by the device and use its values to configure the monitor. 

After you create and configure the monitor, send one more trap from the device. Ensure that the trap is marked as Accepted in the snmptrap.log file.

Last modified

Tags

Classifications

Public