Installing and Configuring MC/ServiceGuard NFS
Configuring an MC/ServiceGuard NFS Package
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
38 | Chapter 2 |
