IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > High Availability Guide for Distributed Systems > Create clusters with monitoring components in a System Automation for Multiplatforms environment

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Create a cluster with all Tivoli Monitoring Components


In the case of a demo or proof of concept, you might want to create a cluster that contains the four IBM Tivoli Monitoring components on one system. This is not recommended for a production environment. To accomplish this, complete the steps in the following table:


Creating a cluster containing all four IBM Tivoli Monitoring components

Task Section in this document
1. Build a base cluster including DB2 Set up a cluster for Tivoli Monitoring
2. Install and set up the monitoring server Install the monitoring server on its base Tivoli System Automation for Multiplatforms cluster
3. Install and set up the portal server Install the portal server on the Tivoli System Automation for Multiplatforms cluster
4. Install and set up the Warehouse Proxy Agent Install the Warehouse Proxy Agent on a Tivoli System Automation for Multiplatforms cluster
5. Install and set up the Summarization and Pruning Aent Install the Summarization and Pruning Agent on a Tivoli System Automation for Multiplatforms cluster

When the previous steps have been completed:


Procedure

  1. On one of the nodes, take the resource group RG_NAME offline:

    chrg –o offline RG_NAME

  2. Verify that the resource group is offline, which can take 1 or 2 minutes:

    lssam -top

  3. Switch to the itm6/BuildScripts directory.

  4. Run the allrscbuild.sh command as root from the same directory.

  5. Start the resource group again using the command:

    chrg –o online RG_NAME

  6. Verify that the resource group is online:

    lssam –top

  7. Test the failover by running the rgreq –o move RG_NAME command, and use lssam -top to verify that monitoring server starts on the other node. If a component doesn’t start:

    1. Fix the values entered in the itm6/BuildScripts/clustervariables.sh file

    2. Remove the Tivoli System Automation for Multiplatforms domain using the following commands:

      stoprpdomain –f domain_name rmrpdomain domain_name

    3. Re-execute the steps in IBM Tivoli Monitoring cluster setup.

      The terminal session might end after the move completes.


Parent topic:

Create clusters with monitoring components in a System Automation for Multiplatforms environment

+

Search Tips   |   Advanced Search