HP Serviceguard Toolkit for NFS manual Package Status State Autorun Node SG-NFS1

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

4.Run the failover packages:

#cmrunpkg –n thyme –v SG-NFS1

#cmrunpkg –n basil –v SG-NFS2

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
SG-NFS-XP-1	up	running	enabled	no

6.2Serviceguard NFS Legacy Package over CFS Packages with File Locking

Serviceguard NFS over CFS packages that require file locking are similar to Serviceguard NFS over VxFS packages. The main differences are that there is no filesystem to mount in the nfs.cntl script, since the CFS multi-node packages already mount the CFS file systems, and the package dependencies are added on the CFS packages. Figure 6 illustrates an example of a Serviceguard NFS package over a CFS configuration with two servers, each with an NFS failover package.

15