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

corresponding to this nfs.cntl file will be hanfs.hapkg.sh. The default shell
script name for this variable is hanfs.sh.
6. If two packages have the same adoptive node, and you want to prevent the adoptive
node from adopting both packages at once, specify the cmmodpkg command with
the package control option (-d) in the customer_defined_run_cmds:
function customer_defined_run_cmds
{
cmmodpkg -d -n hostname pkg02 &
}
The package control option can prevent an adoptive node from becoming
overloaded when multiple packages fail over. If an adoptive node becomes
overloaded, it can fail.
In this example, if a host is an adoptive node for both pkg01 and pkg02, the above
cmmodpkg -d command, in the control script for pkg01, would prevent the host that
is running pkg01 from adopting pkg02. A similar line in the control script for pkg02
could prevent the host that is running pkg02 from adopting pkg01. The ampersand
(&) causes the cmmodpkg command to run in the background. It must run in the
background to allow the control script to finish bringing up the package. The cmmodpkg
command will hang until the package is up, so it must run in the background to allow
the control script to complete.
There is a short time, after one package has failed over but before the cmmodpkg
command has executed, when the other package can fail over and the host will adopt
it. In other words, if two packages fail over at approximately the same time, a host may
adopt both packages, even though the package control option is specified.
See “Example Two - One Adoptive Node for Two Packages with File Lock Migration”
(page 48) for a sample configuration using the package control option.
NOTE: The NFS specific variables have been moved to NFS specific control script in
Serviceguard NFS Toolkit with the A.11.11.02 and A.11.00.05 releases. See section
“Editing the NFS Control Script (hanfs.sh) ” (page 32) for the details.
Editing nfs.cntl for NFS Toolkit A.11.00.04 and A.11.11.01 (or lower)
For Serviceguard NFS Toolkit A.11.00.04 or lower for HP-UX 11.0 or Serviceguard NFS
Toolkit A.11.11.01 or lower for HP-UX 11i v1 using Serviceguard A.11.09 (or below)
framework.
Example steps:
1. Create a separate VG[n] variable for each volume group.
VG[0]=/dev/vg01 VG[1]=/dev/vg02 ...
2. Create a separate LV[n] and FS[n] variable for each volume group and file system
that will be mounted on the server:.
30 Installing and Configuring Serviceguard NFS