This provides some information as to how a maintenance schedule works.
Via USM/OC a maintenance schedule is created.
This adds an entry to the table-> MAINTENANCE_SCHEDULE
A start and end time is added which updates-> MAINTENANCE_WINDOW
Systems are added to the schedule.
CM_COMPUTER_SYSTEM is queried to obtain the system cs_id.
Then the schedule_id and cs_id is added to-> MAINTENANCE_SCHEDULE_MEMBERS
The maintenance_mode probe keeps a list of the systems currently in and soon to be in, an active maintenance schedule.
Every 10 minutes nas requests the list and suppresses alarms for all the devices in an active schedule.
The maintenance_mode log will contain the list of schedule_ids it is working on and the dev_id for the systems in the schedule.
startDate for scheduleId 2029 2017-06-15 15:25:00.003
Device Id D1DA873894D27281FC069128205E2C926 is in an active window
Device Id D84d2a64fc279661c3ab49e92f33afd20 is in an active window
nas log (at loglevel 3)
nas: maint: dev_id 'D2C889FEFFBA9DB9E6047ED9DBD251F02' from 'subscriber' '18.104.22.168' IS in maintenance, alarm is ignored.
How to run a query to show devices in maintenance mode
Cleaning up USM Maintenance Schedules
Article Id: 106216
How to enable remote/secondary NAS probes to access the maintenance_mode probe on the primary hub?
Article Id: 34614
UIM 20.3 Offers Enhanced Maintenance Mode Scheduling in Operator Console - YouTube