Hello,
Trying to set up an Alarm Template to monitor BGP State. The issue I am having is if BGP changes from Established to Idle I need to know so action can be taken. Current alarm template tracks "Established" is OK, if it goes to "Idle", trigger alert. However, BGP continuously tries to re-establish so it goes from Idle to Active, and if it can't re-establish, back to Idle, triggering another alert. I have tried Hysteresis, but that doesn't work correctly. Is there a way to look for Established or Not, ignoring all other states since only Established is good?
Ben,
I found it with the right click. Never knew that existed before. I will update you when I get a chance to confirm.
Hi Craig – Is it possible for your to do one of the two and post a screen shot or email me the results. randy.ulvenes@skyline.be
1) If you can filter on the specific elements alarms and copy the alarms into a spreadheet or maybe attach a screenshot of the alarms….
2) Trend on this parameter and then take a screenshot of the trend of the state changes.
Either of these would help see the transitions BGP transitions timing and help with determine alarm settings…etc. One other option is to use the correlation rules and create a new alarm based a specific BGP state transition.
Hi Craig - sorry for keeping you waiting a bit here. Interesting case though and makes totally sense.
Concerning hysteresis - I had to take a good look also again to make sure. But in essence, hysteresis does function on discrete levels but there are some particular things about it.
Now, I believe I might have found a way to set it up that might get close to what you are looking for.
Set 'Established' to NORMAL in the alarm template (GREEN)
Set 'Idle' to CRITICAL HI in the alarm template (RED)
Set 'Active' to MAJOR HI in the alarm template (YELLOW)
Now also put HYST OFF on x seconds and check the box for CRITICAL HIGH (so it will only apply to the CRITICAL HIGH limit)
What you should be getting now is that when it goes from ESTABLISHED to IDLE, it will create a critical alarm. When it goes from IDLE to ACTIVE, it will not create a major alarm, and will wait for x seconds. Only when it stays in ACTIVE for longer than x seconds, it will create a major alarm for the state ACTIVE, replacing the critical alarm.
I have no idea when it goes to IDLE and then goes into ACTIVE, how long it is there in that mode, before it goes back to IDLE again. But for what you want, you need x to be high enough so that it doesn't update the alarm before going back to IDLE. Then again, keep in mind that this x also applies when going from IDLE to ESTABLISHED, so you do not want it too high.
But probably it actually goes from IDLE to ACTIVE, and then to ESTABLISHED (not from ACTIVE to IDLE and then to ESTABLISHED). In that case, it will depend on how long it was in that ACTIVE state before it went to ESTABLISHED. Example: if you set it to 10 seconds, and it goes from IDLE to ACTIVE, and then after 6 seconds it goes from ACTIVE to ESTABLISHED, then it would take 4 seconds to clear the alarm.
I had to test this and see if we could somehow make it what you are after, so I hope I got it right. If not, maybe this helps to further play around.
Ben,
Unfortunately This did not work as expected. I kept changing the hysteresis to stop the alarms from filling up my email. I ended up with an 660s Hyst off and still was triggering alerts. I will continue to adjust things as there must be a way to accomplish the goal. Thank You for your input, it was a fresh approach.
Ben Thank You for that. I am testing it out but I do not see a check box for setting hysteresis to only Maj Hi. I am running DataMiner (10.3.0.0-13537-CU9).
Thank You Again.