HP Serviceguard Toolkit for NFS manual Editing the NFS Control Script hanfs.sh

Page 41

Installing and Configuring MC/ServiceGuard NFS

Configuring an MC/ServiceGuard NFS Package

Editing the NFS Control Script (hanfs.sh)

The hanfs.sh control script contains NFS specific control variables and functions. The sample steps are as follows:

1.Create a separate XFS[n] variable for each NFS directory to be exported. Specify the directory name and any export options. The directories must be defined in the above mounted file system FS list.

XFS[0]="-o ro /pkg1a" XFS[1]="-o rw /pkg1b"

Do not configure these exported directories in the /etc/exports file. When an NFS server boots up, it attempts to export all file systems in its /etc/exports file. If those file systems are not currently present on the NFS server node, the node cannot boot properly. This happens if the server is an adoptive node for a file system, and the file system is available on the server only after failover of the primary node.

2.If you wish to monitor NFS services (by running the NFS monitor script), set the NFS_SERVICE_NAME and NFS_SERVICE_CMD variables; see the following example:

NFS_SERVICE_NAME[0]=nfs1.monitor

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

If you enable the File Lock Migration feature, ensure that the monitor script name is unique for each package (for example, nfs1.mon). If the File Lock Migration feature is disabled, the monitor script name does not have to be unique to each package (for example, nfs.mon). Multiple instances of the monitor script can run on the same node without any problem. If a package fails over, only the instance associated with that package is killed.

3.You do not have to run the NFS monitor script. If your NFS package configuration file specifies AUTO_RUN YES and

LOCAL_LAN_FAILOVER_ALLOWED YES (the defaults), the package switches to the next adoptive node or to a standby network interface in the event of a node or network failure. The NFS monitor script causes the package failover if any of the monitored NFS services fails.

If you do not want to run the NFS monitor script, comment out the

NFS_SERVICE_NAME and NFS_SERVICE_CMD variables:

Chapter 2

41

Image 41
Contents Edition Managing MC/ServiceGuard NFS A.11.23.02Legal Notices Contents Index Figures Figures NFS Overview of MC/ServiceGuard NFS Limitations of MC/ServiceGuard NFS Overview of the NFS File Lock Migration Feature Overview of the NFS File Lock Migration Feature Supported Configurations Pkg1 disks Simple Failover to an Idle NFS ServerPkg2 Disks Failover from One Active NFS Server to AnotherPackages Host Configured as Adoptive Node for MultipleCascading Failover with Three Adoptive Nodes NFS NFS Server-to-Server Cross MountingSupported Configurations Starting File Lock Migration Starting the NFS ServicesHow the Control and Monitor Scripts Work Halting the NFS Services Monitoring the NFS Services On the Client Side Installing and Configuring Installing and Configuring MC/ServiceGuard NFS Readme Installing MC/ServiceGuard NFSCmmakepkg -p /opt/cmcluster/nfs/nfs.conf ServiceGuard NFS Toolkit Monitoring NFS/TCP Services with MCChapter Before Creating an MC/ServiceGuard NFS Package NUMNFSD=10 Before Creating an MC/ServiceGuard NFS Package Mount -o nointr relocatableip/usr/src /usr/src Configuring an MC/ServiceGuard NFS Package Copying the Template Files Editing the Control Script nfs.cntl IP0=15.13.114.243 SUBNET0=15.13.112.0 Lower Etc/hosts file Configuring an MC/ServiceGuard NFS Package Configuring an MC/ServiceGuard NFS Package Editing the NFS Control Script hanfs.sh Netswitchingenabled Editing the File Lock Migration Script nfs.flm Configuring an MC/ServiceGuard NFS Package Editing the NFS Monitor Script nfs.mon Editing the Package Configuration File nfs.conf Configuring an MC/ServiceGuard NFS Package Configuring Server-to-Server Cross-Mounts Optional SNFS0=nfs1/hanfs/nfsu011CNFS0=/nfs/nfsu011 Configuring an MC/ServiceGuard NFS Package Run the cluster using the following command cmruncl -v-f Configuring an MC/ServiceGuard NFS Package Chapter Sample Configurations Sample Configurations Basil Sage Example One Three-Server Mutual TakeoverThree-Server Mutual Takeover after One Server Fails Cluster Configuration File for Three-Server Mutual Takeover Package Configuration File for pkg01 Nfs.cntl Control Script NFS Control Scripts for pkg01Package Configuration File for pkg02 NFS Control Scripts for pkg02 Package Configuration File for pkg03 NFS Control Scripts for pkg03 Packages with File Lock Migration Example Two One Adoptive Node for TwoSage Basil Pkg02 VOLUMEGROUP/dev/nfsu01 VOLUMEGROUP/dev/nfsu02 Package Configuration File for pkg01 NFS Control Scripts for pkg01 Hanfs.sh Control Script Nfs.flm Script NFS File Lock Migration and Monitor Scripts for pkg01Package Configuration File for pkg02 NFS Control Scripts for pkg02 NFSFLMSCRIPT=$0%/*/nfs2.flm NFS File Lock Migration and Monitor Scripts for pkg02 Failover Example Three Three-Server CascadingCascading Failover with Three Servers after One Server Fails VOLUMEGROUP/dev/nfsu01 VOLUMEGROUP/dev/nfsu02 Package Configuration File for pkg01 NFS Control Scripts for pkg01 NODENAMEthyme NODENAMEsage NODENAMEbasil IP0=15.13.114.244 SUBNET0=15.13.112.0 Example Four Two Servers with NFS Cross-Mounts Thyme Basil Cluster Configuration File for Two-Server NFS Cross-Mount NODENAMEthyme NODENAMEbasil NFS Control Scripts for pkg01 SNFS0=nfs1/hanfs/nfsu011 CNFS0=/nfs/nfsu011 NODENAMEbasil NODENAMEthyme NFS Control Scripts for pkg02 SNFS0=nfs2/hanfs/nfsu021 CNFS0=/nfs/nfsu021 Index Index Package configuration file nfs.conf default values
Related manuals
Manual 28 pages 17.67 Kb Manual 93 pages 21.07 Kb