HP-UX HB v13.00 Ch-15 - Serviceguard

HP-UX Handbook – Rev 13.00 Page 32 (of 108)
Chapter 15 Serviceguard
October 29, 2013
If the cluster has already been configured previously, the cmcheckconf command will compare
the configuration in the cluster ASCII file against the previously configuration information
stored in the binary configuration file and validates the changes. The same rules apply to the
package ASCII file.
root@Node1:/ # cmcheckconf -k -v -C /etc/cmcluster/cluster.ascii
This checks the following:
 Network addresses and connections.
 Cluster lock or lock LUN connectivity (if you are configuring a lock disk) or quorum
server communication.
 Validity of configuration parameters for the cluster and packages.
 Uniqueness of names.
 Existence and permission of scripts specified in the command line.
 Verify specified nodes have the same heartbeat subnets.
 If you specify the wrong configuration filename.
 If 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 is less than 4294 seconds.
 Legitimate value of MEMBER_TIMEOUT.
 The value for AUTO_START_TIMEOUT variables is >=0.
 Heartbeat network minimum requirement. The cluster must have one heartbeat LAN
configured with a standby, two heartbeat LANs, one heartbeat LAN and an RS232
connection, or one heartbeat network with no local LAN switch, but with a primary LAN
that is configured as a link aggregate of at least two interfaces.
 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.
 If a serial (RS-232) heartbeat is configured, there are no more than two nodes in the
cluster, and no more than one serial (RS232) port connection per node.
 VOLUME_GROUP entries are not currently marked as cluster-aware.
 There is only one heartbeat subnet configured if you are using CVM 3.5 disk storage.
If the cluster is online, the check also verifies that all the conditions for the specific change in
configuration have been met.
Using the -k option means that cmcheckconf only checks disk connectivity to the LVM disks
that are identified in the ASCII file. Omitting the -k option (the default behavior) causes
cmcheckconf to test the connectivity of all LVM disks on all nodes. Using -k can result in
significantly faster operation of the command.