HP Serviceguard Toolkit for NFS on Linux User Guide Version A.12.00.00

• To achieve complete validation of cluster and application toolkit using single command
execution.
• To build a steady cluster for high available solution.
You can use either the cmcheckconf –v or cmcheckconf –P commands to initiate the cluster
verification.
Run the cmcheckconf –v command to perform cluster wide verification of resources. This
command also verifies the packages that are presently deployed in the system. Run the
cmcheckconf -v 2 command to display the ERROR, WARNING, or INFO messages during
the package verification.
Run the cmcheckconf –P command to perform the package verification irrespective of the state
of the package in the cluster.
The following are the steps to initiate the package verification by using the cmcheckconf –P
command:
1. While the package is up and running, retrieve the current package configuration values by
using the cmgetconf command.
For example: # cmgetconf -p <package_name> <package_name.conf>
2. Perform verification of the package configuration details that you received in the previous
step.
For example: # cmcheckconf –P <package_name.conf>
Use the cluster verification feature for the NFS toolkit to:
• Verify the presence of the lockfile, and the lsb-release commands.
If the verification fails for the respective commands, the console displays the following error
messages:
ERROR: lockfile command does not exist.
Reason: This error indicates that the lockfile command required for configuring NFS toolkit
package does not exist.
Solution: Install procmail rpm specific to OS distribution to obtain the lockfile command.
ERROR: lsb-release command does not exist.
Reason: This error indicates that the lsb_release command required for configuring NFS
toolkit package does not exist.
Solution: You can obtain the lsb_release command by installing redhat-lsb rpm for
Redhat distribution and lsb-release rpm for SLES11.
• Verify the presence of important binaries that are required to configure the NFS toolkit package
on SLES11.
If the verification fails for the respective commands, the console displays the following error
message:
ERROR: rpc.rquotad binary does not exist.
Reason: The rpc.rquotad binary for SLES11, comes as a part of quota-nfs rpm instead
of main nfs-kernel rpm. There are high chances that the user might have overlooked this
binary. Hence, the Cluster verification verifies the presence of this binary as a part of NFS
toolkit package verification.
Solution: Install quota-nfs rpm on SLES11 to obtain the rpc.rquotad binary.
Managing the NFS toolkit package 15