Managing Serviceguard NFS for Linux, July 2007

Serviceguard NFS for LINUX Introduction
How the Control and Monitor Scripts Work
Chapter 120
After this sequence, the NFS package is inactive on the current node and
may start up on an alternate node or be restarted later on the same node.
Monitoring the NFS Services
The monitor script nfs.mon, located in the file
/usr/local/cmcluster/nfstoolkit for RedHat environments, and
/opt/cmcluster/nfstoolkit for SLES environments), works by
periodically checking the status of NFS services using the rpcinfo
command. If any service fails to respond, the script exits, causing a
switch to an adoptive node.
The monitor script monitors NFS services including:
• portmap
• rpc.statd
• nfsd
• rpc.mountd
• rpc.rquotad, if QUOTO_MON is set to “YES” in hanfs.conf
• lockd
• nfs.flm, if LOCK_MIGRATION and NFS_FLM_MONITOR are set to
“YES” in hanfs.conf
If any of the services are dead or hangs, the nfs.mon. will cause the
package to fail.
NOTE To configure NFS for maximal availability, you must do the following:
•Specify AUTO_RUN=YES in the package configuration file. This allow
the NFS package to start automatically when the cluster starts up,
and to start on an adoptive node after a failure.
• Invoke the NFS Monitoring script, nfs.mon. The default NFS control
script does not invoke the NFS monitoring script, nfs.mon. To invoke
this script (see Chapter 3, “Sample Configurations,”) trigger a
failover if one of the package’s NFS services goes down while the
node and network remain up.