HP Serviceguard Toolkit for NFS manual SNFS0=nfs1/hanfs/nfsu011 CNFS0=/nfs/nfsu011

Page 87

Sample Configurations

Example Four - Two Servers with NFS Cross-Mounts

The first line in the customer_defined_run_cmds function executes the nfs1_xmnt script locally on host thyme (the primary node for pkg01). The second line, beginning with remsh, executes the nfs1_xmnt script remotely on host basil.

If pkg01 fails to come up, or if the remsh to host basil fails, the file system will not be mounted, and no error will be returned. The only way to be sure the file system was mounted successfully is to run the nfs1_xmnt script manually on both host thyme and host basil.

The only user-configurable values in the nfs1_xmnt script are the SNFS[n] and CNFS[n] variables. These specify the server location of the file system and the client mount point for the file system. The following line is the from the nfs1_xmnt script in this example configuration:

SNFS[0]=”nfs1:/hanfs/nfsu011”; CNFS[0]=”/nfs/nfsu011”

In the SNFS[0] variable, “nfs1” is the name that maps to the relocatable IP address of pkg01. It must be configured in the name service the host is using (DNS, NIS, or the /etc/hosts file). If you do not want to configure a name for the package, you can just specify the IP address in the SNFS[0] variable, as follows:

SNFS[0]=”15.13.114.243:/hanfs/nfsu011”;

CNFS[0]=”/nfs/nfsu011”

The client mount point, specified in the CNFS[0] variable, must be different from the location of the file system on the server (SNFS[0]).

The hanfs.sh Control Script

This section shows the NFS control script (hanfs1.sh) for the pkg01 package in this sample configuration. This example includes only the user-configured part of the script; the executable part of the script and most of the comments are omitted. This example does not enable the File Lock Migration feature.

XFS[0]=/hanfs/nfsu011

NFS_SERVICE_NAME[0]="nfs1.monitor

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

NFS_FILE_LOCK_MIGRATION=0

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

Chapter 3

87

Image 87
Contents Edition Serviceguard NFS Toolkit A.11.11.04 Administrator’s GuideLegal 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 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 the NFS Services How the Control and Monitor Scripts WorkStarting File Lock Migration Halting the NFS Services Monitoring the NFS Services On the Client Side Installing and Configuring Installing and Configuring Serviceguard NFS Readme Installing Serviceguard NFSCmmakepkg -p /opt/cmcluster/nfs/nfs.conf Serviceguard NFS Toolkit Monitoring NFS/TCP Services withMonitoring 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 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 Default values
Related manuals
Manual 93 pages 19.37 Kb Manual 28 pages 17.67 Kb