HP Serviceguard Toolkit for NFS manual Before Creating a Serviceguard NFS Package

Page 31

Installing and Configuring Serviceguard NFS

Before Creating a Serviceguard NFS Package

between the primary and adoptive nodes, the client’s file handle would no longer point to the correct file location after movement of the package to a different node.

It is recommended that filesystems used for NFS be created as journalled file systems (FStype vxfs). This ensures the fastest recovery time in the event of a package switch to another node.

9.Make sure the user IDs and group IDs of those who access the Serviceguard NFS file system are the same on all nodes that can run the package. Make sure the /etc/passwd and /etc/group files are the same on the primary node and all adoptive nodes, or use NIS to manage the passwd and group databases. For information on configuring NIS, see the NFS Services Administrator’s Guide.

10.Create an entry for the name of the package in the DNS or NIS name resolution files, or in /etc/hosts, so that users will mount the exported file systems from the correct node. This entry maps the package name to the package’s relocatable IP address.

11.Decide whether to place executables locally on each client or on the NFS server. There are a number of trade-offs to be aware of regarding the location of executables with Serviceguard NFS.

The advantages of keeping executables local to each client are as follows:

No failover time. If the executables are local to the client, there is no delay if the NFS server fails.

Faster access to the executables than accessing them through the network.

The advantage of putting the executables on the NFS server is as follows:

Executable management. If the executables are located in one centralized location, the administrator must update only one copy when changes are made.

If executables are placed on the NFS server, you need to ensure that interrupts are handled correctly in a Serviceguard environment. The client must mount the filesystem using the nointr option. This mount option will ensure that the executable continues running correctly on the client after a failover of the server occurs. For example, enter the following command on the NFS client:

Chapter 2

31

Image 31
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 How the Control and Monitor Scripts Work Starting the NFS ServicesStarting 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