SNMP trap handling
snmptrapd is an SNMP application that receives and logs SNMP TRAP and INFORM messages.
The default is to listen on UDP port 162 on all IPv4 interfaces. Since 162 is a privileged port, snmptrapd must typically be run as root.
Install snmptrapd via your package manager.
For example (Debian based systems):
sudo apt install snmptrapd -y
/etc/snmp/snmptrapd.conf, add :
disableAuthorization yes authCommunity log,execute,net COMMUNITYSTRING traphandle default /opt/librenms/snmptrap.php
To enable snmptrapd to properly parse traps, we will need to add MIBs to service.
Make the folder
/etc/systemd/system/snmptrapd.service.d/ and edit
/etc/systemd/system/snmptrapd.service.d/mibs.conf and add
the following content.
You may want to tweak to add vendor directories for devices you care about. In the example below, standard and cisco directories are defined, and only IF-MIB is loaded.
[Service] Environment=MIBDIRS=+/opt/librenms/mibs:/opt/librenms/mibs/cisco Environment=MIBS=+IF-MIB
For non-systemd systems, you can edit TRAPDOPTS in the init script in /etc/init.d/snmptrapd.
TRAPDOPTS="-Lsd -M /opt/librenms/mibs -m IF-MIB -f -p $TRAPD_PID"
Along with any necessary configuration to receive the traps from your devices (community, etc.)
Tested on Ubuntu 18
Just setup your service like:
[Unit] Description=Simple Network Management Protocol (SNMP) Trap Daemon. After=network.target ConditionPathExists=/etc/snmp/snmptrapd.conf [Service] Environment="MIBSDIR=/opt/librenms/mibs" Type=simple ExecStart=/usr/sbin/snmptrapd -f -m IF-MIB -M /opt/librenms/mibs ExecReload=/bin/kill -HUP $MAINPID [Install] WantedBy=multi-user.target
In Ubuntu 18 is service located by default in
There is a list of snmptrapd options:
|-a||Ignore authenticationFailure traps. [OPTIONAL]|
|-f||Do not fork from the shell|
|-n||Use numeric addresses instead of attempting hostname lookups (no DNS) [OPTIONAL]|
|-m||MIBLIST: use MIBLIST (
|-M||DIRLIST: use DIRLIST as the list of locations to look for MIBs. Option is not recursive, so you need to specify each DIR individually, separated by
Good practice is to avoid
-m ALL because then it will try to load all the MIBs in DIRLIST, which
will typically fail (snmptrapd cannot load that many mibs). Better is to specify the
exact MIB files defining the traps you are interested in, for example for LinkDown and LinkUp
as well as BGP traps, use
-m IF-MIB:BGP4-MIB. Multiple files can be added, separated with
If you want to test or store original TRAPS in log then:
Create folder for storing traps for example in file
sudo mkdir /var/log/snmptrap
Add following config to your snmptrapd.service after
ExecStart=/usr/sbin/snmptrapd -f -m ALL -M /opt/librenms/mibs
After succesfuly configured service reload service files, enable, and start the snmptrapd service:
sudo systemctl daemon-reload sudo systemctl enable snmptrapd sudo systemctl restart snmptrapd
The easiest test is to generate a trap from your device. Usually, changing the configuration on a network device, or
plugging/unplugging a network cable (LinkUp, LinkDown) will generate a trap. You can confirm it using a with
You can also generate a trap using the
snmptrap command from the LibreNMS server itself (if and only if the LibreNMS server is monitored).
How to send SNMP v2 Trap
The command below takes the form of:
snmptrap -v <snmp_version> -c <community> <destination_host> <uptime> <OID_or_MIB> <object> <value_type> <value>
snmptrap -v 2c -c public localhost '' 184.108.40.206.4.1.8072.2.3.0.1 220.127.116.11.4.1.8072.2.3.2.1 i 123456
If you have configured logging of traps to
/var/log/snmptrap/traps.log then you will see in
traps.log new entry:
2020-03-09 16:22:59 localhost [UDP: [127.0.0.1]:58942->[127.0.0.1]:162]: SNMPv2-MIB::sysUpTime.0 = Timeticks: (149721964) 17 days, 7:53:39.64 SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::enterprises.8072.2.3.0.1 SNMPv2-SMI::enterprises.8072.2.3.2.1 = INTEGER: 123456
and in LibreNMS your localhost device eventlog like:
2020-03-09 16:22:59 SNMP trap received: SNMPv2-SMI::enterprises.8072.2.3.0.1
Why we need Uptime
When you send a trap, it must of course conform to a set of standards. Every trap needs an uptime value. Uptime is how long the system has been running since boot. Sometimes this is the operating system, other devices might use the SNMP engine uptime. Regardless, a value will be sent.
So what value should you type in the commands below? Oddly enough, simply supplying no value by using two single quotes '' will instruct the command to obtain the value from the operating system you are executing this on.
You can configure generic event logging for snmp traps. This will log an event of the type trap for received traps. These events can be utilized for alerting.
$config['snmptraps']['eventlog'] = 'unhandled';
Valid options are:
unhandledonly unhandled traps will be logged
alllog all traps
noneno traps will create a generic event log (handled traps may still log events)