Serviceguard NFS Toolkit A.11.11.04 and A.11.23.03 Administrator's Guide

Overview of Serviceguard NFS
How the Control and Monitor Scripts Work
Chapter 122
AUTO_RUN YES and LOCAL_LAN_FAILOVER YES (the defaults), the
package switches to the next adoptive node or to a standby network
interface in the event of a node or network failure. However, if one of the
NFS services goes down while the node and network remain up, you need
the NFS monitor script to detect the problem and to switch the package
to an adoptive node.
Whenever the monitor script detects an event, it logs the event. Each
NFS package has its own log file. This log file is named according to the
NFS control script, nfs.cntl, by adding a .log extension. For example,
if your control script is called /etc/cmcluster/nfs/nfs1.cntl, the log
file is called /etc/cmcluster/nfs/nfs1.cntl.log.
TIP You can specify the number of retry attempts for all these processes in
the nfs.mon file.
On the Client Side
The client should NFS-mount a file system using the package name in
the mount command. The package name is associated with the package’s
relocatable IP address. On client systems, be sure to use a hard mount
and set the proper retry values for the mount. Alternatively, set the
proper timeout for automounter. The timeout should be greater than the
total end-to-end recovery time for the Serviceguard NFS package—that
is, running fsck, mounting file systems, and exporting file systems on
the new node. (With journalled file systems, this time should be between
one and two minutes.) Setting the timeout to a value greater than the
recovery time allows clients to reconnect to the file system after it
returns to the cluster on the new node.
B5140-90021.book Page 22 Wednesday, November 17, 2004 10:52 AM