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
Starting a Serviceguard NFS failover package
Use the following procedure to start a failover package.
1. Verify the cluster and package configuration files on each server.
# cmcheckconf -k -v –C /etc/cmcluster/cluster.conf –P /etc/cmcluster/nfs_modular/nfs1.conf –P
/etc/cmcluster/nfs_modular/nfs2.conf
2. Verify and apply the cluster package configuration files on a single server.
# cmapplyconf –v –C /etc/cmcluster/cluster.conf –P /etc/cmcluster/nfs_modular/nfs1.conf –P
/etc/cmcluster/nfs_modular/nfs2.conf
3. Run the failover packages.
# cmrunpkg –n thyme –v SG-NFS1
# cmrunpkg –n basil –v SG-NFS2
4. If you run the cmviewcl command, the output is similar to the following:
# cmviewcl
CLUSTER STATUS
cluster1 up
NODE STATUS STATE
thyme up running
PACKAGE STATUS STATE AUTO_RUN NODE
SG-NFS1 up running enabled thyme
NODE STATUS STATE
basil up running
PACKAGE STATUS STATE AUTO_RUN NODE
SG-NFS2 up running enabled basil
MULTI_NODE_PACKAGES
PACKAGE STATUS STATE AUTO_RUN SYSTEM
SG-CFS-pkg up running enabled yes
SG-CFS-DG-1 up running enabled no
SG-CFS-MP-1 up running enabled no
SG-CFS-MP-2 up running enabled no
SG-NFS-XP-1 up running enabled no
Serviceguard NFS modular package over CFS Packages with File Locking
Serviceguard NFS over CFS packages that require file locking are similar to Serviceguard NFS
over VxFS packages. The main differences are that there is no file system to configure in the
package configuration file, since the CFS multi-node packages already mount the CFS file systems,
and the package dependencies are added on the CFS packages. Figure 2-3 (page 44) illustrates
an example of a Serviceguard NFS package over a CFS configuration with two servers, each with
an NFS failover package.
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 every server that exports CFS. Use the following procedure to configure the
failover package.
Configuring Serviceguard NFS Modular Package over CFS Packages 63