The incoming trap doesn't have the DNS name (FQDN) of the host : Code: receivedfrom UDP: [129.250.81.157]:33079-> [204.2.140.14]:162. Now format the traps for Zabbix to recognize them (edit snmptt.conf): Do not use unknown traps - Zabbix will not be able to recognize them. Replace the underscores with your Zabbix version number. .1.3.6.1.4.1.1588.3.1.4.1.1 type=4 value=STRING: "CLEAR_ALL_ALERTS" We will use the common "link up" OID in this example: SNMPv3 addresses SNMPv1/v2 security issues and provides authentication and encryption. Container shell access and viewing Zabbix snmptraps logs. See the Zabbix documentation about configuring SNMP traps for more information. If you want to resolve and use the names, you need to download the MIB files and enable loading them. Add to. net-snmp-perlperl, zabbix_trap_receiver.pl Unmatched SNMP Traps Formatting : zabbix - Reddit .1.3.6.1.4.1.1588.3.1.4.1.7 type=4 value=STRING: "0" Problem expression for triggering an interface down event for interface index 5 of host Switch: Recovery expression for the same trigger: Note that in order to Zabbix to link the incoming trap to the correct host the host in Zabbix needs to have an SNMP interface configured with the same IP address that the trap contains. This is a proof that test SNMP trap has been received and passed to Zabbix. transactionid 2 Replace "secret" with the SNMP community string configured on SNMP trap senders: Next we can send a test trap using snmptrap. Our documentation writers will review the example and consider incorporating it into the page. The simplest way to set up trap monitoring after configuring Zabbix is to use the Bash script solution, because Perl and SNMPTT are often missing in modern distributions and require more complex configuration. What are the advantages of running a power tool on 240 V vs 120 V? .1.3.6.1.6.3.18.1.4.0 type=4 value=STRING: "L1b3rty" After translation, the trap is saved to /tmp/zabbix_traps.tmp. We have gotten snmptt to work so the ports and functionality from a trap perspective should be working (trying to move away from snmptt now as that seems not be very consistent). Most Zabbix users use proxies, and those running medium to large instances might have encountered some performance issues. Works directly (host -> zabbix server) Which language's style guidelines should be used when writing code that is supposed to be called from another language? Naturally this error is also not present if you already have configured Zabbix host with a matching SNMP trap item. Next we will configure snmptrapd for our chosen SNMP protocol version and send test traps using the snmptrap utility. Create new hosts with SNMP interfaces for unmatched traps. Right now I'm at a stage where traps are being logged on $SNMPTrapperFile successfully. You are using IPv4, address 64.111.126.32, Majornetwork.net Markku Leini 2011-2023, Configuring SNMP Trap Receiver for Zabbix on Debian, https://git.zabbix.com/projects/ZBX/repos/zabbix/raw/misc/snmptrap/zabbix_trap_receiver.pl, Zabbix documentation about configuring SNMP traps.