Using IM, a device was placed into maintenance but it could not be cancelled.
- Type of maintenance being used (Legacy (controller) versus USM
There are two types of maintenance mode.
The first type is the "older" legacy kind of maintenance, and it is accessed in the Infrastructure Manager, and puts the robot itself into a 'maintenance mode' status. This mode actually suspends the probes on the robot and this stops QOS. This type of maintenance has nothing to do with maintenance_mode probe at all. Normally you can select the Status Tab within the controller probe and rt-click on the status icon and select "Leave suspend mode now" or rt-click on the Hub in the IM and select Maintenance then "Leave maintenance now"
The second type is the maintenance mode in UMP. The design of this type of maintenance mode is only to suppress alarms related to the host which is in maintenance. Infrastructure Manager does not "know about" this type of maintenance and there is no functionality in IM to reflect robots which are in this type of maintenance status.
Note that you can run the following query which will tell you what robots/devices are currently in maintenance from UMP's (USM) perspective:
select distinct cs.name, cs.ip, cs.origin, ms.SCHEDULE_NAME, ms.DESCRIPTION, CONVERT(VARCHAR(50), mw.START_TIME,100) as 'Start Time', CONVERT(VARCHAR(50), mw.END_TIME, 100) as 'End Time' from CM_COMPUTER_SYSTEM cs
INNER JOIN MAINTENANCE_SCHEDULE_MEMBERS msm
INNER JOIN MAINTENANCE_WINDOW mw
INNER JOIN MAINTENANCE_SCHEDULE ms
WHERE mw.END_TIME >=GETDATE()
We recommend using UMP (USM) maintenance mode not the legacy type that relies upon the controller.