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
1. Create the nfs.conf file for each package with the cmmakepkg command (one package for
each server).
# cd /etc/cmcluster/nfs_modular
# cmmakepkg -m sg/all -m nfs/hanfs /etc/cmcluster/nfs_modular/nfs1.conf
# cmmakepkg -m sg/all -m nfs/hanfs /etc/cmcluster/nfs_modular/nfs2.conf
2. Edit the nfs.conf files (nfs1.conf, nfs2.conf) as follows:
a. Specify the IP address for the package and the subnet to which the IP address belongs.
ip_subnet 15.13.112.0
ip_address 15.13.114.243
This IP address is the relocatable IP address for the package. NFS clients that mount
the file systems in the package use this IP address to identify the server. You must
configure a name for this address in the DNS, NIS, or LDAP database, or in the /etc/
hosts file.
b. Set the exported directory in nfs1.conf as follows:
For nfs1.conf generated on HP Serviceguard A.11.18:
XFS “/cfs1”
For nfs1.conf generated on HP Serviceguard A.11.19:
nfs/hanfs_export/XFS “/cfs1”
In nfs2.conf, set the exported directory to “/cfs2”.
c. By default the service_name is enabled and is set to nfs.monitor. If you want to monitor
NFS services by running the NFS monitor script, then change nfs.monitor to a unique
name for each package.
service_name nfs1.monitor
service_cmd "$SGCONF/scripts/nfs/nfs_upcc.mon"
service_restart none
service_fail_fast_enabled no
service_halt_timeout 0
In nfs2.conf, set the service_name variable to nfs2.monitor. If you do not want to monitor
NFS services, comment out the service_name, service_cmd, service_restart,
service_fail_fast_enabled and service_halt_timeout variables.
d. To enable File Lock Migration, set the FILE_LOCK_MIGRATION variable to 1.
For nfs1.conf generated on HP Serviceguard A.11.18:
FILE_LOCK_MIGRATION 1
For nfs1.conf generated on HP Serviceguard A.11.19:
nfs/hanfs_export/FILE_LOCK_MIGRATION
e. The FLM_HOLDING_DIR variable defines the holding directory associated with the
package. Specify the FLM_HOLDING_DIR as below:
For nfs1.conf generated on HP Serviceguard A.11.18:
FLM_HOLDING_DIR "/cfs1/sm"
For nfs1.conf generated on HP Serviceguard A.11.19:
nfs/hanfs_flm/FLM_HOLDING_DIR "/cfs1/sm"
In nfs2.conf, set the variable to “/cfs2/sm”.
f. Specify the package name:
package_name SG-NFS1
In nfs2.conf, set the package_name to SG-NFS2.
g. The package_type should be set to the default value (failover).
64 Installing and Configuring Serviceguard NFS Modular Package