This tab manages basics for Event Definitions.
It has the following fields:
Event Name -- A text identifier for the event.
Notification OID -- The object ID.
Severity -- The severity of any associated alarm. If a new alarm is a clearing severity, then it closes any existing alarm to which it correlates. Otherwise, if a new alarm severity does not match the existing severity then the existing alarm is closed and a new alarm opened for the new severity.
MIB Name -- The MIB with which this event is associated.
Default Behavior -- The options for behavior (Undefined, Alarm, Suppress, Reject). 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)
Resource Propagation -- The hierarchical resource propagation behavior for any alarm based on this event definition (either Default, Impacts subcomponents, or Impacts top level). (See also Alarm Propagation to Services and Customers: What Happens for more about how this impacts services and customers.)
An event definition configures “Resource Propagation” (distinct from “Alarm propagation”) based on the event type. Do alarms based on this event definition impact the overall device (Impacts top level), subcomponents (Impacts subcomponents), or just the correlated inventory entity (Default)?
Service Affecting -- Check this if the event has an impact on services. Indicates whether the alarm has an impact on services. If this is checked then alarms based on this event definition propagate calculated alarm states across services and customers that depend on the (directly) alarmed resource.
For example: If a resource has a service affecting alarm, then Open Manage Network Manager propagates the severity of this alarm across all associated services and customers. If the resource alarm is “clear” then all services depending on this resource are “clear” too. If the resource alarm is “critical,” then all services depending on that resource are “critical” too.
Alarms imported from previous versions appear as not service affecting, regardless of severity.
For more about propagation, see Alarm Propagation to Services and Customers: What Happens.
Advisory Text -- The Advisory Text appears with the event. Configure it in the text box here.