DELL Version 5.3 User Manual

Event Definitions | Key Portlets

163

Fine-Tuning Event Correlations

Dell OpenManage Network Manager’s eventdefs.xml files configure event definitions that

originate in installed MIBs. Dell OpenManage Network Manager’s editor is typically a more

convenient to configure them further.
No edit screen currently exists to configure variable binding objects. If you need to configure

CorrelationType, you can do so by editing the /owareapps/redcell/server/conf/
bindobjectdefs.xml

file.

If an event definition does not correlate correctly for your system—for example the falling alarm

does not clear the initial raising alarm—then you can use one or more of the OIDs for the binding

objects on the Message Template tab, not the OID of the event definition itself, and create entries

for them in this file. The technical help desk may assist in this process.
To customize Dell OpenManage Network Manager’s standard bindings, edit the file. Here is an

example of what appears in that file:

<?xml version="1.0" standalone="yes"?>

<ow:owdata xmlns:ow="urn:doradosoftware" xmlns:tns="urn:com/dorado/

redcell/notifications" xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance">

<!-- ** Notification binding object definitions **

This feature was added to allow for different ways of correlating

notifications when the key bindings are structured differently.

CorrelationType

0 = On value, where all bindings have both an OID and a value, the value

is used to correlate (this is default)

1 = On index, e.g. OID of 1.4.5.3.4389.334 where no binding object

exists with this exact OID but 1.3.5.3 does exist

and is configured this way will use the remainder of the string

(4389.334 in this example) to correlate

-->

</bean>