search cancel

Alarm Occurrence count increment in CA Spectrum after fail-over between primary & secondary SpectroSERVERs then back again


Article ID: 200164


Updated On:


CA Spectrum CA eHealth


During a fail-over from primary SpectroSERVER to secondary, where the alarm is first raised and then when the primary is back up and running again, the alarm occurrence count is incremented. Does this mean that there is a duplicate of alarms between primary and secondary?


Spectrum 10.x and later


The original alarm is transferred to the secondary SpectroSERVER or raised there in the first instance. When the primary comes back up, a new alarm is asserted, but we do recognize it was originally there on the secondary so we increase the occurrences and use a new time stamp.

This is normal as-designed behaviour.