Sample Configurations
Example Four - Two Servers with NFS
The first line in the customer_defined_run_cmds function 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
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/n
fsu021”
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]).
The hanfs.sh Control Script
This section shows the NFS control script (hanfs2.sh) for the pkg02 package in this sample configuration. This example includes only the
XFS[0]=/hanfs/nfsu021
NFS_SERVICE_NAME[0]="nfs2.monitor"
NFS_SERVICE_CMD[0]="/etc/cmcluster/nfs/nfs.mon"
NFS_FILE_LOCK_MIGRATION=0
NFS_FLM_SCRIPT="${0%/*}/nfs.flm"
90 | Chapter 3 |