Template:FAQ:Applications 17

Handling received traps is done using the tool 'snmptrapd'. This can log these traps via the syslog mechanism:

       snmptrapd -Ls 7         (log to 'LOCAL7')
       

printed to standard output

       snmptrapd -f -Lo

or pass them to an external command. This last approach uses a 'traphandle' directive in the configuration file 'snmptrapd.conf'. A typical file might look something like:

       traphandle .1.3.6.1.6.3.1.5.1       page_me up
       traphandle .1.3.6.1.4.1.2021.251.1  page_me up
       traphandle .1.3.6.1.4.1.2021.251.2  page_me down
       traphandle default                  log_it

where 'page_me' and 'log_it' are the command to be run. (You probably need to specify full pathnames, to ensure that the commands will be found. They're just short here for readability).

Note that the first entry uses the OID corresponding to the SNMPv1 'coldStart' trap. See the co-existence RFC (RFC 2576) for details of mapping SNMPv1 traps to SNMPv2 OIDs.

Starting with net-snmp 5.3, snmptrapd will no longer automatically accept all incoming traps. It must be configured with authorized SNMPv1/v2c community strings and/or SNMPv3 users. Non-authorized traps/informs will be dropped. Please refer to the snmptrapd.conf(5) manual page for details.

There's a tutorial with more details on the web site at http://www.net-snmp.org/tutorial-5/commands/snmptrap.html