Managing Serviceguard NFS for Linux, July 2007

Installing and Configuring Serviceguard NFS for Linux
Configuring a Serviceguard NFS Package
Chapter 2 37
test_return 51
NOTE A Serviceguard package can support multiple relocatable 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 is 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 RedHat 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=”/pkg1a/sm”
The above directory should be present in one of the file systems
specified in the package control script.
c. PROPAGATE_INTERVAL: