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 > Install the monitoring server on its base Tivoli System Automation for Multiplatforms cluster

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Install and set up the monitoring server on clusternode1


Use the value that was entered for the CANDLEHOME variable in clustervariables.sh for the installation directory.

Use the value that was entered for the HUBNAME variable in clustervariables.sh for the Hub name.


Procedure

  1. Check which cluster node is active (online):

    lsrg -m

  2. Change the cluster's mode to Manual:

    samctrl –M T

  3. On the active node, install the monitoring server into your chosen directory on the shared file system, according to the IBM Tivoli Monitoring: Installation and Setup Guide.

  4. Use one of the following two methods to configure the monitoring server:

    • To invoke a GUI application, use <CANDLEHOME>/bin/itmcmd manage, which requires a connection to an X Server.

    • To invoke a text application, use <CANDLEHOME>/bin/itmcmd config –S –t hub_name, which prompts you for the configuration values.

  5. Configure the monitoring server host name so that it is the same as the virtual host name of the monitoring server.

    The monitoring server host name is the Host Name field on the GUI Basic Settings tab, and the TEMS Host Name field in the text application.

  6. Set the Primary Network Name to the virtual host name of the monitoring server. That ensures that the agents and portal server can connect to the monitoring server on this IP address.

    The Primary Network Name is the Network Name field in the Optional Primary Network Name box on the GUI Advanced Settings tab, and the Optional Primary Network Name field in the text application.

  7. Start up the monitoring server and add the application support for the desired agent types.

  8. Change the cluster's mode to Automatic:

    samctrl –M F

  9. Disable the automatic startup of the monitoring server:

    1. Edit the /shareddisk/ITM/config/kcirunas.cfg file.

    2. Add the following section after the <agent> line by including the following syntax:

      <productCode>ms</productCode>
      <default>
      <autoStart>no</autoStart>
      </default>

    3. Save the file.

    4. As user root, run...

        /shareddisk/ITM/bin/UpdateAutoRun.sh

    The path to the kcirunas.cfg file and the UpdateAustoRun.sh command (/shareddisk/ITM) might be different on your system.


Parent topic:

Install the monitoring server on its base Tivoli System Automation for Multiplatforms cluster

+

Search Tips   |   Advanced Search