In UMP USM, it may appear that nas alarms/total alarm counts are out of sync with the Infrastructure Manager alarm subconsole/Nimsoft SLM database. Sometimes the local NAS database can get out of sync with the backend database.
In the Infrastructure Manager, the alarm subconsole shows one set of alarms and USM is displaying another set of alarms and/or the total alarm Count is NOT the same or even close.
Please be advised that USM only shows alarms for those systems that belong to a group. If you have systems that are not in a GROUP then these alarms will not show and this Article may not apply.
First, to verify all systems are present in a group, in USM create a Dynamic group containing all systems with the following filter:
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 very close, then take the following stepsin the Solution.
NAS 4.7x or later
1) there is a problem with the local *.db files in the nas probe directory
2) there is a problem with the indexes on the back table to the nas_alarms and
1. Deactivate the nas probe
2. Drop the nas tables
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
DROP TABLE NAS_CS_STATE_MONITOR
3. Remove the following files from the <nimsoft>\probes\service\nas directory
4. Activate the nas probe
When you activate the nas, it should recreate all of the tables and sync them properly.
Some DROP commands may fail if the tables don't exist anymore so you can ignore that as some tables may have changed depending on the Nimsoft/nas version you’re running.
Note that in the nas GUI there are two tabs "Transaction Log" and "NiS Bridge" which independently set the alarm data retention rates for the tables. The "Transaction Log" tab sets the retention for the SQLite database. IF this is set lower than the retention in "NiS Bridge" then you will see less alarms... for example if the transaction log is set to 30 days but NiS Bridge is set to 90 days, when you drop the tables and re-sync, it will only be able to sync back 30 days of alarms because that's all that will be retained in the SQLite database.
Keywords: NAS sync Out of sync USM Alarms NAS Alarms nas nas_alarms alarms alarm count counts nas databases UMP USM Unified Service Manager subconsole off not same