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

LV[0]=/dev/nfsu03/lvol1; FS[0]=/hanfs/nfsu031; FS_MOUNT_OPT[0]="-o rw"
VXVOL="vxvol -g \$DiskGroup startall" #Default
FS_UMOUNT_COUNT=1
FS_MOUNT_RETRY_COUNT=0
IP[0]=15.13.114.245
SUBNET[0]=15.13.112.0
The hanfs.sh Control Script
This section shows the NFS control script (hanfs3.sh) for the pkg03 package in this sample
configuration. This example includes only the user-configured part of the script; the executable part
of the script and most of the comments are omitted. This example does not enable the File Lock
Migration feature.
XFS[0]=/hanfs/nfsu031
NFS_SERVICE_NAME[0]="nfs3.monitor"
NFS_SERVICE_CMD[0]="/etc/cmcluster/nfs/nfs.mon"
NFS_FILE_LOCK_MIGRATION=0
NFS_FLM_SCRIPT="${0%/*}/nfs.flm"
Example Two - One Adoptive Node for Two Packages with File Lock
Migration
This configuration has two packages, each owned by a different server. The adoptive node for
both packages is the same host. This sample configuration uses the package control option, which
prevents the adoptive node from adopting another package if it has already adopted one. Figure 16
illustrates this configuration.
Figure 16 One Adoptive Node for Two Packages
Figure 17 shows this sample configuration after host basil has failed. Host sage has adopted
pkg02. The package control option prevents host sage from adopting another package, so host
sage is no longer an adoptive node for pkg01.
Example Two - One Adoptive Node for Two Packages with File Lock Migration 69