Verifying and synchronizing a cluster configuration

Verification is done before synchronization to ensure the validity of the configuration. Synchronization is required whenever a change is made to the cluster definition.

Verifying the topology configuration

Verification ensures that all nodes agree on the topology of the cluster. For example, it checks for invalid characters in cluster names, node names, network names, network interface names, and resource group names. It checks to ensure that interfaces are properly configured, nodes are reachable, and networks have the required number of interfaces.

It also checks for the reserved words used as cluster names, node names, network names, network interface names and resource group names. These names are listed in the /usr/es/sbin/cluster/etc/reserved_words file.

Verifying the network configuration

Verification ensures that the networks are configured correctly and that all nodes agree on the ownership of all defined resources, such as the following:

• Configuration of network information, such as addresses on all nodes in the cluster.
• No network interfaces configured on unsupported network types (for example, IP, socc, slip and fcs).

Verifying disk and file system configuration

Verification ensures that disks and file systems are in agreement and configured according to the following:

• Agreement among all nodes on the ownership of defined resources (for example, file systems, volume groups, disks, and application controllers). The verification utility checks for the existence and defined ownership of the file systems to be taken over, and then checks the volume group and disks where the file systems reside.
• Agreement among nodes on the major and minor device numbers for NFS-exported file systems.
• If disk fencing is enabled, verification sends an error if all nodes are not included in the concurrent access resource group.

Verifying resource group information

Verification ensures that the resource group information supplied is in agreement and configured according to the following:

• Verification issues warnings in cases when the startup, fallover or fallback preferences that you choose for resource groups may put the high availability of resources at risk in the case of a cluster failure.
• The verification utility checks that the choices for distribution of resources in case of a takeover (node priorities) so that the takeover information matches the owned resources information.

Verifying individual resources

Verification checks individual resources, such as the following:

• Event customization.
• Application controller start and stop scripts exists and that they are executable.

Verifying automatic error notification methods

Verification ensures that automatic error notification (AEN) methods exist and are properly configured for the following:

• Root volume groups
• PowerHA® SystemMirror®-defined volume groups or PowerHA SystemMirror-defined disks
• PowerHA SystemMirror-defined file systems (the underlying disks that support the file system)

Verifying custom configurations

The verification function checks for the existence and consistency of any configured custom cluster snapshot methods

Verifying PowerHA SystemMirror Enterprise Edition configurations

If you are using PowerHA SystemMirror Enterprise Edition configurations, verification confirms that the PowerHA SystemMirror Enterprise Edition cluster configuration for sites and its replicated resources are consistent with your PowerHA SystemMirror cluster configuration.

Verifying service IP labels

If a service IP label is configured on the interface instead of the boot label, verification issues an error reminding you to run the sample utility clchipdev before starting cluster services. If that service IP label is an alias, verification has a correct action to reverse it. The sample utility clchipdev helps configure the application service interface correctly in PowerHA SystemMirror.