White Paper

e) 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

f) Comment out the service_name, service_cmd, service_restart,

service_fail_fast_enabled and service_halt_timeout variables.

# service_name nfs.monitor

# service_cmd "$SGCONF/scripts/nfs/nfs_upcc.mon"

# service_restart none

# service_fail_fast_enabled no

# service_halt_timeout 0

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 (the exportfs multi-node package

will not fail).

Starting a Serviceguard NFS export package

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

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

/etc/cmcluster/nfs_modular/nfs-export.conf

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

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

nfs-export.conf

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

# cmrunpkg –v SG-NFS-XP-1

4. 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