Managing Serviceguard NFS for Linux, September 2006

Serviceguard NFS for LINUX Introduction
How the Control and Monitor Scripts Work
Chapter 114
How the Control and Monitor Scripts Work
As with all Serviceguard packages, the package control scripts start and
stop the NFS package and determine how the package will operate once
it becomes available on a particular node. Each control script contains
two sets of code that operate depending on whether the script is called
with the start parameter or the stop parameter.
A template package control script pkg.cntl can be generated by using
cmmakepkg -s pkg.cntl. The template script hanfs.sh is provided in
/usr/local/cmcluster/nfstoolkit directory for RedHat
environments, and /opt/cmcluster/nfstoolkit for SLES
environments.
Refer to the Managing Serviceguard for Linux-Chapter 6 for additional
information on creating the files. Refer to “Editing the Package Control
Scripts (pkg.cntl)” on page 27 and “Editing the NFS Control Script
(hanfs.sh)” on page 30 for information on how to modify this package
control script template file for your own packages.
Starting the NFS Services
When called with the start parameter, the package control script does
the following:
• Activates MD devices that are used by column groups.
• Activates the volume group or volume groups associated with the
package.
• Mounts each file system associated with the package.
• Invoke toolkit.sh to run the NFS start script.
• The NFS script hanfs.sh, exports each file system associated with
the package so that it can later be NFS-mounted by clients.
• The NFS script 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.
• 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.