Serviceguard NFS Toolkit A.11.11.05 and A.11.23.04 Release Notes
Serviceguard NFS Toolkit A.11.11.05 and A.11.23.04 Release Notes
Features and Fixes in Recent Releases
7
Features and Fixes in Recent Releases
Fixes in The Versions A.11.11.04 and A.11.23.03
The fixes in these versions are as follows:
DTS Number Problem Description
JAGaf11503 The /etc/rmtab file is not synchronized when an NFS package fails over to
the standby node. This is now documented as a known problem.
JAGaf23782 The file name of the NFS_FLM_SCRIPT script must be limited to 13
characters or fewer.
JAGaf26367 The nfs.mon script uses rpcinfo calls to check the status of various
processes. If the rpcbind process is not running, the rpcinfo calls time out
after 75 seconds. Because 10 rpcinfo calls are attempted before failover, it
takes approximately 12 minutes to detect the failure.
JAGaf37266 Change the MC/ServiceGuard NFS Toolkit product name to be
Serviceguard NFS Toolkit.
JAGae26082 In the nfs_xmnt script, if CNFS[0] is set to ” /xxx_dir” and CNFS[1] is set
to “/xxx”, the second filesystem is not mounted and you get the error
message: <date>Note... was already mounted.
New Changes in Serviceguard NFS A.11.11.03 and A.11.23.02
Serviceguard NFS Toolkit A.11.11.03 and A.11.23.02 include a new feature - File Lock
Migration. The detailed information of this feature is as follows:
• Each HA/NFS package designates a unique holding directory located in one of the
filesystems associated with the package. In other words, an empty directory is created in
one of the filesystems that moves between servers as part of the package. This holding
directory is a configurable parameter and must be dedicated to hold the Status Monitor
(SM) entries only.
• A new script, nfs.flm, periodically (default value is five seconds; you can change this
value by modifying the PROPAGATE_INTERVAL parameter in the nfs.flm script) copies
SM entries from the /var/statmon/sm directory into the package holding directory.
• Upon package failover, the holding directory transitions from the primary node to the
adoptive node, because it resides in one of the filesystems configured as part of the
HA/NFS package.