Verifying and synchronizing a PowerHA SystemMirror cluster
Verifying and synchronizing your PowerHA® SystemMirror® cluster assures you that all resources used by PowerHA SystemMirror are configured appropriately and that rules regarding resource ownership and resource takeover are in agreement across all nodes. You should verify and synchronize your cluster configuration after making any change within a cluster. For example, any change to the hardware operating system, node configuration, or cluster configuration.
Whenever you configure, reconfigure, or update a cluster, run the cluster verification procedure to ensure that all nodes agree on the cluster topology, network configuration, and the ownership and takeover of PowerHA SystemMirror resources. If the verification succeeds, the configuration can be synchronized. Synchronization takes effect immediately on an active cluster. A dynamic reconfiguration event is run and the changes are committed to the active cluster.
Note: If you are using the standard configuration paths, synchronization automatically follows a successful verification. If you are using the Custom Cluster Configuration path, you have more options for types of verification. If you are using the Problem Determination Tools path, you can choose whether to synchronize or not.
The messages output from verification indicate where the error occurred (for example, the node, device, or command). The utility uses verbose logging to write to the /var/hacmp/clverify/clverify.log file.
Error conditions result when information is not properly configured on all cluster nodes. This information may be important for the operation of PowerHA SystemMirror, but not part of the PowerHA SystemMirror software itself; for example, AIX® volumes do not exist in the cluster. In some of these situations, you can authorize a corrective action before verification continues. When verification detects certain conditions, such as mismatched PowerHA SystemMirror shared volume group time stamps or a node is missing required entries in /etc/services, PowerHA SystemMirror fixes the problem.
On the node where you run the utility, detailed information is collected into log files, which contain a record of all data collected and the tasks performed.
You can add your own custom verification methods to ensure that specific components within your cluster are properly configured. You can change or remove these methods from the verification process depending on the level of cluster verification you want.