Duplicated alarm coming from celerra / clariion probe

Document ID : KB000043732
Last Modified Date : 31/08/2018
Show Technical Document Details
Introduction:

Problem:

Duplicated alarm coming from celerra / clariion probe.

 

Environment:

celerra / clariion 2.X running in under secondary HUB (You may describe it so many words such as Territory HUB, Location HUB, organizational HUB, Tenant HUB, etc)

 

The secondary HUB has attach queue where subject subscription criteria is “*” (asterisk)

The queue is used to forward the data into Upstream HUB.

01.png

 

Instructions:
Cause:

The issue is caused by multiple baseline_engine instance publishing the same alarm by having the same static threshold configuration.
When you define a monitor with static alarm threshold through Admin Console, static threshold configuration is being sent as “BASELINE_CONFIG” subject so that baseline_engine is able to acknowledge.
03.png
04.png
06.png
05.png
However, in this senario “BASELINE_CONFIG” subject is supposed to be acknowledged by the secondary  baseline_engine within the same HUB, and should not be acknowledged by the other instance of baseline_engine in the other HUB.
 
Workaround:
Deactivate baseline_engine in Upstream HUB if possible.
 
Resolution:
Describe necessary subjects explicitly in the attach queue in the secondary HUB.
 
Example
Subject = QOS_MESSAGE,QOS_DEFINITION,alarm,probe_discovery
02.png
 
Additional Information:  


Please have a look at Where does UIM store static threshold configuration ? as well.