Multiple received snmp traps with the same severity only shown the first trap
Posted: Mon Jul 15, 2024 6:09 pm
Hi,
We are trying to collect SNMP traps from Nagios XI. We encountered an issue with multiple SNMP traps from the same source with the same severity.
Say, we recieved two critical traps from same source as below, the time between the traps does not matter although in this case is only 2 seconds.
Mon Jul 15 22:42:23 2024 .1.3.6.1.4.1.17869.3.1.2.1.1 Critical "Status Events" 10.20.41.95 - Received trap "lmrIwfRaiseAlarm" with variables "esAlarmEventTime:2024-7-15,22:21:3.0 esAlarmEventType:communicationsAlarm esAlarmId:E_CSC_ENG_LINK esAlarmHostName:lmr-iwf-31-gp1 esAlarmAppName:IwfCsc esAlarmAppInstance:1 esAlarmAppVersion:3.1.8-3 esAlarmAppSubComponent:LinkManager esAlarmPerceivedSeverity:major esAlarmDescription:The IWF-CSC has no access to the IWF-ENG application within the IWF network. esAlarmAdditionalInfo:{\"reason\": \"Link Poll Failure\", \"LinkId\": \"IWF-ENG\"} esAlarmProbableCause:applicationSubsystemFailure esAlarmSpecificProblem:The IwfCsc application is monitoring access to the IwfEng application on the local GP node. The IwfCsc considers the IwfEng application to be unreachable. esAlarmNotificationId:2bed72b0-13cd-42dc-87f7-27a198e7ecba"
Mon Jul 15 22:42:25 2024 .1.3.6.1.4.1.17869.3.1.2.1.1 Critical "Status Events" 10.20.41.95 - Received trap "lmrIwfRaiseAlarm" with variables "esAlarmEventTime:2024-7-15,22:21:5.0 esAlarmEventType:communicationsAlarm esAlarmId:E_CSC_GMS_SIP_LINK esAlarmHostName:lmr-iwf-31-gp1 esAlarmAppName:IwfCsc esAlarmAppInstance:1 esAlarmAppVersion:3.1.8-3 esAlarmAppSubComponent:LinkManager esAlarmPerceivedSeverity:major esAlarmDescription:The IWF has no SIP access to the Group Management System (GMS) within the MCPTX network. esAlarmAdditionalInfo:{\"reason\": \"Request Timeout\", \"LinkId\": \"sip:gms@2606:ae00
2107
:22:5060\"} esAlarmProbableCause:applicationSubsystemFailure esAlarmSpecificProblem:The IwfCsc application is monitoring SIP access to the external Group Management System (KMS) within the MCPTX network. The IwfCsc considers the GMS server to be unreachable via SIP. esAlarmNotificationId:abc0f984-fe1d-4856-89fe-ffec7bc784ce"
However, from the display, we can only see the first one but not the second one. Same with the Clear alarm case.
Can you help us to find the reason?
We are trying to collect SNMP traps from Nagios XI. We encountered an issue with multiple SNMP traps from the same source with the same severity.
Say, we recieved two critical traps from same source as below, the time between the traps does not matter although in this case is only 2 seconds.
Mon Jul 15 22:42:23 2024 .1.3.6.1.4.1.17869.3.1.2.1.1 Critical "Status Events" 10.20.41.95 - Received trap "lmrIwfRaiseAlarm" with variables "esAlarmEventTime:2024-7-15,22:21:3.0 esAlarmEventType:communicationsAlarm esAlarmId:E_CSC_ENG_LINK esAlarmHostName:lmr-iwf-31-gp1 esAlarmAppName:IwfCsc esAlarmAppInstance:1 esAlarmAppVersion:3.1.8-3 esAlarmAppSubComponent:LinkManager esAlarmPerceivedSeverity:major esAlarmDescription:The IWF-CSC has no access to the IWF-ENG application within the IWF network. esAlarmAdditionalInfo:{\"reason\": \"Link Poll Failure\", \"LinkId\": \"IWF-ENG\"} esAlarmProbableCause:applicationSubsystemFailure esAlarmSpecificProblem:The IwfCsc application is monitoring access to the IwfEng application on the local GP node. The IwfCsc considers the IwfEng application to be unreachable. esAlarmNotificationId:2bed72b0-13cd-42dc-87f7-27a198e7ecba"
Mon Jul 15 22:42:25 2024 .1.3.6.1.4.1.17869.3.1.2.1.1 Critical "Status Events" 10.20.41.95 - Received trap "lmrIwfRaiseAlarm" with variables "esAlarmEventTime:2024-7-15,22:21:5.0 esAlarmEventType:communicationsAlarm esAlarmId:E_CSC_GMS_SIP_LINK esAlarmHostName:lmr-iwf-31-gp1 esAlarmAppName:IwfCsc esAlarmAppInstance:1 esAlarmAppVersion:3.1.8-3 esAlarmAppSubComponent:LinkManager esAlarmPerceivedSeverity:major esAlarmDescription:The IWF has no SIP access to the Group Management System (GMS) within the MCPTX network. esAlarmAdditionalInfo:{\"reason\": \"Request Timeout\", \"LinkId\": \"sip:gms@2606:ae00
2107
:22:5060\"} esAlarmProbableCause:applicationSubsystemFailure esAlarmSpecificProblem:The IwfCsc application is monitoring SIP access to the external Group Management System (KMS) within the MCPTX network. The IwfCsc considers the GMS server to be unreachable via SIP. esAlarmNotificationId:abc0f984-fe1d-4856-89fe-ffec7bc784ce"However, from the display, we can only see the first one but not the second one. Same with the Clear alarm case.
Can you help us to find the reason?