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

Install Tivoli System Automation for Multiplatforms on the cluster nodes


To set up Tivoli Monitoring with Tivoli System Automation for Multiplatforms, you will need two cluster nodes with at least one NIC (Network Interface Cards) in each computer. For more information regarding the configuration of the cluster creation, see Configure the cluster creation.

For a more robust cluster, use two NICs for each computer, so that the Tivoli System Automation for Multiplatforms heartbeat function has a failover path, in case one of the NICs goes down.

You should then execute the following steps on each of the cluster nodes (depending on how you received Tivoli System Automation for Multiplatforms, you might have it already installed):


Procedure

  1. From the Tivoli System Automation for Multiplatforms version 3.1.0.0 image or CD, run the prereqSAM.sh command to verify that you have the correct prerequisite software. If all prerequisites are present continue to step 2. Otherwise install the required prerequisites. (prereqSAM.sh displays the missing prerequisites, and writes to /tmp/prereqSAM.1.log.)

    Installing Tivoli System Automation for Multiplatforms on AIX is different from installing it on Linux mainly because Tivoli System Automation for Multiplatforms for AIX does not come with the prerequisite packages.

  2. From the Tivoli System Automation for Multiplatforms version 3.1.0.0 image or CD, run the installSAM.sh command.

    If you are using Tivoli System Automation for Multiplatforms version 2.2.0.0, follow the fix pack installation instructions to install the latest Tivoli System Automation for Multiplatforms Version 2.2.0.0 Fix Pack (Fix Pack 2 was used for testing.)

  3. If the nodes will be running DB2 in the cluster, download the DB2 policies db2salinux.tar.gz, from
    ftp://ftp.software.ibm.com/software/data/db2/linux/

    Expand the file. A suggested location is /usr/sbin/rsct/sapolicies because this is where other products might install their policies.

  4. Download additional policies:

    1. For AIX, download additional policies sam.policies.aix.1.2.2.1, from:
      http://www-01.ibm.com/software/brandcatalog/portal/opal/details?catalog.label=1TW10SA01

      To install the policies, use the System Management Interface Tool (more commonly known as SMIT). The policies install to/usr/sbin/rsct/sapolicies.

    2. For Linux:

      To install the policies, use the rpm –i filename command. The policies install to /usr/sbin/rsct/sapolicies.

    Use the latest available version available on the site.


What to do next

Make sure that you run the steps provided above on both cluster nodes.

The Tivoli System Automation for Multiplatforms Version 2.2.0.0 Fix Pack procedure allows you to install the fix pack by either bringing down the entire cluster, or by upgrading the cluster node by node.

With the first method, all of the resources are taken offline, which means that the Tivoli Monitoring components in that cluster is stopped.

With the second method, one node is taken offline and upgraded, while the active node is left online. If a failure occurs on the active node, failover does not occur until the inactive node has been brought online.

For further information, refer to the “Installing and uninstalling service” chapter of the Tivoli System Automation for Multiplatforms Installation Guide, and refer to Applying a fix pack to the Summarization and Pruning Agent for an issue with the service installation documentation.


Parent topic:

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

+

Search Tips   |   Advanced Search