The SNMP Trap agent is used to receive SNMP notifications (traps and informs) and convert them to UDRs.

SNMP Trap Tab

Select the relevant SNMP Collection profile.

Resolving Trap OIDs

The SNMP Trap agent automatically resolves incoming trap OIDs based on MIB definitions from MIB files which are loaded into a profile. This is done for both parts of the notification identifier and the list of variable bindings of the trap.

Changing the Port 162 Privileges

The standard SNMP trap port 162 is not accessible for in, for instance, a Linux/Unix environment. Make sure to solve this issue. You can either do:

Setup port forwarding from 162 to a port that can access using iptables.
Change the privileges for port 162, so non-root can access it.

Example - How to setup UDP port forwarding to forward all UDP datagrams from port 162 to port 5678

$ sudo iptables -t nat -A PREROUTING -i enp0s3 -p udp --dport 162 -j REDIRECT --to-port 5678

Replace enp0s3 with the proper network interface name. Use ifconfig to find out the name of your Ethernet interface (usually - eth0).

Input/Output Data

Input Data

SnmpTrapUDR

Output Data

SnmpTrapUDR

Meta Information Model

For information about the MIM and a list of the general MIM parameters, see Administration and Management(3.0).

The agent does not publish nor access any MIM parameters.

SNMP Trap Agent Event

Agent Message Events

The agent does not produce any message events. However, you can configure the Analysis agent with APL code to produce message events. See the APL Reference Guide for further information about available functions.

Debug Events

The agent does not itself produce any debug events. However, you can configure the Analysis agent with APL code to produce debug events. See the APL Reference Guide for further information about available functions.