HP-UX HB v13.00 Ch-15 - Serviceguard

HP-UX Handbook – Rev 13.00 Page 33 (of 108)
Chapter 15 Serviceguard
October 29, 2013
root@Node1:/etc/cmcluster# cmcheckconf -k -v -C ./cluster.ascii -P \ ./sw/sw-
pkg.conf
Checking cluster file: ./cluster.ascii
Note : a NODE_TIMEOUT value of 2000000 was found in line 134. This value
is recommended if the top priority is to reform the cluster as fast
as possible in case of failure. If the top priority is to minimize
reformations, consider using a higher setting. For more information see
the cluster configuration ASCII file or the Managing Serviceguard manual.
Checking nodes ... Done
Checking existing configuration ... Done
Gathering storage information
Found 3 devices on node Node1
Found 3 devices on node Node2
Analysis of 6 devices should take approximately 1 seconds
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
Found 1 volume groups on node Node1
Found 1 volume groups on node Node2
Analysis of 2 volume groups should take approximately 1 seconds
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
Gathering network information
Beginning network probing (this may take a while)
Completed network probing
Parsing package file: ./sw/sw.conf.
Checking for inconsistencies
Modifying configuration on node Node1
Modifying configuration on node Node2
cmcheckconf: Verification completed with no errors found.
Use the cmapplyconf command to apply the configuration.
Generation and Distribution of a Cluster Configuration
Use the cmapplyconf command to validate and apply Serviceguard cluster configuration and
package configuration files. cmapplyconf performs another cmcheckconf, creates or updates the
binary configuration file called /etc/cmcluster/cmclconfig, and distributes it to all nodes.
This binary configuration file contains the cluster configuration information as well as package
configuration information for all packages specified. Cmapplyconf also installs the cluster lock
structure on the lock VG (if defined) and it installs a cluster ID and the exclusive activation
mode bit in LVM metadata on disks identified with VOLUME_GROUP parameters in the
cluster ASCII file. It also removes the cluster ID and exclusive activation bit on volume groups
that have been removed from the configuration file.
If changes to either the cluster configuration or to any of the package configuration files are
needed, first update the appropriate ASCII file(s) (cluster or package), then validate the changes
using the cmcheckconf command and then use cmapplyconf again to verify and redistribute the
binary file to all nodes.
The cluster ASCII file only needs to be specified if configuring the cluster for the first time, or if
adding or deleting nodes to the cluster. The package ASCII file only needs to be specified if the
package is being added, or if the package configuration is being modified. It is recommended
that the user runs the cmgetconf command to get either the cluster ASCII configuration file or
package ASCII configuration file whenever changes to the existing configuration are required.