Submit a ticketCall us

AnnouncementsWeb Help Desk Integrations eCourse

Looking to reduce response times? Sign up for our eCourse to learn how integrating Web Help Desk with Dameware Remote Support, Network Configuration Manager, Network Performance Monitor, and Server & Application Monitor can improve communication efficiencies.

Register here.

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

Troubleshoot SNMP trap monitors

Table of contents
Created by Norsolihati Selamat, last modified by Rodim Suarez_ret on Aug 31, 2016

Views: 1,003 Votes: 0 Revisions: 4


This article describes how to troubleshoot SNMP trap monitors.


All IPMonitor versions


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


  1. Trap listening: SNMP Trap listening is disabled by default. This is done to ensure that ipMonitor properly co-exists with existing Network management software.
    To enable the SNMP Trap Listener:
    a. Launch the ipMonitor Con figuration Program from the ipMonitor program group.
    b. Select the Communications: Web Server Ports option.
    c.Within 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.
    Note regarding Windows SNMP Trap Service: If the Windows SNMP Trap Service is enabled on the ipMonitor host computer, it is very likely to conflict with ipMonitor's SNMP Trap Listener (depending on configuration parameters).
    Normally, the Windows SNMP Trap Service is configured to listen on IP Address Port 162 (in other words, 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 solve this problem:
    a. Disable the Windows SNMP Trap Service from the Windows Control Panel/Services interface. Normally, this won't present any problems unless you have installed ipMonitor on that same host machine as another SNMP solution that requires use of the Windows SNMP Trap Service.
    b. Alternatively, modify ipMonitor's SNMP Port to an unused Port. Keep in mind that you will also need to modify the outbound Port for any SNMP Agents that will be sending Traps to ipMonitor.
  2. Trap Filters: This is done by configuring an SNMP Trap Monitor with filters for specific values.  A good trick here is  to have the client send one SNMP Trap from the device in question and then open the file \ipmonitor\logs\snmptrap.log.  Within this log will be SNMP traps that are:
  • 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

    Find the Trap that was sent by the Device and use its values to configure the Monitor.  Once the Monitor has been configured and created,  send one more Trap from the Device and ensure the Trap has been marked as ‘Accepted’ within the snmptrap.log file.
Last modified