Managing Serviceguard NFS for Linux, September 2006

Serviceguard NFS for LINUX Introduction
How the Control and Monitor Scripts Work
Chapter 1 15
Halting the NFS Services
When called with the stop parameter, the control script does the
following:
• Removes the package IP address from the LAN card on the current
node.
• The package control script invokes the toolkit.sh to run the NFS
script and to halt the NFS related process.
• The NFS script un-exports all file systems associated with the
package so that they can no longer be NFS-mounted by clients.
• The NFS script halts the monitor process.
• Unmounts each file system associated with the package.
• Deactivates each volume group associated with the package.
• Deactivates each MD device.
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
If any of the services are dead or hangs, the nfs.mon. will cause the
package to fail.