HP Serviceguard Toolkit for NFS manual Etc/hosts file

Page 38

Installing and Configuring Serviceguard NFS

Configuring a Serviceguard NFS Package

4.Specify the IP address for the package and the address of the subnet to which the IP address belongs.

IP[0]=15.13.114.243

SUBNET[0]=15.13.112.0

The IP address you specify 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 should configure a name for this address in the DNS or NIS database, or in the

/etc/hosts file.

5.If you want to run the NFS monitor script , set the

NFS_SERVICE_NAME variable to the value of the SERVICE_NAME variable in the package configuration file. Each package must have a unique service name.

NFS_SERVICE_NAME[0]=nfs1.monitor

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

NFS_SERVICE_NAME and NFS_SERVICE_CMD variables:

#NFS_SERVICE_NAME[0]=nfs.monitor

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

By default, the NFS_SERVICE_NAME and NFS_SERVICE_CMD variables are commented out, and the NFS monitor script is not run.

You do not have to run the NFS monitor script. If your NFS package configuration file specifies PKG_SWITCHING_ENABLED YES and NET_SWITCHING_ENABLED YES (the defaults), the package will switch 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.

6.If you run the NFS monitor script, set the NFS_SERVICE_CMD variable to the full path name of the NFS monitor script.

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

The path name for the executable script does not have to be unique to each package. Every package can use the same script. Multiple instances of the monitor script can run on the same node without any problems, and if a package fails over, only the instance associated with that package is killed.

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

NFS_SERVICE_NAME and NFS_SERVICE_CMD variables:

38

Chapter 2

Image 38
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