Serviceguard NFS Toolkit A.11.11.06, A.11.23.05 and A.11.31.08 Administrator's Guide (October 2011)

All files in this directory are deleted after a failover. This directory must be located in the same
shared volume as FLM_HOLDING_DIR. An example for this parameter is as follows:
For nfs.conf generated on Serviceguard A.11.18
FLM_HOLDING_DIR "/export/sm"
NFSV4_FLM_HOLDING_DIR "/export/nfsv4"
For nfs.conf generated on Serviceguard A.11.19
nfs/hanfs_flm/FLM_HOLDING_DIR "/export/sm"
nfs/hanfs_flm/NFSV4_FLM_HOLDING_DIR "/export/nfsv4"
17. Modify the PROPAGATE_INTERVAL parameter, that represents the number of seconds between
the attempts of the script to copy files from the /var/statmon/sm directory into the holding
directory, specified by FLM_HOLDING_DIR. The default value of this parameter is 5 seconds.
An example for this parameter is as follows:
For nfs.conf generated on Serviceguard A.11.18
PROPAGATE_INTERVAL 5
For nfs.conf generated on Serviceguard A.11.19
nfs/hanfs_flm/PROPAGATE_INTERVAL 5
NOTE: If you enable the File Lock Migration feature, an NFS client (or a group of clients)
may encounter a situation where requesting a file lock on the HA/NFS server and not receiving
a crash recovery notification message when the HA/NFS package migrates to an adoptive
node. This occurs only when the NFS client sends its initial lock request to the HA/NFS server
and then the HA/NFS package moves to an adoptive node before the FLM script copies the
/var/statmon/sm entry for this client to the package holding directory.
The probability of hitting this corner-case problem is not very high, because the SM file copy
interval is very short (by default, five seconds). The chances of an NFS client (or group of NFS
clients) sending its initial lock request (it must be the initial request, since this request generates
the /var/statmon/sm file) to the HA/NFS server and having the package migrate within
this same five seconds window are extremely unlikely.
If you encounter this situation often, reduce the copy time interval by setting the
PROPAGATE_INTERVAL parameter to a lower value.
18. Modify the STATMON_WAITTIME parameter, that represents the amount of time in seconds
to wait before starting the cycle that copies files from the /var/statmon/sm directory into
the holding directory. This allows time for rpc.statd to complete its file lock migration
process since rpc.statd is started just before this script. The default value of this parameter
is 90 seconds. An example for this parameter is as follows:
For nfs.conf generated on Serviceguard A.11.18
STATMON_WAITTIME 90
For nfs.conf generated on Serviceguard A.11.19
nfs/hanfs_flm/STATMON_WAITTIME 90
Configuring Server-to-Server Cross-Mounts (Optional)
Two NFS server nodes may NFS-mount each other's file systems and still act as adoptive nodes
for each other's NFS server packages. Figure 13 illustrates this configuration.
50 Installing and Configuring Serviceguard NFS Modular Package