Hello.
I have a problem with setting up SNMP v3 traps. Whenever I send a test trap, Zabbix is assigning it to correct host, but it is detected as 'unmatched trap'. I believe there is something wrong with SNMPv3 credentials, because if I set the trap to be sent as v2c snmp trap and add proper authCommunity in /etc/snmp/snmptrapd.conf, the trap is detected correctly according to the key in created item.
I use the same credentials for standard SNMPv3 queries and everything works fine.
Below is some basic configuration info:
- I'm using zabbix_trap_receiver.pl as a trap handler
- I have configured user, authentication and privacy information in /etc/snmp/snmpd.conf and snmptrapd.conf
Here's my snmpd.conf:
[...]
createUser -e 0x800000D380500000E0DA2B7400 snmpv3-user MD5 authpass DES privpass
rouser snmpv3-user
snmptrapd.conf:
[..]
createUser -e 800000D380500000E0DA2B7400 snmpv3-user MD5 authpass DES privpass
#authCommunity log,execute,net ro-community
authUser log,execute,net snmpv3-user
perl do "/usr/local/bin/zabbix_trap_receiver.pl";
It looks that entries in /var/lib/net-snmp/snmpd.conf and snmptrapd.conf are created accordingly to the above ones.
I tried pasting the "Engine ID" with and without preceding it with "0x".
Also, if I check the entries in /tmp/zabbix_traps, the Engine ID is always a mess:
10:19:53 2015/12/01 ZBXTRAP 10.255.250.24
PDU INFO:
contextEngineID <80>^@^@Ó<80>P^@^@àÚ+t^@
notificationtype TRAP
version 3
receivedfrom UDP: [10.255.250.24]:57586->[10.255.215.11]
errorstatus 0
messageid 0
securitylevel 3
securityEngineID <80>^@^@Ó<80>P^@^@àÚ+t^@
securityName snmpv3-user
contextName
securitymodel 3
transactionid 1
errorindex 0
requestid 271
I would be very grateful for any tip - I'm struggling with this problem for a third day, and at this point I have no idea what might be wrong.
Best regards,
Pawel
I have a problem with setting up SNMP v3 traps. Whenever I send a test trap, Zabbix is assigning it to correct host, but it is detected as 'unmatched trap'. I believe there is something wrong with SNMPv3 credentials, because if I set the trap to be sent as v2c snmp trap and add proper authCommunity in /etc/snmp/snmptrapd.conf, the trap is detected correctly according to the key in created item.
I use the same credentials for standard SNMPv3 queries and everything works fine.
Below is some basic configuration info:
- I'm using zabbix_trap_receiver.pl as a trap handler
- I have configured user, authentication and privacy information in /etc/snmp/snmpd.conf and snmptrapd.conf
Here's my snmpd.conf:
[...]
createUser -e 0x800000D380500000E0DA2B7400 snmpv3-user MD5 authpass DES privpass
rouser snmpv3-user
snmptrapd.conf:
[..]
createUser -e 800000D380500000E0DA2B7400 snmpv3-user MD5 authpass DES privpass
#authCommunity log,execute,net ro-community
authUser log,execute,net snmpv3-user
perl do "/usr/local/bin/zabbix_trap_receiver.pl";
It looks that entries in /var/lib/net-snmp/snmpd.conf and snmptrapd.conf are created accordingly to the above ones.
I tried pasting the "Engine ID" with and without preceding it with "0x".
Also, if I check the entries in /tmp/zabbix_traps, the Engine ID is always a mess:
10:19:53 2015/12/01 ZBXTRAP 10.255.250.24
PDU INFO:
contextEngineID <80>^@^@Ó<80>P^@^@àÚ+t^@
notificationtype TRAP
version 3
receivedfrom UDP: [10.255.250.24]:57586->[10.255.215.11]
errorstatus 0
messageid 0
securitylevel 3
securityEngineID <80>^@^@Ó<80>P^@^@àÚ+t^@
securityName snmpv3-user
contextName
securitymodel 3
transactionid 1
errorindex 0
requestid 271
I would be very grateful for any tip - I'm struggling with this problem for a third day, and at this point I have no idea what might be wrong.
Best regards,
Pawel
Comment