Serviceguard NFS Toolkit A.11.11.06, A.11.23.05 and A.11.31.05 Administrator's Guide HP-UX 11i v1, v2, and v3
Table Of Contents
- Serviceguard NFS Toolkit A.11.11.06, A.11.23.05 and A.11.31.05 Administrator's Guide
- Table of Contents
- 1 Overview of Serviceguard NFS
- Limitations of Serviceguard NFS
- Overview of Serviceguard NFS Toolkit A.11.31.05 with Serviceguard A.11.18 (or later) and Veritas Cluster File System Support
- Overview of the Serviceguard NFS Modular Package
- Overview of the NFS File Lock Migration Feature
- Overview of NFSv4 File Lock Migration Feature
- Overview of Serviceguard NFS with Serviceguard A.11.17 Support
- Integrating Support for Cluster File Systems into Serviceguard NFS Toolkit
- Overview of Cluster File Systems in Serviceguard NFS Toolkit
- Limitations and Issues with the current CFS implementation
- Supported Configurations
- How the Control and Monitor Scripts Work
- 2 Installing and Configuring Serviceguard NFS Legacy Package
- Installing Serviceguard NFS Legacy Package
- Before Creating a Serviceguard NFS Legacy Package
- Configuring a Serviceguard NFS Legacy Package
- Copying the Template Files
- Editing the Control Script (nfs.cntl)
- Editing the NFS Control Script (hanfs.sh)
- Editing the File Lock Migration Script (nfs.flm)
- Editing the NFS Monitor Script (nfs.mon)
- Editing the Package Configuration File (nfs.conf)
- Configuring Server-to-Server Cross-Mounts (Optional)
- Creating the Cluster Configuration File and Bringing Up the Cluster
- Configuring Serviceguard NFS Legacy Package over CFS Packages
- 3 Installing and Configuring Serviceguard NFS Modular Package
- Installing Serviceguard NFS Modular Package
- Before Creating a Serviceguard NFS Modular Package
- Configuring a Serviceguard NFS Modular Package
- Configuring Serviceguard NFS Modular Package over CFS Packages
- 4 Migration of Serviceguard NFS Legacy Package to Serviceguard NFS Modular Package
- 5 Sample Configurations for Legacy Package
- Example One - Three-Server Mutual Takeover
- Example Two - One Adoptive Node for Two Packages with File Lock Migration
- Cluster Configuration File for Adoptive Node for Two Packages with File Lock Migration
- Package Configuration File for pkg01
- NFS Control Scripts for pkg01
- NFS File Lock Migration and Monitor Scripts for pkg01
- Package Configuration File for pkg02
- NFS Control Scripts for pkg02
- NFS File Lock Migration and Monitor Scripts for pkg02
- Example Three - Three-Server Cascading Failover
- Example Four - Two Servers with NFS Cross-Mounts
- 6 Sample Configurations for Modular Package
- Index

NOTE: The file name of the NFS_FLM_SCRIPT script must be limited to 13 characters or
fewer.
NOTE: The nfs.mon script uses rpcinfo calls to check the status of various processes. If the
rpcbind process is not running, the rpcinfo calls time out after 75 seconds. Because 10 rpcinfo
calls are attempted before failover, it takes approximately 12 minutes to detect the failure.
This problem has been fixed in release version 11.11.04 and 11.23.03.
2. You can call the nfs.mon script with the following optional arguments:
• INTERVAL - the time (in seconds) between the attempts for checking if NFS processes
are up and running. The default is 10 seconds.
• LOCKD_RETRY - the number of attempts to ping rpc.lockd before exiting. The
default is 4 attempts.
• STATD_RETRY, MOUNTD_RETRY, NFSD_RETRY, PCNFSD_RETRY and
NFS_FLM_RETRY - the number of attempts to ping the rpc.statd, rpc.mountd,
nfsd, rpc.pcnfsd, and nfs.flm processes before exiting. The default is 4 attempts.
• PORTMAP_RETRY - the number of attempts to ping the rpcbind process before
exiting. The default is 4 attempts.
These arguments are passed using the NFS_SERVICE_CMD line in the hanfs.sh file. In
order to set these optional arguments, all of the preceding arguments must also be specified
in the NFS_SERVICE_CMD line.
Editing the Package Configuration File (nfs.conf)
1. Serviceguard A.11.17 provides a new package configuration file template. The new package
configuration file template introduces the following dependency variables:
• DEPENDENCY_NAME
• DEPENDENCY_CONDITION
• DEPENDENCY_LOCATION
The above parameters are not supported in Serviceguard NFS Toolkit A.11.23.05. By default,
these variables are commented out in the nfs.conf file.
2. Set the PACKAGE_NAME variable.
PACKAGE_NAME pkg01
You can use the default package name if you will run only one Serviceguard NFS package
on your Serviceguard cluster. Each package must have a unique name.
3. Create a NODE_NAME variable for each node that will run the package. The first NODE_NAME
should specify the primary node. All the NODE_NAME variables following the primary node
should specify the adoptive nodes, in the order in which they will be tried.
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
34 Installing and Configuring Serviceguard NFS Legacy Package