Users Guide

Event Definitions | Alarms, Events, and Automation
OMNM 6.5.3 User Guide 343
<KeyBindings> <!-- OID(s) for bind object value(s) to use as
correlation key -->
<item/>
</KeyBindings>
<CorrelatedEvents> <!-- OID(s) for alarms to clear when this event
occurs. These OIDs can include an extension key as OID::extKey -->
<item>oid[::keyValue[:keyvalue]]</item>
</CorrelatedEvents>
</bean>
Extended Event Definitions
You can extend any event definition that defines one or more key bindings. The extension key
consists of a value for each key binding in the correct order. You must separate each value with a
colon (:).
Only extensions should set an extension key. The key format is dictated by the parent (extended)
definition’s key bindings. Set key bindings for the extension as needed for proper alarm correlation.
The following
Extended Event Definition Example provide some clarification.
NOTE:
Definition extensions do not inherit any settings from the extended definition.
Extended Event Definition Example
Events extend a basic definition:
bigBand 1.3.6.1.4.1.6387
Here are the extensions:
bigBandAdmin 1.3.6.1.4.1.6387::400
bigbandConfig 1.3.6.1.4.1.6387::5* (with partial matching extension key)
bigbandTraps 1.3.6.1.4.1.6387::400:50
bigbandAlarmTrapPrefix 1.3.6.1.4.1.6387::400:50:0
bigbandSessionAlarm 1.3.6.1.4.1.6387.400.50.0.0.2 (v2 OID)
bigbandEscalation 1.3.6.1.4.1.6387::400:50:0:0:3* (with partial matching
extension key)
Another base event:
bigBandCommon 1.3.6.1.4.1.6387.100
Other extensions:
session 1.3.6.1.4.1.6387.100::50
sessionAlarms 1.3.6.1.4.1.6387.100::50:100
sessionAlarmTable 1.3.6.1.4.1.6387.100::50:100:40
sessionAlarmEntry 1.3.6.1.4.1.6387.100::50:100:40:1
sessionAlarmProgramNumber 1.3.6.1.4.1.6387.100::50:100:40:1:2
sessionAlarmEscalation 1.3.6.1.4.1.6387.100::50:100:40:1*:2? (with
partial matching extension key)