Spectrum is running in a Fault Tolerant (FT) environment.
A model belongs to a Global Collection (GC) that has a Policy attached that puts the model into Maintenance Mode (MM).
The model has an underlying Critical "DEVICE LOST CONTACT" alarm.
The primary SpectroSERVER (SS) is shutdown and OneClick fails over to the secondary SS.
While OC is connected to the secondary SS, the model still has the underlying Critical "DEVICE LOST CONTACT" alarm and is still in MM.
The primary SS is started and OC falls back to the primary SS as expected.
The primary SS takes the model out of MM which causes the underlying Critical "DEVICE LOST CONTACT" alarm to be displayed in the Alarms tab of the OC.
After a while, the model is placed back into MM.
Release : Any
Component : Spectrum Core / SpectroSERVER
The model in question is a VM. The VM is placed in MM but the ESX model associated with the VM is not in MM.
There is an attribute on the UIMManager model called SetMaintenanceModeToChildren attribute id 0x633002a whose value is Yes by default.
Basically, the SetMaintenanceModeToChildren attribute id 0x633002a tells Spectrum when the ESX is placed in MM, set the VM's associated with the ESX in MM. When the ESX is taken out of MM, take the VM's associated with the ESX out of MM.
Reference the "Maintenance Mode Correlation" section of the documentation for more information.
In this scenario, the VM is in MM from the Policy on the GC but the ESX is not in MM and the value of the SetMaintenanceModeToChildren attribute id 0x633002a on the UIMManager model is set to Yes.
When starting the primary SS after a fail over to the secondary SS, the functionality of the SetMaintenanceModeToChildren attribute id 0x633002a on the UIMManager model is telling Spectrum to take the VM out of MM because the ESX is not in MM. Then, the Policy attached to the GC says to put the VM back into MM.
If this is not desired, set the SetMaintenanceModeToChildren attribute id 0x633002a on the UIMManager model to No.