HP Serviceguard Toolkit for NFS manual Overview of MC/ServiceGuard NFS

Page 8

Overview of MC/ServiceGuard NFS

MC/ServiceGuard NFS is a tool kit that enables you to use

MC/ServiceGuard to set up highly available NFS servers.

You must set up an MC/ServiceGuard cluster before you can set up Highly Available NFS. For instructions on setting up an MC/ServiceGuard cluster, see the Managing MC/ServiceGuard manual.

MC/ServiceGuard NFS is a separately purchased set of configuration files and control scripts, which you customize for your specific needs. These files, once installed, are located in /opt/cmcluster/nfs.

MC/ServiceGuard allows you to create high availability clusters of HP 9000 Series 800 computers. A high availability computer system allows applications to continue in spite of a hardware or software failure.

MC/ServiceGuard systems protect users from software failures as well as from failure of a system processing unit (SPU) or local area network (LAN) component. In the event that one component fails, the redundant component takes over, and MC/ServiceGuard coordinates the transfer between components.

An NFS server is a host that “exports” its local directories (makes them available for client hosts to mount using NFS). On the NFS client, these mounted directories look to users like part of the client’s local file system.

With MC/ServiceGuard NFS, the NFS server package containing the exported file systems can move to a different node in the cluster in the event of failure. After MC/ServiceGuard starts the NFS package on the adoptive node, the NFS file systems are re-exported from the adoptive node with minimum disruption of service to users. The client side hangs until the NFS server package comes up on the adoptive node. When the service returns, the user can continue access to the file. You do not need to restart the client.

8

Chapter 1

Image 8
Contents Managing MC/ServiceGuard NFS A.11.23.02 EditionLegal 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 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 MC/ServiceGuard NFS Installing MC/ServiceGuard NFS ReadmeCmmakepkg -p /opt/cmcluster/nfs/nfs.conf Monitoring NFS/TCP Services with MC ServiceGuard NFS ToolkitChapter 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 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 Package configuration file nfs.conf default values
Related manuals
Manual 28 pages 17.67 Kb Manual 93 pages 21.07 Kb