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
13. Modify the MONITOR_DAEMONS_RETRY parameter, that represents the number of attempts
to ping the rpc.statd, rpc.mountd, nfsd, rpc.pcnfsd and file lock migration
script, processes before exiting. The default is 4 attempts. An example for this parameter
is as follows:
For nfs.conf generated on Serviceguard A.11.18
MONITOR_DAEMONS_RETRY 4
For nfs.conf generated on Serviceguard A.11.19
nfs/hanfs_export/MONITOR_DAEMONS_RETRY 4
14. Modify the PORTMAP_RETRY parameter, that represents the number of attempts to ping the
rpcbind process before exiting. The default is 4 attempts. An example for this parameter
is as follows:
For nfs.conf generated on Serviceguard A.11.18
PORTMAP_RETRY 4
For nfs.conf generated on Serviceguard A.11.19
nfs/hanfs_export/PORTMAP_RETRY 4
15. The FLM_HOLDING_DIR variable defines the holding directory in a disk volume associated
with the HA/NFS package. This directory contains copies of the files from the /var/
statmon/sm directory and is migrated with the HA/NFS package during a failover. The
contents of this directory are used to populate the /var/statmon/sm directory when
recovering from a failover event. The NFSV4_FLM_HOLDING_DIR variable defines the
directory that will contain copies of the files from the /var/nfs4/v4_state directory
when NFSv4 is enabled.
You must dedicate this directory for holding v4_state entries only. In addition, you must
keep it empty. This directory should not have other files or subdirectories when starting the
cluster. All files in this directory are deleted after a failover. This directory must be located
in the same shared volume as FLM_HOLDING_DIR. An example for this parameter is as
follows:
For nfs.conf generated on Serviceguard A.11.18
FLM_HOLDING_DIR "/export/sm"
NFSV4_FLM_HOLDING_DIR "/export/nfsv4"
For nfs.conf generated on Serviceguard A.11.19
nfs/hanfs_flm/FLM_HOLDING_DIR "/export/sm"
nfs/hanfs_flm/NFSV4_FLM_HOLDING_DIR "/export/nfsv4"
16. Modify the PROPAGATE_INTERVAL parameter, that represents the number of seconds
between the attempts of the script to copy files from the /var/statmon/sm directory into
the holding directory, specified by FLM_HOLDING_DIR. The default value of this parameter
is 5 seconds. An example for this parameter is as follows:
For nfs.conf generated on Serviceguard A.11.18
PROPAGATE_INTERVAL 5
For nfs.conf generated on Serviceguard A.11.19
nfs/hanfs_flm/PROPAGATE_INTERVAL 5
Configuring a Serviceguard NFS Modular Package 55