Verifying the Cluster Configuration

SAM automatically checks the configuration you enter and reports any errors. If you have edited an ASCII cluster configuration file, use the following command to verify the content of the file:

# cmcheckconf -v -C /etc/cmcluster/cmclconf.ascii

This command or automatic verification in SAM both check the following:

Network addresses and connections.
Cluster lock connectivity.
Validity of configuration parameters for the cluster and packages.
Uniqueness of names.
Existence and permission of scripts specified in the command line.
If all nodes specified are in the same heartbeat subnet.
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 HEARTBEAT_INTERVAL is at least one second.
The value for NODE_TIMEOUT is at least twice the value of HEARTBEAT_INTERVAL.
The value for AUTO_START_TIMEOUT variables is >=0.
Heartbeat network minimum requirement. The cluster must have one heartbeat LAN configured with a standby, or two heartbeat LANs, or one heartbeat LAN and an RS232 connection.
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 RS-232 is used, that RS232 is configured on a two node cluster, and there is no more than one serial (RS232) port connection per node.
VOLUME_GROUP and OPS_VOLUME_GROUP entries are not currently marked as cluster-aware.

If the cluster is online, SAM (or the cmcheckconf command) also verifies that all the conditions for the specific change in configuration have been met.

Verifying the Cluster Configuration

Technical documentation

» Table of Contents

» Index