Users Guide

Event Definitions | Alarms, Events, and Automation
OMNM 6.5.3 User Guide 337
Message Template
—A template for messages that accompany this event. Specifying an OID
within the curly braces {} in the template acts as a tag which replaces the OID with its MIB
value. For example: Interface: {1.3.6.1.2.1.2.2.1.1} left the down state.
You can also add optional messages surrounded by double brackets [[ ]]. if the event
definition has the message “aindex: {1.2.3}[[, bindex: {1.2.4}]]” and {1.2.3} is defined as say
“1” but {1.2.4} is not defined then this resolves to “aindex: 1". If they are both defined (say
{1.2.4} is “2”) then this resolves to “aindex: 1, bindex: 2"
If a message template exists for an existing, correlated alarm and the generated text does not
match the original alarm, then OpenManage Network Manager closes the existing alarm, and
generates a new one. Leaving this blank transmits the original message.
NOTE:
Putting an OID in curly brackets amounts to a tag replaced by the MIB text for that OID. Look for OIDs and
messages in the MIB browser (as described in MIB Browser Tool on page 43).
Entity Lookup
This screen lets you configure how events based on this definition will be associated to entities. By
rule, the Equipment attribute of any event will be determined by the source IP address of the
original message (trap, syslog, etc.) By default, the Entity attribute will be the same as the
Equipment, but there might be information in the variable bindings of the trap through with the
event can be resolved to a subcomponent (Port, Interface, etc. )
Variable Binding to Use for Lookup — Indicates the variable binding that should be used for the
entity lookup. This drop down list includes all bindings that are expected to be in the trap payload
and also those that are critical mined. Latent mined bindings cannot be used for this purpose.
Entity Lookup Type — IndIndicates the algorithm that should be used to lookup the entity. For
example, if the variable binding to use for lookup contains an ifIndex then you should select By
ifIndex. It might also be that it instead contains the physical index, in which case there are two
options, either By Physical Index (simple) to simply lookup the entity by this given physical index
and associate to that entity directly, or By Physical Index (find parent) to instead use the physical
index to find the hierarchical parent. This is useful when a vital component of a device, like a power
supply or a fan, has sensors attached. Traps coming from this device contain the physical index of
the sensor rather than the vital component being monitored. This lookup type lets you associate
alarms with the vital components so you can ensure these components are functioning optimally.