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 portal server in a Microsoft Cluster Server

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2


Test the portal server in the cluster

After you bring the resource of the portal server online, log on using the portal browser or portal client. Perform typical tasks, such as creating a situation and associating a situation.

Now, switch the portal server resource group to clusternode2. During the switch, you notice the typical error messages from the portal client about losing the connection. When the switch is finished, the portal client reconnects to the portal server, and you should be able to continue your activities on the client.

The registry replication of services from one cluster node to the other might not work 100% correctly. Partial registry replication of services might cause the resource not to come up after switching to the second node.

In this case, verify that the service is visible in the services on the second computer.

If not, restart the computer.


Parent topic:

Set up the portal server in a Microsoft Cluster Server

+

Search Tips   |   Advanced Search