Users Guide

Event Definitions | Alarms, Events, and Automation
338 OMNM 6.5.3 User Guide
Correlations
This screen lets you configure different forms of correlation for the event definition including
Raising/Clearing Correlated Events, Parent/Child Correlated Events, and Correlation Key
Bindings, the latter of which is essential for event to alarm correlation.
The
Event Definitions Correlated Eventsfor Raising/Clearing panel lets you control what type of
events will automatically clear the correlated alarms that are based on this definition. Within this
panel, click
Add to display a selector (with filter) to find events definitions to correlate with the one
you are editing. What this means is that if there is an existing open alarm based on this definition
(we can call it a raised alarm) and then subsequently another alarm is created that is correlated to
the raised one, it will cause the raised alarm to be cleared (it will no longer be open). Note that this
will only work if the definition you are editing has the severity of cleared and the definition in the
list has a severity other than cleared. For example, link down and link up event definitions are
correlated as raising/clearing, and thus all events and alarms based on these definitions will inherit
these correlations. So consider that a link down event is received that creates a raised alarm and
then subsequently a link up event is created. The link up would then correlate to and clear the link
down alarm.
The
Event Definitions Correlated for Parent/Child panel lets you control what type of alarms will
automatically correlate as parent/child relationships that indicate that one alarm caused the other
or that one alarm blocks progress on the other. What this means is that an open alarm based on the
definition you are editing will form a parent/child correlation to another open alarm based on a
definition in this list. Note that alarms based on the definition you are editing will become
correlated children of alarms based on definitions in the list (the later will become correlated
parents). For example, when new alarms are created that are based on this definition, OpenManage
Network Manager will try to find a correlated match between each new alarm and other existing
open alarms, and it does this based on the entries in this list. If it finds a match, it will correlate the
parent alarm to the child alarm.