Serviceguard NFS Toolkit A.11.31.03 Release Notes (October 2008)

Problem
If you run AutoFS on NFS servers that participate in a HA NFS cluster (through Serviceguard),
the behavior of building a local IP interface list may render Serviceguard unable to migrate an
NFS package during a fail-over event.
NOTE: This problem impacts only HA NFS server systems running AutoFS. You can safely
use AutoFS on client systems.
Cause
HA NFS uses relocatable IP addresses that migrate from a primary NFS server to an adoptive
node during a fail-over event. If you start AutoFS on an HA NFS server after Serviceguard is
running, these relocatable IP addresses are included in AutoFS' list of local IP interfaces. AutoFS
map entries referencing these relocatable addresses cause AutoFS to create LOFS mounts to the
exported local filesystems. These LOFS mounts may create problems with Serviceguard, because
HA NFS does not unmount LOFS filesystems before a package migration. AutoFS-managed
LOFS mounts that are holding resources in the exported filesystems, when Serviceguard tries to
initiate a package failover, may render Serviceguard unable to successfully unmount the local
filesystems and migrate them to the adoptive node.
Workaround
The workaround for this problem is to start automountd with the -L option. This can be done
by setting the AUTOMOUNTD_OPTIONS variable in the /etc/rc.config.d/nfsconf file before
automountd is started.
Problem
The /etc/rmtab file is not synchronized when an NFS package fails over to the standby node.
This is because NFS, by design, does not keep track of the state of the /etc/rmtab file. There
may be old entries in the /etc/rmtab file, and hence unreliable in a standard NFS server and
client environment.
Software Availability in Native Languages
The Serviceguard NFS Toolkit is available only in the English language.
10