Verify and distribute the configuration

Perform the following steps to verify and distribute the configuration.

  1. Use the cmcheckconf utility to verify that the package configuration file is correct. cmcheckconf uses the following 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
    
  2. Perform the following steps to distribute the binary cluster configuration file:

    1. 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
      
    2. Use the cmapplyconf utility to generate the binary configuration file and distribute it across the nodes. cmapplyconf uses the following syntax:

      /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, and similar definitions for secondary_package_name and secondary_companion_name. For example, to generate a binary configuration file for MONEY1:

       # cmapplyconf -v -C /etc/cmcluster/cmclconf.ascii -P /etc/cmcluster/MONEY1/MONEY1.ascii
      -p /etc/cmcluster/PERSONNEL1/PERSONNEL1.ascii
      
    3. Issue the vgchange command to deactivate the cluster lock volume group:

       /etc/sbin/vgchange -a n /dev/vglock
      

NoteThe cluster lock volume group must 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. Make sure you deactivate the cluster lock volume group on the configuration node after cmapplyconf is executed.

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