HP Serviceguard Toolkit for NFS manual Editing the NFS Monitor Script nfs.mon

Page 44

Installing and Configuring Serviceguard NFS

Configuring a Serviceguard NFS Package

NOTE

NOTE

Editing the NFS Monitor Script (nfs.mon)

The NFS monitor script, nfs.mon, contains NFS-specific monitor variables and functions. The nfs.mon script is an optional component of HA/NFS. The hanfs.sh file specifies whether the NFS monitor script is used. The following steps describe how to configure the NFS monitor script:

1.To monitor the File Lock Migration script (nfs.flm), set the

NFS_FILE_LOCK_MIGRATION variable to 1, and set the

NFS_FLM_SCRIPT name to match the hanfs.sh script value for this variable:

NFS_FILE_LOCK_MIGRATION=1

NFS_FLM_SCRIPT="${0%/*}nfs1.flm"

The file name of the NFS_FLM_SCRIPT script must be limited to 13 characters or fewer.

The nfs.mon script uses rpcinfo calls to check the status of various processes. If the rpcbind process is not running, the rpcinfo calls time out after 75 seconds. Because 10 rpcinfo calls are attempted before failover, it takes approximately 12 minutes to detect the failure. This problem has been fixed in release version 11.11.04 and 11.23.03.

2.You can call the nfs.mon script with the following optional arguments:

Interval - the time (in seconds) between the attempts for checking if NFS processes are up and running. The default is 10 seconds.

Lockd Retry - the number of attempts to ping rpc.lockd before exiting. The default is 4 attempts.

Retry - the number of attempts to ping the rpc.statd, rpc.mountd, nfsd, rpc.pcnfsd, and nfs.flm processes before exiting. The default is 4 attempts.

Portmap Retry - the number of attempts to ping the rpcbind process before exiting. The default is 4 attempts.

44

Chapter 2

Image 44
Contents Serviceguard NFS Toolkit A.11.11.04 Administrator’s Guide EditionLegal Notices Contents Index Figures Figures Overview of Serviceguard NFS Overview of Serviceguard NFS Limitations of Serviceguard NFS Overview of the NFS File Lock Migration Feature Overview of the NFS File Lock Migration Feature Supported Configurations Simple Failover to an Idle NFS Server Pkg1 disksFailover from One Active NFS Server to Another Pkg2 DisksHost Configured as Adoptive Node for Multiple PackagesCascading Failover with Three Adoptive Nodes Server-to-Server Cross Mounting NFS NFSSupported 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 Serviceguard NFS Installing Serviceguard NFS ReadmeCmmakepkg -p /opt/cmcluster/nfs/nfs.conf Monitoring NFS/TCP Services with Serviceguard NFS ToolkitMonitoring NFS/TCP Services with Serviceguard NFS Toolkit Before Creating a Serviceguard NFS Package NUMNFSD=10 Before Creating a Serviceguard NFS Package Mount -o nointr relocatableip/usr/src /usr/src Configuring a 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 a Serviceguard NFS Package Editing the NFS Control Script hanfs.sh Netswitchingenabled Editing the File Lock Migration Script nfs.flm Configuring a Serviceguard NFS Package Editing the NFS Monitor Script nfs.mon Configuring a Serviceguard NFS Package Editing the Package Configuration File nfs.conf Configuring a Serviceguard NFS Package Configuring Server-to-Server Cross-Mounts Optional SNFS0=nfs1/hanfs/nfsu011CNFS0=/nfs/nfsu011 Configuring a Serviceguard NFS Package Run the cluster using the following command cmruncl -v-f Configuring a Serviceguard NFS Package Chapter Sample Configurations Sample Configurations Example One Three-Server Mutual Takeover Basil SageThree-Server Mutual Takeover after One Server Fails Cluster Configuration File for Three-Server Mutual Takeover Package Configuration File for pkg01 NFS Control Scripts for pkg01 Nfs.cntl Control ScriptPackage Configuration File for pkg02 NFS Control Scripts for pkg02 Package Configuration File for pkg03 NFS Control Scripts for pkg03 Example Two One Adoptive Node for Two Packages with File Lock MigrationSage Basil Pkg02 VOLUMEGROUP/dev/nfsu01 VOLUMEGROUP/dev/nfsu02 Package Configuration File for pkg01 NFS Control Scripts for pkg01 Hanfs.sh Control Script NFS File Lock Migration and Monitor Scripts for pkg01 Nfs.flm ScriptPackage Configuration File for pkg02 NFS Control Scripts for pkg02 NFSFLMSCRIPT=$0%/*/nfs2.flm NFS File Lock Migration and Monitor Scripts for pkg02 Example Three Three-Server Cascading FailoverCascading 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 Default values
Related manuals
Manual 93 pages 19.37 Kb Manual 28 pages 17.67 Kb