Serviceguard NFS Toolkit A.11.11.06, A.11.23.05 and A.11.31.08 Administrator's Guide (October 2011)

directory is a configurable parameter and must be dedicated to hold the v4_state entries only.
Both holding directories should be located in the same filesystem.
• The nfs.flm script now copies v4_state entries from /var/nfs4/v4_state to the NFSv4 holding
directory when copying SM entries from the /var/statmon/sm directory into the NFSv2 and
NFSv3 holding directory.
• Upon package failover, the v4_state entries in the NFSv4 holding directory are also copied
to the /var/nfs4/v4_state on the adoptive node when the SM entries residing in NFSv2
and NFSv3 holding directory are copied to the /var/statmon/sm directory. This populates
the new server's SM and v4_state directories with the entries from the primary server,
respectively.
• After failover, nfsd is also killed and restarted when rpc.lockd and rpc.statd are killed and
restarted on the adoptive node. The killing and restarting of nfsd forces NFSv4 servers to begin
the grace period during which time the NFSv4 clients will reclaim their locks.
• After the nfs.flm script is started on the adoptive node, it once again copies entries in the
/var/statmon/sm and /var/nfs4/v4_state directories on the HA/NFS server into the holding
directories, every five seconds.
To enable the NFSv4 file lock migration feature, it is necessary to configure NFS servers using
protocol version 4 (NFSv4) with enabling current file lock migration feature. See “Editing the NFS
Control Script (hanfs.sh)” on how to enable file lock migration feature.
The NFSv4 servers are configured as follows. See “NFS Services Administrator's Guide: HP-UX
11i v3” for more information on how to configure NFSv4 servers.
1. On the primary node and all adoptive nodes for a NFS package, set the
NFS_SERVER_VERSMAX variable to 4 in the /etc/default/nfs file.
NFS_SERVER_VERSMAX=4
2. Stop and start the NFS startup script on all nodes
/sbin/init.d/nfs.server stop
/sbin/init.d/nfs.server start
NOTE: To enable NFSv4 File Lock Migration Feature, you need Serviceguard version A.11.18
or above in HP-UX 11i v3.
Overview of Serviceguard NFS with Serviceguard A.11.17 Support
Serviceguard NFS Toolkit A.11.23.05 can work with Serviceguard A.11.17. Serviceguard A.11.17
supports Veritas Cluster File System (CFS) which allows a file system to be created that can be
mounted by all nodes in a cluster environment. The detailed information of using Serviceguard
NFS Toolkit A.11.23.05 with Serviceguard A.11.17 is as follows:
• Serviceguard NFS Toolkit A.11.23.05 supports the new variable
HA_NFS_SCRIPT_EXTENSION in the control script (nfs.cntl). This new variable can be
used to modify the name of the NFS specific control shell script (hanfs.sh) that is associated
with a package.
For example, if you set the HA_NFS_SCRIPT_EXTENSION variable to hapkg or hapkg.sh,
then the NFS specific control script executed by the package corresponding to this nfs.cntl
file will be hanfs.hapkg.sh. The default shell script name for this variable is hanfs.sh.
• Serviceguard with Veritas CFS feature integration provides the capability of creating a file
system that can be mounted by all nodes in a cluster. The Serviceguard CFS feature provides
performance improvement and cache coherency.
HP recommends that you use the Serviceguard CFS feature instead of setting up server-to-server
cross-mounting configuration. To use Serviceguard with the Veritas CFS feature, you need to
install Serviceguard version A.11.17. For more information, refer to Managing Serviceguard,
Overview of Serviceguard NFS with Serviceguard A.11.17 Support 9