HP Serviceguard Toolkit for NFS manual Configuring a Serviceguard NFS failover package

Page 13

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.Copy the following scripts and make a separate copy for each package. You must create one package for each server.

#cd /etc/cmcluster/nfs

#cmmakepkg –p /etc/cmcluster/nfs/nfs1.conf

#cmmakepkg –s /etc/cmcluster/nfs/nfs1.cntl

#cp /opt/cmcluster/nfs/hanfs.sh hanfs.1.sh

#cp /opt/cmcluster/nfs/nfs.mon nfs1.mon

#cmmakepkg –p /etc/cmcluster/nfs/nfs2.conf

#cmmakepkg –s /etc/cmcluster/nfs/nfs2.cntl

#cp /opt/cmcluster/nfs/hanfs.sh hanfs.2.sh

#cp /opt/cmcluster/nfs/nfs.mon nfs2.mon

2.Edit the nfs.cntl scripts (nfs1.cntl, nfs2.cntl). Specify the IP address for the package and the subnet to which the IP address belongs:

IP[0]=15.13.114.243

SUBNET[0]=15.13.112.0

This IP address is the relocatable IP address for the package. NFS clients that mount the file systems in the package will use this IP address to identify the server. You must configure a name for this IP address in the DNS, NIS, or LDAP database, or in the /etc/hosts file.

3.Set the HA_NFS_SCRIPT_EXTENSION to “1.sh” in the nfs1.cntl file: HA_NFS_SCRIPT_EXTENSION = “1.sh”

This will set the NFS specific control script to be run by the package to hanfs.1.sh as we have named it in the copy command above. Set this to “2.sh” in nfs2.cntl.

4.Edit the hanfs.sh scripts (hanfs.1.sh and hanfs.2.sh) if you want to monitor NFS services (by running the NFS monitor script). To monitor NFS services, set the NFS_SERVICE_NAME and NFS_SERVICE_CMD variables:

NFS_SERVICE_NAME[0]=nfs1.monitor

NFS_SERVICE_CMD[0]=/etc/cmcluster/nfs/nfs1.mon

In hanfs.2.sh, set NFS_SERVICE_NAME[0] to nfs2.monitor and set

NFS_SERVICE_CMD[0] to /etc/cmcluster/nfs/nfs2.mon. If you do not want to monitor NFS services, leave these variables commented out.

5.Edit the nfs.conf scripts (nfs1.conf and nfs2.conf) as follows: a) Specify the package name:

PACKAGE_NAME SG-NFS1

13

Image 13
Contents Serviceguard NFS Toolkit Support for Cluster File System Starting a Serviceguard NFS failover package Non-CFS Implementation with Package Failover Integrating Support for CFS into Serviceguard NFS ToolkitCFS vs. Non-CFS Implementation Current SG-NFS over VxFS SupportSG NFS Servers over VxFS High Availability Issues and Limitations with the Current CFS Implementation Prerequisites Node Status State Cluster StatusMultinodepackages Package Status State Autorun SG-CFS-DG-1SG NFS over CFS without file locking Configuring a Serviceguard NFS export packageRunscripttimeout Notimeout # Failoverpolicy Configurednode # Failbackpolicy ManualPackagename SG-NFS-XP-1 Packagetype MultinodeHaltscripttimeout Notimeout Starting a Serviceguard NFS export packageSG-NFS-XP-1 Packagename SG-NFS1 Configuring a Serviceguard NFS failover packageDEPENDENCYCONDITIONSG-NFS-XP-1=UP Dependencylocationsamenode Starting a Serviceguard NFS failover packagePackage Status State Autorun Node SG-NFS2 Package Status State Autorun Node SG-NFS1SG NFS over CFS with file locking NFSFILELOCKMIGRATION=1 Nfs2.conf file set these variables to Starting a Serviceguard NFS failover package Cluster1 up XFS Starting a Serviceguard NFS export package Configuring a Serviceguard NFS failover package Starting a Serviceguard NFS failover package Package Status State Autorun Node SG-NFS1 FILELOCKMIGRATION1 Starting a Serviceguard NFS failover package Thyme Running
Related manuals
Manual 93 pages 19.37 Kb Manual 93 pages 21.07 Kb