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

Do not configure these exported directories in the/etc/exports file. When an
NFS server boots up, it attempts to export all file systems in its /etc/exports
file. If those file systems are not currently present on the NFS server node, the node
cannot boot properly. This happens if the server is an adoptive node for a file
system, and the file system is available on the server only after failover of the
primary node.
2. If you wish to monitor NFS services (by running the NFS monitor script), set the
NFS_SERVICE_NAME and NFS_SERVICE_CMD variables; see the following example:
NFS_SERVICE_NAME[0]=nfs1.monitor
NFS_SERVICE_CMD[0]=/etc/cmcluster/nfs/nfs.mon
If you enable the File Lock Migration feature, ensure that the monitor script name
is unique for each package (for example, nfs1.mon). If the File Lock Migration
feature is disabled, the monitor script name does not have to be unique to each
package (for example, nfs.mon). Multiple instances of the monitor script can run
on the same node without any problem. If a package fails over, only the instance
associated with that package is killed.
3. You do not have to run the NFS monitor script. If your NFS package configuration
file specifies AUTO_RUN YES and LOCAL_LAN_FAILOVER_ALLOWED YES (the
defaults), the package switches to the next adoptive node or to a standby network
interface in the event of a node or network failure. The NFS monitor script causes
the package failover if any of the monitored NFS services fails.
If you do not want to run the NFS monitor script, comment out the
NFS_SERVICE_NAME and NFS_SERVICE_CMD variables:
# NFS_SERVICE_NAME[0]=nfs.monitor
# NFS_SERVICE_CMD[0]=/etc/cmcluster/nfs/nfs.mon
By default, the NFS_SERVICE_NAME and NFS_SERVICE_CMD variables are
commented out, and the NFS monitor script is not run.
NOTE: The Serviceguard A.11.13 configuration file includes the following
changes:
• AUTO_RUN replaces obsolete PKG_SWITCHING_ENABLED.
• LOCAL_LAN_FAILOVER_ALLOWED replaces obsolete
NET_SWITCHING_ENABLED.
4. To enable File Lock Migration (available on 11i v1 and 11i v2), set the
NFS_FILE_LOCK_MIGRATION variable to 1:
NFS_FILE_LOCK_MIGRATION=1
By default, this variable is set to 0 (disabled). The NFS_FLM_SCRIPT variable is
the name of the script that manages synchronization of the file lock status entries
for the primary and adoptive nodes associated with this HA/NFS package. By
Configuring a Serviceguard NFS Package 33