as the path locations for start and stop scripts for the application. These scripts have to be in the same location on every service node.
Just as for pre- and
4.3.1.4 Synchronizing Cluster Resources
After defining these resources and their relationship with the resource group, the act of synchronizing cluster resources sends the information contained on the current node to all defined cluster nodes.
Note
All configured nodes must be on their boot addresses when a cluster has been configured and the nodes are synchronized for the first time. Any node not on its boot address will not have its /etc/rc.net file updated with the HACMP entry; this causes problems for the reintegration of this node into the cluster.
If a node attempts to join the cluster when its configuration is
4.4 Initial Testing
After installing and configuring your cluster, it is recommended that you do some initial testing in order to verify that the cluster is acting as it should.
4.4.1 Clverify
Running /usr/sbin/cluster/diag/clverify is probably a good start to the testing. It allows you to check the software and the cluster.
Software checking is reduced to lpp checking, which is basically checking whether
Cluster verification is divided into topology and configuration checking. These two parts do basically the same as smit clverify, i.e. verifying that the clusters topology as well as the resource configurations are in sync on the cluster nodes.