Managing Serviceguard Fifteenth Edition, reprinted May 2008

Building an HA Cluster Configuration
Preparing Your Systems
Chapter 5200
NOTE If these variables are not defined on your system, then source the file
/etc/cmcluster.conf in your login profile for user root. For example,
you can add this line to root’s .profile file:
. /etc/cmcluster.conf
Throughout this book, system filenames are usually given with one of
these location prefixes. Thus, references to $SGCONF/filename can be
resolved by supplying the definition of the prefix that is found in this file.
For example, if SGCONF is defined as /etc/cmcluster/, then the
complete pathname for file $SGCONF/cmclconfig is
/etc/cmcluster/cmclconfig.
NOTE Do not edit the /etc/cmcluster.conf configuration file.
Configuring Root-Level Access
The subsections that follow explain how to set up HP-UX root access
between the nodes in the prospective cluster. (When you proceed to
configuring the cluster, you will define various levels of non-root access
as well; see “Controlling Access to the Cluster” on page 239.)
NOTE For more information and advice, see the white paper Securing
Serviceguard at http://docs.hp.com -> High Availability ->
Serviceguard -> White Papers.
Allowing Root Access to an Unconfigured Node
To enable a system to be included in a cluster, you must enable HP-UX
root access to the system by the root user of every other potential cluster
node. The Serviceguard mechanism for doing this is the file
$SGCONF/cmclnodelist. This is sometimes referred to as a “bootstrap”
file because Serviceguard consults it only when configuring a node into a
cluster for the first time; it is ignored after that. It does not exist by
default, but you will need to create it.