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

NOTE: Check spelling especially carefully when typing wildcards, such as ANY_USER and
ANY_SERVICEGUARD_NODE. If they are misspelled, Serviceguard will assume they are specific
users or nodes.
Package versus Cluster Roles
Package configuration will fail if there is any conflict in roles between the package configuration
and the cluster configuration, so it is a good idea to have the cluster configuration file in front of
you when you create roles for a package; use cmgetconf to get a listing of the cluster configuration
file.
If a role is configured for a username/hostname in the cluster configuration file, do not specify a
role for the same username/hostname in the package configuration file; and note that there is no
point in assigning a package administration role to a user who is root on any node in the cluster;
this user already has complete control over the administration of the cluster and its packages.
Adding Volume Groups
Add any LVM volume groups you have configured to the cluster configuration file, with a separate
VOLUME_GROUP entry for each cluster-aware volume group that will be used in the cluster. These
volume groups will be initialized with the cluster ID when the cmapplyconf command is used.
In addition, you should add the appropriate volume group, logical volume and file system
information to each package that activates a volume group; see vg (page 248).
NOTE: If you are using CVM disk groups, they should be configured after cluster configuration
is done, using the procedures described in “Creating the Storage Infrastructure with Veritas Cluster
Volume Manager (CVM)” (page 219). Add CVM disk groups to the package configuration file; see
cvm_dg (page 249).
Verifying the Cluster Configuration
If you have edited a cluster configuration file using the command line, use the following command
to verify the content of the file:
cmcheckconf -k -v -C /etc/cmcluster/clust1.conf
The following items are checked:
• Network addresses and connections, and that all IP addresses configured into the cluster are
in each node's /etc/hosts file.
• Cluster lock connectivity (if you are configuring a lock disk).
• Validity of configuration parameters for the cluster and packages.
• Uniqueness of names.
• Existence and permissions of scripts specified on the command line.
• That all nodes specified are in the same heartbeat subnet, except in cross-subnet
configurations(page 30) .
• That the configuration filename is correcy.
• That all nodes are reachable.
• That no more than one CLUSTER_NAME and AUTO_START_TIMEOUT are specified.
• That the value for package run and halt script timeouts is less than 4294 seconds.
• That the value for AUTO_START_TIMEOUT variables is >=0.
• That the heartbeat network minimum requirement is met. See the entry for HEARTBEAT_IP
under “Cluster Configuration Parameters ” (page 109) .
• That at least one NODE_NAME is specified.
Configuring the Cluster 197