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
Known problems and limitations
This section includes specific characteristics and constraints of the Tivoli Monitoring installation and setup on a Windows environment and their effects on the cluster setup.
During the certification test for Tivoli Monitoring clustering, issues encountered when setting up the clustered environment are formally reported as defects. These defects are typically related to the setup of Tivoli Monitoring in a non-default manner, instead of being specific to the cluster environment. These defects are handled as part of the Tivoli Monitoring service stream. See the following list of known problems and workarounds.
Installation-related issues:
- Tivoli Monitoring components cannot be installed in multiple installation directories in the same way that you can install them on UNIX or Linux systems. Under this limitation, every Tivoli Monitoring component must use the same cluster shared disk resource. Each component must be defined under the same cluster resource group. You cannot use more than one shared disk for the Tivoli Monitoring components.
- As a consequence of the preceding limitation, if you have a Monitoring Agent for Windows OS installed on the same computer as the clustered hub monitoring server, the OS agent must also be clustered and move together with the resource group.
- Tivoli Monitoring components on Windows operating systems are registered as services. You may have only one instance of each service on the computer. You cannot set up a clustered environment where two main hub monitoring servers use each other‘s computers as their failover hub (such as by having another instance of the hub installed and running as part of a second resource group) because you may have only one instance of the monitoring server service installed and running on a given computer.
Configuration-related issues:
- Tivoli Monitoring “Set Network Interface” capability issues:
- If you use the “Set Network Interface” function on the Tivoli Monitoring GUI to set a Network Interface for one agent (for instance, when running such an agent as part of the Tivoli Monitoring clustered resource group and assigning the virtual host name to it), the setting affects all other agents on the same node. This is the current default behavior of Tivoli Monitoring.
- Uninstall Tivoli Monitoring might not remove the KDEB_INTERFACELIST entry in registry if this has been configured. To completely remove this setting, you need to remove the following registry entry:
- HKEY_Local_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\KDEB_INTERFACELIST
- If the clustered Tivoli Enterprise Portal Server does not start after failover or switching, complete the following steps:
- Make sure Tivoli Enterprise Portal Server starts successfully on the first computer in your cluster.
- Switch to the first cluster computer.
- For Windows systems:
Change the current directory to %CANDLE_HOME%\CNPSJ\profiles\ITMProfile\config\cells\ITMCell\nodes\ITMNode
- For UNIX or Linux systems:
Change the current directory to $CANDLE_HOME/<architecture>/iw/profiles/ITMProfile/config/cells/ITMCell/nodes/ITMNode
- Locate and open the serverindex.xml file.
- Check if all "hostName" and "host" properties match the virtual host name for the Tivoli Enterprise Portal Server cluster. Correct incorrect values.
- For each unique and invalid host name found in step 5, apply steps 2–5 accordingly.
- If the Eclipse Help Server will not start on a particular node, you might need to add a dependency to the Eclipse Service on the Tivoli Enterprise Portal Server. Add the dependency in the Cluster Manager, as shown in Figure 1.
Figure 1. Adding a dependency to the Eclipse Service on the Tivoli Enterprise Portal Server
- If the DB2 resource fails to come online, review the registry entries for "DB2ADMNS" on both the nodes. The group should not be created under the local node names. Modify the value and create the group under the domain groups.
Maintenance-related issues:
- When using the "Modify" option in a Tivoli Monitoring installation to modify a running Tivoli Monitoring environment, such as adding additional agent support to the monitoring server or portal server, the processing might start Tivoli Monitoring services at the end of the change.
- When you are upgrading IBM Tivoli Monitoring, the monitoring server and the portal server might automatically start at the end of the upgrade, even when the startup of these services was set to Manual. After the upgrade, the monitoring server and portal server have to be manually stopped if they were started. Use Cluster Administrator to bring them online so that these clustered resources function in the cluster as expected.
Parent topic:
Create clusters with Tivoli Monitoring components in a Microsoft Cluster Server environment