Serviceguard NFS Toolkit A.11.11.06, A.11.23.05 and A.11.31.05 Administrator's Guide HP-UX 11i v1, v2, and v3

Editing nfs.cntl for NFS Toolkit A.11.00.05, A.11.11.02 (or above) and A.11.23.01 (or above)
Starting with Serviceguard A.11.13, a package can have LVM volume groups, CVM disk groups
and VxVM disk groups.
Example steps:
1. Create a separateVG[n] variable for each LVM volume group that is used by the package:
VG[0]=/dev/vg01 VG[1]=/dev/vg02 ...
2. Create a separate VXVM_DG[n] variable for each VxVM disk group that is used by the
package:
VXVM_DG[0]=dg01 VXVM_DG[1]=dg02 ...
3. Create a separate LV[n] and FS[n] variable for each volume group/disk group and file
system that will be mounted on the server:
For the LVM example, if this package uses the file systems pkg1a and pkg1b, which are
mounted on the logical volumes lvol1 and lvol2 with read and write options enter:
LV[0]=/dev/vg01/lvol1; FS[0]=/pkg1a; FS_MOUNT_OPT[0]="-o rw"
LV[1]=/dev/vg01/lvol2; FS[1]=/pkg1b; FS_MOUNT_OPT[1]="-o rw"
For the VxVM example, if this package uses the file systems pkg1a and pkg1b, which are
mounted on the volumes lvol1 and lvol2 with read and write options enter:
LV[0]="/dev/vx/dsk/dg01/vol01"; FS[0]="/pkg1a"; FS_MOUNT_OPT[0]="-o rw"
LV[1]="/dev/vx/dsk/dg01/vol02"; FS[1]="/pkg1b"; FS_MOUNT_OPT[1]="-o rw"
4. Specify the IP address for the package and the address of the subnet to which the IP address
belongs:
IP[0]=15.13.114.243 SUBNET[0]=15.13.112.0
The IP address you specify is the relocatable IP address for the package. NFS clients that
mount the file systems in the package will use this IP address to identify the server. You
should configure a name for this address in the DNS or NIS database, or in the /etc/hosts
file.
5. Serviceguard NFS Toolkit A.11.23.05 supports the new variable
HA_NFS_SCRIPT_EXTENSION in the control script (nfs.cntl). This new variable can be
used to modify the name of the NFS specific control shell script (hanfs.sh) that is associated
with a package.
For example, if you set the HA_NFS_SCRIPT_EXTENSION variable to hapkg orhapkg.sh,
then the NFS specific control script executed by the package 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.
Configuring a Serviceguard NFS Legacy Package 29