Users Guide

Event Definitions | Alarms, Events, and Automation
342 OMNM 6.5.3 User Guide
Extending Event Definitions
To extend event definitions, you create “child” events that extend a “parent” event. Extend an
event definition as follows.
1 Save the parent event for which you configured Extensions.
2 S elect it from the Event Definitions manager.
3 Right-click your selection and then select Add Extended Event Definition.
The
Adding Extended Event Definitions on page 340 window the Extension Key Values
fields configured from the
Event Definitions , Extensions panel. The variables also show in
the order you selected from the
Extensions panel. A suggested name for this event is the
parent event name, followed by a colon-separated list of the field values entered on this
screen.
Once configured, this extended event overrides the parent.
Extending Event Definition XML
After loading its base event definitions, the OpenManage Network Manager (OMNM) application
loads all event definitions in the XML files in the server\conf directory under each module (for
example \owareapps\redcell\server\conf\eventdefs.xml) and applies them as overrides. The OMNM
application discards any XML event definitions if the notification type is unknown—that is, not in
a loaded MIB. If you alter this XML file, you need to import it in Event Definitions Manager before
the alterations take effect.
Extended event definitions (EEDs) support system extensions along with system overrides. An
extension creates a unique definition for a MIB-based event that only applies to certain instances
of the event. The extension appears as a separate event in the event definition manager and you
can modify it as you can any other event.
Extension exist primarily to create specialized event definitions for recognizable variations from
the basic event.
For details, see the following:
•
XML Event Definition
• Extended Event Definitions
• Extended Event Definition Example
XML Event Definition
The format format is of an XML event definition:
<bean xsi:type="tns:NotificationDefinitionNP">
<NotificationOID/> <!-- required -->
<ExtensionKey/> <!-- extensions only - syntax: key1Value[:key2Value]-
->
<Description/> <!-- message text - supports object OID tag
replacement: {objectOID} -->
<Behavior/ <!-- 1=alarm, 2=suppress, 3=reject (default is
alarm)-->
<Severity/> <!-- 0=clearing, 1=info, 2=unkown, 3=warning,
4=minor, 5=major, 6=critical -->
<ImpactPropagation/> <!-- 1=up, 2=down, 3=both (default is none) -->