USM shows duplicated alarms instances in the alarm history

Document ID : KB000009312
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

The USM alarm history (Show Historic), for a particular alarm, is showing duplicated instance of the same instance of the same suppressed alarm. I see 2 entries at the same time for the same alarm instance inside the USM alarm history. Looking at the NAS_TRANSACTION_LOG duplicated rows exist for the same instance (same time/same nimid).

 

Environment:
UIM 8.x
Cause:

This issue can be caused by NIS-Bridge enabled on a secondary nas. 

Only the primary nas (the nas probe deployed by the UIM instance on the primary hub) supports having the NIS-Bridge enabled.

 

Resolution:

Check if you have any secondary nas with the nis_bridge enabled:

In the nas.cfg see if you have these entries:

 

   nis_bridge = yes

   nis_trans_details = yes

 

If you do, and if the they set to "yes", most likely this is why the issue is occurring.

 

To resolve this:

 

1. deactivate the primary nas

2. deactivate the secondary nas

3. in the secondary nas, using raw configure, set these the 2 keys to "no" (or delete the entire sections):

 

From:

 

   nis_bridge = yes

   nis_trans_details = yes

 

To:

 

   nis_bridge = no

   nis_trans_details = no

 

4. Execute the following drop queries*:

 

DROP TABLE NAS_VERSION 
DROP TABLE NAS_ALARMS 
DROP TABLE NAS_TRANSACTION_SUMMARY 
DROP TABLE NAS_TRANSACTION_LOG 
DROP TABLE NAS_NOTES 
DROP TABLE NAS_ALARM_NOTE 

5. activate the primary nas

6. activate the secondary nas

 

*this step is required for the table to be repopulated correctly. By applying this procedure no alarm will be lost. The Alarms are stored in the nas.db (open alarms) and database.db (closed alarms) in the primary hub nas folder -- they are replicated to the NAS_x tables in the nis Database (the nas nis-bridge does this). If we DROP those tables, and restart the nas, it will rebuild the replica of the open and closed alarms from the SQLlite db files to the nis DB.

Additional Information:

I am getting duplicate alarms in USM and my alarm counts between USM and IM are mismatched.

https://support.ca.com/us/knowledge-base-articles.TEC1981917.html