Download  Print this page

Red Hat CLUSTER FOR ENTERPRISE LINUX 5.0 Configuration Manual

Hide thumbs

Advertisement

Quick Links

Configuring and Managing a Red Hat
Cluster
Red Hat Cluster for Red
Hat Enterprise Linux 5.0
5.0
ISBN: N/A
Publication date:

Advertisement

loading

  Also See for Red Hat CLUSTER FOR ENTERPRISE LINUX 5.0

  Summary of Contents for Red Hat CLUSTER FOR ENTERPRISE LINUX 5.0

  • Page 1 Configuring and Managing a Red Hat Cluster Red Hat Cluster for Red Hat Enterprise Linux 5.0 ISBN: N/A Publication date:...
  • Page 2 Configuring and Managing a Red Hat Cluster Configuring and Managing a Red Hat Cluster describes the configuration and management of Red Hat cluster systems for Red Hat Enterprise Linux 5.0. It does not include information about Red Hat Linux Virtual Servers (LVS). Information about installing and configuring LVS is in a separate document.
  • Page 3 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 4 Configuring and Managing a Red Hat Cluster...
  • Page 5: Table Of Contents

    Introduction ......................vii 1. Document Conventions ................viii 2. Feedback ...................... ix 1. Red Hat Cluster Configuration and Management Overview ........1 1. Configuration Basics ..................1 1.1. Setting Up Hardware ................1 1.2. Installing Red Hat Cluster software ............2 1.3.
  • Page 6: Configuring

    Configuring and Managing a Red Hat Cluster 4. Managing Red Hat Cluster With Conga ..............49 1. Starting, Stopping, and Deleting Clusters ............49 2. Managing Cluster Nodes ................50 3. Managing High-Availability Services ...............51 4. Diagnosing and Correcting Problems in a Cluster ..........52 5.
  • Page 7: Introduction

    Introduction This document provides information about installing, configuring and managing Red Hat Cluster components. Red Hat Cluster components are part of Red Hat Cluster Suite and allow you to connect a group of computers (called nodes or members) to work together as a cluster. This document does not include information about installing, configuring, and managing Linux Virtual Server (LVS) software.
  • Page 8: Document Conventions

    Red Hat Cluster Suite documentation and other Red Hat documents are available in HTML, PDF, and RPM versions on the Red Hat Enterprise Linux Documentation CD and online at http://www.redhat.com/docs/. 1. Document Conventions Certain words in this manual are represented in different fonts, styles, and weights. This highlighting indicates that the word is part of a specific category.
  • Page 9: Feedback

    Feedback bold font Bold font represents application programs and text found on a graphical interface. When shown like this: OK , it indicates a button on a graphical application interface. Additionally, the manual uses different strategies to draw your attention to pieces of information. In order of how critical the information is to you, these items are marked as follows: Note A note is typically information that you need to understand the behavior of the...
  • Page 10 Introduction hear from you. Please submit a report in Bugzilla (http://bugzilla.redhat.com/bugzilla/) against the component Documentation-cluster Be sure to mention the manual's identifier: Cluster_Administration RHEL 5.0 (2008-06-01T14:54) By mentioning this manual's identifier, we know exactly which version of the guide you have.
  • Page 11: Red Hat Cluster Configuration And Management Overview

    Chapter 1. Red Hat Cluster Configuration and Management Overview Red Hat Cluster allows you to connect a group of computers (called nodes or members) to work together as a cluster. You can use Red Hat Cluster to suit your clustering needs (for example, setting up a cluster for sharing files on a GFS file system or setting up service failover).
  • Page 12: Installing Red Hat Cluster Software

    Chapter 1. Red Hat Cluster Configuration and Management Overview Other options are available for storage according to the type of storage interface; for example, iSCSI or GNBD. A Fibre Channel switch can be configured to perform fencing. • Storage — Some type of storage is required for a cluster. The type required depends on the purpose of the cluster.
  • Page 13 Configuring Red Hat Cluster Software relationship among the cluster components. Figure 1.2, “Cluster Configuration Structure” shows an example of the hierarchical relationship among cluster nodes, high-availability services, and resources. The cluster nodes are connected to one or more fencing devices. Nodes can be grouped into a failover domain for a cluster service.
  • Page 14: Conga

    Chapter 1. Red Hat Cluster Configuration and Management Overview A brief overview of each configuration tool is provided in the following sections: • Section 2, “Conga” • Section 3, “ Cluster Administration GUI” system-config-cluster • Section 4, “Command Line Administration Tools” In addition, information about using Conga and is provided in system-config-cluster...
  • Page 15 Conga To administer a cluster or storage, an administrator adds (or registers) a cluster or a computer to a luci server. When a cluster or a computer is registered with luci, the FQDN hostname or IP address of each computer is stored in a luci database. You can populate the database of one luci instance from another luciinstance.
  • Page 16 Chapter 1. Red Hat Cluster Configuration and Management Overview Figure 1.4. luci cluster Tab...
  • Page 17: Cluster Administration Gui

    Cluster system-config-cluster Figure 1.5. luci storage Tab Cluster Administration GUI system-config-cluster This section provides an overview of the cluster administration graphical user interface (GUI) available with Red Hat Cluster Suite — . It is for use with the cluster system-config-cluster infrastructure and the high-availability service management components.
  • Page 18: Cluster Configuration Tool

    Chapter 1. Red Hat Cluster Configuration and Management Overview While provides several convenient tools for configuring system-config-cluster and managing a Red Hat Cluster, the newer, more comprehensive tool, Conga, provides more convenience and flexibility than system-config-cluster 3.1. Cluster Configuration Tool You can access the Cluster Configuration Tool (Figure 1.6, “Cluster Configuration Tool”)
  • Page 19 Administration GUI The Cluster Configuration Tool represents cluster configuration components in the configuration file ( ) with a hierarchical graphical display in the left /etc/cluster/cluster.conf panel. A triangle icon to the left of a component name indicates that the component has one or more subordinate components assigned to it.
  • Page 20: Cluster Status Tool

    Chapter 1. Red Hat Cluster Configuration and Management Overview Services. Using configuration buttons at the bottom of the right frame (below Properties), you can create services (when Services is selected) or edit service properties (when a service is selected). 3.2. Cluster Status Tool You can access the Cluster Status Tool (Figure 1.7, “Cluster Status Tool”) through the...
  • Page 21: Command Line Administration Tools

    Command Line Administration Tools The nodes and services displayed in the Cluster Status Tool are determined by the cluster configuration file ( ). You can use the Cluster Status Tool to /etc/cluster/cluster.conf enable, disable, restart, or relocate a high-availability service. 4.
  • Page 23: Before Configuring A Red Hat Cluster

    Before configuring Red Hat Cluster software, make sure that your cluster uses appropriate hardware (for example, supported fence devices, storage devices, and Fibre Channel switches). Refer to the hardware configuration guidelines at http://www.redhat.com/cluster_suite/hardware/ for the most current hardware compatibility information. 2. Enabling IP Ports Before deploying a Red Hat Cluster, you must enable certain IP ports on the cluster nodes and on computers that run luci (the Conga user interface server).
  • Page 24: Enabling Ip Ports On Computers That Run Luci

    Chapter 2. Before Configuring a Red Hat Cluster Cluster Nodes” lists the IP port numbers, their respective protocols, the components to which the port numbers are assigned, and references to rule examples. At each cluster iptables node, enable IP ports according to Table 2.1, “Enabled IP Ports on Red Hat Cluster Nodes”.
  • Page 25: Examples Of Rules

    Examples of Rules iptables If a cluster node is running luci, port 11111 should already have been enabled. IP Port Protocol Component Reference to Example of Number Rules iptables 8084 luci (Conga user interface Example 2.2, “Port 8084: luci server) (Cluster Node or Computer Running luci)”...
  • Page 26 Chapter 2. Before Configuring a Red Hat Cluster 10.10.10.0/24 -d 10.10.10.0/24 --dports 11111 -j ACCEPT Example 2.3. Port 11111: ricci (Cluster Node and Computer Running luci) -A INPUT -i 10.10.10.200 -m state --state NEW -m multiport -p tcp -s 10.10.10.0/24 -d 10.10.10.0/24 --dports 14567 -j ACCEPT Example 2.4.
  • Page 27: Configuring Acpi For Use With Integrated Fence Devices

    For the most current information about integrated fence devices supported by Red Hat Cluster Suite, refer to http://www.redhat.com/cluster_suite/hardware/ If a cluster node is configured to be fenced by an integrated fence device, disable ACPI Soft-Off for that node. Disabling ACPI Soft-Off allows an integrated fence device to turn off a node...
  • Page 28: Disabling Acpi Soft-Off With Management

    Chapter 2. Before Configuring a Red Hat Cluster • Changing the BIOS setting to "instant-off" or an equivalent setting that turns off the node without delay Note Disabling ACPI Soft-Off with the BIOS may not be possible with some computers. •...
  • Page 29: Disabling Acpi Soft-Off With The Bios

    Fence Devices management. — OR — • — This command turns off chkconfig --level 2345 acpid off acpid 2. Reboot the node. 3. When the cluster is configured and running, verify that the node turns off immediately when fenced. You can fence the node with the command or Conga.
  • Page 30 Chapter 2. Before Configuring a Red Hat Cluster may vary among computers. However, the objective of this procedure is to configure the BIOS so that the computer is turned off via the power button without delay. 4. Exit the program, saving the BIOS configuration. BIOS CMOS Setup Utility 5.
  • Page 31: Disabling Acpi Completely In The File

    Disabling ACPI Completely in the grub.conf 3.3. Disabling ACPI Completely in the File grub.conf The preferred method of disabling ACPI Soft-Off is with management (Section 3.1, chkconfig “Disabling ACPI Soft-Off with Management”). If the preferred method is not effective chkconfig for your cluster, you can disable ACPI Soft-Off with the BIOS power management (Section 3.2, “Disabling ACPI Soft-Off with the...
  • Page 32: Configuring Max_Luns

    Chapter 2. Before Configuring a Red Hat Cluster title Red Hat Enterprise Linux Server (2.6.18-36.el5) root (hd0,0) kernel /vmlinuz-2.6.18-36.el5 ro root=/dev/VolGroup00/LogVol00 console=ttyS0,115200n8 acpi=off initrd /initrd-2.6.18-36.el5.img In this example, has been appended to the kernel boot command line — the line acpi=off starting with "kernel /vmlinuz-2.6.18-36.el5".
  • Page 33 File Important Overall, heuristics and other parameters for your Red Hat Cluster qdiskd depend on the site environment and special requirements needed. To understand the use of heuristics and other parameters, refer to the qdiskd qdisk(5) man page. If you require assistance understanding and using qdiskd your site, contact an authorized Red Hat support representative.
  • Page 34: Multicast Addresses

    Chapter 2. Before Configuring a Red Hat Cluster Note Using JBOD as a quorum disk is not recommended. A JBOD cannot provide dependable performance and therefore may not allow a node to write to it quickly enough. If a node is unable to write to a quorum disk device quickly enough, the node is falsely evicted from a cluster.
  • Page 35 General Configuration Considerations No-single-point-of-failure hardware configuration Clusters can include a dual-controller RAID array, multiple bonded network channels, multiple paths between cluster members and storage, and redundant un-interruptible power supply (UPS) systems to ensure that no single failure results in application down time or loss of data.
  • Page 37: Configuring Red Hat Cluster With Conga

    Chapter 3. Configuring Red Hat Cluster With Conga This chapter describes how to configure Red Hat Cluster software using Conga, and consists of the following sections: • Section 1, “Configuration Tasks” • Section 2, “Starting luci and ricci” • Section 3, “Creating A Cluster” •...
  • Page 38: Starting Luci And Ricci

    Chapter 3. Configuring Red Hat Cluster With Conga 2. Starting luci and ricci To administer Red Hat Clusters with Conga, install and run luci and ricci as follows: 1. At each node to be administered by Conga, install the ricci agent. For example: # yum install ricci 2.
  • Page 39: Creating A Cluster

    Creating A Cluster 5. Start luci using . For example: service luci restart # service luci restart Shutting down luci: Starting luci: generating https SSL certificates... done Please, point your web browser to https://nano-01:8084 to access luci 6. At a Web browser, place the URL of the luci server into the URL address box and click Go (or the equivalent).
  • Page 40: Global Cluster Properties

    Chapter 3. Configuring Red Hat Cluster With Conga 4. Global Cluster Properties When a cluster is created, or if you select a cluster to configure, a cluster-specific page is displayed. The page provides an interface for configuring cluster-wide properties and detailed properties.
  • Page 41 Global Cluster Properties 3. Multicast tab — This tab provides an interface for configuring these Multicast Configuration parameters: Let cluster choose the multicast address and Specify the multicast address manually. Red Hat Cluster software chooses a multicast address for cluster management communication among cluster nodes; therefore, the default setting is Let cluster choose the multicast address.
  • Page 42: Configuring Fence Devices

    Chapter 3. Configuring Red Hat Cluster With Conga Parameter Description Minimum Score The minimum score for a node to be considered "alive". If omitted or set to 0, the default function, , is used, where is the floor((n+1)/2) sum of the heuristics scores. The Minimum Score value must never exceed the sum of the heuristic scores;...
  • Page 43 Configuring Fence Devices The following shared fence devices are available: • APC Power Switch • Brocade Fabric Switch • Bull PAP • Egenera SAN Controller • GNBD • IBM Blade Center • McData SAN Switch • QLogic SANbox2 • SCSI Fencing •...
  • Page 44: Creating A Shared Fence Device

    Chapter 3. Configuring Red Hat Cluster With Conga The starting point of each procedure is at the cluster-specific page that you navigate to from Choose a cluster to administer displayed on the cluster tab. 5.1. Creating a Shared Fence Device To create a shared fence device, follow these steps: 1.
  • Page 45 Modifying or Deleting a Fence Device Figure 3.1. Fence Device Configuration 3. At the Add a Sharable Fence Device page, click the drop-down box under Fencing Type and select the type of fence device to configure. 4. Specify the information in the Fencing Type dialog box according to the type of fence device. Refer to Appendix B, Fence Device Parameters for more information about fence device...
  • Page 46: Modifying Or Deleting A Fence Device

    Chapter 3. Configuring Red Hat Cluster With Conga 5.2. Modifying or Deleting a Fence Device To modify or delete a fence device, follow these steps: 1. At the detailed menu for the cluster (below the clusters menu), click Shared Fence Devices. Clicking Shared Fence Devices causes the display of the fence devices for a cluster and causes the display of menu items for fence device configuration: Add a Fence Device and Configure a Fence Device.
  • Page 47: Adding A Member To A Running Cluster

    Adding a Member to a Running Cluster Creating a cluster consists of selecting a set of nodes (or members) to be part of the cluster. Once you have completed the initial step of creating a cluster and creating fence devices, you need to configure cluster nodes.
  • Page 48: Deleting A Member From A Cluster

    Chapter 3. Configuring Red Hat Cluster With Conga 4. Click Submit. Clicking Submit causes the following actions: a. Cluster software packages to be downloaded onto the added node. b. Cluster software to be installed (or verification that the appropriate software packages are installed) onto the added node.
  • Page 49: Configuring A Failover Domain

    Configuring a Failover Domain 1. Click the link of the node to be deleted. Clicking the link of the node to be deleted causes a page to be displayed for that link showing how that node is configured. Note To allow services running on a node to fail over when the node is deleted, skip the next step.
  • Page 50 Chapter 3. Configuring Red Hat Cluster With Conga be started (either manually or by the cluster software). • Unordered — When a cluster service is assigned to an unordered failover domain, the member on which the cluster service runs is chosen from the available failover domain members with no priority ordering.
  • Page 51: Adding A Failover Domain

    Modifying a Failover Domain 7.1. Adding a Failover Domain To add a failover domain, follow the steps in this section. The starting point of the procedure is at the cluster-specific page that you navigate to from Choose a cluster to administer displayed on the cluster tab.
  • Page 52 Chapter 3. Configuring Red Hat Cluster With Conga displayed on the cluster tab. 1. At the detailed menu for the cluster (below the clusters menu), click Failover Domains. Clicking Failover Domains causes the display of failover domains with related services and the display of menu items for failover domains: Add a Failover Domain and Configure a Failover Domain .
  • Page 53: Adding Cluster Resources

    Adding Cluster Resources 9. To make additional changes to the failover domain, continue modifications at the Failover Domain Form page and click Submit when you are done. 8. Adding Cluster Resources To add a cluster resource, follow the steps in this section. The starting point of the procedure is at the cluster-specific page that you navigate to from Choose a cluster to administer displayed on the cluster tab.
  • Page 54 Chapter 3. Configuring Red Hat Cluster With Conga File System ID — When creating a new file system resource, you can leave this field blank. Leaving the field blank causes a file system ID to be assigned automatically after you click Submit at the File System Resource Configuration dialog box.
  • Page 55: Adding A Cluster Service To The Cluster

    Adding a Cluster Service to the Cluster Options — Additional client access rights. For more information, refer to the exports(5) man page, General Options NFS Export Name — Enter a name for the NFS export resource. Script Name — Enter a name for the custom user script. File (with path) —...
  • Page 56 Chapter 3. Configuring Red Hat Cluster With Conga service must be started manually any time the cluster comes up from the stopped state. Use a descriptive name that clearly distinguishes the service from other services in the cluster. 4. Add a resource to the service; click Add a resource to this service. Clicking Add a resource to this service causes the display of two drop-down boxes: Add a new local resource and Use an existing global resource.
  • Page 57: Configuring Cluster Storage

    Configuring Cluster Storage 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1356 qdisc pfifo_fast qlen 1000 link/ether 00:05:5d:9a:d8:91 brd ff:ff:ff:ff:ff:ff inet 10.11.4.31/22 brd 10.11.7.255 scope global eth0 inet6 fe80::205:5dff:fe9a:d891/64 scope link inet 10.11.4.240/22 scope global secondary eth0...
  • Page 58 Chapter 3. Configuring Red Hat Cluster With Conga computer. This page is divided into three sections: • Hard Drives • Partitions • Volume Groups Each section is set up as an expandable tree, with links to property sheets for specific devices, partitions, and storage entities.
  • Page 59: Managing Red Hat Cluster With Conga

    Chapter 4. Managing Red Hat Cluster With Conga This chapter describes various administrative tasks for managing a Red Hat Cluster and consists of the following sections: • Section 1, “Starting, Stopping, and Deleting Clusters” • Section 2, “Managing Cluster Nodes” •...
  • Page 60: Managing Cluster Nodes

    Chapter 4. Managing Red Hat Cluster With Conga • Delete this cluster — Selecting this action halts a running cluster, disables cluster software from starting automatically, and removes the cluster configuration file from each node. You can select this action for any state the cluster is in. Deleting a cluster frees each node in the cluster for use in another cluster.
  • Page 61: Managing High-Availability Services

    Managing High-Availability Services Selecting Have node leave cluster shuts down cluster software and makes the node leave the cluster. Making a node leave a cluster prevents the node from automatically joining the cluster when it is rebooted. Selecting Have node join cluster starts cluster software and makes the node join the cluster.
  • Page 62: Diagnosing And Correcting Problems In A Cluster

    Chapter 4. Managing Red Hat Cluster With Conga • If service is running — Configure this service, Restart this service, and Stop this service. • If service is not running — Configure this service, Start this service, and Delete this service.
  • Page 63: Configuring Red Hat Cluster With System-Config-Cluster

    Chapter 5. Configuring Red Hat Cluster With system-config-cluster This chapter describes how to configure Red Hat Cluster software using , and consists of the following sections: system-config-cluster • Section 1, “Configuration Tasks” • Section 2, “Starting the Cluster Configuration Tool” •...
  • Page 64: Starting The Cluster Configuration Tool

    Chapter 5. Configuring Red Hat Cluster With system-config-cluster 3. Creating fence devices. Refer to Section 4, “Configuring Fence Devices”. 4. Creating cluster members. Refer to Section 5, “Adding and Deleting Members”. 5. Creating failover domains. Refer to Section 6, “Configuring a Failover Domain”.
  • Page 65 Starting the Cluster Configuration Tool Figure 5.1. Starting a New Configuration File Note The Cluster Management tab for the Red Hat Cluster Suite management GUI is available after you save the configuration file with the Cluster Configuration Tool, exit, and restart the Red Hat Cluster Suite management GUI ).
  • Page 66 Chapter 5. Configuring Red Hat Cluster With system-config-cluster dialog box if you enable Use a Quorum disk: Interval, TKO, Votes, Minimum Score, Device, Label, and Quorum Disk Heuristic. Table 5.1, “Quorum-Disk Parameters” describes the parameters. Important Quorum-disk parameters and heuristics depend on the site environment and special requirements needed.
  • Page 67 Starting the Cluster Configuration Tool Figure 5.2. Creating A New Configuration 4. When you have completed entering the cluster name and other parameters in the New Configuration dialog box, click OK. Clicking OK starts the Cluster Configuration Tool, displaying a graphical representation of the configuration (Figure 5.3, “The Cluster Configuration Tool”).
  • Page 68 Chapter 5. Configuring Red Hat Cluster With system-config-cluster Figure 5.3. The Cluster Configuration Tool Parameter Description Use a Quorum Disk Enables quorum disk. Enables quorum-disk parameters in the New Configuration dialog box. Interval The frequency of read/write cycles, in seconds. The number of cycles a node must miss in order to be declared dead.
  • Page 69: Configuring Cluster Properties

    Configuring Cluster Properties Parameter Description Device The storage device the quorum daemon uses. The device must be the same on all nodes. Label Specifies the quorum disk label created by the utility. If this mkqdisk field contains an entry, the label overrides the Device field. If this field is used, the quorum daemon reads and checks /proc/partitions...
  • Page 70: Configuring Fence Devices

    Chapter 5. Configuring Red Hat Cluster With system-config-cluster 5. Specify the Fence Daemon Properties parameters: Post-Join Delay and Post-Fail Delay. a. The Post-Join Delay parameter is the number of seconds the fence daemon ( fenced waits before fencing a node after the node joins the fence domain. The Post-Join Delay default value is .
  • Page 71: Adding And Deleting Members

    Adding and Deleting Members Figure 5.4. Fence Device Configuration 2. At the Fence Device Configuration dialog box, click the drop-down box under Add a New Fence Device and select the type of fence device to configure. 3. Specify the information in the Fence Device Configuration dialog box according to the type of fence device.
  • Page 72 Chapter 5. Configuring Red Hat Cluster With system-config-cluster 2. At the bottom of the right frame (labeled Properties), click the Add a Cluster Node button. Clicking that button causes a Node Properties dialog box to be displayed. The Node Properties dialog box presents text boxes for Cluster Node Name and Quorum Votes (refer to Figure 5.5, “Adding a Member to a New Cluster”).
  • Page 73: Adding A Member To A Running Cluster

    Adding a Member to a Running Cluster box to be displayed. c. At the Fence Configuration dialog box, bottom of the right frame (below Properties), click Add a New Fence Level. Clicking Add a New Fence Level causes a fence-level element (for example, Fence-Level-1, Fence-Level-2, and so on) to be displayed below the node in the left frame of the Fence Configuration dialog box.
  • Page 74 Chapter 5. Configuring Red Hat Cluster With system-config-cluster nodes, follow these steps: 1. Add the node and configure fencing for it as in Section 5.1, “Adding a Member to a Cluster”. 2. Click Send to Cluster to propagate the updated configuration to other running nodes in the cluster.
  • Page 75: Deleting A Member From A Cluster

    Deleting a Member from a Cluster 2. Click Send to Cluster to propagate the updated configuration to other running nodes in the cluster. 3. Use the command to send the updated file from one of /etc/cluster/cluster.conf the existing cluster nodes to the new node. 4.
  • Page 76: Configuring A Failover Domain

    Chapter 5. Configuring Red Hat Cluster With system-config-cluster Figure 5.6. Confirm Deleting a Member 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 77 Configuring a Failover Domain • 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. If none of the members in a restricted failover domain are available, the cluster service cannot be started (either manually or by the cluster software).
  • Page 78: Adding A Failover Domain

    Chapter 5. Configuring Red Hat Cluster With system-config-cluster • Section 6.1, “Adding a Failover Domain” • Section 6.2, “Removing a Failover Domain” • Section 6.3, “Removing a Member from a Failover Domain” 6.1. Adding a Failover Domain To add a failover domain, follow these steps: 1.
  • Page 79 Adding a Failover Domain Figure 5.7. Failover Domain Configuration: Configuring a Failover Domain 4. Click the Available Cluster Nodes drop-down box and select the members for this failover domain. 5. To restrict failover to members in this failover domain, click (check) the Restrict Failover To This Domains Members checkbox.
  • Page 80 Chapter 5. Configuring Red Hat Cluster With system-config-cluster Figure 5.8. 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. Priority is indicated by the position in the Member Node column and the value in the Priority column.
  • Page 81: Removing A Failover Domain

    Removing a Member from a Failover Domain 6.2. Removing a Failover Domain To remove a failover domain, follow these steps: 1. At the left frame of the Cluster Configuration Tool, click the failover domain that you want to delete (listed under Failover Domains). 2.
  • Page 82: Adding Cluster Resources

    Chapter 5. Configuring Red Hat Cluster With system-config-cluster • New cluster — If this is a new cluster, choose File => Save to save the changes to the cluster configuration. • Running cluster — If this cluster is operational and running, and you want to propagate the change immediately, click the Send to Cluster button.
  • Page 83 Adding Cluster Resources Options — Mount options. File System ID — When creating a new file system resource, you can leave this field blank. Leaving the field blank causes a file system ID to be assigned automatically after you click OK at the Resource Configuration dialog box.
  • Page 84: Adding A Cluster Service To The Cluster

    Chapter 5. Configuring Red Hat Cluster With system-config-cluster addresses (with wild-card support), and netgroups. Read-Write and Read Only options — Specify the type of access rights for this NFS client resource: • Read-Write — Specifies that the NFS client has read-write access. The default setting is Read-Write.
  • Page 85 Adding a Cluster Service to the Cluster 2. At the bottom of the right frame (labeled Properties), click the Create a Service button. Clicking Create a Service causes the Add a Service dialog box to be displayed. 3. At the Add a Service dialog box, type the name of the service in the Name text box and click OK.
  • Page 86 Chapter 5. Configuring Red Hat Cluster With system-config-cluster a Failover Domain” for instructions on how to configure a failover domain.) 5. Autostart This Service checkbox — This is checked by default. If Autostart This Service is checked, the service is started automatically when a cluster is started and running. If Autostart This Service is not checked, the service must be started manually any time the cluster comes up from stopped state.
  • Page 87: Propagating The Configuration File: New Cluster

    Propagating The Configuration File: New 9. If needed, you may also create a private resource that you can create that becomes a subordinate resource by clicking on the Attach a new Private Resource to the Selection button. The process is the same as creating a shared resource described in Section 7, “Adding Cluster Resources”.
  • Page 88: Starting The Cluster Software

    Chapter 5. Configuring Red Hat Cluster With system-config-cluster Propagating the cluster configuration file this way is necessary for the first time a cluster is created. Once a cluster is installed and running, the cluster configuration file is propagated using the Red Hat cluster management GUI Send to Cluster button.
  • Page 89: Managing Red Hat Cluster With System-Config-Cluster

    Chapter 6. Managing Red Hat Cluster With system-config-cluster This chapter describes various administrative tasks for managing a Red Hat Cluster and consists of the following sections: • Section 1, “Starting and Stopping the Cluster Software” • Section 2, “Managing High-Availability Services” •...
  • Page 90: Managing High-Availability Services

    Chapter 6. Managing Red Hat Cluster With system-config-cluster , if CLVM has been used to create clustered volumes service clvmd stop service cman stop Stopping the cluster services on a member causes its services to fail over to an active member. 2.
  • Page 91 Modifying the Cluster Configuration You can use the Cluster Status Tool to enable, disable, restart, or relocate a high-availability service. The Cluster Status Tool displays the current cluster status in the Services area and automatically updates the status every 10 seconds. To enable a service, you can select the service in the Services area and click Enable.
  • Page 92: Modifying The Cluster Configuration

    Chapter 6. Managing Red Hat Cluster With system-config-cluster 3. Modifying the Cluster Configuration To modify the cluster configuration (the cluster configuration file ), use the Cluster Configuration Tool. For more information /etc/cluster/cluster.conf about using the Cluster Configuration Tool, refer to Chapter 5, Configuring Red Hat Cluster With system-config-cluster...
  • Page 93: Backing Up And Restoring The Cluster Database

    Backing Up and Restoring the Cluster 3. Clicking Send to Cluster causes a Warning dialog box to be displayed. Click Yes to save and propagate the configuration. 4. Clicking Yes causes an Information dialog box to be displayed, confirming that the current configuration has been propagated to the cluster.
  • Page 94: Disabling The Cluster Software

    Chapter 6. Managing Red Hat Cluster With system-config-cluster 9. Propagate the updated configuration file throughout the cluster by clicking Send to Cluster. 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 running the Cluster Configuration Tool is not a member of the cluster.
  • Page 95: Diagnosing And Correcting Problems In A Cluster

    Database in the order shown to restart cluster software: service cman start , if CLVM has been used to create clustered volumes service clvmd start , if you are using Red Hat GFS service gfs start service rgmanager start 6. Diagnosing and Correcting Problems in a Cluster For information about diagnosing and correcting problems in a cluster, contact an authorized Red Hat support representative.
  • Page 97: Example Of Setting Up Apache Http Server

    Appendix A. Example of Setting Up Apache HTTP Server This appendix provides an example of setting up a highly available Apache HTTP Server on a Red Hat Cluster. The example describes how to set up a service to fail over an Apache HTTP Server.
  • Page 98: Configuring Shared Storage

    Appendix A. Example of Setting Up Apache HTTP Server systems from accessing the same data simultaneously, which may result in data corruption. Therefore, do not include the file systems in the file. /etc/fstab 2. Configuring Shared Storage To set up the shared file system resource, perform the following tasks as root on one cluster system: 1.
  • Page 99 Installing and Configuring the Apache HTTP your configuration. For example: • Specify the directory that contains the HTML files. Also specify this mount point when adding the service to the cluster configuration. It is only required to change this field if the mount point for the web site's content differs from the default setting of /var/www/html/ For example:...
  • Page 100 Appendix A. Example of Setting Up Apache HTTP Server Before the service is added to the cluster configuration, ensure that the Apache HTTP Server directories are not mounted. Then, on one node, invoke the Cluster Configuration Tool to add the service, as follows. This example assumes a failover domain named httpd-domain created for this service.
  • Page 101 Server or leave it as None. • Click the Add a Shared Resource to this service button. From the available list, choose each resource that you created in the previous steps. Repeat this step until all resources have been added. •...
  • Page 103: Fence Device Parameters

    Appendix B. Fence Device Parameters This appendix provides tables with parameter descriptions of fence devices. Note Certain fence devices have an optional Password Script parameter. The Password Scriptparameter allows specifying that a fence-device password is supplied from a script rather than from the Password parameter. Using the Password Script parameter supersedes the Password parameter, allowing passwords to not be visible in the cluster configuration file /etc/cluster/cluster.conf...
  • Page 104 Appendix B. Fence Device Parameters Field Description IP Address The IP address assigned to the PAP console. Login The login name used to access the PAP console. Password The password used to authenticate the connection to the PAP console. Password The script that supplies a password for access to the fence device.
  • Page 105 Table B.6. GNBD (Global Network Block Device) Field Description Name A name for the server with HP iLO support. Hostname The hostname assigned to the device. Login The login name used to access the device. Password The password used to authenticate the connection to the device. Password The script that supplies a password for access to the fence device.
  • Page 106 Appendix B. Fence Device Parameters Field Description 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. Password Script The script that supplies a password for access to the fence device. (optional) Using this supersedes the Password parameter.
  • Page 107 Field Description Port The switch outlet number. Table B.13. RPS-10 Power Switch (two-node clusters only) 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 108 Appendix B. Fence Device Parameters Field Description Name A name for the WTI power switch connected to the cluster. IP Address The IP address assigned to the device. Password The password used to authenticate the connection to the device. Password The script that supplies a password for access to the fence device.
  • Page 109: Upgrading A Red Hat Cluster From Rhel 4 To Rhel 5

    Appendix C. Upgrading A Red Hat Cluster from RHEL 4 to RHEL 5 This appendix provides a procedure for upgrading a Red Hat cluster from RHEL 4 to RHEL 5. The procedure includes changes required for Red Hat GFS and CLVM, also. For more information about Red Hat GFS, refer to Global File System: Configuration and Administration.
  • Page 110 Appendix C. Upgrading A Red Hat Cluster from RHEL 4 to RHEL 5 f. Run service ccsd stop 3. Disable cluster software from starting during reboot. At each node, run /sbin/chkconfig follows: # chkconfig --level 2345 rgmanager off # chkconfig --level 2345 gfs off # chkconfig --level 2345 clvmd off # chkconfig --level 2345 fenced off # chkconfig --level 2345 cman off...
  • Page 111 You shouldn't change any of these values if the filesystem is mounted. Are you sure? [y/n] y current lock protocol name = "lock_gulm" new lock protocol name = "lock_dlm" Done 6. Update the software in the cluster nodes to RHEL 5 and Red Hat Cluster Suite for RHEL 5. You can acquire and update software through Red Hat Network channels for RHEL 5 and Red Hat Cluster Suite for RHEL 5.
  • Page 113: Index

    cluster configuration, 27 Index modifying, 82 Cluster Configuration Tool accessing, 10 cluster database backing up, 83 ACPI restoring, 83 configuring, 17 cluster service Apache HTTP Server displaying status, 11, 81 httpd.conf, 88 cluster service managers setting up service, 87 configuration, 45, 74, 77 cluster services, 45, 74 (see also adding to the cluster cluster...
  • Page 114 Index Apache HTTP Server httpd.conf, 88 setting up, 87 upgrading, RHEL 4 to RHEL 5, 99 integrated fence devices configuring ACPI, 17 introduction, vii other Red Hat Enterprise Linux documents, IP ports enabling, 13 iptables configuring, 13 max_luns configuring, 22 multicast addresses considerations for using with network switches and multicast addresses, 24...