Operator Console (OC) alarm count is not updating in DX UIM

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We have noticed that the time and count of alarms in OC are not getting updated as they should. As mentioned in the KB34697 I have set the supp_divisor to a certain value, but OC isn't respecting it.

Environment

DX UIM 20.4.* / 23.4.*

Cause

New key enabled by default in NAS 9.2 and later

Resolution

For improving OC performance NAS 9.2 introduces a new key.

The new is called "nis_update_skip_factor = 100"

(by default it comes with value 100)

This configuration forces the NAS_ALARMS in the UIM DB (the alarms that show in USM/OC) to update every 100 occurrences, even if the local alarms (database.db - the alarms that show in IM) are increasing the count at higher rate count as determined by the Example: supp_divisor = 1" key.  (at every occurreance of the same alarm). 

The "nis_update_skip_factor equals to 100 makes identical suppressed alarms to update in USM every 100 occurrences.

To disable this new configuration key please set it to "nis_update_skip_factor = 0"

When disabling the function, USM alarms will update the count following the supp_divisor key, as described in KB34697

Below a summary of what each key corresponds to in the NAS GUI and what it does:

NAS GENERAL Tab:

Publish alarm updates every " " duplicate messages

KEY: [supp_divisor = 20]

This value determines how often the 'suppcount' is updated in the NAS_ALARMS table in the database.db.
The first alarm has a value of '0'. This reflects in the IM alarm subconsole "count" value for each alarm. The first alarm will show in IM alarm details as Count = "1"
If supp_divisor =1 , at EVERY identical alarm, the count increases.
If supp_divisor =20 the 'suppcount' in the database.db and the "count" in IM will increase only once you receive the 21st suppressed alarm


NAS TRANSACTION-LOG tab:

Log alarm updates every " " duplicate messages

KEY: transactionlog_divisor = 20

This value determines how often the 'suppcount' is updated in the NAS_TRANSACTION_SUMMARY table in the transactionlog.db.

If transactionlog_divisor=1 , at EVERY alarm, the count increases.
If transactionlog_divisor =20 the 'suppcount' in the database.db will increase only once you receive the 21st suppressed alarm


NEW KEY IN NAS 9.2

KEY: nis_update_skip_factor
This key will do the same as supp_divisor does but in the UIM DB NAS_ALARMS table.

If nis_update_skip_factor=1 , at EVERY alarm, the count increases in UIM DB NAS_ALARMS table and so, count in USM/OC.
If nis_update_skip_factor=0 this new key is DISABLED meaning that behavior will be the same as before NAS 9.20
If nis_update_skip_factor=20 the 'suppcount' in the NAS_ALARMS in the UIM DB will increase only once you receive the 21st suppressed alarm

Additional Information

Where are the alarms stored in DX UIM?

Time related fields in the NAS_* alarm tables (broadcom.com)

What is the meaning of the of nas alarm Subjects?

Some Alarms' "count" increase immediately while others don't even when the alarms are suppressed