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

---

Install and set up the monitoring server on clusternode1

You may install only one installation of IBM Tivoli Monitoring on a Windows computer. The installation on the shared disk removes any Tivoli Monitoring V6.x component that was previously installed locally on the node. Previously installed components are removed because the installation directory changed from the local disk to the shared disk. Therefore, you must make sure that no Tivoli Monitoring 6.x component is installed locally before you start the setup.

Before installing the monitoring server, complete the following prerequisite steps:

• If necessary, uninstall IBM Tivoli Monitoring, remove all related registry settings, Tivoli Enterprise Portal Server and Warehouse ODBC data sources, and all IBM Tivoli Monitoring users.

• Within the Failover Cluster Manager, move resources to the IVTCS003 node (Node 1) by right-clicking on HUBTems group and choosing Move Group.

• Before installing or configuring any components in a Microsoft Cluster environment, all other components that are already added to resource groups on this cluster should be offline. This precautionary measure prevents conflicts between the cluster management tool and the Tivoli Monitoring MTEMS tool. Within the Failover Cluster Manager, stop cluster service after right-clicking on IVTCS004 (Node 2).

Procedure

1. Start the installation using the setup.exe command. After the Welcome to Tivoli Monitoring window, the InstallShield Wizard displays the Software License agreement.

2. Click Accept to accept the Software License agreement. The window to specify the destination folder is displayed.

   Figure 1. Specifying a destination folder

3. Install Tivoli Monitoring on the shared disk (the default is R:\IBM\ITM, but you can specify a different folder).

4. Click Next after you specify a destination folder. The window to specify features you want to install is displayed. Select only Tivoli Enterprise Monitoring Server - TEMS. Additional features are selected automatically.

   Figure 2. Starting the IBM Tivoli Monitoring InstallShield Wizard

5. Provide the User data Encryption Key and perform a typical setup with application support for the agents you need. The TEPS Desktop and Browser Signon ID and Password window is displayed.

   Figure 3. Specifying the TEPS Desktop and Browser Signon ID and Password

6. The setup prompts you for the monitoring server name. The monitoring server name is not the host name, so you can choose your preferred hub Tivoli Enterprise Monitoring Server name. Avoid using the node name as the Tivoli Enterprise Monitoring Server name because Tivoli Enterprise Monitoring Server will be running on both nodes of the cluster.

   Figure 4. Specifying the Tivoli Enterprise Monitoring Server name

7. When the setup window prompts you for the host name of the monitoring server, type in the virtual host name that you just created and brought online as part of the cluster resources setup. In this case, the virtual host name is IVTCS005.

8. Select OK when the following warning message displays.

   Figure 5. Incorrect value for the Hub TEMS configuration

   To complete the setup, the monitoring server starts up and loads the selected application support.

9. When the setup is complete, open the Manage Tivoli Enterprise Services tool. Then, stop the monitoring server and switch the startup to manual. Changing the monitoring server startup to manual is required because the cluster must handle the startup and shutdown processes of the monitoring server.

What to do next

To prepare for the next step (which requires a restart of clusternode1), stop cluster service for clusternode2 to prevent Microsoft Cluster Server from moving the resource to the clusternode2.

1. Right-click the monitoring server again. Select Advanced, and then select Set Network Interface.

2. Set the network interface to the virtual host name. In this example, the virtual host name is IVTCS005.

3. Run regedit.exe. Navigate to the following directory:

   HKEY_Local_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

   The key

   KDEB_INTERFACELIST

   must specify IVTCS005.

   The registry replication entries might not be identical to the ones in this document.

   This setting affects all components installed on the same computer (node).

   Although the monitoring server is configured to use the virtual host name, the monitoring server logs are named after each specific node in the cluster.

4. Restart machine IVTCS003.

5. When the computer is back online, make sure that the cluster resources are still active on clusternode1. Then, start cluster service on clusternode2.

Parent topic:

Set up the hub monitoring server in a Microsoft Cluster Server

---

+

Search Tips   |   Advanced Search