Receive SNMP traps/informs

Meridian lets you receive and process SNMP traps and informs out of the box. The Meridian services run as an unprivileged user and cannot bind on port numbers below 1024 without escalated privileges. For this reason, the default port for the SNMP trap/inform listener is set to 10162/udp instead of the IANA registered port number 162/udp. The following example shows how to configure the local firewall daemon to forward port 162/udp to 10162/udp.

If you need the SNMP trap listener on port 162/udp directly, see Binding to privileged ports.

  • CentOS/RHEL 7/8/9

Enable Masquerade to allow port forwarding
sudo firewall-cmd --permanent --add-masquerade
Forward SNMP trap UDP port 162 to 10162
sudo firewall-cmd --permanent --add-port=162/udp
sudo firewall-cmd --permanent --add-port=10162/udp
sudo firewall-cmd --permanent --add-forward-port=port=162:proto=udp:toport=10162
sudo systemctl reload firewalld

You can verify your firewall and port forwarding configuration by sending an SNMP trap from a remote system to your Meridian instance:

snmptrap -v 2c -c public opennms-core-host '' 1.3.6.1.4.1.2021.991.17 .1.3.6.1.2.1.1.6.0 s "Milky Way" (1)(2)
1 By default, Meridian uses the public community string. If you changed the community string in Meridian, use the updated name here.
2 Replace opennms-core-host with your Meridian instance’s IP or FQDN.
On RHEL and CentOS, the snmptrap command line tool is part of the net-snmp-utils. If you run on Debian or Ubuntu, the tool is part of the snmp-utils package.

To verify your configuration, look for an SNMP trap event in the Meridian web UI:

  1. Sign in to the web UI.

  2. Click Status  Events.

  3. Under Event Queries, select All Events.

  4. Search the list for a uei.opennms.org/generic/traps/EnterpriseDefault event from your test host.