Serviceguard NFS Toolkit A.11.31.02, A.11.11.06, and A.11.23.05 Administrator's Guide

default, this is set to nfs.flm. You must assign a unique name to this script in
every HA/NFS package in the cluster (for example, nfs1.flm, nfs2.flm, and so on):
NFS_FLM_SCRIPT="${0%/*}/nfs1.flm"
If you wish to monitor the File Lock Migration script, then you must also set the
NFS_FILE_LOCK_MIGRATION and NFS_FLM_SCRIPT variables in the NFS monitor
script.
If you enable File Lock Migration, then you can configure the File Lock Migration
script (see “Editing the File Lock Migration Script (nfs.flm)” (page 34)).
NOTE: The file name of theNFS_FLM_SCRIPT script must be limited to 13 characters
or fewer.
Editing the File Lock Migration Script (nfs.flm)
The File Lock Migration script, nfs.flm, handles the majority of the work involved
in maintaining file lock integrity that follows an HA/NFS failover. The nfs.flm script
includes the following configurable parameters:
• 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/statmon/sm files 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 keep it empty. 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="/pkg1a/sm"
• PROPAGATE_INTERVAL - Number of seconds between the attempts of the script
to copy files from the /var/statmon/sm directory 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
34 Installing and Configuring Serviceguard NFS