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
XFS[0]="/cfs1"
XFS[1]="/cfs2"
CAUTION: Do not modify other variables or contents in this script since doing so is not
supported.
5. Edit the nfs-export.conf file as follows:
a. Set the PACKAGE_NAME variable to SG-NFS-XP-1 (by default this variable is set to
FAILOVER)
PACKAGE_NAME SG-NFS-XP-1
b. Change the PACKAGE_TYPE from FAILOVER to MULTI_NODE
PACKAGE_TYPE MULTI_NODE
c. Comment out the FAILOVER_POLICY and FAILBACK_POLICY since this package
will run on each server and will not failover if a server fails
#FAILOVER_POLICY CONFIGURED_NODE
#FAILBACK_POLICY MANUAL
d. Add NODE_NAME variables for each sever in the cluster that will run the export
package (the order of the servers does not matter)
NODE_NAME thyme
NODE_NAME basil
e. Set the RUN_SCRIPT and HALT_SCRIPT variables to the full path of the control script,
with no timeout
RUN_SCRIPT /etc/cmcluster/nfs/nfs-export.cntl
RUN_SCRIPT_TIMEOUT NO_TIMEOUT
HALT_SCRIPT /etc/cmcluster/nfs/nfs-export.cntl
HALT_SCRIPT_TIMEOUT NO_TIMEOUT
f. Set the DEPENDENCY_NAME, DEPENDENCY_CONDITION, and
DEPENDENCY_LOCATION variables so that the export package will only run if the
Serviceguard CFS multi-node packages are already running. Since there are two CFS
file systems in this example, there are also two CFS multi-node packages
DEPENDENCY_NAME SG-CFS-MP-1-dep
DEPENDENCY_CONDITION SG-CFS-MP-1=UP
DEPENDENCY_LOCATION SAME_NODE
DEPENDENCY_NAME SG-CFS-MP-2-dep
DEPENDENCY_CONDITION SG-CFS-MP-2=UP
DEPENDENCY_LOCATION SAME_NODE
NOTE: The NFS export multi-node package does not monitor exported file systems. For
example, if a file system becomes unexported or inaccessible. It checks that the CFS dependent
packages have access to the file systems. If the NFS failover package loses access and cannot
read or write to the disk, it will fail. However, the exportfs multi-node package will not fail.
Starting a Serviceguard NFS export package
Use the following procedure to start an export 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/nfs-export.conf
3. Verify and apply the cluster package configuration files on a single server
40 Installing and Configuring Serviceguard NFS Legacy Package