SNMPCollector alarms appear delayed

Products

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

Issue/Introduction

The snmpcollector (pollagent) probe is backed up and the Time Received Column is showing the alarm was received at for example 6:25 AM but the Time Origin is showing 5:27 AM. So it seems our alarms are backed up now and cant be caught up since we ran the callback-> Apply template for the snmpcollector. Alarms are delayed and about an hour behind.

Environment

Release : 20.1

Component : UIM - SNMPCOLLECTOR

Resolution

In some cases, you may find that the baseline_engine.QOS_MESSAGE queue is simply backed up.  If that is the case, just empty the queue and then restart the baseline_engine and then check if "Time Origin" and "Time Arrival" are accurate or close to accurate (no delays).

Otherwise, reset the nas/clear out the existing alarms where  the delay occurred...

Make sure the baseline_engine queue is green and processing messages..

Check the hub->Status Tab to make sure the baseline_engine QOS messages are flowing to the Primary hub and being processed via the GET queue there.

Then do the following:

1. Deactivate the 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 nas probe

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