Why persistent alarms are re-generated, losing Acknowledged, Trouble Ticket ID, Assignment, and Status info
Article ID: 208735
Updated On:
Products
Issue/Introduction
After I started back the SpectroSERVER application, all the existing alarms with Acknowledged, Assignment, Trouble Ticked ID, and Status information are lost, because new alarms were generated, even though they are persistent alarms.
Based on the following section of the Spectrum guide, the alarm information such as Acknowledged, Assignment, Trouble Ticked ID, and Status information should be retained.
Specify Alarm Options
You can specify the following advanced options for an alarm:
Alarm is Persistent
If this option is selected, the alarm is retained in memory, in case the SpectroSERVER is shut down and restarted.
Stopped the SpectroSERVER and Archive Manager via SCP:
The OneClick lost contact with the SpectroSERVER and Archive Manager:
Started the SpectroSERVER and Archive Manager via SCP:
The Acknowledged, Assignment, Trouble Ticked ID, and Status information are still available after SpectroSERVER shutdown and restart:
Environment
Release : 10.x
Component : Spectrum Core / SpectroSERVER
Cause
The SSdb database was restored. The ssEvents.db, ssEvents.ix, ssAlarms.db, and ssAlarms.ix files are not saved in the SSdb backup.
Resolution
One possible workaround would be making a backup of the ssAlarms.db and ssAlarms.ix files from the $SPECROOT/SS/ directory before the SSdb restore, while the SpectroSERVER is down.
Once the SSdb restore has finished, copy back the ssAlarms.db and ssAlarms.ix files.
Another option would be establishing a Fault-Tolerant Environment.
Please read the following section of the Spectrum guide about SpectroSERVER Alarm Synchronization:
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/spectrum/10-4-3/administrating/distributed-spectroserver-administration/spectroserver-alarm-synchronization.html
Additional Information
Feedback
