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
e. 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
f. Add node_name variables for each server in the cluster that will run the export package
(the order of the servers does not matter).
node_name thyme
node_name basil
g. 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
h. Comment out the service_name, service_cmd, service_restart, service_fail_fast_enabled
and service_halt_timeout variables.
# service_name nfs.monitor
# service_cmd "$SGCONF/scripts/nfs/nfs_upcc.mon"
# service_restart none
# service_fail_fast_enabled no
# service_halt_timeout 0
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 if 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 (the exportfs multi-node package
will not fail).
Starting a Serviceguard NFS export package
Use the following procedure to start an export 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/nfs-export.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/nfs-export.conf
3. Run the export package on a single server with the following command:
# cmrunpkg –v SG-NFS-XP-1
4. You can verify if the export package is running with the cmviewcl command. The output
is similar to the following:
# cmviewcl
CLUSTER STATUS
cluster1 up
NODE STATUS STATE
thyme up running
NODE STATUS STATE
basil up running
Configuring Serviceguard NFS Modular Package over CFS Packages 61