Users Guide

Variable Binding Definitions | Alarms, Events, and Automation
OMNM 6.5.3 User Guide 349
nonetheless be a device that sends data based on this definition as a string. If this is set to true,
then this will enable a conversion mechanism so that it will ensure that the data will conform to the
data type specified in the MIB.
Variable Bindings — This panel contains a list of additional variable bindings to mine after a trap
comes in. The variable bindings present in any SNMP trap is supposed to be specified in the MIB,
but sometimes more variable bindings are needed to so that the resulting alarm message contains
the necessary contextual information. If more variable bindings are needed, but can only be
accessed by using data from one that has already come in then this should be specified here where
the variable binding you are editing is the one that is expected to come in the payload of the trap
and the binding listed within this panel are then mined using the index of the binding that is based
on the definition you are editing. You can push the button
Add Latent Mined Binding and select a
binding from the popup and add it to this list. After you save this screen, the bindings you add will
show on the Message Template tab of any event definition that contains this binding in its trap
payload based on the trap definition as specified in the MIB. Note that any bindings added to this
list are latent mined, meaning that they are only mined during alarm correlation. The data from
these bindings can be used in the message template and/or key bindings of the respective event
definition, but latent mined bindings cannot be used in filters, nor for extensions, and nor for
entity lookup. If you would like to use a mined binding for any of those features, you will have to
use critical mining rather than latent mining. Critical mined bindings are defined at the event
definition level rather than at the variable binding definition level. Please see
Using Extended
Event Definitions
on page 341 for more information.