Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Building an HA Cluster Configuration
Configuring the Cluster
Chapter 5188
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.
Verifying the Cluster Configuration
If you have edited a cluster configuration template file, use the following
command to verify the content of the file:
cmcheckconf -v -C $SGCONF/clust1.config
This command checks the following:
• Network addresses and connections.
• Quorum server connection.
• All lock LUN device names on all nodes refer to the same physical
disk area.
• One and only one lock LUN device is specified per node.
• A quorum server or lock LUN is configured, but not both.
• Uniqueness of names.
• Existence and permission of scripts specified in the command line.
• If all nodes specified are in the same heartbeat subnet.
• Correct configuration filename.
• All nodes can be accessed.
• No more than one CLUSTER_NAME, HEARTBEAT_INTERVAL, and
AUTO_START_TIMEOUT are specified.
• The value for package run and halt script timeouts does not exceed
the maximum.