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

---

Set up basic cluster resources

For hub monitoring server installation and setup on a Microsoft Cluster Server, the following four resources are necessary:

• Shared disk R: You can assign a different drive letter for the shared disk.

• IP address: Must be a valid domain name system registered IP, using static IP.

• Host name: Must be a valid domain name system registered host name with the IP above.

• Hub monitoring server: Contains all required information.

These resources might have already been created by your cluster administrator. If they are not created in your environment, complete the following steps to create these resources.

In the test environment, Windows Server 2008 R2 Enterprise 64-bit was used. Each cluster was set up with a single quorum device and two nodes.

To set up of the basic cluster resources, start with clusternode1:

1. Start the Cluster Administrator and connect it to the cluster that you are working in. Make sure that the cluster is running on clusternode1.

   By default, the Cluster Administrator contains a Cluster Group (for internal cluster setup), and a Group 0. Use Group 0 as the resource group for IBM Tivoli Monitoring. The Cluster Group contains a Cluster Name (in this case, IVTCS001), which is used for follow on configurations.

   The disk R is by default held in “Group 0”. You can now rename this group according to your needs. In the testing environment, it was renamed to HUBTems. You can also create a new group and then move this shared disk into that new group.

   Do not put any Tivoli Monitoring related resources into the default group named Cluster Group, which contains Cluster IP, Name, and the quorum disk.

   The shared disk resource has been set, and set the IP address and the host name. You define the hub monitoring server service after the installation process.

2. To set up the resource for the IP address, complete these steps:

   1. In the left-hand pane of the Failover Cluster Manager, right-click Services and applications, click More actions > Create Empty service or application.

   2. Right-click new service or application.

   3. Select Add a resource > More resources... > Add IP Address and then specify the name you want, as shown in Figure 1:

      Figure 1. Specify the resource name and virtual IP address

   4. Specify the dependencies. Ensure that the shared disk is available before anything else, so you can specify the shared disk R as the dependency for the IP Address.

      Right-click on the New Service or Application, and seleect Add Storage.

      Figure 2. Specify the resources that must be brought online before this resource can be brought online

   5. Select both of the node names in the Possible Owners window:

      Figure 3. Specification of Possible Owners

      Node names are selected as possible owners by default.

   6. Specify the virtual IP Address to be used for the hub TEMS cluster.

      The Cluster IP Address is the virtual IP Address. If a virtual IP Address already exists, this address is the cluster name.

   7. Click Finish.

      The following message is displayed: Cluster resource "TEMS IP" created successfully

3. Right-click this resource and then click Bring Online, as shown in Figure 4:

   Figure 4. Cluster Administrator before Bring Online function

4. Create the resource for the network name, by following a similar procedure. The only difference is that you select the Client Access Point resource type when you add a resource in the Failover Cluster Manager. In the test environment, the Network Name is IVTCS007.

   Figure 5. Create the resource for the network name

5. Follow the prompts to create a virtual host name for your virtual IP address. The dependencies are the disk R and the IP address. Also bring this host name online. Test the virtual host name by pinging it from another computer.

   Figure 6. Specify the dependencies of the Client Access Point

6. Create the Tivoli Monitoring default user ID sysadmin as a local user on the first and on the second node of the cluster.

You are now ready to install the monitoring server.

Parent topic:

Set up the hub monitoring server in a Microsoft Cluster Server

---

+

Search Tips   |   Advanced Search