White Paper

HALT_SCRIPT /etc/cmcluster/nfs/nfs-export.cntl

HALT_SCRIPT_TIMEOUT NO_TIMEOUT

f) Set the DEPENDENCY_NAME, DEPENDENCY CONDITION, and

DEPENDENCY_LOCATION variables so that the export package will only run

if the Serviceguard CFS multi-node packages are already running. Since

there are two CFS file systems in this example, there are also two CFS

multi-node packages:

DEPENDENCY_NAME SG-CFS-MP-1-dep

DEPENDENCY_CONDITION SG-CFS-MP-1=UP

DEPENDENCY_LOCATION SAME_NODE

DEPENDENCY_NAME SG-CFS-MP-2-dep

DEPENDENCY_CONDITION SG-CFS-MP-2=UP

DEPENDENCY_LOCATION SAME_NODE

Note: The NFS export multi-node package does not monitor exported file systems (for

example if a file system becomes unexported or inaccessible). It checks if the CFS

dependent packages have access to the file systems. If the NFS failover package loses

access and cannot read or write to the disk, it will fail. However, the exportfs multi-

node package will not fail.

Starting a Serviceguard NFS export package

1. Copy the configuration files to each server in the cluster:

# rcp –p /etc/cmcluster/nfs/* {hostname}:/etc/cmcluster/nfs

2. Verify the cluster and package configuration files on each server:

# cmcheckconf –k –v –C /etc/cmcluster/cluster.conf –P /etc/cmcluster/nfs/\

nfs-export.conf

3. Verify and apply the cluster package configuration files on a single server:

# cmapplyconf –v –C /etc/cmcluster/cluster.conf –P /etc/cmcluster/nfs/\

nfs-export.conf

4. Run the export package on a single server with the command:

# cmrunpkg –v SG-NFS-XP-1

5. You can verify if the export package is running with the cmviewcl command.

The output is similar to the following:

# cmviewcl

CLUSTER STATUS

cluster1 up

NODE STATUS STATE

thyme up running

NODE STATUS STATE

basil up running