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

4 Migration of Serviceguard NFS Legacy Package to
Serviceguard NFS Modular Package
This chapter explains how to migrate from the current Serviceguard NFS Legacy package to the
new Serviceguard NFS Modular package.
The migration of the Legacy packages to the Modular package configuration is done using the
cmmigratepkg command. The cmmigratepkg command automates the migration of a legacy
package to a modular package for standard Serviceguard module parameters. The NFS module
parameters need to be manually configured in the modular package. The syntax of cmmigratepkg
command is as follows:
cmmigratepkg –p <package_name> [-x<external_script_name>] -o <output_file>
The package must be a configured legacy package and should be brought to offline state before
starting the migration. The cmmigratepkg command reads control script of the package.
Therefore, the control script must be located on the node where the command is run.
For detailed information on migrating packages from legacy to modular style, see the Migrating
Packages from Legacy to Modular Style at http://docs.hp.com/en/ha.html
Migrating a sample legacy package with control script
This section explains about migrating a sample legacy package (pkg01) with control script
(nfs1.cntl) and configuration file (nfs1.conf) located in /etc/cmcluster/nfs directory
to the modular style. The NFS specific control scripts for this example are hanfs.1.sh, nfs1.mon
and nfs1.flm.
Perform the following steps to migrate the Legacy package to Modular package configuration.
1. The package must be a configured legacy package and should be brought to offline state
using cmhaltpkg command.
cmhaltpkg pkg01
2. Enter the directory where the legacy NFS package configuration file (.conf) and the control
script (.cntl) to be migrated are stored.
cd /etc/cmcluster/nfs
Create another directory to hold the contents of the migrated files and set the permission to
744.
mkdir /etc/cmcluster/nfs/modular
chmod 744 /etc/cmcluster/nfs/modular
3. Comment the HA_NFS_SCRIPT_EXTENSION variable definition in the package control
script. The following line must be commented in the nfs1.cntl file.
# HA_NFS_SCRIPT_EXTENSION = "1.sh"
4. Comment the service specific parameter definitions in the package configuration file. The
following lines must be commented in the nfs1.conf file.
# SERVICE_NAME nfs1.monitor
# SERVICE_FAIL_FAST_ENABLED NO
# SERVICE_HALT_TIMEOUT 300
5. Run cmapplyconf command to apply the above two configuration changes to the legacy
package.
cmapplyconf -P /etc/cmcluster/nfs/nfs1.conf
Modify the package configuration ([y]/n)? y
Completed the cluster update
Migrating a sample legacy package with control script 67