HP XC System Software Installation Guide Version 4.0

NOTE: The cluster_config utility processing time can take approximately ten minutes
longer if it is run on a head node that is configured for improved availability with Serviceguard
when the remaining nodes of the cluster are up and running.
After the entire system has been imaged and booted, you might need to rerun the
cluster_config procedure to modify the node configuration. If the other node in the availability
set with the head node is up and running, the Serviceguard daemons attempt to establish
Serviceguard related communication with the node when they are restarted. Because the other
node in the availability set is not actively participating in a Serviceguard cluster, it will not
respond to the Serviceguard communication.
The Serviceguard software on the head node retries this communication until the communication
times out. On a system running with the default Serviceguard availability configuration, the
time out is approximately ten minutes.
To configure the system:
1. Start a script to capture command output into a file. This step is optional, but HP recommends
doing so.
# script your_filename
2. Change to the configuration directory:
# cd /opt/hptc/config/sbin
CAUTION: Make sure that no other terminal windows or shells are actively open in the
/hptc_cluster directory. The cluster_config utility does not properly export the
/hptc_cluster directory if any processes are using the directory when the
cluster_config utility mounts the file system.
3. Begin the cluster configuration process:
# ./cluster_config
4. Decide whether you want to back up the database before proceeding:
HP recommends that you back up the database before proceeding.
Do you want to back up the database? (yes/no) [y]: y
If you answer yes, the database backup file is stored in the /var/hptc/database directory.
5. Proceed to one of the following sections:
• If you have installed and configured an availability tool (such as HP Serviceguard),
proceed to Section 6.3 (page 101) to configure availability sets.
• If you are not configuring availability sets, proceed to Section 6.4 (page 103).
6.3 Configuring Availability Sets
This task is optional. If you have not installed and configured an availability tool, you are not
prompted to configure availability sets.
Section 1.9 (page 26) described the advance planning that is required to achieve improved
availability of services. Planning includes determining the services for which you want to configure
improved availability, the nodes you want to associate in availability sets, and special
considerations for role assignments on the head node.
The first step to enable improved availability is to define nodes into availability sets now. Keep
in mind the default node role assignments and decide on the nodes you want to associate in an
availability set.
For example, assume that you have decided that nagios and nat are the services for which you
want to enable improved availability. For the purposes of this example, use nodes n7 and n8.
Thus, if one of those nodes becomes unavailable, the services fail over to the other node.
6.3 Configuring Availability Sets 101