Sun Cluster 2.2 Software Installation Guide

Installing and Configuring Sun Cluster HA for Lotus

This section describes the steps used to install, configure, register, and start Sun Cluster HA for Lotus.

How to Install and Configure Sun Cluster HA for Lotus
  1. On each Sun Cluster server that will be running HA-Lotus, run the hadsconfig(1M) command to configure Sun Cluster HA for Lotus.

    Use the hadsconfig(1M) command to create, edit, and delete instances of Sun Cluster HA for Lotus. Refer to "Configuration Parameters for Sun Cluster HA for Lotus", for information on the input you will need to supply to the hadsconfig(1M) command. See the hadsconfig(1M) man page for details.


    Note -

    You can configure multiple instances of Lotus Domino per cluster only when using Lotus Domino 4.6.3.



    # hadsconfig
    
  2. Register and activate Sun Cluster HA for Lotus using the hareg(1M) command.

    The hareg(1M) command adds the Sun Cluster HA for Lotus data service to the Cluster Configuration Database, performs a cluster reconfiguration, and starts all of your Lotus Domino servers. Run this command on only one node:


    # hareg -s -r lotus
    ...
    # hareg -y lotus
    

  3. Verify the Sun Cluster HA for Lotus configuration.

    Log in as notes and verify the configuration by starting and stopping the Lotus Domino server on one of the Sun Cluster servers:


    phys-hahost1# /opt/lotus/bin/server
    ...
    phys-hahost1# /opt/lotus/bin/server -q
    

    You can test more of the configuration by starting the cluster, mastering the logical hosts from various physical hosts, and then starting and stopping the Lotus Domino server from those physical hosts. For example:


    phys-hahost1# scadmin startcluster phys-hahost1 clustername
    phys-hahost2# scadmin startnode clustername
    phys-hahost1# haswitch phys-hahost2 hahost1 hahost2
    

    Log in as user notes, and stop and start the Lotus Domino server from the Domino data directory. For example:


    phys-hahost2# cd /hahost1/data_directory
    phys-hahost2# /opt/lotus/bin/server
    ...
    phys-hahost2# /opt/lotus/bin/server -q
    


Note -

If any of the Lotus Domino instances fail to start, make sure that user notes has permission to access the data directories and data files, then start the instances.


This completes the configuration and activation of Sun Cluster HA for Lotus.

Configuration Parameters for Sun Cluster HA for Lotus

This section describes the information you supply to the hadsconfig(1M) command to create configuration files for each Sun Cluster HA for Lotus data service. The hadsconfig(1M) command uses templates to create these configuration files, and stores the files in the /etc/opt/SUNWsclts directory. The templates contain some default, some hard-coded, and some unspecified parameters. You must provide values for the parameters that are unspecified.

The fault probe parameters, in particular, can affect the performance of Sun Cluster HA for Lotus. 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.

You must set the takeover flag for Sun Cluster HA for Lotus. This flag specifies how Sun Cluster will handle partial failover. There are two options:

Configuration Parameters for Sun Cluster HA for Lotus

Configure the Sun Cluster HA for Lotus parameters listed in the hadsconfig(1M) input form by supplying options described in Table 13-3.

Table 13-3 Configuration Parameters for Sun Cluster HA for Lotus

Parameter 

Description 

Name of the instance 

Logical host name used as an identifier for the instance. The log messages generated by Sun Cluster HA for Lotus refer to this identifier. The hadsconfig(1M) command prefixes the package name to the logical host name you supply. For example, if you specify "hahost1," hadsconfig(1M)produces "SUNWsclts_hahost1."

Logical host 

Name of the logical host that provides service for this instance of Sun Cluster HA for Lotus. 

Base directory of product installation 

Rooted path name specifying the location on the multihost disk of the HA Lotus installation. This is the "instance path," for example, /hahost1/lotus-home/lotus_1.

Configuration directory 

The directory of the database, for example, /hahost1/d1/Lotus/database.db.

Remote probe 

Specifies whether the Lotus fault probe will probe the remote host. Default value is n.

Local probe 

Specifies whether the Lotus fault probe will probe the local host. Default value is y.

Probe interval 

The time, in seconds, between fault probes. The default interval is 60 seconds. 

Probe timeout 

The time, in seconds, after which a fault probe will time out. The default timeout value is 60 seconds. 

Server port number

Unique port for this instance of Sun Cluster HA for Lotus. The default port number is 1352. 

Takeover flag 

Specifies whether a failure of this instance will cause a takeover or failover of the logical host associated with the data service instance. Possible values are y (yes) or n (no). Default value is y. Values are described in "Configuration Parameters for Sun Cluster HA for Lotus".

Lotus server type 

This parameter is meaningful only for configurations using Lotus Domino 4.6.3. The default value is single. When configuring a Lotus Domino server or a primary partitioned server, always use the default value. When configuring additional partitioned servers, use any value besides single.

Lotus password file 

This parameter is meaningful only for configurations using Lotus Domino 4.6.3. The default value is default_file. When configuring a Lotus Domino server or a primary partitioned server, use the default value, because no password is required for start up. When configuring an additional partitioned server, enter the name of the file in which the password for the additional partitioned server startup resides. If the Lotus Domino server is installed on a shared disk, make sure the password file is available on all cluster nodes, or install the password file on the shared disk.