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

The rest of the configuration is dependent upon whether or not the cluster requires file locking
(as described in the “Limitations and Issues with the current CFS implementation” (page 15)).
If file locking is not required, follow the instructions in section “Serviceguard NFS Modular
Package over CFS Packages without File Locking” (page 60). If file locking is required, follow
the instructions in section “Serviceguard NFS modular package over CFS Packages with File
Locking” (page 63).
Serviceguard NFS Modular Package over CFS Packages without File Locking
Each active server in the cluster needs to run an export multi-node package and an NFS failover
package. An export multi-node package is a package that runs on each server in the cluster and
exports all the cluster file systems. Each standby server (i.e. a server that is an adoptive node for
NFS failover packages) needs to have an export multi-node package running to be able to become
active in the event of a failover. Figure 2-2 (page 38) shows an example Serviceguard over CFS
configuration with two servers, each with an NFS failover package and a multi-node export
package.
Configuring a Serviceguard NFS export package
There should only be one NFS export multi-node package per cluster. This package will run on
each server in the cluster.
NOTE: All steps in this section must be completed on a single server.
1. Create the nfs-export.conf file with the cmmakepkg command.
# cd /etc/cmcluster/nfs_modular
# cmmakepkg -m sg/all -m nfs/hanfs /etc/cmcluster/nfs_modular/nfs-export.conf
This command creates the package configuration file by including the parameters from the
modules all and hanfs, where,
all refers to a set of standard Serviceguard modules.
hanfs refers to the HA-NFS module.
2. Edit the nfs-export.conf file as follows:
a. Specify each NFS directory to be exported. In this example, these NFS directories are
the same as the CFS file systems that are mounted (you could have CFS file systems
mounted and not export them, or export only a subdirectory of a mounted file system).
b. Add an XFS variable for each NFS directory to be exported. Specify the directory name
and any export options. These directories must not be included in the /etc/exports
file.
For nfs-export.conf generated on HP Serviceguard A.11.18:
XFS “/cfs1”
XFS “/cfs2”
For nfs-export.conf generated on HP Serviceguard A.11.19:
nfs/hanfs_export/XFS “/cfs1”
nfs/hanfs_export/XFS “/cfs2”
c. Set the package_name variable to SG-NFS-XP-1 (by default this variable is set to
FAILOVER).
package_name SG-NFS-XP-1
d. Change the package_type from failover to multi_node.
package_type multi_node
60 Installing and Configuring Serviceguard NFS Modular Package