Hello @ here,
Would anyone know if it would be possible to clear a “Critical HI” alarm if the condition remains for 30 mins. I am using Arista Manager protocol and configuring Operation State and I want to know when an interface goes down however, there are several ports disconnected so the Alarm Template sees that as a Critical high as configured. I need to figure out how to clear down ports if they are down for more than 30. This is assuming the port is down or disconnected by an administrator which shouldn’t be flagged as a Critical High 
Hello @pieterVanCompernolle
We created a condition both in the Alarm Template and LCA to achieve the alert we were looking for. We added information to idx table under the column Description for each port in used, the condition is as follows, only alert if there is a description and Admin state is UP, If Operation state goes now flag the alert. Any other condition does not apply do not alert. Here’s a screenshot of a Down port that meets the above condition, any other port that does not have a description is not being flagged.
Yes @Peter
Our network administrator has to fill in the description in order for the "condition" to work. Visually in a LCA this will allow the engineering team with a quick easy visual when a configured port goes down and not have to sort through all down ports.
ok, nice solution!
Hi Juan
Maybe is better to use another approach, we got a similar situation with cisco devices, and we reached the desired monitoring combining the admin status and the operational status.
For instance:
If the admin status was down that port wasn’t monitor, only the ones with oper and admin status up.
let me know if it works for you.
Thanks @ Jaime Leal,
we though of that initially however, not sure how that would be configured in the alarm template. Do you have an example I can see?
Hey Juan
Here the image of the exclusion you can set on the oper status parameter, to avoid monitoring the admin down interfaces.
Now I’m not sure if this is what you want to achieve.
That exclusion works for, still trying to see where/how I can clear a Critical HI when Operational Status Down past 30 mins
We are already ignoring Operational Status if Admin Status is down And also at some point want to ignore those if they are admin down for a period of time so protocol is not constantly alerting Min Hi
Did you already consider masking the alarms after 30? Either manually or via a persistent correlation rule? It’s not really what you asked, but it could maybe also resolve your use case?
Hi Juan,
I would try the following solution if I understood the problem correct:
This way it should go off after 30mins. We don’t alarm on Admin State only on Oper. State. I hope it helps.
This is hysteresis you are trying to apply. Not sure if this will solve the problem mentioned here. Hysteresis will delay the alarm or the clearance of the alarm. Here we want to get the alarm immediately, but want it cleared after 30.
Hi Juan,
Does this mean the 'Administrator' now fills in the 'description' your condition links to (instead of waiting for 30?). So basically, you've find a way to move forward with this?