Serviceguard NFS Toolkit A.11.11.06, A.11.23.05 and A.11.31.03 Administrator's Guide

In this example, nfs1is the name that maps to the package's relocatable IP address. It must
be configured in the name service used by the server (DNS, NIS, or the /etc/hosts file).
If a server for the package will NFS-mount the package's file systems, the client mount point
(CNFS) must be different from the server location (SNFS).
3. Copy the script you have just modified to all the servers that will NFS-mount the file systems
in the package.
4. After the package is active on the primary node, execute the nfs_xmnt script on each server
that will NFS-mount the file systems.
/etc/cmcluster/nfs/nfs1_xmnt start
Hewlett-Packard recommends that you execute the nfs_xmnt script from the command
line after the package is active on the primary node. However, you can configure the
nfs_xmnt script to be executed by the NFS control script in the
customer_defined_run_cmds function.
function customer_defined_run_cmds
{
/etc/cmcluster/nfs/nfs1_xmnt start
remsh sage /etc/cmcluster/nfs/nfs1_xmnt start
}
The second line in the function invokes remsh to run the nfs_xmnt script on remote host
sage.
Running the nfs_xmnt script from the NFS control script guarantees that the package is
active before the mount command executes. It prevents cross-mounted servers from becoming
deadlocked while each server hangs on the mount command, waiting for the other server's
package to become active. However, if the package fails to activate, or if the remsh command
fails, the file systems will not be mounted, and no error will be returned. The only way to
be sure the file systems are mounted successfully is to run the nfs_xmnt script manually
on each host where the file systems should be mounted.
For an example of a configuration with cross-mounted servers, see “Example Four - Two Servers
with NFS Cross-Mounts” (page 62).
Creating the Cluster Configuration File and Bringing Up the Cluster
To create the cluster configuration file, verify the cluster and package configuration files, and
run the cluster, perform the following steps:
1. Use the cmquerycl command in the following manner to create the cluster configuration
file from your package configuration files. You must run this command on all nodes in the
cluster:
cmquerycl -v -C /etc/cmcluster/nfs/cluster.conf -n basil -n sage -n thyme
2. Set the FIRST_CLUSTER_LOCK_VG and MAX_CONFIGURED_PACKAGES variables in the
cluster.conf script on each node.
3. Verify the cluster and package configuration files on each node using the following command:
cmcheckconf -k -v -C /etc/cmcluster/nfs/cluster.conf -P /etc/cmcluster/nfs/nfs1.conf
-P /etc/cmcluster/nfs/nfs2.conf ...
4. Activate the cluster lock volume group (corresponding to the FIRST_CLUSTER_LOCK_VG
value) on one node using the following command:
vgchange -a y /dev/vg_nfsu01
5. Verify and apply the cluster and package configuration files using the following command:
cmapplyconf -v -C /etc/cmcluster/nfs/cluster.conf -P /etc/cmcluster/nfs/nfs1.conf
-P /etc/cmcluster/nfs/nfs2.conf ...
6. Deactivate the cluster lock volume group using the following command:
Configuring a Serviceguard NFS Package 35