maintenance_mode Release Notes

The maintenance_mode probe sets user-specified maintenance windows for devices. During these maintenance windows, only informational and clear alarm messages are displayed during a maintenance window.
uimpga-ga
maintenance_mode_RN
The maintenance_mode probe sets user-specified maintenance windows for devices. During these maintenance windows, only informational and clear alarm messages are displayed during a maintenance window.
Contents
Revision History
This section describes the history of the revisions for the maintenance_mode probe.
Support case(s) may not be viewable to all customers.
Version
Description
State
Date
20.30
(Included in CA UIM 20.3.0)
What's New:
  • Introduced few optimizations on the register_maintenance_subscriber callback which is responsible for providing maintenance information to subscribers like NAS, EMS.
    To accomodate this change, Minimum and Maximum JVM memory utilization of the maintenance_mode have been increased to 512mb and 1024mb respectively to avoid memory issues for the probe.
Fixed Defects:
  • (9.20 HF2T1) Fixed an issue where machines in Maintenance Mode still generate Alerts. (Support Cases: 20280426, 31811590)
GA
September 2020
20.10
(Included in CA UIM 20.1.0)
What's New:
  • A new table maintenance_window_history will be created on installation/upgrade of maintenance_mode probe. Also the data from the maintenance_window will be dumped into maintenance_window_history. By default, the newly data written in the maintenance_window table will be written to maintenance_window_history table as well.
  • Introduced a new key "purge_maintenance_window_history_interval" in maintenance_mode.cfg in <setup> section which will delete expired windows from maintenance_window_history table. It is disabled by default.
    To enable it, purge_maintenance_window_history_interval (a new configuration) is to be set to a whole integer in the maintenance mode probe configuration under setup (for example, 1, which means the task would run every one hour). If the task is run, all the expired maintenance window entries would get deleted. To disable the task, it has to be reset to -1. (Support Case: 01302475)
Fixed Defects:
  • (9.02 HF4) Fixed an issue where spectrumgtw syncing of the maintenance schedules was causing sluggish UMP performance. (Support Case: 20042333)
  • (9.10 HF1 and 9.20 HF1) Fixed an issue in which users were getting duplicate maintenance schedules after Spectrum integration. (Support Case: 20045094)
  • Fixed an issue related to the unknown error when deleting robot from maintenance schedule. (Support Case: 20047617)
  • Fixed an issue with spectrumgtw syncing of maintenance schedules causing sluggish ump performance. (Support Case: 20042333)
  • Fixed an issue with the UMP Maintenance Schedules at wrong day/time. (Support Case: 1278720)
  • Fixed an issue with USM which throws an error when removing device from maintenance schedule. (Support Case: 20109406)
  • Fixed an issue where UIM is impacting Spectrum causing memory issues with model creations/deletions. (Support Case: 20046860)
  • A new background task is added which handles the maintenance schedules by adjusting the time. It is scheduled to run on startup and every 24 hrs by default, the time interval is configurable. To change the time interval, "handle_dst_interval" key should be set under the setup section. As an example, In order to schedule the task to run every 24 hrs, set as: "handle_dst_interval=24" (Support Case: 20280779,20094790,20098531
GA
March 2020
9.20
(Included in CA UIM 9 SP1)
What's New:
  • Fixed an issue in which the maintenance schedules in USM were not appearing as expected. Sometimes, they were not showing up, and then they would randomly show up without doing anything. (Support Case: 01236634)
  • Fixed an issue in which the maintenance_mode probe version 9.02 package was not available in Nimsoft archive. (Support Case: 01294815)
  • Fixed an issue in which USM performance issues were occurring because of the growth of the maintenance_window table. The maintenance_window table was growing excessively and when there were more than 2000 rows in it, USM performance was affected. (Support Case: 01184935)
  • (9.02 HF3) Fixed an issue in which while editing a maintenance schedule in UMP, users were receiving the following error. Even refreshing the browser did not solve the issue. This issue started occurring after users upgraded from CA UIM 8.51 to CA UIM 9.0.2: (Support Case: 01324224)
    An unknown error has occurred.
    Refreshing your browser may resolve the issue.
  • Fixed an issue in which after upgrading to CA UIM 9.0.2, users started viewing various errors in the maintenance_mode log and the CPU usage also was very high. (Support Case: 01302475)
  • CA UIM 9.2.0 has adopted OpenJDK 8u212 instead of Oracle JDK. Because of this change, CA UIM 9 SP1 (9.1.0) that was using Oracle JDK (JRE) 8u212 is no longer available and has been removed from the Support site. All the functionality that was included in 9.1.0 is now released as part of CA UIM 9.2.0. Consequently, all references to the 9.1.0 release and the probe version 9.10 (released with it) have also been removed from this probe documentation. We recommend that you move to this version 9.20 of this probe, as the previous version 9.10 is no longer available now. For more information about the OpenJDK usage in CA UIM, see Adopting OpenJDK.
GA
August 2019
9.02
What's New:
  • Updated this probe as part of addressing CVE-2018-13820 and CVE-2018-13819 vulnerabilities in CA UIM 9.0.2.
  • Updated this probe as part of removing known security vulnerabilities in CA UIM 9.0.2 by using the upgraded MariaDB components.
  • Updated this probe as part of supporting TLS v1.2 in CA UIM for establishing secure communication with the UIM databases: Microsoft SQL Server and Oracle. For more information about how to enable TLS v1.2 support in CA UIM, see TLS v1.2 Support for Microsoft SQL Server and TLS v1.2 Support for Oracle.
Fixed Defects:
  • After DST changes, Western Australia schedules windows is not synchronized. It still shows only 2 hours difference instead of 3. (Support Case: 00879457)
  • (8.53 HF2) Added the MAINTENANCE_WINDOW purge task, where the MAINTENANCE_WINDOW entries are purged when the corresponding MAINTENANCE_SCHEDULE is deleted. Additionally, it has a new task in the maintenance mode that deletes the expired maintenance windows, thereby improving the UMP performance. It is disabled by default. To enable the task, purge_maintenance_window_interval (a new configuration) is to be set to a whole integer in the maintenance mode probe configuration under setup (for example, 1, which means the task would run every one hour). If the task is run, all the expired maintenance window entries would get deleted. To disable the task, it has to be reset to -1.
    (Support Case: 01184935)
GA
October 2018
8.53
Fixed Defect:
  • The maintenance schedule among different servers no longer goes out of sync after incorporating Daylight Saving Time (DST) changes. (Support Case: 00245759)
GA
February 2018