Users Guide

Event Definitions | Alarms, Events, and Automation
OMNM 6.5.3 User Guide 341
The Extended Event Definitions editor has the Extension Key Values fields that are the same as
those configured in
Extensions , and the following general properties:
Event Name —An identifier for the Extended Event. This field is editable, but if left blank the
system creates a name based on the name of the parent event definition and the key bindings
entered here.
MIB Name —A MIB identifier for the Extended Event
Parent Name —An identifier for the parent of the Extended Event
Notification OID —As with parent event definitions, this is the object ID. OpenManage Network
Manager automatically generates this based on the Notification OID of the parent and key
binding values entered. For example, if the parent event definition has a Notification OID of
“1.2.3.4” and the key binding values of the extended definition are 5 and 6 (the parent must
have previously been configured to have two extension bindings available) then the resulting
Notification OID for this new extended event definition will be “1.2.3.4::5:6”.
The remaining fields are as described in the Event Definition Editor
General screen. The Message
Template tab is as described in
Message Template on page 336, only this message template is for
the configured extended event definition.
Click
Save to create or re-configure an extended event, or Cancel to abandon your edits. See
Extending Event Definitions on page 342 for detailed steps.
Using Extended Event Definitions
To handle complex networks, you can configure event responses with a “Base Event Definition”
and several “Extended Event Definitions” (EEDs). You can customize events, the reaction to them,
and even extend events with EEDs. Modified or extended event definitions override the base set of
definitions that comes from the traps and notifications found in loaded MIB files, and their OIDs
appear in the
Event Definition Editor on page 334.
You can modify Extended Event Definitions two ways:
•
Extending Event Definitions
• Extending Event Definition XML
You can configure extended event definitions to perform partial matching on variable bindings by
including
wildcard characters in the extension key. The asterisk * matches any number of
characters and the question mark ? matches a single character. For example an extension key of 1*
matchs variable bindings that start with a 1 including 11, 12, 134, and so on. An extension key of 1?
matchs 11, 12, 13 but does not match 134. An extension key of *3* matchs any variable binding
that includes the number 3 somewhere, including 34, 13, 3, 438.