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
6. Edit the nfs.conf scripts (nfs1.conf and nfs2.conf
a. Specify the package name
PACKAGE_NAME SG-NFS1
b. In nfs2.conf set the PACKAGE_NAME to SG-NFS2
c. Set the NODE_NAME variables for each node that can run the package. The first
NODE_NAME should specify the primary node, followed by adoptive node(s) in the
order in which they will be tried
NODE_NAME thyme
NODE_NAME basil
d. Set the RUN_SCRIPT and HALT_SCRIPT variables to the full path of the control script,
with no timeout
RUN_SCRIPT /etc/cmcluster/nfs/nfs1.cntl
RUN_SCRIPT_TIMEOUT NO_TIMEOUT
HALT_SCRIPT /etc/cmcluster/nfs/nfs1.cntl
HALT_SCRIPT_TIMEOUT NO_TIMEOUT
Similarly, set the RUN_SCRIPT and HALT_SCRIPT variables to
/etc/cmcluster/nfs/nfs2.cntl in nfs2.conf
e. Set the DEPENDENCY_NAME, DEPENDENCY_CONDITION, and
DEPENDENCY_LOCATION variables so that the failover package will only run if the
corresponding CFS package is already running. In nfs1.conf set these to
DEPENDENCY_NAME SG-CFS-XP-1-dep
DEPENDENCY_CONDITION SG-CFS-XP-1=UP
DEPENDENCY_LOCATION SAME_NODE
In nfs2.conf set these to
DEPENDENCY_NAME SG-CFS-XP-2-dep
DEPENDENCY_CONDITION SG-CFS-XP-2=UP
DEPENDENCY_LOCATION SAME_NODE
f. To monitor NFS services, set the SERVICE_NAME variable in nfs1.conf
SERVICE_NAME nfs1.monitor
g. In nfs2.conf, set SERVICE_NAME to nfs2.monitor. The SERVICE_NAME variable in
the nfs.conf scripts must match the NFS_SERVICE_NAME[0] variable in the
hanfs.sh.script. If you do not want to monitor NFS services, leave this variable
commented out.
h. Set the SUBNET variable in both nfs1.conf and nfs2.conf
SUBNET 15.13.112.0
Starting a Serviceguard NFS failover package
Use the following procedure to start a failover package
1. Copy the configuration files to each server in the cluster
# rcp -p /etc/cmcluster/nfs/* (hostname):/etc/cmcluster/nfs
2. Verify the cluster and package configuration files on each server
# cmcheckconf -k -v -C /etc/cmcluster/cluster.conf -P /etc/cmcluster/nfs/nfs1.conf
-P /etc/cmcluster/nfs/nfs2.conf -P /etc/cmcluster/nfs/nfs2.conf
3. Verify and apply the cluster package configuration files on a single server
# cmapplyconf -v -C /etc/cmcluster/cluster.conf -P /etc/cmcluster/nfs/nfs1.conf
-P /etc/cmcluster/nfs/nfs2.conf
46 Installing and Configuring Serviceguard NFS Legacy Package