Serviceguard NFS Toolkit A.11.11.06, A.11.23.05 and A.11.31.05 Administrator's Guide HP-UX 11i v1, v2, and v3

Each package must have a unique service name. The SERVICE_NAME variable in the package
configuration file must match the NFS_SERVICE_NAME variable in the NFS control script.
If you do not want to run the NFS monitor script, comment out the SERVICE_NAME variable:
# SERVICE_NAME nfs.monitor
6. Set the SUBNET variable to the subnet that will be monitored for the package.
SUBNET 15.13.112.0
You can use the default values for the rest of the variables in the package configuration file, or
you can change them as needed. For instructions on modifying the default values, see the Managing
Serviceguard manual, or read the comments in the /opt/cmcluster/nfs/nfs.conf template
file.
Configuring Server-to-Server Cross-Mounts (Optional)
Two NFS server nodes may NFS-mount each other's file systems and still act as adoptive nodes
for each other's NFS server packages. Figure 2-1 illustrates this configuration.
Figure 2-1 Server-to-Server Cross-Mounting
The advantage of server-to-server cross-mounting is that every server has an identical view of
the file systems. The disadvantage is that, on the node where a file system is locally mounted,
the file system is accessed through an NFS mount, which has poorer performance than a local
mount.
Configuring a Serviceguard NFS Legacy Package 35