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

Figure 2-3 Serviceguard NFS over CFS with file locking
Configuring a Serviceguard NFS failover package
Configuring a Serviceguard NFS failover package for a CFS environment is similar to configuring
the package for a non-CFS environment. The main difference is that you must configure one
failover package for each server that exports CFS. Use the following procedure to configure a
failover package.
1. Copy the following scripts and make a spearate copy for each package (one package for
each server)
# cd /etc/cmcluster/nfs
# cmmakepkg -p /etc/cmcluster/nfs/nfs1.conf
# cmmakepkg -s /etc/cmcluster/nfs/nfs1.cntl
# cp /opt/cmcluster/nfs/hanfs.sh hanfs.1.sh
# cp /opt/cmcluster/nfs/nfs.mon nfs1.mon
# cp /opt/cmcluster/nfs/nfs.flm nfs1.flm
# cmmakepkg -p /etc/cmcluster/nfs/nfs2.conf
# cmmakepkg -s /etc/cmcluster/nfs/nfs2.cntl
# cp /opt/cmcluster/nfs/hanfs.sh hanfs.2.sh
# cp /opt/cmcluster/nfs/nfs.mon nfs2.mon
# cp /opt/cmcluster/nfs/nfs.flm nfs2.flm
2. Edit the nfs.cntl scripts (nfs1.cntl, nfs2.cntl). Do not modify the FILESYSTEMS section (leave
it commented out), since the file systems are mounted and unmounted by the CFS packages.
Specify the IP address for the package and the subnet to which the IP address belongs.
IP[0]=15.13.114.243
SUBNET[0]=15.13.112.0
This IP address is the relocatable IP address for the package. NFS clients that mount the file
systems in the package will use this IP address to identify the server. You should configure
a name for this address in the DNS, NIS or LDAP database, or in the /etc/hosts file.
3. Set the HA_NFS_SCRIPT_EXTENSION to 1.sh in the nfs1.cntl file
HA_NFS_SCRIPT_EXTENSION = "1.sh"
This will set the NFS specific control script to be run by the package to hanfs.1.sh as we have
named it in the copy command above. Set this to 2.sh in nfs2.cntl.
4. Edit the hanfs.sh scripts (hanfs.1.sh and hanfs.2.sh) as follows
44 Installing and Configuring Serviceguard NFS Legacy Package