Result=`$ZABBIX_SENDER -z $ZABBIX_SERVER -p $ZABBIX_PORT -s $hostname -k $KEY -o Hostname=`echo “$ZABBIX_HOST” | cut -f2 -d]`Įcho $FINDER “FINDER” > /tmp/snmptrapzabbix.logĮcho $ZABBIX_HOST “ZABBIX HOST” > /tmp/snmptrapzabbix.logĮcho $ZABBIX_SERVER “ZABBIX_SERVER” > /tmp/snmptrapzabbix.logĮcho $hostname “HOSTNAME” > /tmp/snmptrapzabbix.logĮcho $KEY “KEY” > /tmp/snmptrapzabbix.log ZABBIX_HOST=`grep $hostname $ZABBIX_HOSTSFILE` Here is what I did to resolve the problem: I use crontab to update the IP-to-hostname file two times each hour. You can create triggers based on snmp trap content as you want. You can also create a template and attach it to hosts you want to monitor.

With this script you need an Item with type=”ZABBIX Trapper” and key=”snmptrap” for each host you want trap handling. Result=`$ZABBIX_SENDER -z $ZABBIX_SERVER -p $ZABBIX_PORT Hostname=`echo '$ZABBIX_HOST' | cut -f2 -d]` # used if the script can't find the hostname ZABBIX_HOSTSFILE='/home/zabbix/zabbix-1.6.2/misc/snmptrap/zabbixhosts' # path to zabbixhosts, containing IP/hostname pairs ZABBIX_SENDER='/home/zabbix/zabbix-1.6.2/src/zabbix_sender/zabbix_sender' With few changes to the original script I can send traps to the right Zabbix host, grabbing the hostname from the mySql dump ( zabbixhosts): # CONFIGURATION Running this script every 30 minutes I have a file containing pairs of IP/HostName such these: MYWEBSERVER Mysql -batch -silent -e 'SELECT CONCAT( '', Host )įROM zabbix.hosts WHERE IP '' AND IP '0.0.0.0'' > $DST Usage: zabbix_sender file, using mysql client: DST='/home/zabbix/zabbix-1.6.2/misc/snmptrap/zabbixhosts' Zabbix_sender, used to send traps information to the server, can’t translate IP address to hostname: #. It works! The problem is that, whatever the sender is, trap data is always binded to one host: snmptraps.

On Zabbix, you can setup a fake Host with an Item of type “ZABBIX Trapper”: in the original script, both host and item’s key are referenced as snmptraps. Finally, the script runs zabbix_sender to send information to the Zabbix server. This is how it works: snmptrapd starts listening on port UDP 162, receives traps and sends them to a handler, which runs the script and pass trap information to its standard input. Traps can be received using Net-SNMP suite and snmptrap.sh, a script released within the misc directory of Zabbix. In my opinion Zabbix is a really good NMS, but it’s lacking on SNMP traps handling.

Debian snmp trap receiver