Page 1: Red Hat Enterprise Linux
Red Hat Enterprise Linux 4 Cluster Administration Configuring and Managing a Red Hat Cluster...
Page 2 Cluster Administration Red Hat Enterprise Linux 4 Cluster Administration Configuring and Managing a Red Hat Cluster Edition 1.0 Copyright © 2009 Red Hat, Inc. This material may only be distributed subject to the terms and conditions set forth in the Open Publication License, V1.0 or later (the latest version of the OPL is presently available at http://www.opencontent.org/openpub/).
Page 3: Table Of Contents
Introduction 1. Document Conventions ....................vi 1.1. Typographic Conventions ..................vi 1.2. Pull-quote Conventions ..................viii 1.3. Notes and Warnings ................... viii 2. Feedback ........................ix 1. Red Hat Cluster Configuration and Management Overview 1.1. Configuration Basics ..................... 1 1.1.1. Setting Up Hardware ..................1 1.1.2.
Page 4: Configuring
Cluster Administration 4. Managing Red Hat Cluster With Conga 4.1. Starting, Stopping, and Deleting Clusters ..............43 4.2. Managing Cluster Nodes .................... 44 4.3. Managing High-Availability Services ................45 4.4. Diagnosing and Correcting Problems in a Cluster ............46 5. Configuring Red Hat Cluster With system-config-cluster 5.1.
Page 5: 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 6: Document Conventions
Red Hat Cluster Suite documentation and other Red Hat documents are available in HTML, http:// PDF, and RPM versions on the Red Hat Enterprise Linux Documentation CD and online at www.redhat.com/docs/. 1. Document Conventions This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
Page 7 Typographic Conventions The first sentence highlights the particular key cap to press. The second highlights two sets of three key caps, each set pressed simultaneously. If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in Mono-spaced Bold. For example: File-related classes include filesystem for file systems, file for files, and dir for directories.
Page 8: Pull-Quote Conventions
Introduction Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example: When the Apache HTTP Server accepts requests, it dispatches child processes or threads to handle them. This group of child processes or threads is known as a server-pool.
Page 9: Feedback
2. 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: Cluster_Administration(EN)-4.8 (2009-5-13T12:45)
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 Figure 1.1. Red Hat Cluster Hardware Overview 1.1.2. Installing Red Hat Cluster software To install Red Hat Cluster software, you must have entitlements for the software. If you are using the Conga configuration GUI, you can let it install the cluster software. If you are using other tools to configure the cluster, secure and install the software as you would with Red Hat Enterprise Linux software.
Page 13: Command Line Tools
Configuring Red Hat Cluster Software Figure 1.2. Cluster Configuration Structure The following cluster configuration tools are available with Red Hat Cluster: • Conga — This is a comprehensive user interface for installing, configuring, and managing Red Hat clusters, computers, and storage attached to clusters and computers. •...
Page 14: Conga
Chapter 1. Red Hat Cluster Configuration and Management Overview 1.2. Conga Conga is an integrated set of software components that provides centralized configuration and management of Red Hat clusters and storage. Conga provides the following major features: • One Web interface for managing cluster and storage •...
Page 15 Conga The following figures show sample displays of the three major luci tabs: homebase, cluster, and storage. For more information about Conga, refer to Chapter 3, Configuring Red Hat Cluster With Conga, Conga, and the online help available with the luci server. Chapter 4, Managing Red Hat Cluster With Figure 1.3.
Page 16: System-Config-Cluster Cluster Administration Gui
Chapter 1. Red Hat Cluster Configuration and Management Overview Figure 1.5. luci storage Tab 1.3. system-config-cluster Cluster Administration GUI This section provides an overview of the cluster administration graphical user interface (GUI) available with Red Hat Cluster Suite — system-config-cluster. It is for use with the cluster infrastructure and the high-availability service management components.
Page 17: Cluster Configuration Tool
Cluster Configuration Tool 1.3.1. Cluster Configuration Tool You can access the Cluster Configuration Tool (Figure 1.6, “Cluster Configuration Tool”) through the Cluster Configuration tab in the Cluster Administration GUI. Figure 1.6. Cluster Configuration Tool The Cluster Configuration Tool represents cluster configuration components in the configuration file (/etc/cluster/cluster.conf) with a hierarchical graphical display in the left panel.
Page 18: Cluster Status Tool
Chapter 1. Red Hat Cluster Configuration and Management Overview • Fence Devices — Displays fence devices. Fence devices are represented as subordinate elements under Fence Devices. Using configuration buttons at the bottom of the right frame (below Properties), you can add fence devices, delete fence devices, and edit fence-device properties. Fence devices must be defined before you can configure fencing (with the Manage Fencing For This Node button) for each node.
Page 19: Command Line Administration Tools
Command Line Administration Tools Figure 1.7. Cluster Status Tool The nodes and services displayed in the Cluster Status Tool are determined by the cluster configuration file (/etc/cluster/cluster.conf). You can use the Cluster Status Tool to enable, disable, restart, or relocate a high-availability service. 1.4.
Page 20 Chapter 1. Red Hat Cluster Configuration and Management Overview Command Line Used With Purpose Tool Cluster ccs_tool is a program for making online updates to the ccs_tool — Cluster Infrastructure cluster configuration file. It provides the capability to create Configuration and modify cluster infrastructure components (for example, System Tool creating a cluster, adding and removing a node).
Page 21: Before Configuring A Red Hat Cluster
2.1. Compatible Hardware 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 http://www.redhat.com/cluster_suite/hardware/ hardware configuration guidelines at for the most current hardware compatibility information.
Page 22: Enabling Ip Ports On Computers That Run Luci
Chapter 2. Before Configuring a Red Hat Cluster IP Port Protocol Component Reference to Example of Number iptables Rules Example 2.3, “Port 11111: ricci 11111 ricci (part of Conga remote (Cluster Node and Computer agent) Running luci)” Example 2.4, “Port 14567: gnbd” 14567 gnbd (Global Network Block Device)
Page 23: Examples Of Iptables Rules
Examples of iptables Rules IP Port Protocol Component Reference to Example of Number iptables Rules Example 2.3, “Port 11111: ricci 11111 ricci (Conga remote agent) (Cluster Node and Computer Running luci)” Table 2.2. Enabled IP Ports on a Computer That Runs luci 2.2.3.
Page 24: Configuring Acpi For Use With Integrated Fence Devices
Note 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 immediately and completely rather than attempting a clean shutdown (for example, shutdown -h now).
Page 25: Disabling Acpi Soft-Off With Chkconfig Management
Disabling ACPI Soft-Off with chkconfig Management relying on the operating system to turn off the node; therefore, the fence device turns off the node in a time span much longer than four to five seconds. To disable ACPI Soft-Off, use chkconfig management and verify that the node turns off immediately when fenced.
Page 26: Disabling Acpi Soft-Off With The Bios
Chapter 2. Before Configuring a Red Hat Cluster • chkconfig --level 2345 acpid off — This command turns off acpid. 2. Reboot the node. 3. When the cluster is configured and running, verify that the node turns off immediately when fenced.
Page 27 Disabling ACPI Soft-Off with the BIOS +-------------------------------------------------|------------------------ ACPI Function [Enabled] Item Help ACPI Suspend Type [S1(POS)] |------------------------| x Run VGABIOS if S3 Resume Auto | Menu Level Suspend Mode [Disabled] HDD Power Down [Disabled] Soft-Off by PWR-BTTN [Instant-Off] CPU THRM-Throttling [50.0%] Wake-Up by PCI card [Enabled]...
Page 28: Disabling Acpi Completely In The Grub.conf File
Chapter 2. Before Configuring a Red Hat Cluster 2.3.3. Disabling ACPI Completely in the grub.conf File (Section 2.3.1, The preferred method of disabling ACPI Soft-Off is with chkconfig management “Disabling ACPI Soft-Off with chkconfig Management”). If the preferred method is not effective for your (Section 2.3.2, “Disabling cluster, you can disable ACPI Soft-Off with the BIOS power management ACPI Soft-Off with the...
Page 29: Configuring Max_Luns
Configuring max_luns # grub.conf generated by anaconda # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that all kernel and initrd paths are relative to /boot/, eg. root (hd0,0) kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 initrd /initrd-version.img...
Page 30: Considerations For Using Quorum Disk
Chapter 2. Before Configuring a Red Hat Cluster # cd /boot # mkinitrd -f -v initrd-kernel.img kernel For example, the currently running kernel in the following mkinitrd command is 2.6.9-34.0.2.EL: # mkinitrd -f -v initrd-2.6.9-34.0.2.EL.img 2.6.9-34.0.2.EL Note You can determine the currently running kernel by running uname -r. 5.
Page 31: Red Hat Cluster Suite And Selinux
Red Hat Cluster Suite and SELinux qdiskd membership timeout value. The reason is because the quorum daemon must detect failed nodes on its own, and can take much longer to do so than CMAN. The default value for CMAN membership timeout is 10 seconds. Other site-specific conditions may affect the relationship between the membership timeout values of CMAN and qdiskd.
Page 32: General Configuration Considerations
Chapter 2. Before Configuring a Red Hat Cluster 2.8. General Configuration Considerations You can configure a Red Hat Cluster in a variety of ways to suit your needs. Take into account the following considerations when you plan, configure, and implement your Red Hat Cluster. 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)
Page 33: Configuration Tasks
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 3.1, “Configuration Tasks” • Section 3.2, “Starting luci and ricci”. • Section 3.3, “Creating A Cluster” •...
Page 34 Chapter 3. Configuring Red Hat Cluster With Conga # up2date -i ricci 2. At each node to be administered by Conga, start ricci. For example: # service ricci start Starting ricci: 3. Select a computer to host luci and install the luci software on that computer. For example: # up2date -i luci Note Typically, a computer in a server cage or a data center hosts luci;...
Page 35: Creating A Cluster
Creating A Cluster 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). The URL syntax for the luci server is https://luci_server_hostname:8084. The first time you access luci, two SSL certificate dialog boxes are displayed.
Page 36: Global Cluster Properties
Chapter 3. Configuring Red Hat Cluster With Conga A progress page shows the progress of those actions for each node in the cluster. When the process of creating a new cluster is complete, a page is displayed providing a configuration interface for the newly created cluster. 3.4.
Page 37 Global Cluster Properties 3. GULM tab (GULM clusters only) — This tab provides an interface for configuring GULM lock servers. The tab indicates each node in a cluster that is configured as a GULM lock server and provides the capability to change lock servers. Follow the rules provided at the tab for configuring GULM lock servers and click Apply for changes to take effect.
Page 38: Configuring Fence Devices
Chapter 3. Configuring Red Hat Cluster With Conga Parameter Description Votes The number of votes the quorum daemon advertises to CMAN when it has a high enough score. The number of cycles a node must miss to be declared dead. Minimum Score The minimum score for a node to be considered "alive".
Page 39: Creating A Shared Fence Device
Creating a Shared Fence Device • Bull PAP • Egenera SAN Controller • GNBD • IBM Blade Center • McData SAN Switch • QLogic SANbox2 • SCSI Fencing • Virtual Machine Fencing • Vixel SAN Switch • WTI Power Switch The following non-shared fence devices are available: •...
Page 40 Chapter 3. Configuring Red Hat Cluster With Conga Note If this is an initial cluster configuration, no fence devices have been created, and therefore none are displayed. 2. Click Add a Fence Device. Clicking Add a Fence Device causes the Add a Sharable Fence Device page to be displayed (refer to Figure 3.1, “Fence Device Configuration”).
Page 41: Modifying Or Deleting A Fence Device
Modifying or Deleting a Fence Device 5. Click Add this shared fence device. 6. Clicking Add this shared fence device causes a progress page to be displayed temporarily. After the fence device has been added, the detailed cluster properties menu is updated with the fence device under Configure a Fence Device.
Page 42: Adding A Member To A Running Cluster
Chapter 3. Configuring Red Hat Cluster With Conga 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. 1. At the detailed menu for the cluster (below the clusters menu), click Nodes. Clicking Nodes causes the display of an Add a Node element and a Configure element with a list of the nodes already configured in the cluster.
Page 43: Deleting A Member From A Cluster
Deleting a Member from a Cluster 5. When the process of adding a node is complete, a page is displayed providing a configuration interface for the cluster. 6. At the detailed menu for the cluster (below the clusters menu), click Nodes. Clicking Nodes causes the following displays: •...
Page 44: Configuring A Failover Domain
Chapter 3. Configuring Red Hat Cluster With Conga b. On that page, at the Choose a task drop-down box, choose to either disable the service are start it on another node and click Go. c. Upon confirmation that the service has been disabled or started on another node, click the cluster tab.
Page 45: Adding A Failover Domain
Adding a Failover Domain run the cluster service, you must set up only the members in the restricted failover domain that you associate with the cluster service. Note To configure a preferred member, you can create an unrestricted failover domain comprising only one cluster member.
Page 46: Modifying A Failover Domain
Chapter 3. Configuring Red Hat Cluster With Conga 8. To make additional changes to the failover domain, continue modifications at the Failover Domain Form page and click Submit when you are done. 3.7.2. Modifying a Failover Domain To modify 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 47: Adding Cluster Resources
Adding Cluster Resources 3.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 48 Chapter 3. Configuring Red Hat Cluster With Conga • Force unmount — If checked, forces the file system to unmount. The default setting is unchecked. Force Unmount kills all processes using the mount point to free up the mount when it tries to unmount. •...
Page 49: Adding A Cluster Service To The Cluster
Adding a Cluster Service to the Cluster Samba Service Name — Enter a name for the Samba server. Workgroup — Enter the Windows workgroup name or Windows NT domain of the Samba service. Note When creating or editing a cluster service, connect a Samba-service resource directly to service, not to a resource within a service.
Page 50: Configuring Cluster Storage
Chapter 3. Configuring Red Hat Cluster With Conga Note If you are adding a Samba-service resource, connect a Samba-service resource directly to the service, not to a resource within a service. 6. If you want to add resources to that resource, click Add a child. Clicking Add a child causes the display of additional options to local and global resources.
Page 51 Configuring Cluster Storage example, if you know that most of your storage is measured in gigabytes, terabytes, or other more familiar representations). Additionally, the Welcome to Storage Configuration Interface page lists systems that you are authorized to access, but currently are unable to administer because of a problem. Examples of problems: •...
Page 53: 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 4.1, “Starting, Stopping, and Deleting Clusters” • Section 4.2, “Managing Cluster Nodes” • Section 4.3, “Managing High-Availability Services”...
Page 54: Managing Cluster Nodes
Chapter 4. Managing Red Hat Cluster With Conga • For Restart this cluster and Stop this cluster/Start this cluster — Displays a page with the list of nodes for the cluster. • For Delete this cluster — Displays the Choose a cluster to administer page in the cluster tab, showing a list of clusters.
Page 55: Managing High-Availability Services
Managing High-Availability Services 4. Clicking Go causes a progress page to be displayed. When the action is complete, a page is displayed showing the list of nodes for the cluster. 4.3. Managing High-Availability Services You can perform the following management functions for high-availability services through the luci server component of Conga: •...
Page 56: Diagnosing And Correcting Problems In A Cluster
Chapter 4. Managing Red Hat Cluster With Conga • Restart this service and Stop this service — These selections are available when the service is running. Select either function and click Go to make the change take effect. Clicking Go causes a progress page to be displayed. When the change is complete, another page is displayed showing a list of services for the cluster.
Page 57: Configuration Tasks
Chapter 5. Configuring Red Hat Cluster With system-config-cluster This chapter describes how to configure Red Hat Cluster software using system-config-cluster, and consists of the following sections: Section 5.1, “Configuration Tasks” • Section 5.2, “Starting the Cluster Configuration Tool” • Section 5.3, “Configuring Cluster Properties” •...
Page 58: Starting The Cluster Configuration Tool
Chapter 5. Configuring Red Hat Cluster With system-config-cluster Section 5.8, “Adding a Cluster Service to the Cluster”. Refer to 8. Propagating the configuration file to the other nodes in the cluster. Section 5.9, “Propagating The Configuration File: New Cluster”. Refer to Section 5.10, “Starting the Cluster Software”.
Page 59 Starting the Cluster Configuration Tool cluster service operation. To manage the cluster system further, choose the Cluster Configuration tab.) 3. Clicking Create New Configuration causes the New Configuration dialog box to be displayed Configuration”). The New Configuration dialog box provides Figure 5.2, “Creating A New (refer to a text box for a cluster name and group boxes for the following configuration options: Choose...
Page 60 Chapter 5. Configuring Red Hat Cluster With system-config-cluster 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,...
Page 61 Starting the Cluster Configuration Tool (Figure 5.3, “The Cluster Configuration displaying a graphical representation of the configuration Tool”). 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.
Page 62: Configuring Cluster Properties
Chapter 5. Configuring Red Hat Cluster With system-config-cluster 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 mkqdisk utility. If this field contains an entry, the label overrides the Device field.
Page 63: Configuring Fence Devices
Configuring Fence Devices b. The Post-Fail Delay parameter is the number of seconds the fence daemon (fenced) waits before fencing a node (a member of the fence domain) after the node has failed.The Post-Fail Delay default value is 0. Its value may be varied to suit cluster and network performance. Note For more information about Post-Join Delay and Post-Fail Delay, refer to the fenced(8) man page.
Page 64: Adding And Deleting Members
Chapter 5. Configuring Red Hat Cluster With system-config-cluster 5. Choose File => Save to save the changes to the cluster configuration. 5.5. Adding and Deleting Members The procedures to add or delete a cluster member vary depending on whether the cluster is a newly configured cluster or a cluster that is already configured and running.
Page 65 Adding a Member to a New Cluster Figure 5.6. Adding a Member to a New GULM Cluster 3. At the Cluster Node Name text box, specify a node name. The entry can be a name or an IP address of the node on the cluster subnet. Note Each node must be on the same subnet as the node from which you are running the Cluster Configuration Tool and must be defined either in DNS or in the /etc/...
Page 66: Adding A Member To A Running Dlm Cluster
Chapter 5. Configuring Red Hat Cluster With system-config-cluster At the Fence Properties dialog box, click the Fence Device Type drop-down box and select the fence device for this node. Also, provide additional information required (for example, Port and Switch for an APC Power Device). g.
Page 67 Adding a Member to a Running DLM Cluster b. service gfs stop, if you are using Red Hat GFS c. service clvmd stop, if CLVM has been used to create clustered volumes d. service fenced stop e. service cman stop service ccsd stop 6.
Page 68: Deleting A Member From A Dlm Cluster
Chapter 5. Configuring Red Hat Cluster With system-config-cluster c. service fenced start d. service clvmd start, if CLVM has been used to create clustered volumes e. service gfs start, if you are using Red Hat GFS service rgmanager start, if the cluster is running high-availability services (rgmanager) Section 5.2, “Starting the Cluster Configuration Tool”).
Page 69 Deleting a Member from a DLM Cluster Figure 5.7. 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 70: Adding A Gulm Client-Only Member
Chapter 5. Configuring Red Hat Cluster With system-config-cluster Note Make sure to configure other parameters that may be affected by changes in this section. Section 5.1, “Configuration Tasks”. Refer to 5.5.4. Adding a GULM Client-only Member The procedure for adding a member to a running GULM cluster depends on the type of GULM node: either a node that functions only as a GULM client (a cluster member capable of running applications, but not eligible to function as a GULM lock server) or a node that functions as a GULM lock server.
Page 71 Deleting a GULM Client-only Member applications, but not eligible to function as a GULM lock server) or a node that functions as a GULM lock server. The procedure in this section describes how to delete a member that functions only as Section 5.5.6, a GULM client.
Page 72: Adding Or Deleting A Gulm Lock Server Member
Chapter 5. Configuring Red Hat Cluster With system-config-cluster a. service rgmanager stop, if the cluster is running high-availability services (rgmanager) b. service gfs stop, if you are using Red Hat GFS c. service clvmd stop, if CLVM has been used to create clustered volumes d.
Page 73 Adding or Deleting a GULM Lock Server Member 1. At one of the running members (running on a node that is not to be deleted), start system- Tool”). At the Cluster Section 5.2, “Starting the Cluster Configuration config-cluster (refer to Status Tool tab, disable each service listed under Services.
Page 74: Configuring A Failover Domain
Chapter 5. Configuring Red Hat Cluster With system-config-cluster Note Propagating the cluster configuration file this way is necessary under these circumstances because the cluster software is not running, and therefore not capable of propagating the configuration. 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 75: Adding A Failover Domain
Adding a Failover Domain • Ordered — Allows you to specify a preference order among the members of a failover domain. The member at the top of the list is the most preferred, followed by the second member in the list, and so Note Changing a failover domain configuration has no effect on currently running services.
Page 76 Chapter 5. Configuring Red Hat Cluster With system-config-cluster Note The name should be descriptive enough to distinguish its purpose relative to other names used in your cluster. Figure 5.10. Failover Domain Configuration: Configuring a Failover Domain 4. Click the Available Cluster Nodes drop-down box and select the members for this failover domain.
Page 77: Removing A Failover Domain
Removing a Failover Domain Figure 5.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. Priority is indicated by the position in the Member Node column and the value in the Priority column.
Page 78: Removing A Member From A Failover Domain
Chapter 5. Configuring Red Hat Cluster With system-config-cluster 2. At the bottom of the right frame (labeled Properties), click the Delete Failover Domain button. Clicking the Delete Failover Domain button causes a warning dialog box do be displayed asking if you want to remove the failover domain. Confirm that the failover domain identified in the warning dialog box is the one you want to delete and click Yes.
Page 79 Adding Cluster Resources 1. On the Resources property of the Cluster Configuration Tool, click the Create a Resource button. Clicking the Create a Resource button causes the Resource Configuration dialog box to be displayed. 2. At the Resource Configuration dialog box, under Select a Resource Type, click the drop-down box.
Page 80 Chapter 5. Configuring Red Hat Cluster With system-config-cluster IP Address IP Address — Type the IP address for the resource. Monitor Link checkbox — Check the box to enable or disable link status monitoring of the IP address resource NFS Mount Name —...
Page 81: Adding A Cluster Service To The Cluster
Adding a Cluster Service to the Cluster Workgroup — Enter the Windows workgroup name or Windows NT domain of the Samba service. Note When creating or editing a cluster service, connect a Samba-service resource directly to the service, not to a resource within a service. That is, at the Service Management dialog box, use either Create a new resource for this service or Add a Shared Resource to this service;...
Page 82 Chapter 5. Configuring Red Hat Cluster With system-config-cluster Figure 5.12. Adding a Cluster Service 4. If you want to restrict the members on which this cluster service is able to run, choose a failover domain from the Failover Domain drop-down box. (Refer to Section 5.6, “Configuring a Failover Domain”...
Page 83 Adding a Cluster Service to the Cluster Note Circumstances that require enabling Run Exclusive are rare. Enabling Run Exclusive can render a service offline if the node it is running on fails and no other nodes are empty. 7. Select a recovery policy to specify how the resource manager should recover from a service failure.
Page 84: Propagating The Configuration File: New Cluster
Chapter 5. Configuring Red Hat Cluster With system-config-cluster 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 valid_lft forever preferred_lft forever 5.9.
Page 85: Starting The Cluster Software
Starting the Cluster Software result in data corruption. If you have any concerns please contact your Red Hat service representative. 5. service gfs start, if you are using Red Hat GFS 6. service rgmanager start, if the cluster is running high-availability services (rgmanager) 7.
Page 87: 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 6.1, “Starting and Stopping the Cluster Software” • Section 6.2, “Managing High-Availability Services” •...
Page 88 Chapter 6. Managing Red Hat Cluster With system-config-cluster Figure 6.1. Cluster Status Tool 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.
Page 89: Modifying The Cluster Configuration
Modifying the Cluster Configuration Members Status Description Member The node is part of the cluster. Note: A node can be a member of a cluster; however, the node may be inactive and incapable of running services. For example, if rgmanager is not running on the node, but all other cluster software components are running in the node, the node appears as a Member in the Cluster Status Tool.
Page 90: Backing Up And Restoring The Cluster Database
Chapter 6. Managing Red Hat Cluster With system-config-cluster Important Section 5.5, “Adding and If you are changing the number of cluster members, refer to Deleting Members”. You must take into account certain circumstances for both DLM and GULM clusters when adding or deleting members. To edit the cluster configuration file, click the Cluster Configuration tab in the cluster configuration GUI.
Page 91: Disabling The Cluster Software
Disabling the Cluster Software 1. At the Cluster Configuration Tool tab of the Red Hat Cluster Suite management GUI, click File => Open. 2. Clicking File => Open causes the system-config-cluster dialog box to be displayed. 3. At the the system-config-cluster dialog box, select a backup file (for example, /etc/cluster/ cluster.conf.bak.1).
Page 92: Diagnosing And Correcting Problems In A Cluster
Chapter 6. Managing Red Hat Cluster With system-config-cluster # 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 # chkconfig --level 2345 fenced on...
Page 93: 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. Variables in the example apply to this example only;...
Page 94: Installing And Configuring The Apache Http Server
Appendix A. Example of Setting Up Apache HTTP Server 1. On one cluster node, use the interactive parted utility to create a partition to use for the document root directory. Note that it is possible to create multiple document root directories on different disk partitions.
Page 95 Installing and Configuring the Apache HTTP Server This IP address then must be configured as a cluster resource for the service using the Cluster Configuration Tool. • If the script directory resides in a non-standard location, specify the directory that contains the CGI programs.
Page 96 Appendix A. Example of Setting Up Apache HTTP Server • 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. • Choose ext3 from the File System Type drop-down menu. •...
Page 97: 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 98 Appendix B. Fence Device Parameters Field Description Password The script that supplies a password for access to the fence device. Using this supersedes the Password parameter. Script (optional) Domain Domain of the Bull PAP system to power cycle. Table B.3. Bull PAP (Platform Administration Processor) Field Description Name...
Page 99 Field Description Server The hostname of the server to fence the client from, in either IP address or hostname form. For multiple hostnames, separate each hostname with a space. IP address The cluster name of the node to be fenced. Refer to the fence_gnbd(8) man page for more information.
Page 100 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 (optional) The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
Page 101 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. Password The script that supplies a password for access to the fence device.
Page 102 Appendix B. Fence Device Parameters Field Description Password The script that supplies a password for access to the fence device. Using this supersedes the Password parameter. Script (optional) Port The switch outlet number. Use SSH (Rhel 4.8 and later) Indicates that system will use SSH to access the device. Table B.20.
Page 103: Revision History
Appendix C. Revision History Revision 1.0 Mon Apr 13 2009...
Page 105: Index
Index cluster service managers configuration, 39, 71, 74 cluster services, 39, 71 (see also adding to the cluster configuration) Apache HTTP Server, setting up, 83 ACPI httpd.conf, 84 configuring, 14 cluster software Apache HTTP Server configuration, 23 httpd.conf, 84 disabling, 81 setting up service, 83 installation and configuration, 47 starting and stopping, 77...
Page 106 Index configuring, 19 parameters, fence device, 87 power controller connection, configuring, 87 power switch, 87 (see also power controller) qdisk considerations for using, 20 quorum disk considerations for using, 20 SELinux configuring, 21 starting the cluster software, 74 System V init, 77 table command line tools, 9 tables...

Red Hat ENTERPRISE LINUX 4 - ADMINISTRATION Manual

Quick Links

Red Hat Enterprise Linux 4

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Red Hat ENTERPRISE LINUX 4 - ADMINISTRATION

Summary of Contents for Red Hat ENTERPRISE LINUX 4 - ADMINISTRATION

Table of Contents