Distributing and Verifying the Configuration

Distributing the Configuration File And Control Script with SAM

When you have finished creating a package in the Package Configuration subarea in SAM, you are asked to verify the copying of the files to all the nodes in the cluster. When you respond OK to the verification prompt, MC/LockManager copies the binary configuration file and package control script to all the nodes in the cluster.

Copying Package Control Scripts with HP-UX commands

Use HP-UX commands to copy package control scripts from the configuration node to the same pathname on all nodes which can possibly run the package. Use your favorite method of file transfer (e. g., rcp or ftp). For example, from ftsys9, you can issue the rcp command to copy the package control script to ftsys10:

# rcp /etc/cmcluster/pkg1/control.sh ftsys10:/etc/cmcluster/pkg1/control.sh 

Distributing the Binary Cluster Configuration File with HP-UX Commands

Use the following steps from the node on which the ASCII cluster and package configuration files exist:

The cmapplyconf command creates a binary version of the cluster configuration file and distributes it to all nodes in the cluster. This action ensures that the contents of the file are consistent across all nodes.

	NOTE: cmcheckconf and cmapplyconf must be used again any time changes are made to the cluster and package configuration files.

Verifying Cluster and Package Configuration

While configuring your MC/LockManager cluster, it's a good idea to test that the various components of the cluster behave correctly in case of a failure. See the chapter "Troubleshooting Your Cluster" for an explanation of how to test that your cluster responds properly in the event of a package failure, a node failure, or a LAN failure.