I have created custom events and alarms for device and interface models. If the event exists on the interface model and it's associated device model at the same time, I need to correlate them so the interface model is the root cause alarm.
How to create a Spectrum Condition Correlation to correlate an alarm on an interface model with an alarm on the associated device model.
After creating the custom events and alarms, do the following:
1. Log into OneClick as an ADMIN user
2. Launch the Condition Correlation Editor by selecting Tools -> Utilities -> Condition Correlation Editor
3. Click on the Condition tab and create a condition for each event.
a. For the event generated on the interface model, configure a Model Attribute Parameter for the Device_Mdl_Handle attribute id 0x10069. The Device_Mdl_Handle attribute on the interface model contains the model handle of it's associated device model. See example below:
b. For the event generated on the device model, configure a Model Attribute Parameter for the Model_Handle attribute id 0x129fa. See example below:
4. Click on the Rules tab and create a new rule. In the new rule:
a. Enter a Rule Name
b. Select both the interface and device conditions in the Symptom Conditions(s) section
c. Select Caused By for the Relationship
d. Select the interface condition in the Root Cause Condition section
e. Click on the Show Advanced button
f. Click on the Parameter tab
g. In the Left Operand section of the Parameter tab, select the interface condition for the Condition field and Device Mdl Handle for the parameter field
h. Select Equal To for the Operator field in the Parameter tab
i. In the Right Operand section of the Parameter tab, select the device condition for the Condition field and Model Handle for the parameter field
j. Click on the Insert Criterion button to add the rule criteria
5. Click on the OK button to save
5. Click on the Policies tab, create a new policy and add the rule created in step 4
6. Click on the Domains tab, create a new domain, add the policy created in step 5 and add the device and interface models as resources
The next time the interface alarm is asserted and the device alarm is asserted on it's associated device model at the same time, the interface alarm will be the primary alarm while the device alarm will become a symptomatic alarm seen in the Symptoms subview of the Impact tab when the interface alarm is selected.
Please reference the "Condition Correlation" section of the documentation for more information.