Note - All command examples given in this section are executed on the SNMP management station, unless instructions indicate otherwise. This section provides examples of how to use the following SNMP commands: Tcpdump: verbose output suppressed, use -v or -vv for full protocol decode Here is what I see when traps are sent from Juniper device: snmp]# tcpdump -i enp0s3 port 162 But for some reason, it is silently ignoring the incoming traps from the Juniper device without further processing. I ran a tcpdump on port 162 of trap receiver server and found that the traps sent from Juniper switch is reaching the server. > ifIndex i 2 ifAdminStatus i 1 ifOperStatus i 1Īnd it was processed as expected too: snmp]# cat /var/log/snmptraplog.txt

Further, to check this, I tried sending a test trap from another CentOS server like below: snmptrap -v 2c -c public centos-Main. I sent few test traps from localhost itself and it is completely working as expected. This is what mydummyhandler.sh looks like: snmp]# cat mydummyhandler.shĮcho 'Trap Received' > /var/log/snmptraplog.txtīut when traps are sent from the Juniper router, my snmptrapd doesn't process it and does not write anything to /var/log/snmptraplog.txt. Traphandle default /etc/snmp/mydummyhandler.sh In my snmptrapd configuration, I am calling a very basic shell script just to identify if the trap was received: snmp]# cat /etc/snmp/nf

I am trying to configure this as a SNMP trap receiver.

Setup snmp trap receiver ubuntu 14.04