Managing Serviceguard NFS for Linux, March 2009

NOTE: The argument to be passed to the HA_APP_SCRIPT for lock migration should
contain the same name or IP address used by the clients while mounting the exported file
system.
Example: If client mounts the NFS file system using the package name, specify the same in
customer_defined_run_cmds as shown below:
function customer_defined_run_cmds
{
$HA_APP_SCRIPT lock_migration:
<package name>
test_return 51
}
NOTE: A Serviceguard package can support multiple re-locatable IP addresses associated
with it. However, if lock migration feature is enabled then only one IP is allowed to be
specified in the NFS package control script since the NFS limits server reboot/failover
notification to be sent using only a single IP. In the package control script, only one IP/Subnet
address pair is allowed to be specified under IP_ADDRESS section.
3. Configure the following variables in hanfs.conf:
a. LOCK_MIGRATION:
To enable File Lock Migration, set the LOCK_MIGRATION variable to “YES”. By default
the variable is set to “NO”.
An example for this parameter is as follows: LOCK_MIGRATION=”YES”
b. NFS_FLM_HOLDING_DIR:
Name of a unique directory created in one of the shared volumes associated with this
package. This directory holds copies of the /var/lib/nfs/sm files on SLES and /var/
lib/nfs/statd/sm files on Red Hat for this package. You must create this directory
in one of the shared volumes associated with this package so that it can migrate with
the package (from the primary server to the adoptive server).
You must dedicate this directory for holding SM entries only. In addition, you must
not add any files as this directory is maintained by the toolkit. This directory should
not have other files or subdirectories when starting the cluster. All files in this directory
are deleted after a failover.
An example for this parameter is as follows: NFS_FLM_HOLDING_DIR=/ha_root/sm
The above directory should be present in one of the file systems specified in the package
control script.
c. PROPAGATE_INTERVAL:
Number of seconds between the attempts of the script to copy files from the /var/
lib/nfs/sm directory on SLES and /var/lib/nfs/statd/sm on Red Hat into the
holding directory, specified by NFS_FLM_HOLDING_DIR. The default value of this
parameter is five seconds.
An example for this parameter is as follows:
PROPAGATE_INTERVAL=5
26 Installing and Configuring Serviceguard NFS for Linux