You've got a wrong configuration there. You're trying to create an alarm with the severity Normal for the event code/cause code 0x3b10039. You should not do that. On the Generated Alarm you should have None and on the lower section, marked "Cleared Alarms" you have specified the cause code 0x3b1003a with discriminators "2,4".
In this popup, you're missing the OK button because you don't have anything selected on top, in the Cause Code* section. Once you have a cause code selected, you'll see the OK button not being grayed out.
------------------------------
Cătălin Fărcășanu
Senior Consultant
SolvIT Networks
------------------------------
Original Message:
Sent: Oct 04, 2023 11:09 AM
From: Saqib Qureshi
Subject: Alerts don't clear once condition no longer exist
For "JNX BGP M2 Backword Transition" the discriminator is set to 2,4
But for "jnxBgpM2Established" unable to set to 2,4 or any other number. The OK button remains greyed out
Original Message:
Sent: Oct 04, 2023 10:46 AM
From: Catalin Farcasanu
Subject: Alerts don't clear once condition no longer exist
The discriminator cannot be 0. It starts from 1, until the last varbind in the trap. It can be a combination of values starting with 1. You can have "1", "1,2", etc. This is the determined by the required level of uniqueness for the alarms generated.
In your case, I think it should be "2,4". So for each unique combination of jnxBgpM2PeerLocalAddr (2) + jnnxBgpM2PeerRemoteAddr (4) you should have an unique alarm alarm created.
The same would apply for the corresponding event that clears the alarm.
------------------------------
Cătălin Fărcășanu
Senior Consultant
SolvIT Networks
Original Message:
Sent: Oct 04, 2023 10:41 AM
From: Saqib Qureshi
Subject: Alerts don't clear once condition no longer exist
I have edited the "JNX BGP M2 Backword Transition" trap and set the discriminator to "0" as shown below. Did not make any changes to "jnxBgpM2Established" as the severity is set to "Normal". Is this setting looks good? Will this auto clear the clear the alert from the alarm board?
Original Message:
Sent: Oct 04, 2023 09:24 AM
From: Catalin Farcasanu
Subject: Alerts don't clear once condition no longer exist
Check the discriminator on the alarm creation and clearing event. It should match the varbind with the neighbor ID.
------------------------------
Cătălin Fărcășanu
Senior Consultant
SolvIT Networks
Original Message:
Sent: Oct 04, 2023 09:10 AM
From: Saqib Qureshi
Subject: Alerts don't clear once condition no longer exist
I have configured "JNX BGP M2 Backword Transition" alert i.e., whenever BGP state is other than "Established" Spectrum (Version 22.2.9.0.9) generates the alert. However, alerts won't clear once session is reestablished, and condition doesn't exist any longer. Can someone help how to configure these alerts to be auto clear.