Alarms are not 'in sync' between OC and Infrastructure Manager (IM)
search cancel

Alarms are not 'in sync' between OC and Infrastructure Manager (IM)

book

Article ID: 142778

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM) Unified Infrastructure Management for Mainframe

Issue/Introduction

In the OC alarm viewer, it may appear that nas alarms / total alarm counts are out of sync with the Infrastructure Manager alarm subconsole. Sometimes the local NAS database becomes 'out of sync' with the backend UIM database tables.

Environment

DX UIM 20.4.* / 23.4.*

Cause

There could be 1 or more causes including the size/integrity of the local nas .db files
 
- database.db
- transactionlog.db
 
or the nas backend database tables
 
- nas_alarms
- nas_transaction_summary
- nas_transaction_log

Resolution

In the Infrastructure Manager (IM), the alarm subconsole shows one set of alarms and OC alarm Viewer is displaying another set of alarms and/pr the total alarm count is NOT the same or not close.

First, create a Group with a filter of:

'not ip address is null'

Save it, then select the top-level ‘Groups’ icon and click on the Alarms tab to see if the alarm counts are now closer between the nas and IM alarm subconsole.


 
If the alarm count is not the same or at least close, then take the following steps.

 

1. Deactivate the alarm_enrichment and nas probe

2. Drop the nas tables listed below from database using SQL Management studio 
 
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
 
3. Activate the alarm_enrichment, then the nas probe

When you activate the nas, it should recreate all of the tables and sync them properly with the existing alarms that appear in IM.



If this does not resolve the issue, it is possible that the local NAS database files have become corrupted.   If that is the case, you can take the following steps:

1. Deactivate the alarm_enrichment and nas probe

2. Drop the nas tables listed below.
 
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;
 
3. Rename the following files in the <nimsoft>\probes\service\nas directory to something like .db.old in order to preserve them while setting them aside.
 
    - transactionlog.db
    - database.db
    - nisQueue.db (if it exists)
 

4. Activate the alarm_enrichment and then the nas probe


When you activate the nas, it should recreate those two files, and all of the tables and sync them properly.

IMPORTANT NOTE:

Renaming the .db files above will cause the complete "reset" of all alarms in the environment.  So, if you have integrated your NAS with external systems/ticketing systems/etc. please be aware that on the next polling cycle, all of the previously alarms which are still active will come in again, which could cause new/duplicate tickets to be created.  Please be aware of this and take steps to mitigate (such as temporarily disabling such integrations until the alarms regenerate.)

Additional Information

Powered by Wolken Software