Page 1 of 1

Multiple traps from different device is showing as single

Posted: Fri Jun 19, 2020 8:25 am
by covid19
when Multiple traps from different device are coming at the same time then trap out put is combine in a single device output.
for ex : Today we received 3 traps from 3 devices at 19.17.3 CET. (At the same time)


1 : nagios GUI should show 3 trap for 3 device but we are getting only one trap including out of remaining 2 device trap.
2 : nagios.log output :

[root@lp000app4129 backup]# cat /tools/list/nagios/var/nagios.log
[1592507969] SERVICE ALERT: XXXX;TRAP;CRITICAL;HARD;1;down:OSPF router id x.x.x.x , neighbor router id x.x.0.4 with peering address x.x.102.49 state changed to down:TEST1[1592507953]

PROCESS_SERVICE_CHECK_RESULT:x.x.192.70:TRAP:2:down:OSPF router id x.x.100.70 , neighbor router id x.x.0.4 with peering address x.x.102.69 state changed to down:TEST1[1592507953]

PROCESS_SERVICE_CHECK_RESULT:x.x.193.34:TRAP:2:down:OSPF router id x.x.0.34 , neighbor router id x.x.0.4 with peering address x.x.2.33 state changed to down:TEST1[1592507953]
#########################################################
sharing the snmptt.log output for all received TRAP, in snmptt.log trap format is completly OK but in nagios.log all 3 TRAPS coming together in one single TRAP.

[root@xxxx4129 backup]# cat /tools/list/log/backup/snmptt.log | grep x.x.192.70
Thu Jun 18 21:19:03 2020 ospfNbrStateChange Normal "Status Events" x.x.192.70 - OSPF Neighbour State Change: OSPF router id x.x.100.70 neighbor area x.x.102.69, neighbor router id x.x.0.4 state changed to down.

Thu Jun 18 21:19:08 2020 ospfNbrStateChange Normal "Status Events" x.x.192.70 - OSPF Neighbour State Change: OSPF router id x.x.100.70 neighbor area x.x.102.69, neighbor router id x.x.0.4 state changed to down.

[root@xxxapp4129 backup]# cat /tools/list/log/backup/snmptt.log | grep x.x.193.34
Thu Jun 18 21:19:03 2020 ospfNbrStateChange Normal "Status Events" x.x.193.34 - OSPF Neighbour State Change: OSPF router id x.x.0.34 neighbor area x.x.2.33, neighbor router id x.x.0.4 state changed to down.

Thu Jun 18 21:19:08 2020 ospfNbrStateChange Normal "Status Events" x.x.193.34 - OSPF Neighbour State Change: OSPF router id x.x.0.34 neighbor area x.x.2.33, neighbor router id x.x.0.4 state changed to down.

[root@xxxapp4129 backup]# cat /tools/list/log/backup/snmptt.log | grep x.x.192.50
Thu Jun 18 21:19:03 2020 ospfNbrStateChange Normal "Status Events" x.x.192.50 - OSPF Neighbour State Change: OSPF router id x.x.100.50 neighbor area x.x.102.49, neighbor router id x.x.0.4 state changed to down.

Thu Jun 18 21:19:08 2020 ospfNbrStateChange Normal "Status Events" x.x.192.50 - OSPF Neighbour State Change: OSPF router id x.x.100.50 neighbor area x.x.102.49, neighbor router id x.x.0.4 state changed to down.

PROCESS_SERVICE_CHECK_RESULT:x.x.192.70:TRAP:2:down:OSPF router id x.x.100.70 , neighbor router id x.x.0.4 with peering address x.x.102.69 state changed to down:TEST1[1592507953]

PROCESS_SERVICE_CHECK_RESULT:x.x.192.50:TRAP:2:down:OSPF router id x.x.100.50 , neighbor router id x.x.0.4 with peering address x.x.102.49 state changed to down:TEST1[1592507953]

PROCESS_SERVICE_CHECK_RESULT:x.x.193.34:TRAP:2:down:OSPF router id x.x.0.34 , neighbor router id x.x.0.4 with peering address x.x.2.33 state changed to down:TEST1[1592507969]

PROCESS_SERVICE_CHECK_RESULT:XX.10.34:TRAP:0:Normal:Test3