Managing HP Serviceguard A.11.20.20 for Linux, May 2013

5.2.8.5 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.
5.2.9 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.conf
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, MEMBER_TIMEOUT, and AUTO_START_TIMEOUT are
specified.
• The value for package run and halt script timeouts does not exceed the maximum.
• The value for AUTO_START_TIMEOUT variables is greater than zero.
• Heartbeat network minimum requirement. See HEARTBEAT_IP under “Cluster Configuration
Parameters ” (page 91).
• At least one NODE_NAME is specified.
• Each node is connected to each heartbeat network.
• All heartbeat networks are of the same type of LAN.
• The network interface device files specified are valid LAN device files.
• Other configuration parameters for the cluster and packages are valid.
If the cluster is online the cmcheckconf command also verifies that all the conditions for the
specific change in configuration have been met.
5.2.10 Cluster Lock Configuration Messages
The cmquerycl, cmcheckconf and cmapplyconf commands will return errors if the cluster
lock is not correctly configured. If there is no cluster lock in a cluster with two nodes, the following
message is displayed in the cluster configuration file:
5.2 Configuring the Cluster 163