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

LV[0]=/dev/vg01/lvol1;FS[0]=/ha_root
LV[1]=/dev/vg01/lvol2;FS[1]=/users/scaf
LV[2]=/dev/vg02/lvol1;FS[2]=/ha_data
3. Create a separate XFS[n] variable for each NFS directory to be exported. Specify the directory
name and any export options.
XFS[0]="/ha_root" XFS[1]="/users/scaf" XFS[2]="-o ro /ha_data"
Do not configure these exported directories in the /etc/exports file. When an NFS server
boots up, it attempts to export all file systems in its /etc/exports file. If those file systems
are not currently present on the NFS server node, the node cannot boot properly. This
happens if the server is an adoptive node for a file system, and the file system is available
on the server only after failover of the primary node.
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. If you want to run the NFS monitor script , set the NFS_SERVICE_NAME variable to the
value of the SERVICE_NAME variable in the package configuration file. Each package must
have a unique service name.
NFS_SERVICE_NAME[0]=nfs1.monitor
If you do not want to run the NFS monitor script, comment out the NFS_SERVICE_NAME
and NFS_SERVICE_CMD variables:
# NFS_SERVICE_NAME[0]=nfs.monitor
# NFS_SERVICE_CMD[0]=/etc/cmcluster/nfs/nfs.mon
By default, the NFS_SERVICE_NAME and NFS_SERVICE_CMD variables are commented
out, and the NFS monitor script is not run.
You do not have to run the NFS monitor script. If your NFS package configuration file
specifies PKG_SWITCHING_ENABLED YES and NET_SWITCHING_ENABLED YES (the
defaults), the package will switch to the next adoptive node or to a standby network interface
in the event of a node or network failure. The NFS monitor script causes the package failover
if any of the monitored NFS services fails.
6. If you run the NFS monitor script, set the NFS_SERVICE_CMD variable to the full path name
of the NFS monitor script.
NFS_SERVICE_CMD[0]=/etc/cmcluster/nfs/nfs.mon
The path name for the executable script does not have to be unique to each package. Every
package can use the same script. Multiple instances of the monitor script can run on the
same node without any problems, and if a package fails over, only the instance associated
with that package is killed.
If you do not want to run the NFS monitor script, comment out the NFS_SERVICE_NAME
and NFS_SERVICE_CMD variables:
# NFS_SERVICE_NAME[0]=nfs.monitor
# NFS_SERVICE_CMD[0]=/etc/cmcluster/nfs/nfs.mon
By default, the NFS_SERVICE_NAME and NFS_SERVICE_CMD variables are commented
out, and the NFS monitor script is not run.
7. 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.
Configuring a Serviceguard NFS Package 29