Managing MC/ServiceGuard NFS A.11.11.03 and A.11.23.02 (June 2004)

Installing and Configuring MC/ServiceGuard NFS
Configuring an MC/ServiceGuard NFS Package
Chapter 242
# 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 MC/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 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)” on page 43).
B5140-90020.book Page 42 Thursday, June 3, 2004 5:04 PM