Managing HP Serviceguard A.11.20.10 for Linux, December 2012

SGROOT=/opt/cmcluster # SG root directory
SGCONF=/opt/cmcluster/conf # configuration files
SGSBIN=/opt/cmcluster/bin # binaries
SGLBIN=/opt/cmcluster/bin # binaries
SGLIB=/opt/cmcluster/lib # libraries
SGRUN=/opt/cmcluster/run # location of core dumps from daemons
SGAUTOSTART=/opt/cmcluster/conf/cmcluster.rc # SG Autostart file
Throughout this document, 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 /usr/local/cmcluster/conf, then
the complete pathname for file $SGCONF/cmclconfig would be
/usr/local/cmcluster/conf/cmclconfig.
5.1.3 Enabling Serviceguard Command Access
To allow the creation of a Serviceguard configuration, you should complete the following steps on
all cluster nodes before running any Serviceguard commands. Alternatively, you can also use
cmpreparecl to configure the nodes. For more information, see cmpreparecl(1M) .
1. Make sure the root user’s path includes the Serviceguard executables. If the Serviceguard
commands are not accessible, run the following commands:
. /etc/profile.d/serviceguard.sh for Bourne-type shells
. /etc/profile.d/serviceguard.csh for C-type shells
2. Edit the /etc/man.config file for Red Hat Enterprise Linux Server and /etc/
manpath.config file for SUSE Linux Enterprise Server to include the following:
For Red Hat Enterprise Linux Server:
MANPATH /usr/local/cmcluster/doc/man
For SUSE Linux Enterprise Server:
‘MANDATORY_MANPATH` /opt/cmcluster/doc/man
This will allow use of the Serviceguard man pages.
NOTE: Update the $MANPATH environment variable with /opt/cmcluster/doc/man/.
3. Enable use of Serviceguard variables.
If the Serviceguard variables are not defined on your system, then include the file /etc/
cmcluster.conf in your login profile for user root:
. /etc/cmcluster.conf
You can confirm the access to the one of the variables as follows:
cd $SGCONF
5.1.4 Configuring Root-Level Access
The subsections that follow explain how to set up 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” (page 152)).
NOTE: For more information and advice, see the white paper Securing Serviceguard at http://
www.hp.com/go/hpux-serviceguard-docs (Select HP Serviceguard -> White Papers).
5.1.4.1 Allowing Root Access to an Unconfigured Node
To enable a system to be included in a cluster, you must enable Linux 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
130 Building an HA Cluster Configuration