6.8 Notes about running ITSLM in a cluster system
-
If you run ITSLM in a cluster system, you must specify restart in the managerStartMode property in the system definition file.
When you set up a logical host that is run in a cluster system, restart is set in the managerStartMode property depending on the command. After you have set up the logical host, do not change this property value to normal. If it is changed to normal, the monitoring of monitored services cannot be restarted after failover.
-
If ITSLM - UR starts, stops, or fails over while failover processing is underway on ITSLM - Manager, a start or termination notification from ITSLM - UR to ITSLM - Manager might timeout. To avoid such a timeout, we recommend that you adjust the values of the announceRetryCount and announceRetryInterval properties in the system definition file to satisfy the following condition:
announceRetryCount property value
![[Figure]](GRAPHICS/ZUENG005.GIF)
announceRetryInterval property value > amount of time in seconds required from start to completion of ITSLM - Manager failover -
Whether ITSLM is run in a physical host environment or a logical host environment is determined after ITSLM has been set up. ITSLM cannot be run in both physical and logical environments at the same time. Also, ITSLM does not support running more than one logical host at a time.
-
When the cluster environment setup is undone, database-related files might remain on the shared disk. If you do not need these files, delete them manually.
-
If you want to set up as a standby host a host that has already been set up as the active host, or vice versa, make sure that you first undo the setup and then perform the setup again. The unsetup process deletes the existing data. Therefore, before you undo the setup, export data that you need. Import the data after you have finished setting up the host.
-
When you set up logical hosts in a cluster environment, specify the same settings in the options files in both the active and standby systems.
-
If you run ITSLM in a cluster environment, do not use the JP1/Base function for controlling the order in which Windows services are started. If you want to specify the order in which the Windows services for ITSLM and JP1/Base are started and stopped, use the cluster software's function for controlling the Windows service start sequence.