Managing Serviceguard A.11.20, March 2013

NOTE: Using the -k option means that cmcheckconf only checks disk connectivity to the LVM
disks that are identified in the ASCII file. Omitting the -k option (the default behavior) means that
cmcheckconf tests the connectivity of all LVM disks on all nodes. Using -k can result in significantly
faster operation of the command.
For more information, see the manpage for cmcheckconf (1m) and “Checking Cluster
Components” (page 278).
Distributing the Binary Configuration File
After specifying all cluster parameters, apply the configuration. This action distributes the binary
configuration file to all the nodes in the cluster. HP recommends doing this separately before you
configure packages (as described in the next chapter) so you can verify the cluster lock, heartbeat
networks, and other cluster-level operations by using the cmviewcl command on the running
cluster. Before distributing the configuration, ensure that your security files permit copying among
the cluster nodes. See “Preparing Your Systems” at the beginning of this chapter.
Use the following steps to generate the binary configuration file and distribute the configuration
to all nodes in the cluster:
• Activate the cluster lock volume group so that the lock disk can be initialized:
vgchange -a y /dev/vglock
• Generate the binary configuration file and distribute it:
cmapplyconf -k -v -C /etc/cmcluster/clust1.conf
or
cmapplyconf -k -v -C /etc/cmcluster/clust1.ascii
NOTE: Using the -k option means that cmapplyconf only checks disk connectivity to the
LVM disks that are identified in the ASCII file. Omitting the -k option (the default behavior)
means that cmapplyconf tests the connectivity of all LVM disks on all nodes. Using -k can
result in significantly faster operation of the command.
• Deactivate the cluster lock volume group.
vgchange -a n /dev/vglock
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 that the cmapplyconf command does not distribute the ASCII configuration file.
NOTE: The apply will not complete unless the cluster lock volume group is activated on exactly
one node before applying. There is one exception to this rule: a cluster lock had been previously
configured on the same physical volume and volume group.
After the configuration is applied, the cluster lock volume group must be deactivated.
Storing Volume Group and Cluster Lock Configuration Data
After configuring the cluster, create a backup copy of the LVM volume group configuration by
using the vgcfgbackup command for each volume group you have created. If a disk in a volume
group must be replaced, you can then restore the disk's metadata by using the vgcfgrestore
command. The procedure is described under “Replacing Disks” in the “Troubleshooting” chapter.
Be sure to use vgcfgbackup for all volume groups, especially the cluster lock volume group.
Configuring the Cluster 203