Serviceguard NFS Toolkit A.11.11.06, A.11.23.05 and A.11.31.07 Administrator's Guide (September 2010)

Create a directory on each server in the cluster to hold all of the configuration files (if this directory

already exists you should save the contents before continuing):

# mkdir /etc/cmcluster/nfs

The rest of the configuration is dependent upon whether or not the cluster requires file locking

(as described in the Limitations and Issues with the current CFS Implementation“Limitations

and Issues with the current CFS implementation” (page 16) section). If file locking is not required,

follow the instructions in the next section “Serviceguard NFS Legacy over CFS Packages without

File Locking” (page 38). If the locking is required, follow the instructions in the section

“Serviceguard NFS Legacy Package over CFS packages with File Locking” (page 43).

Serviceguard NFS Legacy over CFS Packages without File Locking

Each active server in the cluster needs to run an export multi-node package and an NFS failover

package. An export multi-node package is a package that runs on each server in the cluster and

exports all the cluster file systems. Each standby server (i.e. a server that is just an adoptive node

for NFS failover packages) needs to have an export multi-node package running to be able to

become active in the event of a failover.

Figure 2–2 shows an example Serviceguard over CFS configuration with two servers, each with

an NFS failover package and a multi-node export package.

Figure 2-2 Serviceguard over CFS without file locking

Configuring a Serviceguard NFS export package

There should only be one NFS export multi-node package per cluster. This package will run on

each server in the cluster.

NOTE: All steps in this section must be completed on a single server.

1. Create the nfs-export.conf and nfs-export.cntl files with the cmmakepkg command. Use the

-p option to create the nfs-export.conf file and the -s option to create the nfs-export.cntl