SNMPCollector alarms appear delayed

book

Article ID: 191857

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Infrastructure Management

Issue/Introduction

The snmpcollector 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 about an hour behind.

Environment

Release : 20.1

Component : UIM - SNMPCOLLECTOR

Resolution

Reset the nas/clear out the existing alarms where  the delay occurred...

Re-enable the baseline_engine queue.

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.