9.3 Installing and Configuring Sun Cluster HA for Tivoli

This section describes the steps to install, configure, register, and start Sun Cluster HA for Tivoli. You must install and set up Sun Cluster and the Tivoli product before configuring Sun Cluster HA for Tivoli.

You will configure Sun Cluster HA for Tivoli by using the hadsconfig(1M) command. See the hadsconfig(1M) man page for details.

9.3.1 How to Install and Configure Sun Cluster HA for Tivoli

1. On each Sun Cluster server, install the Tivoli package, SUNWsctiv, in the default location, if it is not installed already.

   If the Tivoli package is not installed already, use the scinstall(1M) command to install it on each Sun Cluster server that is a potential master of the logical host on which Tivoli is installed.

2. Run the hadsconfig(1M) command on one node to configure Sun Cluster HA for Tivoli for both the server and managed node.

   Use the hadsconfig(1M) command to create, edit, and delete instances of the Sun Cluster HA for Tivoli data service for both the server and managed node. Refer to "9.3.2 Configuration Parameters for Sun Cluster HA for Tivoli", for information on input to supply to hadsconfig(1M). Run the command on one node only.

   phys-hahost1# hadsconfig

   ---

   Note -

   Only the Tivoli server and Tivoli managed node should be configured as instances under the control of Sun Cluster. The Tivoli managed nodes used for probing need not be controlled by Sun Cluster.

   ---

3. Register the Sun Cluster HA for Tivoli data service by running the hareg(1M) command.

   Run the command on only one node:

   phys-hahost1# hareg -s -r tivoli

4. Use the hareg(1M) command to enable Sun Cluster HA for Tivoli and perform a cluster reconfiguration.

   Run the command on only one node:

   phys-hahost1# hareg -y tivoli

   The configuration is complete.

9.3.2 Configuration Parameters for Sun Cluster HA for Tivoli

This section describes the information you supply to the hadsconfig(1M) command to create configuration files for Sun Cluster HA for Tivoli. The hadsconfig(1M) command uses templates to create these configuration files. The templates contain some default, some hard coded, and some unspecified parameters. You must provide values for those parameters that are unspecified.

The fault probe parameters, in particular, can affect the performance of Sun Cluster HA for Tivoli. Tuning the probe interval value too low (increasing the frequency of fault probes) might encumber system performance, and also might result in false takeovers or attempted restarts when the system is simply slow.

Configure Sun Cluster HA for Tivoli by supplying the hadsconfig(1M) command with parameters listed in Table 9-1.

Table 9-1 Configuration Parameters for Sun Cluster HA for Tivoli

Parameter	Description
Name of the instance	Nametag used as an identifier for the instance. The log messages generated by Sun Cluster HA for Tivoli refer to this nametag. The hadsconfig(1M) command prefixes the package name to the value you supply here. For example, if you specify "tivoli," the hadsconfig(1M) command produces "SUNWsctiv_tivoli."
Logical host	Name of the logical host that provides service for this instance of Sun Cluster HA for Tivoli.
Port number	Unique port for Sun Cluster HA for Tivoli. The default port number is 94.
Configuration directory	The directory of the database, that is, the full path of the $DBDIR. For example, /hahost1/d1/Tivoli/<database>.db.
Local probe flag	Specifies whether the local probe is started automatically at cluster reconfiguration or when the Tivoli service is activated. Possible values are y or -n.
Probe interval	Time in seconds between successive fault probes. The default is 60 seconds.
Probe timeout	Time out value in seconds for the probe. If the probe has not completed within this amount of time, Sun Cluster HA for Tivoli considers it to have failed. The default is 60 seconds.
Takeover flag	Specifies whether a failure of this instance will cause a takeover or failover of the logical host associated with the Tivoli instance. Possible values are -y or -n.
TIV_OSERV_TYPE	This is the TME type. Possible values are server or client.
TIV_BIN	The path to the TME binaries specified during installation of the instance. This is equivalent to $BINDIR without the "Solaris2" suffix. For example, /hahost1/d1/Tivoli/bin.
TIV_LIB	The path to the TME libraries specified during installation of the instance. For example, /hahost1/di/Tivoli/lib. This is equivalent to $LIBDIR without the "Solaris2" suffix.