search cancel

Service Manager alarms are not updating in the Service Manager tables


Article ID: 214679


Updated On:


CA Spectrum


We have noticed that Service Manager data that is used to create monthly availability reports are not being updated.  When checking the Service Manager Dashboard we can see that the Service Manager data is not being updated on a single SpectroSERVER landscape in a DSS enivornment.


Release : 20.2

Component : Spectrum Service Manager


Processing between the SpectroSERVER and OneClick server hangs after an intermittent network disruption.  This caused the processing of the Service Manager tables not to be processed.


It appears that there was a network disruption between the OneClick server and the SpectroSERVER that stopped the Service Manager tables from being updated.  Once both the SpectroSERVER and OneClick server were restarted, the data was resumed and the reports showed correctly.

Additional Information

All the SRM and Service Manager tables are part of reporting database.  The SpectroSERVER will monitor all the service/resource status including service policy rules.
Whenever any change in resource happens it will send events to the corresponding OneClick server for updating the database.
Although the entire intelligence is with SpectroSERVER, the database is remotely updated with the OneClick server
Once the database has been updated,  the OneClick view / Service Dashboard will be notified to read the latest database and show the updated values.
The main reason for this architecture to make OneClick responsible is that we can have a multiple service hierarchy. Once the leaf level service is updated by OneClick, then from the database it reads it's parent services and decides whether it needs to be updated or not
This way SpectroSERVER will be left with core processing and the time consuming database operation will given to OneClick server.