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

vxvol_cmd "vxvol -g \$DiskGroup startall" #Default
fs_umount_retry_count 1
fs_mount_retry_count 0
ip_address 15.13.114.244
ip_subnet 15.13.112.0
XFS "/hanfs/nfsu021"
FILE_LOCK_MIGRATION 0
The external script file for this package can be created in any package specific location using the
external script template file.
cp /etc/cmcluster/examples/external_script.template /pkg02_location/pkg02_ext
Also, specify the external script file location in the package configuration file (nfs2.conf) as
external_script /pkg02_location/pkg02_ext
In the external script file, add the following lines to the start_command function.
function start_command
{
/etc/cmcluster/nfs/nfs2_xmnt start
remsh thyme /etc/cmcluster/nfs/nfs2_xmnt start
return 0
}
The external script invokes another script called nfs2_xmnt. This script NFS-mounts the file
system exported by the package pkg02. If you configured the file system in the /etc/fstab
file, the package might not be active yet when the servers tried to mount the file system at system
boot. By configuring the external script to NFS-mount the file system, you ensure that the package
is active before the mount command is invoked.
The first line in the start_command function of the external script, executes the nfs2_xmnt
script locally on host basil (the primary node for pkg02). The second line, beginning with
remsh, executes the nfs2_xmnt script remotely on host thyme.
If pkg02 fails to come up, or if the remsh to host thyme fails, the file system will not be mounted,
and no error will be returned. The only way to be sure the file system was mounted successfully
is to run the nfs2_xmnt script manually on both host basil and host thyme.
The only user-configurable values in the nfs2_xmnt script are the SNFS[n] and CNFS[n]
variables. These specify the server location of the file system and the client mount point for the
file system. The following line is the from the nfs2_xmnt script in this example configuration:
SNFS[0]="nfs2:/hanfs/nfsu021"; CNFS[0]="/nfs/nfsu021"
In the SNFS[0] variable, nfs2 is the name that maps to the relocatable IP address of pkg02. It
must be configured in the name service the host is using (DNS, NIS, or the /etc/hosts file). If
you do not want to configure a name for the package, you can just specify the IP address in the
SNFS[0] variable, as follows:
SNFS[0]="15.13.114.244:/hanfs/nfsu021"; CNFS[0]="/nfs/nfsu021"
The client mount point, specified in the CNFS[0] variable, must be different from the location
of the file system on the server (SNFS[0]).
110 Sample Configurations for Modular Package