IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > High Availability Guide for Distributed Systems > The clustering of IBM Tivoli Monitoring components > What to expect from the IBM Tivoli Monitoring infrastructure in a clustered environment
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Maintenance
The maintenance requirements of a Tivoli Monitoring environment (patches, fix packs, or release upgrades) when running in a cluster resemble those of running an unclustered Tivoli Monitoring environment. The cluster controls the starting and stopping of Tivoli Monitoring services. To return this control to the installation procedure, stop the cluster while the maintenance is being performed. Also, due to current restrictions of the Tivoli Monitoring installation procedures, some settings that are completed during Tivoli Monitoring cluster setup might need to be repeated after the maintenance is completed and before the cluster is restarted.
In a Tivoli System Automation for Multiplatform environment, you will need to switch off the automatic clustering when upgrading your environment. By switching off the clustering, you prevent the components, stopped by the installer, from restarting during the upgrade. However, you must keep the basic resources online (such as VIP and shared disk).
Also, when using the UNIX or LINUX installer, you must remove the inittab entries again after maintenance. The installer adds the inittab entries again despite having been removed in the previous installation of the cluster. The failure to remove the inittab entries might cause problems in your environment.
Parent topic:
What to expect from the IBM Tivoli Monitoring infrastructure in a clustered environment