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

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

7.2Serviceguard NFS modular 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 file system to configure in the package configuration file, 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.

Configuring a Serviceguard NFS failover package

Configuring a Serviceguard NFS failover package for a CFS environment is similar to configuring the package for a non-CFS environment. The main difference is that you must configure one failover package for every server that exports CFS.

1.Create the nfs.conf file for each package with the cmmakepkg command (one package for each server).

#cd /etc/cmcluster/nfs_modular

#cmmakepkg -m sg/all -m nfs/hanfs /etc/cmcluster/nfs_modular/\ nfs1.conf

#cmmakepkg -m sg/all -m nfs/hanfs /etc/cmcluster/nfs_modular/\ nfs2.conf

2. Edit the nfs.conf files (nfs1.conf, nfs2.conf) as follows:

a)Specify the IP address for the package and the subnet to which the IP address belongs:

ip_subnet15.13.112.0

ip_address15.13.114.243

25