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

NOTE: If the package is getting configured to have NFS file lock migration feature, it is
strongly recommended to list the hanfs module as the last module name parameter in the
cmmakepkg command.
Example 3-1 In the example below, two module names mod1 and mod2 are configured with
hanfs module. The hanfs is specified as the last module name in the cmmakepkg command.
cmmakepkg -m mod1 -m mod2 -m nfs/hanfs /etc/cmcluster/pkg1/nfs.conf
Before Creating a Serviceguard NFS Package
Before creating a Serviceguard NFS package, complete the following tasks:
1. Set up the Serviceguard cluster. For more information on setting up the Serviceguard cluster,
see the Managing Serviceguard manual.
2. On the primary node and all adoptive nodes for the NFS package, set the NFS_SERVER
variable to 1 in the /etc/rc.config.d/nfsconf file.
NFS_SERVER=1
Do not configure the exported directories in the /etc/exports file. When an NFS server
boots up, it attempts to export all file systems in its /etc/exports file. If those file systems
are not currently present on the NFS server node, the node cannot boot properly. This
happens if the server is an adoptive node for a file system, and the file system is available
on the server only after failover of the primary node.
3. If your NFS servers must serve PC clients, set the PCNFS_SERVER variable to 1 in the /etc/
rc.config.d/nfsconf file on the primary node and each adoptive node.
PCNFS_SERVER=1
If you run the NFS monitor script, setting the PCNFS_SERVER variable to 1 will cause the
monitor script to monitor the pcnfsd daemon. Then, if the pcnfsd daemon fails, your NFS
package will failover to an adoptive node. If you do not want to monitor pcnfsd, do not
run the NFS monitor script, or set the PCNFS_SERVER variable to 0 and run pcnfsd manually
from the command line.
4. If your NFS servers also functions as NFS clients, set the START_MOUNTD variable to 1 in
the /etc/rc.config.d/nfsconf file on the primary node and each adoptive node.
START_MOUNTD=1
If you configure rpc.mountd in the /etc/inetd.conf file, set the START_MOUNTD variable
to 0. If the START_MOUNTD variable is set to 0, the NFS monitor script will not monitor the
rpc.mountd process. If the START_MOUNTD variable is set to 1, and you run the NFS monitor
script, your NFS package will fail over to an adoptive node if rpc.mountd fails.
5. On the primary node and all adoptive nodes for the NFS package, set the NUM_NFSD variable
in the /etc/rc.config.d/nfsconf file to the number of nfsd daemons required to
support all the NFS packages that could run on that node at once. It is better to run too many
nfsd processes than too few. In general, you should configure a minimum of four nfsd
processes and at least two nfsd processes for each exported file system. So, for example, if
a node is the primary node for a package containing two exported file systems, and it is an
adoptive node for another package containing three exported file systems, you should
configure it to run at least 10 nfsd processes.
NUM_NFSD=10
6. Start the NFS server process on the primary node and all adoptive nodes.
/sbin/init.d/nfs.server start
50 Installing and Configuring Serviceguard NFS Modular Package