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

NODE_NAME thyme NODE_NAME basil NODE_NAME sage
4. Set the RUN_SCRIPT and HALT_SCRIPT variables to the full path name of the
control script (/etc/cmcluster/nfs/nfs.cntl or whatever you have renamed
it). You do not have to specify a timeout for either script.
RUN_SCRIPT /etc/cmcluster/nfs/nfs1.cntl
RUN_SCRIPT_TIMEOUT NO_TIMEOUT
HALT_SCRIPT /etc/cmcluster/nfs/nfs1.cntl
HALT_SCRIPT_TIMEOUT NO_TIMEOUT
5. If you want to run the NFS monitor script, set the SERVICE_NAME variable to
indicate the NFS monitor script:
SERVICE_NAME nfs1.monitor
Each package must have a unique service name. The SERVICE_NAME variable in
the package configuration file must match the NFS_SERVICE_NAME variable in
the NFS control script.
If you do not want to run the NFS monitor script, comment out the SERVICE_NAME
variable:
# SERVICE_NAME nfs.monitor
6. Set the SUBNET variable to the subnet that will be monitored for the package.
SUBNET 15.13.112.0
You can use the default values for the rest of the variables in the package configuration
file, or you can change them as needed. For instructions on modifying the default
values, see the Managing Serviceguard manual, or read the comments in the
/opt/cmcluster/nfs/nfs.conf template file.
Configuring Server-to-Server Cross-Mounts (Optional)
Two NFS server nodes may NFS-mount each other’s file systems and still act as adoptive
nodes for each other’s NFS server packages. Figure 2-1 illustrates this configuration.
Configuring a Serviceguard NFS Package 37