Alarms do not replicate from the Nas probe in the secondary hub to the primary hub Nas

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Alarms do not replicate from the Nas probe in the secondary hub to the primary hub Nas 
Not receiving any alarms from the secondary hub to the primary after hub restart

Environment

Release :UIM 20.x

Component :HUB, Nas

Resolution

The value of alarm_enrichment queue in the Hub probe is set by the value of the enrichment_subject in the nas.cfg.

Renaming the alarm_enrichment queue on the hub probe will be reverted every time the hub is restarted, the value has to be set from the nas.cfg.

Please do the following:
 

1. From IM select the Primary hub, then nas probe then raw configure.
2. Select the setup section then edit enrichment_subject key and change it to alarm
   
   
3. apply the change.
4. restart the primary hub 
5. Once the primary hub with all the probes have port and pid, check the alarm_enrichment queue in the Hub probe and it should have alarm_enrichment set to alarm

Additional Information

in rare cases the change reverts back to alarm1 so, please do the below:

1. Open nas probe in Raw Configure.
Please change value of "enrichment_subject" key (in setup section) from "alarm1" to "alarm", and save the change.

2. Deactivate trellis probe, delete trellis probe and rename probe folder (<UIM>/probes/service/trellis)

3. Deploy trellis probe to the Primary UIM hub and activate trellis probe.

4. Open hub probe GUI in the Primary hub, go to [Queues] tab, highlight alarm_enrichment queue, delete the queue and save it.

5. restart the hub

 

Note: The Trellis probe is valid till DX UIM 20.4 CU5. From DX UIM 20.4 CU6, the alarm routing probe is introduced as an independent probe. It does not depend on Trellis to access NAS and EMS.
For more information, see Alarm Routing Service.