HP Serviceguard A.11.20- Managing Serviceguard Twentieth Edition, August 2011

6. Verify the storage using the following commands:
• For LVM volume groups:
vgdisplay
• For VxVM/CVM disk groups:
vxdg list
The volume group or the disk group can now be used by packages; see Chapter 6 (page 227).
NOTE: cmpreparestg requires either -l <vgname> or -g <dgname> in all cases. The
command must be run on one of the specified nodes (ftsys9 or ftsys10 in this example).
Other forms of cmpreparestg allow you to import a volume group or disk group that already
exists, create a single logical volume or multiple logical volumes, and create and mount a file
system on it. You can use the -o vg_opts option to specify options for newly created volume
groups; this is particularly useful if you need to create an LVM version 2.<x> volume group. You
can also use the -o dg_opts option to specify options for newly created VxVM/CVM disk groups.
See the manpage for more information.
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” (page 192).)
As of Serviceguard A.11.20, much of this configuration can be done by means of the Serviceguard
command cmpreparecl (1m) (or cmpdeploycl (1m), which calls cmpreparecl). See the
cmpreparecl manpage for more information. See also “Using Easy Deployment Commands to
Configure the Cluster” (page 162).
NOTE: For more information and advice, see the white paper Securing Serviceguard at http://
www.hp.com/go/hpux-serviceguard-docs.
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.
NOTE: cmclnodelist is created automatically by cmpreparecl (1m) (or cmpdeploycl
(1m), which calls cmpreparecl). You can skip the rest of this subsection if you have used, or
plan to use, either of these commands. See “Using Easy Deployment Commands to Configure the
Cluster” (page 162).
You may want to add a comment such as the following at the top of the file:
###########################################################
# Do not edit this file!
# Serviceguard uses this file only to authorize access to an
# unconfigured node. Once the node is configured,
# Serviceguard will not consult this file.
###########################################################
The format for entries in cmclnodelist is as follows:
<hostname> <user> #<comment>
166 Building an HA Cluster Configuration