Managing Serviceguard 14th Edition, June 2007

Building an HA Cluster Configuration

Configuring the Cluster

Chapter 5 243

vgchange -a y /dev/vglock

• Generate the binary configuration file and distribute it:

cmapplyconf -k -v -C /etc/cmcluster/clust1.config

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.