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

NFS Control Scripts for pkg01
The nfs.cntl Control Script
This section shows the NFS control script (nfs1.cntl) for the pkg01 package in this
sample configuration. Only the user-configured part of the script is shown; the
executable part of the script and most of the comments are omitted.
PATH=/sbin:/usr/bin:/usr/sbin:/etc:/bin
VGCHANGE=”vgchange -a e” # Default
CVM_ACTIVATION_CMD="vxdg -g \$DiskGroup set activation=exclusivewrite"
VG[0]=nfsu01
LV[0]=/dev/nfsu01/lvol1; FS[0]=/hanfs/nfsu011; 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.243
SUBNET[0]=15.13.112.0
function customer_defined_run_cmds
{
cmmodpkg -d -n ‘hostname‘ pkg02 &
}
The function customer_defined_run_cmds calls the cmmodpkg command with
the package control option (-d). This command prevents the host that is running pkg01
from adopting pkg02. The ampersand (&) causes the cmmodpkg command to run in
the background. It must run in the background to allow the control script to complete.
There is a short time, after one primary node has failed but before the cmmodpkg
command has executed, when the other primary node can fail and the adoptive node
will adopt its package. In other words, if both thyme and basil fail at approximately
the same time, host sage may adopt two packages, even though the package control
option is specified.
If you omit the cmmodpkg -d command from the NFS control script, host sage can
adopt both pkg01 and pkg02 if their primary nodes fail.
The hanfs.sh Control Script
This section shows the NFS control script (hanfs1.sh) for the pkg01 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
enables the File Lock Migration feature.
XFS[0]=/hanfs/nfsu011
52 Sample Configurations