How to make sure SNMP trap works as expected?

How can I test if SNMP trap works as expected?

Q: At the moment I have a APC 7500 Smart UPS in our LAN. An SNMP test trap sent from this agent is not recorded by IPNetwork Monitor (both the agent and IPNetwork Monitor are in the same IP range). I can add the host and even set up a monitor. But after “netstat -a -b” I do not see the port 162 being opened. Why?

A: By default IPNetwork Monitor uses port 162 to listen to incoming traps, but its installer can choose another one if the default port 162 is not accessible during installation. Please find the actual port number in
%ProgramData%\IPNetwork Monitor\nms.ini
file, the UDPTrapReceiverPort option. You can change it to the default 162 port.

In order to change the port:

  • Stop the monitoring service (Tools -> Stop monitoring service) and close Client;
  • After that change the “UDPTrapReceiverPort” setting in
    %ProgramData%\IPNetwork Monitor\nms.ini
    file;
  • Start Client and start the monitoring service (Tools -> Start monitoring service).
Related topics

How can I monitor SNMP-enabled devices?

Frequently Asked Questions

Check out our Knowledge Base where we answer questions regarding various topics.

Why might IPNetwork Monitor not be listening on UDP port 162?

If port 162 was unavailable during installation, the installer may have selected another SNMP trap receiver port.

Where is the actual SNMP trap receiver port stored?

Check the UDPTrapReceiverPort option in %ProgramData%\IPNetwork Monitor\nms.ini.

How can the SNMP trap receiver port be changed?

Stop the monitoring service and close the client, edit UDPTrapReceiverPort in nms.ini, then start the client and monitoring service again.