Verifying and distributing the configuration

Use the cmquerycl utility to create the cluster configuration information file:

cmquerycl -n primary_node_name -n secondary_node_name -v -C
/etc/cmcluster/cmclconfig.ascii

primary_node_name – the host name for the primary node.

secondary_node_name – the host name for the secondary node.

In the cmclconfig.ascii file, change the max_configured_packages to 2.

Use the cmcheckconf utility to verify that the package configuration file is correct. cmcheckconf uses this syntax:

cmcheckconf -C /etc/cmcluster/cmclconfig.ascii -P /etc/cmcluster/package_name/primary_companion_name.ascii -P /etc/cmcluster/secondary_package_name/secondary_companion_name.ascii

where:

package_name is the name of the directory you created
primary_companion_name is the name of the companion you are configuring,
and secondary_companion_name is the name of its secondary companion.

For example, to verify the package configuration file for MONEY1:

cmcheckconf -C /etc/cmcluster/cmclconfig.ascii -P /etc/cmcluster/MONEY1/MONEY1.ascii
-P /etc/cmcluster/PERSONNEL1/PERSONNEL1.ascii

To distribute the binary cluster configuration file:

Issue the vgchange command to activate the cluster lock volume group so that the lock disk can be initialized:
```
/usr/sbin/vgchange -a y /dev/vglock
```
Use the cmapplyconf utility to generate the binary configuration file and distribute it across the nodes:
```
/usr/sbin/cmapplyconf -v -C /etc/cmcluster/cmclconf.ascii -P /etc/cmcluster/primary_package_name/primary_companion_name.ascii
-P /etc/cmcluster/secondary_package_name/secondary_companion_name.ascii
```
where primary_package_name is the name of the directory you created, primary_companion_name is the name of the companion you are configuring, secondary_package_name is the name of the secondary directory you created, and secondary_companion_name is the name of the secondary companion. For example, to generate a binary configuration file for MONEY1, enter:
```
 # cmapplyconf -v -C /etc/cmcluster/cmclconf.ascii -P   /etc/cmcluster/MONEY1/MONEY1.ascii
  -P /etc/cmcluster/PERSONNEL1/PERSONNEL1.ascii
```
To deactivate the cluster lock volume group:
```
 /etc/sbin/vgchange -a n /dev/vglock
```

The cluster lock volume group can be activated only on the node from which you issue the cmapplyconf command so that the lock disk can be initialized. When you configure the cluster, the cluster lock volume group must be active only on the configuration node and deactivated on all other nodes. Deactivate the cluster lock volume group on the configuration node after cmapplyconf is executed.

You must run cmcheckconf and cmapplyconf any time you make changes to the cluster and package configuration files.