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 > Set up the hub monitoring server in a Microsoft Cluster Server
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Test the monitoring server on clusternode2
Procedure
- While clusternode2 is online, check that the TEMS1 service, Tivoli Enterprise Monitoring Svcs – TEMS1, is listed on Windows Services. If it is, then the monitoring server on clusternode2 is ready.
If the service is not listed on Windows Services, then check whether the correct registry entries are replicated. If the registry entries are not replicated, you must force replication to occur by completing the following steps:
- On clusternode1, in Cluster Administrator:
- Right-click on the TEMS resource group.
- Select Move Group.
This Move Group fails and the cluster is back on clusternode1 again.
- You can restart clusternode2 for the registry entries to take effect.
When clusternode2 is available again, it is ready.
- On clusternode1, in Cluster Administrator:
- Right-click on the TEMS resource group.
- Select Move Group.
The Cluster Resources on the “HUBTems” resource group start the failover: the lower resource in the dependency goes off line first (and then the others in order). Next, one by one, the resources are available online on clusternode2.
- You can test the monitoring server on clusternode2 using the same method you used on clusternode1.
- To see the monitoring server on the Manage Tivoli Monitoring Services GUI, start it on clusternode2 by running the following command:
R:\IBM\ITM\InstallITM\kinconfig.exe
Parent topic:
Set up the hub monitoring server in a Microsoft Cluster Server