Owner's Manual

828 Events, Rules and Actions
General
This tab has the following fields
-
Event Name —A read-only reminder of which event this is.
-
Notification OID —The object identifier for the event.
-
MIB Name —The name of the MIB in which this event’s information appears.
-
Severity —If the new alarm is a clearing severity, then any existing alarm to which it correlates is
closed. Otherwise, if the new alarm severity does not match the existing severity then the
existing alarm is closed and a new alarm opened for the new severity.
-
Default Behavior —The default that occurs with this event. You can alter the default with the
pick list (
Alarm, Reject, Suppress ). Alarm means: Process at the mediation server, generate
event history and an alarm.
Suppress means: Process at the mediation server and generate an
event (
not an alarm). Reject means: Reject at the mediation server (do not process)
-
Propagation —Only service effecting alarms are propagated. By default, events are service-
effecting, provided their severity is indeterminate or above. Select the propagation type from
the pick list. Options include
Default, Impacts subcomponents, Impacts top level , and Not
service effecting
.
An event definition configures “Impact Propagation” (distinct from “Alarm propagation”)
based on the event type. Does the event impact the overall device (
Impacts top level ),
subcomponents (
Impacts subcomponents ), or just the correlated inventory entity ( Default )?
Not Service Effecting means that alarm propagation ignores alarms for this event. In other
words, no impact to associated entities occurs. This also means alarms created for this event
type appear as
Not Service Effecting in the alarm manager—handy to help clean up noisy
alarm views since you can filter to conceal these.
For example, link propagation works like this: If one or both associated endpoints have an
impacting alarm, then OpenManage Network Manager generates a calculated alarm for the
corresponding link at the highest severity of either endpoint. If both endpoints are clear then
the resulting, calculated event is clear. This means alarm correlation removes any existing
calculated alarm against the link.
If you upgrade your OpenManage Network Manager system, all alarms migrated to this
version will appear as service-effecting, regardless of severity. To alter multiple events’ impact
propagation, export the event definitions, and alter the XML export to reflect the kind of
propagation desired for events.
Search for the paired
<ImpactPropagation>0</ImpactPropagation> tags, and alter
the numbers within them as follows:
Default—0
Impacts Top Level—1
Impacts Subcomponents—2