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 3-1 Server-to-Server Cross-Mounting
The advantage of server-to-server cross-mounting is that every server has an identical view of
the file systems. The disadvantage is that, on the node where a file system is locally mounted,
the file system is accessed through an NFS mount, which has poorer performance than a local
mount.
In order to make a Serviceguard file system available to all servers, all servers must NFS-mount
the file system. By doing so, access to the file system is not interrupted when the package fails
over to an adoptive node. An adoptive node cannot access the file system through the local
mount, because it would have to unmount the NFS-mounted file system before it can mount it
locally. Also, unmount the NFS-mounted file system, it must kill all processes using the file
system.
To set up an NFS package with file systems that are NFS-mounted by Serviceguard NFS servers,
complete the following steps:
1. Create a package specific directory at /etc/cmcluster/nfs/pkg1.
2. Make a copy of the /opt/cmcluster/nfs/nfs_xmnt script.
cd /etc/cmcluster/nfs/pkg1
cp /opt/cmcluster/nfs/nfs_xmnt nfs1_xmnt
3. In the copy of the nfs_xmnt script, create an SNFS[n] and CNFS[n] variable for each file
system in the package that will be NFS-mounted by servers. The SNFS[n] variable is the
Configuring a Serviceguard NFS Modular Package 57