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 1 19
How the Control and Monitor Scripts Work
As with all Serviceguard packages, the control script starts and stops the
NFS package and determines how the package operates when it is
available on a particular node. The 11i v1 and 11i v2 control script
(hanfs.sh) contains three sets of code that operate depending on the
parameter - start, stop,orfile_lock_migration - with which you call
the script. On 11.0, there are two sets of code that you can call with the
start or stop parameter.
Starting the NFS Services
When called with the start parameter, the control script does the
following:
• Activates the volume group or volume groups associated with the
package.
• Mounts each file system associated with the package.
• Initiates the NFS monitor script to check periodically on the health
of NFS services, if you have configured your NFS package to use the
monitor script.
• Exports each file system associated with the package so that it can
later be NFS-mounted by clients.
• Assigns a package IP address to the LAN card on the current node.
After this sequence, the NFS server is active, and clients can NFS-mount
the exported file systems associated with the package.
Starting File Lock Migration
If you call the control script with the file_lock_migration parameter
after enabling the File Lock Migration feature, the control script does the
following:
• Populates the /var/statmon/sm directory with the Status Monitor
entries from the configured holding directory of the package, and
subsequently removes the entries from the holding directory.
• Kills any running copy of the NFS File Lock Recovery
synchronization script.
B5140-90021.book Page 19 Wednesday, November 17, 2004 10:52 AM