Some devices are showing up as in maintenance mode in OneClick even though the device is not a part of the maintenance schedule:
The issue started after the SpectroSERVER SSdb was restored and the SpectroSERVER restarted.
DX NetOps Spectrum all currently supported releases
This is most likely due to inconsistency in model attributes (isManaged or In_Maintenance) or corruption of maintenance schedule pointers after the DB restore and SpectroSERVER restart.
When isManaged is set to Yes (1 or True), Spectrum actively polls the device and processes its alarms. When set to No (0 or False), the device is immediately placed into Maintenance Mode.
Restart the OneClick server.
Ideally, once the SSDB is restored and initialized completely, then a restart of the Spectrum tomcat (OneClick server) service should be done to flush out the cache and eliminate inconsistencies between the old SpectroSERVER landscape instance and the new one with restored SSdb