Issues with clearing alarms
-
As a long term administrator of HP OML/OMi, I (and the operations staff) are used to seeing a clearing alarm when an anomalous issue has been corrected. The "standard" has always been to have the clearing alarm terminate the problem alarm, then after 60 seconds, the clearing alarm terminates automatically.
I am looking for a way to accomplish this (if possible).
Any help would be appreciated.
-
This is done by alarm keys. When you create "problem" alarm, you create event processing policy rule that do "generate alarm" and here you can set the key. For terminating you create another rule that handles recovery event and do "terminate alarm" with the given key. You can look at rules for SYS_NODE_DOWN and SYS_NODE_UP events.
Best regards,
VictorP.S. Questions like this have much more chances to be responded quickly if placed into correct section on forum. "Development" section is intended for developing of product itself or using it's APIs, so many users simply never look at posts there.
-
-
Two ways here:
-
Set alarm timeout and what event will be generated, and then create another rule to terminate alarm on timeout event. Note that timeout event will be generated only if alarm will still be in outstanding state.
-
Execute script action with required delay in same rule, and terminate alarm from that script.
Best regards,
Victor -
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login