admin管理员组文章数量:1123097
I'm in the process of setting up Zabbix on Alma 9 and I'm having an odd issue with SNMP traps. We have sip switch that has SNMP enabled and is pointing at the server, but for some reason snmptrapd isn't processing the incoming traps
Zabbix is install and running. snmp and trap is running
[root@dev:~]$ ps ax | grep snmp
1472 ? S 0:00 /usr/sbin/zabbix_server: snmp trapper [processed data in 0.000060 sec, idle 1 sec]
1527 ? Sl 0:00 /usr/sbin/zabbix_server: snmp poller #1 [got 0 values, queued 0 in 5 sec, awaiting 0]
2174 ? Ss 0:00 /usr/sbin/snmptrapd -Lsd -f
2585 pts/1 S+ 0:00 grep --color=auto snmp
running snmptrapwalk works
snmptrap -v 2c -c public 10.5.5.122 '' SNMPv2-MIB::snmpMIB IF-MIB::linkDown s eth0
2025-01-10T16:51:09+0000 ZBXTRAP 10.5.5.122
PDU INFO:
receivedfrom UDP: [10.5.5.122]:47786->[10.5.5.122]:162
version 1
transactionid 2
requestid 1130383097
errorstatus 0
messageid 0
notificationtype TRAP
errorindex 0
community public
VARBINDS:
DISMAN-EVENT-MIB::sysUpTimeInstance type=67 value=Timeticks: (337607) 0:56:16.07
SNMPv2-MIB::snmpTrapOID.0 type=6 value=OID: SNMPv2-MIB::snmpMIB
IF-MIB::linkDown type=4 value=STRING: "eth0"
On our sip switch if I restart one of the modules, it triggers the snmpt trap Using TCP dump I can it being sent to the zabbix server
tcpdump -i ens18 -T snmp -n dst portrange 161-162
17:14:35.573815 IP 10.7.7.113.33830 > 10.5.5.122.snmptrap: V2Trap(174) .1.3.6.1.2.1.1.3.0=1877147173 .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.17236.2.1 .1.3.6.1.4.1.17236.1.1="CRITICAL : 003 010008 000007 10/01/2025 17:14:35 : Connection to 0XA070771 (SIP Switch 3 - BT) lost"
17:14:36.427854 IP 10.7.7.113.43173 > 10.5.5.122.snmptrap: V2Trap(152) .1.3.6.1.2.1.1.3.0=1877147258 .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.17236.2.1 .1.3.6.1.4.1.17236.1.1="CRITICAL : 003 010000 000000 10/01/2025 17:14:36 : Application Server stopped"
17:14:37.434487 IP 10.7.7.113.54710 > 10.5.5.122.snmptrap: V2Trap(222) .1.3.6.1.2.1.1.3.0=1877147359 .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.17236.2.1 .1.3.6.1.4.1.17236.1.1="MAJOR : 007 023009 000000 10/01/2025 17:14:37 : Shout.Ocp.OcpLink (127.0.0.1:10012) has failed. Reason: Unexpected error in Heartbeat thread."
17:14:41.627673 IP 10.7.7.113.34462 > 10.5.5.122.snmptrap: V2Trap(230) .1.3.6.1.2.1.1.3.0=1877147778 .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.17236.2.1 .1.3.6.1.4.1.17236.1.1="MAJOR : 007 023009 000000 10/01/2025 17:14:41 : Shout.Ocp.OcpLink (127.0.0.1:10012) has failed. Reason: Unable to read beyond the end of the stream..
Yep there is nothing in the logs. This is what I have in /etc/snmp/snmptrap.conf
#Zabbix 1 and 2
disableAuthorization yes
authCommunity execute public
#Zabbix SNMP trap receiver
perl do "/usr/bin/zabbix_trap_receiver.pl";
Selinux is disabled and so it the firewall. I get no error messages and nothing is showing in /var/log/messages indicating any issues. I'm stumped
本文标签: zabbixSNMP Trap not logging remote trapsStack Overflow
版权声明:本文标题:zabbix - SNMP Trap not logging remote traps - Stack Overflow 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1736548138a1944476.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论