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

13. Modify the MONITOR_DAEMONS_RETRY parameter, that represents the number of attempts
to ping the rpc.statd, rpc.mountd, nfsd, rpc.pcnfsd and file lock migration
script, processes before exiting. The default is 4 attempts. An example for this parameter
is as follows:
For nfs.conf generated on Serviceguard A.11.18
MONITOR_DAEMONS_RETRY 4
For nfs.conf generated on Serviceguard A.11.19
nfs/hanfs_export/MONITOR_DAEMONS_RETRY 4
14. Modify the PORTMAP_RETRY parameter, that represents the number of attempts to ping the
rpcbind process before exiting. The default is 4 attempts. An example for this parameter is
as follows:
For nfs.conf generated on Serviceguard A.11.18
PORTMAP_RETRY 4
For nfs.conf generated on Serviceguard A.11.19
nfs/hanfs_export/PORTMAP_RETRY 4
15. Modify the SUPPORTED_NETIDS parameter, that represents a list of Internet transport protocols
on which the NFS service daemons listen for service requests.
The package control script monitors the health of the NFS service daemons on all the listed
transport protocols. By default, the NFS daemons on all the supported Internet transport
protocols are monitored based on the type of the package IP address(s) configured. For
example, if the package IP address is of type IPv4, then the daemons are monitored for both
tcp and udp. If the package IP address is of type IPv6, then the daemons are monitored for
both tcp6 and udp6. If multiple package IP addresses, belonging to both IPv4 and IPv6, are
configured, then the monitoring is done for tcp, udp, tcp6 and udp6.
Modifying these parameters overrides the default logic of monitoring the NFS service daemons,
based on the type (IPv4/IPv6) of the package IP address(s) configured.
Modify these parameters only if you want to monitor the NFS services on a selected list of
Internet transport protocols. For example, the NFS server daemon can be configured to listen
only on tcp. In that case, the parameter SUPPORTED_NETIDS must have "tcp" as the value
configured.
Following are the valid values for this parameter,
On a IPv4-enabled system: tcp, udp
On a IPv6-enabled system: tcp6, udp6
On IPv4 and IPv6 enabled system: tcp, tcp6, udp, udp6
An example for this parameter is as follows:
For nfs.conf generated on Serviceguard A.11.18
SUPPORTED_NETIDS tcp
For nfs.conf generated on Serviceguard A.11.19
nfs/hanfs_export/SUPPORTED_NETIDS tcp
16. The FLM_HOLDING_DIR variable defines the holding directory in a disk volume associated
with the HA/NFS package. This directory contains copies of the files from the /var/statmon/
sm directory and is migrated with the HA/NFS package during a failover. The contents of
this directory are used to populate the /var/statmon/sm directory when recovering from
a failover event. The NFSV4_FLM_HOLDING_DIR variable defines the directory that will
contain copies of the files from the /var/nfs4/v4_state directory when NFSv4 is enabled.
You must dedicate this directory for holding v4_state entries only. In addition, you must keep
it empty. This directory should not have other files or subdirectories when starting the cluster.
Configuring a Serviceguard NFS Modular Package 49