IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > High Availability Guide for Distributed Systems > Create clusters with Tivoli Monitoring components in a Microsoft Cluster Server environment
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Upgrade IBM Tivoli Monitoring in a Microsoft Cluster environment
Before upgrading IBM Tivoli Monitoring within a Microsoft Cluster, the following steps need to be completed to return IBM Tivoli Monitoring to a pre-cluster configuration. Failure to do these steps might cause the upgrade of IBM Tivoli Monitoring to hang or fail. After the upgrade completes, the resources should be checked to verify that they connect to the cluster resources and not to the installation node resources.
In the following procedure, ITM_Home refers to the location where IBM Tivoli Monitoring was installed. This path is usually C:\IBM\ITM. The path can be the same, but the drive letter is usually a Shared Disk seen by all members of the cluster. For the installation example, drive R: is used. So in the following steps R:\IBM\ITM replaces ITM_Home.
- Ensure that the upgrade is done from the cluster node where IBM Tivoli Monitoring was originally installed.
- Delete the ITM_Home\CNPSJ\itmEwasRegistry.properties file.
- Delete the ITM_Home\CNPS\profiles\ITMProfile directory.
- Clear the ITM_Home\logs directory (remove all files).
- Modify the ITM_Home\CNPSJ\properties\profileRegistry.xml file to remove the data between the <profiles> and </profiles> statement.
- Run the upgrade.
- After the upgrade completes, change the host name for eWas from the installation cluster host name to the cluster resource host name. You must complete this change before the cluster can be switched from the installation computer another member of the cluster. Run the updateTEPSEHostname command in the ITM_Home\CNPSJ\scripts directory to perform the rename. The syntax is as follows:
updateTEPSEHostname oldname newname
- Verify the post installation information to validate that Tivoli Enterprise Monitoring Server and monitoring agents are configured correctly to connect to the cluster resource.
- Test the cluster failover scenarios.
Parent topic:
Create clusters with Tivoli Monitoring components in a Microsoft Cluster Server environment