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

h. Set the node_name variables for each node that can run the package. The first node_name
must specify the primary node, followed by adoptive node(s) in the order in which they
will be tried.
node_name thyme
node_name basil
i. Set the dependency_name, dependency_condition, and dependency_location variables
so that the failover package runs only if the export package is already running.
dependency_name SG-CFS-MP-1-dep
dependency_condition SG-CFS-MP-1=up
dependency_location same_node
In nfs2.conf set these to:
dependency_name SG-CFS-MP-2-dep
dependency_condition SG-CFS-MP-2=UP
dependency_location same_node
Starting a Serviceguard NFS failover package
Use the following steps to start a failover 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/nfs1.conf –P
/etc/cmcluster/nfs_modular/nfs2.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/nfs1.conf –P
/etc/cmcluster/nfs_modular/nfs2.conf
3. Run the failover packages.
# cmrunpkg –n thyme –v SG-NFS1
# cmrunpkg –n basil –v SG-NFS2
4. If you run the cmviewcl command, the output is similar to the following:
# cmviewcl
CLUSTER STATUS
cluster1 up
NODE STATUS STATE
thyme up running
PACKAGE STATUS STATE AUTO_RUN NODE
SG-NFS1 up running enabled thyme
NODE STATUS STATE
basil up running
PACKAGE STATUS STATE AUTO_RUN NODE
SG-NFS2 up running enabled basil
MULTI_NODE_PACKAGES
PACKAGE STATUS STATE AUTO_RUN SYSTEM
SG-CFS-pkg up running enabled yes
SG-CFS-DG-1 up running enabled no
SG-CFS-MP-1 up running enabled no
SG-CFS-MP-2 up running enabled no
Configuring Serviceguard NFS Modular Package over CFS Packages 65