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
• Initiates the NFS monitor script to check periodically on the health of NFS services, if you
have configured your NFS package to use the monitor script.
• Exports each file system associated with the package so that it can later be NFS-mounted
by clients.
• Assigns a package IP address to the LAN card on the current node.
After this sequence, the NFS server is active, and clients can NFS-mount the exported file systems
associated with the package.
Starting File Lock Migration
If you call the control script with the file_lock_migration parameter after enabling the File
Lock Migration feature, the control script does the following:
• Populates the /var/statmon/sm directory with the Status Monitor entries from the
configured holding directory of the package, and subsequently removes the entries from
the holding directory.
• Kills any running copy of the NFS File Lock Recovery synchronization script.
• Halts the rpc.statd and rpc.lockd daemons to release file locks so that file systems can
be unmounted. If the server is also an NFS client, it loses the NFS file locks obtained by
client-side processes when these daemons are killed.
• Restarts the rpc.statd and rpc.lockd daemons so that these daemons can manage file
locks for other NFS packages running on the server. Restarting these daemons also triggers
a crash recovery notification event, whereby rpc.statd sends crash notification messages
to all clients listed in the /var/statmon/sm directory.
• Starts the File Lock Migration synchronization script, which periodically copies the /var/
statmon/sm directory entries to the holding directory.
Halting the NFS Services
When called with the stop parameter, the control script does the following:
• Removes the package IP address from the LAN card on the current node.
• Un-exports all file systems associated with the package so that they can no longer be
NFS-mounted by clients.
• Halts the monitor process.
• Halts the File Lock Migration synchronization script if you enable the File Lock Migration
feature (available on 11i v1 and 11i v2).
• Halts the rpc.statd and rpc.lockd daemons to release file locks so that file systems can
be unmounted. If the server is also an NFS client, it loses the NFS file locks obtained by
client-side processes when these daemons are killed.
• Restarts the rpc.statd and rpc.lockd daemons so that these daemons can manage file
locks for other NFS packages running on the server.
• Unmounts each file system associated with the package.
• Deactivates each volume group associated with the package.
After this sequence, the NFS package is inactive on the current node and may start up on an
alternate node or be restarted later on the same node.
Monitoring the NFS Services
The monitor script /etc/cmcluster/nfs/nfs.mon works by periodically checking the status
of NFS services using the rpcinfo command. If any service fails to respond, the script exits,
causing a switch to an adoptive node. The monitor script provides the ability to monitor the
22 Overview of Serviceguard NFS