1. Manuals
  2. Brands
  3. Red Hat Manuals
  4. Software
  5. CLUSTER SUITE - CONFIGURING AND MANAGING A CLUSTER...
  6. Manual

Red Hat CLUSTER SUITE - CONFIGURING AND MANAGING A CLUSTER 2006 Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Red Hat Cluster Suite
Configuring and Managing a
Cluster

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the CLUSTER SUITE - CONFIGURING AND MANAGING A CLUSTER 2006 and is the answer not in the manual?

Questions and answers

Related Manuals for Red Hat CLUSTER SUITE - CONFIGURING AND MANAGING A CLUSTER 2006

Summary of Contents for Red Hat CLUSTER SUITE - CONFIGURING AND MANAGING A CLUSTER 2006

  • Page 1 Red Hat Cluster Suite Configuring and Managing a Cluster...
  • Page 2 All other trademarks referenced herein are the property of their respective owners. The GPG fingerprint of the security@redhat.com key is: CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E...

  • Page 3: Table Of Contents

    Table of Contents Introduction........................i 1. How To Use This Manual ..................i 2. Document Conventions..................ii 3. More to Come ......................v 3.1. Send in Your Feedback .................v 4. Activate Your Subscription ................vi 4.1. Provide a Red Hat Login..............vi 4.2.
  • Page 4 5.2. Configuring Shared Storage..............77 5.3. Installing and Configuring the Apache HTTP Server......78 II. Configuring a Linux Virtual Server Cluster ............81 6. Introduction to Linux Virtual Server..............83 6.1. Technology Overview .................83 6.2. Basic Configurations................84 7. Linux Virtual Server Overview................85 7.1. A Basic LVS Configuration ..............85 7.2.
  • Page 5 Index..........................165 Colophon.........................171...

  • Page 7: Introduction

    HTML, PDF, and RPM versions of the manuals are available on the Red Hat Enterprise Linux Documentation CD and online at: http://www.redhat.com/docs/ 1. How To Use This Manual This manual contains information about setting up a Red Hat Cluster Manager system.

  • Page 8: Document Conventions

    Introduction Chapter 2 Hardware Installation and Operating System Configuration • Chapter 3 Installing and Configuring Red Hat Cluster Suite Software • Part II Configuring a Linux Virtual Server Cluster describes how to achieve load balancing in an Red Hat Enterprise Linux cluster by using the Linux Virtual Server. Appendix A Supplementary Hardware Information contains detailed configuration infor- mation on specific hardware devices and shared storage configurations.
  • Page 9 Introduction file in your home directory contains bash shell definitions and aliases .bashrc for your own use. file contains information about different system devices and file /etc/fstab systems. Install the RPM if you want to use a Web server log file analysis program. webalizer application This style indicates that the program is an end-user application (as opposed to system...
  • Page 10 Introduction button on a GUI screen or window This style indicates that the text can be found on a clickable button on a GUI screen. For example: Click on the Back button to return to the webpage you last viewed. computer output Text in this style indicates text displayed to a shell prompt such as error messages and responses to commands.

  • Page 11: More To Come

    Introduction Note Remember that Linux is case sensitive. In other words, a rose is not a ROSE is not a rOsE. The directory contains additional documentation for packages installed /usr/share/doc/ on your system. Important If you modify the DHCP configuration file, the changes do not take effect until you restart the DHCP daemon.

  • Page 12: Send In Your Feedback

    If you spot a typo, or if you have thought of a way to make this manual better, we would love to hear from you. Please submit a report in Bugzilla (http://bugzilla.redhat.com/bugzilla/) against the component rh-cs Be sure to mention the manual’s identifier: rh-cs(EN)-4-Print-RHI (2007-01-05T17:28) By mentioning this manual’s identifier, we know exactly which version of the guide you...

  • Page 13: Provide Your Subscription Number

    You can provide your subscription number when prompted during the Setup Agent or by visiting http://www.redhat.com/register/. 4.3. Connect Your System The Red Hat Network Registration Client helps you connect your system so that you can begin to get updates and perform systems management.
  • Page 14 viii Introduction...

  • Page 15: Using The Red Hat Cluster Manager

    I. Using the Red Hat Cluster Manager Clustered systems provide reliability, scalability, and availability to critical production ser- vices. Using the Red Hat Cluster Manager, administrators can create high availability clus- ters for filesharing, Web servers, and more. This part discusses the installation and con- figuration of cluster systems using the recommended hardware and Red Hat Enterprise Linux.

  • Page 17: Red Hat Cluster Manager Overview

    Chapter 1. Red Hat Cluster Manager Overview Red Hat Cluster Manager allows administrators to connect separate systems (called mem- bers or nodes) together to create failover clusters that ensure application availability and data integrity under several failure conditions. Administrators can use Red Hat Cluster Manager with database applications, file sharing services, web servers, and more.

  • Page 18: Red Hat Cluster Manager Features

    Chapter 1. Red Hat Cluster Manager Overview In addition, you can cleanly stop the cluster services running on a cluster system and then restart them on another system. This cluster-service relocation capability allows you to maintain application and data availability when a cluster node requires maintenance. 1.1.

  • Page 19: Watchdog Timers

    Chapter 1. Red Hat Cluster Manager Overview network-accessible database cluster service is usually assigned an IP address, which is failed over along with the cluster service to maintain transparent access for clients. The cluster-service framework can also easily extend to other applications through the use of customized init scripts.
  • Page 20 Chapter 1. Red Hat Cluster Manager Overview maintain application availability and data integrity. For example, if a node completely fails, a healthy node (in the associated failover domain, if used) starts the service or services that the failed node was running prior to failure. Cluster services already running on the healthy node are not significantly disrupted during the failover process.

  • Page 21: Cluster

    Chapter 1. Red Hat Cluster Manager Overview Software Components Description Subsystem Cluster Command used to manage cluster system-config-cluster Configuration Tool configuration in a graphical setting. Cluster Notifies of an updated ccs_tool ccsd Configuration file. Also, used for cluster.conf System (CCS) upgrading a configuration file from a Red Hat GFS 6.0 (or earlier) cluster to the format of the Red Hat...
  • Page 22 Chapter 1. Red Hat Cluster Manager Overview Software Components Description Subsystem Fence agent for Bull Novascale fence_bullpap Platform Administration Processor (PAP) Interface. Fence agent for Dell Remote fence_drac Access Controller/Modular Chassis (DRAC/MC). Fence agent used with Egenera fence_egenera BladeFrame system. Fence agent used with GNBD fence_gnbd storage.
  • Page 23 Chapter 1. Red Hat Cluster Manager Overview Software Components Description Subsystem Fence agent for WTI power switch. fence_wti The fence daemon. Manages the fenced fence domain. Library for Distributed Lock libdlm.so.1.0.0 Manager (DLM) support. Kernel module that is installed on dlm.ko cluster nodes for Distributed Lock Manager (DLM) support.
  • Page 24 Chapter 1. Red Hat Cluster Manager Overview...

  • Page 25: Hardware Installation And Operating System Configuration

    Chapter 2. Hardware Installation and Operating System Configuration To set up the hardware configuration and install Red Hat Enterprise Linux, follow these steps: Choose a cluster hardware configuration that meets the needs of applications and users; • refer to Section 2.1 Choosing a Hardware Configuration. Set up and connect the members and the optional console switch and network switch or •...
  • Page 26 Chapter 2. Hardware Installation and Operating System Configuration Performance requirements of applications and users Choose a hardware configuration that provides adequate memory, CPU, and I/O re- sources. Be sure that the configuration chosen can handle any future increases in workload as well. Cost restrictions The hardware configuration chosen must meet budget requirements.
  • Page 27 Chapter 2. Hardware Installation and Operating System Configuration Warning The minimum cluster configuration is not a supported solution and should not be used in a production environment, as it does not ensure data integrity under all failure conditions. Hardware Description At least two server systems Each system becomes a node exclusively for use in the cluster;...
  • Page 28 Chapter 2. Hardware Installation and Operating System Configuration Table 2-2. Improving Availability and Data Integrity Figure 2-1 illustrates a hardware configuration with improved availability. This configura- tion uses a fence device (in this case, a network-attached power switch) and the nodes are configured for Red Hat GFS storage attached to a Fibre Channel SAN switch.

  • Page 29: Cluster Hardware

    Chapter 2. Hardware Installation and Operating System Configuration Network power switches to enable each node to power-cycle the other nodes during the • failover process Ethernet interfaces configured to use channel bonding • At least two UPS systems for a highly-available source of power •...

  • Page 30: Cluster Hardware Components

    Chapter 2. Hardware Installation and Operating System Configuration switch or network hub, which enables the connection of the nodes to a network. A cluster may also include a console switch, which facilitates the management of multiple nodes and eliminates the need for separate monitors, mouses, and keyboards for each node. One type of console switch is a terminal server, which enables connection to serial con- soles and management of many nodes from one remote location.

  • Page 31: Cluster Node Hardware

    Chapter 2. Hardware Installation and Operating System Configuration Hardware Quantity Description Required Cluster Each node must provide enough PCI slots, nodes (maximum network slots, and storage adapters for the supported) cluster hardware configuration. Because attached storage devices must have the same device special file on each node, it is recommended that the nodes have symmetric I/O subsystems.
  • Page 32 Chapter 2. Hardware Installation and Operating System Configuration Hardware Quantity Description Required Network One for each Each network connection requires a interface network network interface installed in a node. connection Network A network switch or hub allows switch or connection of multiple nodes to a network. Network One for each A conventional network cable, such as a...
  • Page 33 Chapter 2. Hardware Installation and Operating System Configuration Hardware Quantity Description Required External At least one Use Fibre Channel or single-initiator disk storage parallel SCSI to connect the cluster nodes enclosure to a single or dual-controller RAID array. To use single-initiator buses, a RAID controller must have multiple host ports and provide simultaneous access to all the logical units on the host ports.

  • Page 34: Setting Up The Nodes

    Chapter 2. Hardware Installation and Operating System Configuration Hardware Quantity Description Required Fibre As required A Fibre Channel cable connects a host bus Only for Channel by hardware adapter to a storage enclosure port, a Fibre Fibre cable configura- Channel hub, or a Fibre Channel switch. If Channel tion a hub or switch is used, additional cables...

  • Page 35: Installing The Basic Cluster Hardware

    Chapter 2. Hardware Installation and Operating System Configuration optional console switch and network switch or hub. Follow these steps: 1. In all nodes, install the required network adapters and host bus adapters. Refer to Section 2.3.1 Installing the Basic Cluster Hardware for more information about per- forming this task.

  • Page 36: Shared Storage

    Chapter 2. Hardware Installation and Operating System Configuration Table 2-10. Installing the Basic Cluster Hardware Most systems come with at least one serial port. If a system has graphics display capabil- ity, it is possible to use the serial console port for a power switch connection. To expand your serial port capacity, use multi-port serial PCI cards.
  • Page 37 Chapter 2. Hardware Installation and Operating System Configuration For remote file systems such as NFS, you may use gigabit Ethernet for improved band- • width over 10/100 Ethernet connections. Consider redundant links or channel bonding for improved remote file system availability. Refer to Section 2.5.1 Configuring Ethernet Channel Bonding for more information.

  • Page 38: Installing And Configuring Red Hat Enterprise Linux

    Chapter 2. Hardware Installation and Operating System Configuration After setting up the network switch or hub, connect it to each node by using conven- tional network cables. A terminal server, if used, is connected to the network switch or hub through a network cable.
  • Page 39 Chapter 2. Hardware Installation and Operating System Configuration 5. Decrease the alternate kernel boot timeout limit to reduce boot time for nodes. Refer to Section 2.4.2 Decreasing the Kernel Boot Timeout Limit for more information about performing this task. 6. Ensure that no login (or ) programs are associated with the serial ports that getty are being used for the remote power switch connection (if applicable).
  • Page 40 Chapter 2. Hardware Installation and Operating System Configuration 127.0.0.1 localhost.localdomain localhost 192.168.1.81 node1.example.com node1 193.186.1.82 node2.example.com node2 193.186.1.83 node3.example.com node3 The previous example shows the IP addresses and hostnames for three nodes (node1, node2, and node3), Important Do not assign the node hostname to the localhost (127.0.0.1) address, as this causes issues with the CMAN cluster management system.
  • Page 41 Itanium system, apply changes made file, invoke the command. /boot/efi/efi/redhat/elilo.conf /sbin/elilo 2.4.3. Displaying Console Startup Messages Use the command to display the console startup messages. Refer to the dmesg(8) dmesg man page for more information. The following example of output from the...
  • Page 42 Chapter 2. Hardware Installation and Operating System Configuration May 22 14:02:11 storage3 kernel: Detected scsi disk sdg at scsi1, channel 0, id 9, l May 22 14:02:11 storage3 kernel: Vendor: SEAGATE Model: ST318203LC Rev: 0 May 22 14:02:11 storage3 kernel: Detected scsi disk sdh at scsi1, channel 0, id 10, May 22 14:02:11 storage3 kernel: Vendor: SEAGATE Model: ST318203LC...

  • Page 43: Setting Up And Connecting The Cluster Hardware

    Chapter 2. Hardware Installation and Operating System Configuration 128 ptm 136 pts 171 ieee1394 180 usb 216 rfcomm 226 drm 254 pcmcia Block devices: 1 ramdisk 2 fd 3 ide0 8 sd 9 md 65 sd 66 sd 67 sd 68 sd 69 sd 70 sd...
  • Page 44 Chapter 2. Hardware Installation and Operating System Configuration 1. Shut down the nodes and disconnect them from their power source. 2. When using power switches, set up the switches and connect each node to a power switch. Refer to Section 2.5.2 Configuring a Fence Device for more information. In addition, it is recommended to connect each power switch (or each node’s power cord if not using power switches) to a different UPS system.

  • Page 45: Configuring

    Chapter 2. Hardware Installation and Operating System Configuration 2.5.1. Configuring Ethernet Channel Bonding Ethernet channel bonding in a no-single-point-of-failure cluster system allows for a fault tolerant network connection by combining two Ethernet devices into one virtual device. The resulting channel bonded interface ensures that in the event that one Ethernet device fails, the other device will become active.
  • Page 46 Chapter 2. Hardware Installation and Operating System Configuration 2.5.2. Configuring a Fence Device Fence devices enable a node to power-cycle another node before restarting its services as part of the failover process. The ability to remotely disable a node ensures data integrity is maintained under any failure condition.
  • Page 47 Chapter 2. Hardware Installation and Operating System Configuration It is not recommended to use a single UPS infrastructure as the sole source of power for the cluster. A UPS solution dedicated to the cluster is more flexible in terms of manageability and availability.
  • Page 48 Chapter 2. Hardware Installation and Operating System Configuration Figure 2-3. Single UPS System Configuration Many vendor-supplied UPS systems include Red Hat Enterprise Linux applications that monitor the operational status of the UPS system through a serial port connection. If the battery power is low, the monitoring software initiates a clean system shutdown.
  • Page 49 Chapter 2. Hardware Installation and Operating System Configuration beginning of the given range. The following example shows how to create two partitions of 20 MB each on an empty disk. (parted) mkpart primary ext3 0 20 (parted) mkpart primary ext3 20 40 (parted) p Disk geometry for /dev/sda: 0.000-4340.294 megabytes Disk label type: msdos...
  • Page 50 Chapter 2. Hardware Installation and Operating System Configuration 998.872 2001.952 logical A partition may be removed using ’s command. For example: • parted (parted) rm 1 (parted) p Disk geometry for /dev/sda: 0.000-4340.294 megabytes Disk label type: msdos Minor Start Type Filesystem Flags...

  • Page 51: Installing And Configuring Red Hat Cluster Suite Software

    Chapter 3. Installing and Configuring Red Hat Cluster Suite Software This chapter describes how to install and configure Red Hat Cluster Suite software and consists of the following sections: Section 3.1 Software Installation and Configuration Tasks • Section 3.2 Overview of the Cluster Configuration Tool •...

  • Page 52: Overview Of The Cluster Configuration Tool

    Chapter 3. Installing and Configuring Red Hat Cluster Suite Software 5. Creating cluster members. Refer to Section 3.7 Adding and Deleting Members. 6. Creating failover domains. Refer to Section 3.8 Configuring a Failover Domain. 7. Creating resources. Refer to Section 3.9 Adding Cluster Resources. 8.
  • Page 53 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software Figure 3-1. Cluster Configuration Tool The Cluster Configuration Tool uses a hierarchical structure to show relationships among components in the cluster configuration. A triangle icon to the left of a component name indicates that the component has one or more subordinate components assigned to it.
  • Page 54 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software Managed Resources — Defines failover domains, resources, and services. • Failover Domains — Use this section to configure one or more subsets of cluster • nodes used to run a service in the event of a node failure. Failover domains are rep- resented as subordinate elements under Failover Domains.

  • Page 55: Installing The Red Hat Cluster Suite Packages

    Suite and Red Hat GFS packages. From the Red Hat Network channel, you can manage entitlements for your cluster nodes and upgrade packages for each node within the Red Hat Network Web-based interface. For more information on using Red Hat Network, visit http://rhn.redhat.com.

  • Page 56: Starting The Cluster Configuration Tool

    Chapter 3. Installing and Configuring Red Hat Cluster Suite Software To automatically install RPMs, follow these steps at each node: 1. Log on as the root user. Note The following steps specify using with the option. up2date installall --force Using the option includes kernels that are required for successful instal- --force lation of Red Hat Cluster Suite and Red Hat GFS.
  • Page 57 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software #system-config-cluster a. If this is the first time you have started the Cluster Configuration Tool, the program prompts you to either open an existing configuration or create a new one. Click Create New Configuration to start a new configuration file (refer to Figure 3-3).
  • Page 58 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software Figure 3-4. Choosing a Lock Method 2. Starting the Cluster Configuration Tool displays a graphical representation of the configuration (Figure 3-5) as specified in the cluster configuration file, /etc/cluster/cluster.conf...

  • Page 59: Naming The Cluster

    Chapter 3. Installing and Configuring Red Hat Cluster Suite Software Figure 3-5. The Cluster Configuration Tool 3.5. Naming The Cluster Naming the cluster consists of specifying a cluster name, a configuration version (optional), and values for Post-Join Delay and Post-Fail Delay. Name the cluster as follows: 1.

  • Page 60: Configuring Fence Devices

    Chapter 3. Installing and Configuring Red Hat Cluster Suite Software Choose the cluster name carefully. The only way to change the name of a Red Hat cluster is to create a new cluster configuration with the new name. 4. (Optional) The Config Version value is set to 1 by default and is automatically incremented each time you save your cluster configuration.
  • Page 61 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software 1. Click Fence Devices. At the bottom of the right frame (labeled Properties), click the Add a Fence Device button. Clicking Add a Fence Device causes the Fence Device Configuration dialog box to be displayed (refer to Figure 3-6). Figure 3-6.
  • Page 62 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software Field Description Name A name for the Brocade device connected to the cluster. IP Address The IP address assigned to the device. Login The login name used to access the device. Password The password used to authenticate the connection to the device.
  • Page 63 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software Field Description Name A name for the GNBD device used to fence the cluster. Note that the GFS server must be accessed via GNBD for cluster node fencing support. Server The hostname of each GNBD to disable.
  • Page 64 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software Field Description IP Address The IP address assigned to the IPMI port. Login The login name of a user capable of issuing power on/off commands to the given IPMI port. Password The password used to authenticate the connection to the IPMI port.

  • Page 65: Adding And Deleting Members

    Chapter 3. Installing and Configuring Red Hat Cluster Suite Software Field Description Name A name for the SANBox2 device connected to the cluster. IP Address The IP address assigned to the device. Login The login name used to access the device. Password The password used to authenticate the connection to the device.
  • Page 66 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software 3.7.1. Adding a Member to a Cluster To add a member to a new cluster, follow these steps: 1. Click Cluster Node. 2. At the bottom of the right frame (labeled Properties), click the Add a Cluster Node button.
  • Page 67 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software Note The node on which you are running the Cluster Configuration Tool must be explic- itly added as a cluster member; the node is not automatically added to the cluster configuration as a result of running the Cluster Configuration Tool.
  • Page 68 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software 8. Choose File => Save to save the changes to the cluster configuration. 3.7.2. Adding a Member to a Running Cluster The procedure for adding a member to a running cluster depends on whether the cluster contains only two nodes or more than two nodes.
  • Page 69 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software 6. Start cluster software on all cluster nodes (including the added one) by running the following commands in this order: service ccsd start service cman start service fenced start service clvmd start , if you are using Red Hat GFS service gfs start service rgmanager start...
  • Page 70 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software 5. Start the Red Hat Cluster Suite management GUI. At the Cluster Configuration Tool tab, verify that the configuration is correct. At the Cluster Status Tool tab verify that the nodes and services are running as expected. 3.7.3.

  • Page 71: Configuring A Failover Domain

    Chapter 3. Installing and Configuring Red Hat Cluster Suite Software d. At that dialog box, click Yes to confirm deletion. e. Propagate the updated configuration by clicking the Send to Cluster button. (Propagating the updated configuration automatically saves the configuration.) 4.
  • Page 72 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software Unrestricted — Allows you to specify that a subset of members are preferred, but that a • cluster service assigned to this domain can run on any available member. Restricted — Allows you to restrict the members that can run a particular cluster service. •...
  • Page 73 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software 2. At the bottom of the right frame (labeled Properties), click the Create a Failover Domain button. Clicking the Create a Failover Domain button causes the Add Failover Domain dialog box to be displayed. 3.
  • Page 74 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software Figure 3-11. Failover Domain Configuration: Adjusting Priority b. For each node that requires a priority adjustment, click the node listed in the Member Node/Priority columns and adjust priority by clicking one of the Adjust Priority arrows.
  • Page 75 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software 3.8.2. Removing a Failover Domain To remove a failover domain, follow these steps: 1. At the left frame of the the Cluster Configuration Tool, click the failover domain that you want to delete (listed under Failover Domains). 2.

  • Page 76: Adding Cluster Resources

    Chapter 3. Installing and Configuring Red Hat Cluster Suite Software 5. At the Cluster Configuration Tool, perform one of the following actions depending on whether the configuration is for a new cluster or for one that is operational and running: New cluster —...
  • Page 77 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software File System Type — Choose the file system for the resource using the drop- down menu. Mount Point — Choose the path to which the file system resource is mounted. Device —...
  • Page 78 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software NFS Client Name — Enter a name for the NFS client resource. Target — Enter a target for the NFS client resource. Supported targets are host- names, IP addresses (with wild-card support), and netgroups. Read-Write and Read Only options —...

  • Page 79: Adding A Cluster Service To The Cluster

    Chapter 3. Installing and Configuring Red Hat Cluster Suite Software 3.10. Adding a Cluster Service to the Cluster To add a cluster service to the cluster, follow these steps: 1. At the left frame, click Services. 2. At the bottom of the right frame (labeled Properties), click the Create a Service button.
  • Page 80 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software 6. Run Exclusive checkbox — This sets a policy wherein the service only runs on nodes that have no other services running on them. For example, for a very busy web server that is clustered for high availability, it would would be advisable to keep that service on a node alone with no other services competing for his resources —...

  • Page 81: Propagating The Configuration File: New Cluster

    Chapter 3. Installing and Configuring Red Hat Cluster Suite Software Note To verify the existence of the IP service resource used in a cluster service, you must use command on a cluster node. The following output shows the /sbin/ip addr list command executed on a node running a cluster service: /sbin/ip addr list 1: lo:...
  • Page 82 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software service ccsd start according to the type service lock_gulmd start service cman start of lock manager used (DLM clusters only) service fenced start service clvmd start , if you are using Red Hat GFS service gfs start service rgmanager start 7.

  • Page 83: Cluster Administration

    Chapter 4. Cluster Administration This chapter describes the various administrative tasks for maintaining a cluster after it has been installed and configured. 4.1. Overview of the Cluster Status Tool The Cluster Status Tool is part of the Red Hat Cluster Suite management GUI, (the package) and is accessed by a tab in the Red Hat Cluster Suite system-config-cluster management GUI.

  • Page 84: Displaying Cluster And Service Status

    Chapter 4. Cluster Administration Figure 4-1. Cluster Status Tool 4.2. Displaying Cluster and Service Status Monitoring cluster and application service status can help identify and resolve problems in the cluster environment. The following tools assist in displaying cluster status information: The Cluster Status Tool •...

  • Page 85: Service Status

    Chapter 4. Cluster Administration Cluster and service status includes the following information: Cluster member system status • Service status and which cluster system is running the service or owns the service • The following tables describe how to analyze the status information shown by the Cluster Status Tool and the utility.
  • Page 86 Chapter 4. Cluster Administration Service Status Description Started The service resources are configured and available on the cluster system that owns the service. Pending The service has failed on a member and is pending start on another member. Disabled The service has been disabled, and does not have an assigned owner.

  • Page 87: Starting And Stopping The Cluster Software

    Chapter 4. Cluster Administration To monitor the cluster and display status at specific time intervals from a shell prompt, option, where time specifies the number of seconds invoke with the -i time clustat between status snapshots. The following example causes the utility to display clustat cluster status every 10 seconds:...
  • Page 88 Chapter 4. Cluster Administration Warning Do not manually edit the contents of the file without guid- /etc/cluster/cluster.conf ance from an authorized Red Hat representative or unless you fully understand the con- sequences of editing the file manually. /etc/cluster/cluster.conf Important Although the Cluster Configuration Tool provides a Quorum Votes parameter in the Properties dialog box of each cluster member, that parameter is intended only for use during initial cluster configuration.

  • Page 89: Backing Up And Restoring The Cluster Database

    Chapter 4. Cluster Administration 4.5. Backing Up and Restoring the Cluster Database The Cluster Configuration Tool automatically retains backup copies of the three most recently used configuration files (besides the currently used configuration file). Retaining the backup copies is useful if the cluster does not function correctly because of misconfig- uration and you need to return to a previous working configuration.

  • Page 90: Updating The Cluster Software

    Chapter 4. Cluster Administration Note The Cluster Configuration Tool does not display the Send to Cluster button if the cluster is new and has not been started yet, or if the node from which you are run- ning the Cluster Configuration Tool is not a member of the cluster. If the Send to Cluster button is not displayed, you can still use the Cluster Configuration Tool;...

  • Page 91: Diagnosing And Correcting Problems In A Cluster

    Chapter 4. Cluster Administration chkconfig --level 2345 lock_gulmd off chkconfig --level 2345 cman off chkconfig --level 2345 ccsd off Once the problems with the disabled cluster member have been resolved, use the following commands to allow the member to rejoin the cluster: chkconfig --level 2345 rgmanager on chkconfig --level 2345 gfs on chkconfig --level 2345 clvmd on...
  • Page 92 Chapter 4. Cluster Administration...

  • Page 93: Setting Up Apache Http Server

    Chapter 5. Setting Up Apache HTTP Server This chapter contains instructions for configuring Red Hat Enterprise Linux to make the Apache HTTP Server highly available. The following is an example of setting up a cluster service that fails over an Apache HTTP Server.

  • Page 94: Installing And Configuring The Apache Http Server

    Chapter 5. Setting Up Apache HTTP Server 5.2. Configuring Shared Storage To set up the shared file system resource, perform the following tasks as root on one cluster system: 1. On one cluster node, use the interactive utility to create a partition to use for parted the document root directory.
  • Page 95 Chapter 5. Setting Up Apache HTTP Server Specify a unique IP address to which the service will listen for requests. For ex- • ample: Listen 192.168.1.100:80 This IP address then must be configured as a cluster resource for the service using the Cluster Configuration Tool.
  • Page 96 Chapter 5. Setting Up Apache HTTP Server 2. Add a device for the Apache HTTP Server content files and/or custom scripts. Click Create a Resource. • In the Resource Configuration dialog, select File System from the drop-down • menu. Enter the Name for the resource (for example, httpd-content. •...

  • Page 97: Configuring A Linux Virtual Server Cluster

    II. Configuring a Linux Virtual Server Cluster Building a Linux Virtual Server (LVS) system offers highly-available and scalable solution for production services using specialized routing and load-balancing techniques configured through the Piranha Configuration Tool. This part discusses the configuration of high- performance systems and services with Red Hat Enterprise Linux and LVS.

  • Page 99: Introduction To Linux Virtual Server

    Chapter 6. Introduction to Linux Virtual Server Using Red Hat Enterprise Linux, it is possible to create highly available server clustering solutions able to withstand many common hardware and software failures with little or no interruption of critical services. By allowing multiple computers to work together in offer- ing these critical services, system administrators can plan and execute system maintenance and upgrades without service interruption.

  • Page 100: Basic Configurations

    Chapter 6. Introduction to Linux Virtual Server hardware to implement a fully redundant environment in which services can run uninter- rupted by hardware failures. However, fault tolerant systems do not account for operator and software errors which Red Hat Enterprise Linux can address through service redundancy. Also, since Red Hat Enterprise Linux is designed to run on commodity hardware, it creates an environment with a high level of system availability at a fraction of the cost of fault tolerant hardware.

  • Page 101: Linux Virtual Server Overview

    Chapter 7. Linux Virtual Server Overview Red Hat Enterprise Linux LVS clustering uses a Linux machine called the active router to send requests from the Internet to a pool of servers. To accomplish this, LVS clusters consist of two basic machine classifications — the LVS routers (one active and one backup) and a pool of real servers which provide the critical services.
  • Page 102 Chapter 7. Linux Virtual Server Overview Figure 7-1. A Basic LVS Configuration Service requests arriving at the LVS cluster are addressed to a virtual IP address or VIP. This is a publicly-routable address the administrator of the site associates with a fully- qualified domain name, such as www.example.com, and which is assigned to one or more virtual server .

  • Page 103: A Three Tiered Lvs Configuration

    Chapter 7. Linux Virtual Server Overview The active router also dynamically monitors the overall health of the specific services on the real servers through simple send/expect scripts. To aid in detecting the health of services that require dynamic data, such as HTTPS or SSL, the administrator can also call external executables.
  • Page 104 Chapter 7. Linux Virtual Server Overview 7.2. A Three Tiered LVS Configuration Figure 7-2 shows a typical three tiered LVS cluster topology. In this example, the active LVS router routes the requests from the Internet to the pool of real servers. Each of the real servers then accesses a shared data source over the network.

  • Page 105: Lvs Scheduling Overview

    Chapter 7. Linux Virtual Server Overview cluster to serve both of these roles simultaneously. The third tier in the above example does not have to use Red Hat Cluster Manager, but failing to use a highly available solution would introduce a critical single point of failure. 7.3.

  • Page 106: Weighted Least Connections

    Chapter 7. Linux Virtual Server Overview that it is network-connection based and not host-based. LVS round-robin scheduling also does not suffer the imbalances caused by cached DNS queries. Weighted Round-Robin Scheduling Distributes each request sequentially around the pool of real servers but gives more jobs to servers with greater capacity.

  • Page 107: Routing Methods

    Chapter 7. Linux Virtual Server Overview the real server with the least connections from the overall pool of real servers to the subset of real servers for that destination IP. The most loaded node is then dropped from the real server subset to prevent over-replication. Destination Hash Scheduling Distributes requests to the pool of real servers by looking up the destination IP in a static hash table.
  • Page 108 Chapter 7. Linux Virtual Server Overview 7.4.1. NAT Routing Figure 7-3, illustrates an LVS cluster utilizing NAT routing to move requests between the Internet and a private network. Figure 7-3. An LVS Cluster Implemented with NAT Routing In the example, there are two NICs in the active LVS router. The NIC for the Internet has a real IP address on eth0 and has a floating IP address aliased to eth0:1.

  • Page 109: Persistence And Firewall Marks

    Chapter 7. Linux Virtual Server Overview In this example, the LVS router’s public LVS floating IP address and private NAT floating IP address are aliased to two physical NICs. While it is possible to associate each floating IP address to its own physical device on the LVS router nodes, having more than two NICs is not a requirement.

  • Page 110: Lvs Cluster - A Block Diagram

    Chapter 7. Linux Virtual Server Overview firewall marks can be used to bundle HTTP connections on port 80 and secure, HTTPS connections on port 443. By assigning the same firewall mark to the virtual server for each protocol, state information for the transaction can be preserved because the LVS router forwards all requests to the same real server after a connection is opened.
  • Page 111 Chapter 7. Linux Virtual Server Overview Once started, the daemon calls the utility to configure and maintain the IPVS ipvsadm routing table in the kernel and starts a process for each configured virtual server on nanny each real server. Each process checks the state of one configured service on one nanny real server, and tells the...

  • Page 112: Piranha Configuration Tool

    Chapter 7. Linux Virtual Server Overview 7.6.1.4. nanny monitoring daemon runs on the active LVS router. Through this daemon, the nanny active router determines the health of each real server and, optionally, monitors its work- load. A separate process runs for each service defined on each real server. 7.6.1.5.

  • Page 113: Initial Lvs Configuration

    Chapter 8. Initial LVS Configuration After installing Red Hat Enterprise Linux, you must take some basic steps to set up both the LVS routers and the real servers in the LVS cluster. This chapter covers these initial steps in detail. Note The LVS router node that becomes the active node once the cluster is started is also referred to as the primary node.

  • Page 114: Setting A Password For The Piranha Configuration Tool

    Chapter 8. Initial LVS Configuration If you are clustering multi-port services or using firewall marks, you must also enable the service. iptables It is best to set these services to activate in both runlevel 3 and runlevel 5. To accomplish this using , type the following command for each service: chkconfig...

  • Page 115: Starting The Piranha Configuration Tool Service

    Chapter 8. Initial LVS Configuration If the password is changed during an active Piranha Configuration Tool session, the administrator is prompted to provide the new password. 8.3. Starting the Piranha Configuration Tool Service After you have set the password for the Piranha Configuration Tool, start or restart the service located in .

  • Page 116: Limiting Access To The Piranha Configuration Tool

    Chapter 8. Initial LVS Configuration 8.3.1. Configuring the Piranha Configuration Tool Web Server Port The Piranha Configuration Tool runs on port 3636 by default. To change this port num- ber, change the line in Section 2 of the Web server config- Listen 3636 piranha-gui uration file...

  • Page 117: Turning On Packet Forwarding

    Chapter 8. Initial LVS Configuration Order deny,allow Deny from all Allow from 192.168.1.100 Allow from 172.16.57 In this example, only Web browsers from the machine with the IP address of 192.168.1.100 and machines on the 172.16.57/24 network can access the Piranha Configuration Tool. Caution Editing the Piranha Configuration Tool file limits access to the configura-...
  • Page 118 Chapter 8. Initial LVS Configuration It may also be useful to access the real servers remotely, so the daemon should also sshd be installed and running.

  • Page 119: Setting Up A Red Hat Enterprise Linux Lvs Cluster

    Chapter 9. Setting Up a Red Hat Enterprise Linux LVS Cluster A Red Hat Enterprise Linux LVS cluster consists of two basic groups: the LVS routers and the real servers. To prevent a single point of failure, each groups should contain at least two member systems.
  • Page 120 Chapter 9. Setting Up a Red Hat Enterprise Linux LVS Cluster ration Tool. In particular, FTP services and the use of firewall marks requires extra manual configuration of the LVS routers to route requests properly. 9.1.1. Configuring Network Interfaces for a NAT LVS Cluster To set up a NAT LVS cluster, the administrator must first configure the network interfaces for the public network and the private network on the LVS routers.
  • Page 121 Chapter 9. Setting Up a Red Hat Enterprise Linux LVS Cluster Important Be sure each interface on the backup node services the same network as the interface on primary node. For instance, if eth0 connects to the public network on the primary node, it must also connect to the public network on the backup node as well.

  • Page 122: Putting The Cluster Together

    Chapter 9. Setting Up a Red Hat Enterprise Linux LVS Cluster 9.1.3. Enabling NAT Routing on the LVS Routers In a simple NAT LVS cluster where each clustered service uses only one port, like HTTP on port 80, the administrator needs only to enable packet forwarding on the LVS routers for the requests to be properly routed between the outside world and the real servers.
  • Page 123 Chapter 9. Setting Up a Red Hat Enterprise Linux LVS Cluster After physically connecting together the cluster hardware, configure the network inter- faces on the primary and backup LVS routers. This can be done using a graphical ap- plication such as system-config-network or by editing the network scripts manually. For more information about adding devices using system-config-network, see the chapter ti- tled Network Configuration in the Red Hat Enterprise Linux System Administration Guide.

  • Page 124: Multi-Port Services And Lvs Clustering

    Chapter 9. Setting Up a Red Hat Enterprise Linux LVS Cluster 9.3. Multi-port Services and LVS Clustering LVS routers under any topology require extra configuration when creating multi-port LVS services. Multi-port services can be created artificially by using firewall marks to bundle together different, but related protocols, such as HTTP (port 80) and HTTPS (port 443), or when LVS is used to cluster true multi-port protocols, such as FTP.

  • Page 125: Ftp In An Lvs Cluster

    Chapter 9. Setting Up a Red Hat Enterprise Linux LVS Cluster VIP to the public network interface, see Section 10.6.1 The VIRTUAL SERVER Subsec- tion. Also note that you must log in as root and load the module for before iptables issuing rules for the first time.
  • Page 126 Chapter 9. Setting Up a Red Hat Enterprise Linux LVS Cluster Active Connections When an active connection is established, the server opens a data connection to the client from port 20 to a high range port on the client machine. All data from the server is then passed over this connection.
  • Page 127 Chapter 9. Setting Up a Red Hat Enterprise Linux LVS Cluster 9.4.3.1. Rules for Active Connections The rules for active connections tell the kernel to accept and forward connections coming to the internal floating IP address on port 20 — the FTP data port. iptables /sbin/iptables -t nat -A POSTROUTING -p tcp \ -s n.n.n.0/24 --sport 20 -j MASQUERADE...

  • Page 128: Saving Network Packet Filter Settings

    Chapter 9. Setting Up a Red Hat Enterprise Linux LVS Cluster iptables /sbin/iptables -t mangle -A PREROUTING -p tcp \ -d n.n.n.n/32 --dport 21 -j MARK --set-mark 21 /sbin/iptables -t mangle -A PREROUTING -p tcp \ -d n.n.n.n/32 \ --dport 10000:20000 -j MARK --set-mark 21 commands, n.n.n.n should be replaced with the floating IP for In the above iptables...

  • Page 129: Setting Up A Red Hat Enterprise Linux Lvs Cluster

    Chapter 9. Setting Up a Red Hat Enterprise Linux LVS Cluster The next chapter explains how to use the Piranha Configuration Tool to configure the LVS router and describe the steps necessary to active an LVS cluster.
  • Page 130 Chapter 9. Setting Up a Red Hat Enterprise Linux LVS Cluster...

  • Page 131: Configuring The Lvs Routers With Piranha Configuration Tool

    Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool The Piranha Configuration Tool provides a structured approach to creating the necessary configuration file for a Piranha cluster — . This chapter /etc/sysconfig/ha/lvs.cf describes the basic operation of the Piranha Configuration Tool and how to activate the cluster once configuration is complete.

  • Page 132: Control/Monitoring

    Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool or real IP address for the server followed by :3636. Once the browser connects, you will see the screen shown in Figure 10-1. Figure 10-1. The Welcome Panel Click on the Login button and enter piranha for the Username and the administrative password you created in the Password field.
  • Page 133 Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool Figure 10-2. The CONTROL/MONITORING Panel Auto update The status display on this page can be updated automatically at a user configurable interval. To enable this feature, click on the Auto update checkbox and set the desired update frequency in the Update frequency in seconds text box (the default value is 10 seconds).

  • Page 134: Global Settings

    Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool The Auto update feature does not work with all browsers, such as Mozilla. Update information now You can manually update the status information manually by clicking this button. CHANGE PASSWORD Clicking this button takes you to a help screen with information on how to change the administrative password for the Piranha Configuration Tool.
  • Page 135 Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool Figure 10-3. The GLOBAL SETTINGS Panel The top half of this panel sets up the primary LVS router’s public and private network in- terfaces. These are the interfaces already configured in Section 9.1.1 Configuring Network Interfaces for a NAT LVS Cluster.

  • Page 136: Redundancy

    Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool The primary LVS router’s private IP can be configured on any interface that accepts TCP/IP, whether it be an Ethernet adapter or a serial port. Use network type Click the NAT button to select NAT routing. The next three fields deal specifically with the NAT router’s virtual network interface con- nected the private network with the real servers.
  • Page 137 Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool The first time you visit this screen, it displays an "inactive" Backup status and an ENABLE button. To configure the backup LVS router, click on the ENABLE button so that the screen matches Figure 10-4.

  • Page 138: Virtual Servers

    Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool Redundant server private IP Enter the backup node’s private real IP address in this text field. If you do not see the field called Redundant server private IP, go back to the GLOBAL SETTINGS panel and enter a Primary server private IP address and click ACCEPT.
  • Page 139 Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool Figure 10-5. The VIRTUAL SERVERS Panel Each server displayed in the VIRTUAL SERVERS panel can be configured on subsequent screens or subsections. To add a service, click the ADD button. To remove a service, select it by clicking the radio button next to the virtual server and click the DELETE button.
  • Page 140 Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool are located along the top of the page. But before configuring any of the subsections related to this virtual server, complete this page and click on the ACCEPT button. Figure 10-6. The VIRTUAL SERVERS Subsection Name Enter a descriptive name to identify the virtual server.
  • Page 141 Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool Protocol Choose between UDP and TCP in the drop-down menu. Web servers typically com- municate via the TCP protocol, so this is selected in the example above. Virtual IP Address Enter the virtual server’s floating IP address in this text field.
  • Page 142 Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool Quiesce server When the Quiesce server radio button is selected, anytime a new real server node comes online, the least-connections table is reset to zero so the active LVS router routes requests as if all the real servers were freshly added to the cluster.
  • Page 143 Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool Note Before the advent of firewall marks, persistence limited by subnet was a crude way of bundling connections. Now, it is best to use persistence in relation to firewall marks to achieve the same result.
  • Page 144 Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool Figure 10-7. The REAL SERVER Subsection Click the ADD button to add a new server. To delete an existing server, select the radio button beside it and click the DELETE button. Click the EDIT button to load the EDIT REAL SERVER panel, as seen in Figure 10-8.
  • Page 145 Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool Figure 10-8. The REAL SERVER Configuration Panel This panel consists of three entry fields: Name A descriptive name for the real server. This name is not the hostname for the machine, so make it descriptive and easily identifiable.
  • Page 146 Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool Weight An integer value indicating this host’s capacity relative to that of other hosts in the pool. The value can be arbitrary, but treat it as a ratio in relation to other real servers in the cluster.
  • Page 147 Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool Figure 10-9. The EDIT MONITORING SCRIPTS Subsection Sending Program For more advanced service verification, you can use this field to specify the path to a service-checking script. This functionality is especially helpful for services that require dynamically changing data, such as HTTPS or SSL.
  • Page 148 Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool The following is a sample script to use as a guide when composing an external service- checking script: #!/bin/sh TEST=‘dig -t soa example.com @$1 | grep -c dns.example.com if [ $TEST != "1" ]; then echo "OK else echo "FAIL"...

  • Page 149: Synchronizing Configuration Files

    Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool Warning Remember to click the ACCEPT button after making any changes in this panel. To make sure you do not lose any changes when selecting a new panel. Once you have configured virtual servers using the Piranha Configuration Tool, you must copy specific configuration files to the backup LVS router.
  • Page 150 Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool Important must be running on the backup router, see Section 8.1 Configur- To use sshd ing Services on the LVS Routers for details on how to properly configure the necessary services on the LVS routers.

  • Page 151: Starting The Cluster

    Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool Once you have copied these files over to the backup router and started the appropriate services (see Section 8.1 Configuring Services on the LVS Routers for more on this topic) you are ready to start the cluster.

  • Page 152: Configuring The Lvs Routers With Piranha Configuration Tool

    Chapter 10. Configuring the LVS Routers with Piranha Configuration Tool...

  • Page 153: Appendixes

    III. Appendixes This section is licensed under the GNU Free Documentation License. For details refer to the Copyright page. Table of Contents A. Supplementary Hardware Information ..............139 B. Selectively Installing Red Hat Cluster Suite Packages ..........147 File for Red Hat Enterprise Linux 4 Update 3 .....157 Multipath-usage.txt...

  • Page 155: Supplementary Hardware Information

    Appendix A. Supplementary Hardware Information The following sections provide additional information about configuring the hardware used in a cluster system. A.1. Attached Storage Requirements The following sections detail the steps to consider when directly connecting storage de- vices to cluster nodes, whether using SCSI host-bus adapters or Fibre Channel connections. A.2.
  • Page 156 Appendix A. Supplementary Hardware Information Figure A-1. Single-controller RAID Array Connected to Single-initiator Fibre Chan- nel Interconnects The external RAID array must have a separate SCSI channel for each cluster node. In clusters with more than two nodes, connect each node to the SCSI channel on the RAID array, using a single-initiator SCSI bus as shown in Figure A-1.

  • Page 157: Scsi Storage Requirements

    Appendix A. Supplementary Hardware Information Figure A-2. Dual-controller RAID Array Connected to Single-initiator Fibre Channel Interconnects A.3. SCSI Storage Requirements A single-initiator SCSI bus has only one node connected to it, and provides host isolation and better performance than a multi-initiator bus. Single-initiator buses ensure that each node is protected from disruptions due to the workload, initialization, or repair of the other nodes.
  • Page 158 Appendix A. Supplementary Hardware Information Use the appropriate SCSI cable to connect each host bus adapter to the storage enclosure. • Setting host bus adapter termination is done in the adapter BIOS utility during system boot. To set RAID controller termination, refer to the vendor documentation. Figure A-3 shows a configuration that uses two single-initiator SCSI buses.

  • Page 159: Scsi Configuration Requirements

    Appendix A. Supplementary Hardware Information Figure A-5. Dual-controller RAID Array Connected to Single-initiator SCSI Buses A.3.1. SCSI Configuration Requirements SCSI devices must adhere to a number of configuration requirements to operate correctly. Failure to adhere to these requirements adversely affects cluster operation and resource availability.

  • Page 160: Scsi Bus Length

    Appendix A. Supplementary Hardware Information A.3.2. SCSI Bus Termination A SCSI bus is an electrical path between two terminators. A device (host bus adapter, RAID controller, or disk) attaches to a SCSI bus by a short stub, which is an unterminated bus segment that usually must be less than 0.1 meter in length.

  • Page 161: Scsi Identification Numbers

    Appendix A. Supplementary Hardware Information A cluster supports LVD (low voltage differential) buses. The maximum length of a single- initiator LVD bus is 25 meters. The maximum length of a multi-initiator LVD bus is 12 meters. According to the SCSI standard, a single-initiator LVD bus is a bus that is con- nected to only two devices, each within 0.1 meter from a terminator.
  • Page 162 Appendix A. Supplementary Hardware Information...

  • Page 163: Selectively Installing Red Hat Cluster Suite Packages

    Appendix B. Selectively Installing Red Hat Cluster Suite Packages B.1. Installing the Red Hat Cluster Suite Packages Red Hat Cluster Suite consists of the following RPM packages: — Manages cluster services and resources • rgmanager — Contains the Cluster Configuration Tool, used to •...
  • Page 164 Red Hat Network Web-based interface. For more information on using Red Hat Network, visit the following URL: http://rhn.redhat.com You can install Red Hat Cluster Suite and Red Hat GFS RPMs using either of the following methods: Automatic RPM installation —...
  • Page 165 Appendix B. Selectively Installing Red Hat Cluster Suite Packages 2. Run for Red Hat Cluster Suite. The up2date --installall --channel Label following example shows running the command for i386 RPMs: # up2date --installall --channel rhel-i386-as-4-cluster 3. (Optional) If you are installing Red Hat GFS, run up2date --installall for Red Hat GFS.
  • Page 166 Appendix B. Selectively Installing Red Hat Cluster Suite Packages Table B-3 — For Red Hat GFS • The tables contain the following information to assist you in determining which packages to install: RPMs — The names of the RPMs (excluding revision numbers) •...
  • Page 167 Appendix B. Selectively Installing Red Hat Cluster Suite Packages RPMs Inclusion Depends Purpose Kernel Type? The Cluster ccs-ver-rel.arch Configuration System The Cluster cman-ver-rel.arch Manager The Cluster cman-kernel-ver-rel.arch Manager kernel cman-kernel-hugemem-ver-rel.arch modules cman-kernel-smp-ver-rel.arch Note: The types of RPMs available vary according to RHN channel. The Distributed dlm-ver-rel.arch Lock Manager...
  • Page 168 Appendix B. Selectively Installing Red Hat Cluster Suite Packages RPMs Inclusion Depends Purpose Kernel Type? Open source HA rgmanager-ver-rel.arch resource group failover GUI to manage system-config-cluster-ver-rel.arch cluster configuration Utility to administer ipvsadm-ver-rel.arch the Linux Virtual Server Cluster piranha-ver-rel.arch administration tools CCS static library ccs-devel-ver-rel.arch kernel header...
  • Page 169 Appendix B. Selectively Installing Red Hat Cluster Suite Packages RPMs Inclusion Depends Purpose Kernel Type? The Cluster ccs-ver-rel.arch Configuration System The cluster I/O fence-ver-rel.arch fencing system The Grand Unified gulm-ver-rel.arch Lock Manager (GULM, available for this release and earlier versions of Red Hat GFS) A library that iddev-ver-rel.arch...
  • Page 170 Appendix B. Selectively Installing Red Hat Cluster Suite Packages RPMs Inclusion Depends Purpose Kernel Type? A cluster/lock magma-devel-ver-rel.arch manager API abstraction library Table B-2. RPM Selection Criteria: Red Hat Cluster Suite with GULM RPMs Inclusion Depends Purpose Kernel Type? The Red Hat GFS GFS-ver-rel.arch module The Red Hat GFS...
  • Page 171 3. Copy all the RPM files from the CD (located in /media/cdrom/RedHat/RPMS/ to the temporary directory created earlier. For example: $ cp /media/cdrom/RedHat/RPMS/*.rpm /tmp/RPMS/ Note If your local computer is running a version of Red Hat Enterprise Linux that is earlier than Red Hat Enterprise Linux 4, the path to the RPMs on the CD may be different.
  • Page 172 Red Hat Enterprise Linux 4, the path to the RPMs on the CD may be different. For example, on Red Hat Enterprise Linux 3, the path is /mnt/cdrom/RedHat/RPMS/ 7. Eject the CD from the CD-ROM drive. 8. Change to the temporary directory containing the copied RPM files. For example: $ cd /tmp/RPMS/ 9.

  • Page 173: Multipath-Usage.txt

    Appendix C. File for Red Hat Multipath-usage.txt Enterprise Linux 4 Update 3 This appendix contains the file. The file is included with the Multipath-usage.txt RPM and provides guidelines for using with Red Hat dm-multipath dm-multipath Cluster Suite for Red Hat Enterprise Linux 4 Update 3: RHEL4 U3 Device Mapper Multipath Usage Overview ------------...
  • Page 174 Multipath-usage.txt Appendix C. File for Red Hat Enterprise Linux 4 Update 3 DM-MP works with a variety of storage arrays. It auto-configures the following storage arrays: o 3PARdata VV o Compaq HSV110 o Compaq MSA1000 o DDN SAN DataDirector o DEC HSG80 o EMC SYMMETRIX o EMC CLARiiON o FSC CentricStor...
  • Page 175 Multipath-usage.txt Appendix C. File for Red Hat Enterprise Linux 4 Update 3 Path States: ready - Path is able to handle I/O requests. shaky - Path is up, but temporarily not available for normal operations. faulty - Path is unable to handle I/O requests. ghost - Path is a passive path, on an active/passive controller.
  • Page 176 Multipath-usage.txt Appendix C. File for Red Hat Enterprise Linux 4 Update 3 priority path group. Other options for multipathd are to (a) wait for a user-defined length of time (for the path groups to stabilize) and then switch or (b) for multipathd to do nothing and wait for manual intervention.
  • Page 177 Multipath-usage.txt Appendix C. File for Red Hat Enterprise Linux 4 Update 3 For some conditions, that may not be sufficient. If DM-MP is multipathing devices that you do not want it to work on, you can blacklist the devices by either device name or WWID. NOTE: It is safest to blacklist individual devices by WWID, because their device names may change.
  • Page 178 Multipath-usage.txt Appendix C. File for Red Hat Enterprise Linux 4 Update 3 "devnode_blacklist", and "devices" sections of the configuration file. To see what these are, refer to the following file: /usr/share/doc/device-mapper-multipathd-0.4.5/multipath.conf.synthetic If you are using one of the storage arrays listed in the preceding text (in "Overview"), you probably do not need to modify the "devices"...
  • Page 179 DM-MP cannot be run on either the root or boot device. Other Sources of information ---------------------------- Configuration file explanation: /usr/share/doc/device-mapper-multipathd-0.4.5/multipath.conf.annotated Upstream documentation: http://christophe.varoqui.free.fr/wiki/wakka.php?wiki=Home mailing list: dm-devel@redhat.com Subscribe to this from https://www.redhat.com/mailman/listinfo/dm-devel. The list archives are at https://www.redhat.com/archives/dm-devel/ Man pages: multipath.8, multipathd.8, kpartx.8 mpath_ctl.8...
  • Page 180 Multipath-usage.txt Appendix C. File for Red Hat Enterprise Linux 4 Update 3...
  • Page 181 Index modifying the cluster configuration, 71 restoring the cluster database, 73 starting and stopping the cluster software, 71 updating the cluster software, 74 Symbols cluster configuration /etc/hosts minimum editing, 23 example, 10 /etc/sysconfig/ha/lvs.cf file, 96 modifying, 71 Cluster Configuration Tool accessing, 38 cluster database backing up, 73...
  • Page 182 definition of, 83 high-availability clustering, 83 feedback, vi (See Also Red Hat Cluster Manager) fence device definition of, 83 configuring, 30 load-balance clustering, 83 fence devices, 14 network-attached, 14 (See Also LVS clustering) serial-attached, 14 definition of, 83 watchdog timers, 14 overview of, 83 hardware-based, 14 components...
  • Page 183 LVS routers configuring services, 97 installation necessary services, 97 Red Hat Enterprise Linux, 22 primary node, 97 installing basic cluster hardware, 19 installing the basic cluster hardware, 19 multi-port services, 108 introduction, i FTP, 109 how to use this manual, i nanny daemon, 96 other Red Hat Enterprise Linux manuals, i NAT routing...
  • Page 184 VIRTUAL SERVERS, 122 piranha-gui service, 97 nanny daemon, 96 piranha-passwd, 98 power controller connection, configuring, 45 enabling, 106 routing methods, LVS, 91 power switch, 45 network address translation (See Also power controller) (See NAT) pulse daemon, 95 network hardware table, 16 pulse service, 97 network hub, 13 network switch, 13...
  • Page 185 service status, 70 shared disk storage hardware, 16 scheduling, job (LVS), 89 UPS system hardware, 18 SCSI bus length, 144 terminal server, 14 SCSI bus termination, 144 troubleshooting SCSI configuration requirements, 143 diagnosing and correcting problems in a SCSI identification numbers, 145 cluster, 75 SCSI storage requirements, 141...
  • Page 187 Colophon The manuals are written in DocBook SGML v4.1 format. The HTML and PDF formats are produced using custom DSSSL stylesheets and custom jade wrapper scripts. The DocBook SGML files are written using Emacs with the help of PSGML mode. Garrett LeSage created the admonition graphics (note, tip, important, caution, and warn- ing).
  • Page 188 Runa Bhattacharjee — Bengali translations Chester Cheng — Traditional Chinese translations Verena Fuehrer — German translations Kiyoto Hashida — Japanese translations N. Jayaradha — Tamil translations Michelle Jiyeen Kim — Korean translations Yelitza Louze — Spanish translations Noriko Mizumoto — Japanese translations Ankitkumar Rameshchandra Patel —...

This manual is also suitable for:

Cluster suite

Table of Contents