1. Manuals
  2. Brands
  3. Red Hat Manuals
  4. Software
  5. ENTERPRISE LINUX 5 - VIRTUAL SERVER...
  6. Configuration

Red Hat Cluster for Enterprise Linux 5 Configuration

Configuring and managing
Hide thumbs Also See for Cluster for Enterprise Linux 5:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Configuration Manual, Installation Manual
Configuring and Managing a Red
Hat Cluster
Red Hat Cluster for Red Hat Enterprise
Linux 5

Advertisement

Table of Contents
loading

Related Manuals for Red Hat Cluster for Enterprise Linux 5

Summary of Contents for Red Hat Cluster for Enterprise Linux 5

  • Page 1 Configuring and Managing a Red Hat Cluster Red Hat Cluster for Red Hat Enterprise Linux 5...
  • Page 2 Configuring and Managing a Red Hat Cluster: Red Hat Cluster for Red Hat Enterprise Linux 5 Copyright © 2007 Red Hat, Inc. Configuring and Managing a Red Hat Cluster describes the configuration and management of Red Hat cluster systems for Red Hat Enterprise Linux 5. It does not include information about Red Hat Linux Virtual Servers (LVS).

  • Page 4: Table Of Contents

    Table of Contents Introduction ....................... vi 1. Document Conventions ................. vii 2. Feedback ....................viii 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 5 Configuring and Managing a Red Hat Cluster 5.3. Deleting a Member from a Cluster ............45 6. Configuring a Failover Domain ...............46 6.1. Adding a Failover Domain ..............47 6.2. Removing a Failover Domain ..............50 6.3. Removing a Member from a Failover Domain ........50 7.

  • Page 6: 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 7: Document Conventions

    1. Document Conventions • Linux Virtual Server Administration — Provides information on configuring high-performance systems and services with the Linux Virtual Server (LVS). • Red Hat Cluster Suite Release Notes — Provides information about the current release of Red Hat Cluster Suite. 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 ht- tp://www.redhat.com/docs/.

  • Page 8: Feedback

    2. Feedback A tip is typically an alternative way of performing a task. Important Important information is necessary, but possibly unexpected, such as a configura- tion change that will not persist after a reboot. Caution A caution indicates an act that would violate your support agreement, such as re- compiling the kernel.

  • Page 9: 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 10: Installing Red Hat Cluster Software

    1.2. Installing Red Hat Cluster software Other options are available for storage according to the type of storage interface; for ex- ample, 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 11 1.3. Configuring Red Hat Cluster Software grouped into a failover domain for a cluster service. The services comprise resources such as NFS exports, IP addresses, and shared GFS partitions. Figure 1.2. Cluster Configuration Structure The following cluster configuration tools are available with Red Hat Cluster: •...

  • Page 12: Conga

    2. Conga In addition, information about using Conga and is provided in sub- system-config-cluster sequent chapters of this document. Information about the command line tools is available in the man pages for the tools. 2. Conga Conga is an integrated set of software components that provides centralized configuration and management of Red Hat clusters and storage.
  • Page 13 2. Conga ine which users are allowed to access clusters and computers registered in the luci database. It is possible to import users as a batch operation in a new luci server, just as it is possible to im- port clusters and computers. When a computer is added to a luci server to be administered, authentication is done once.
  • Page 14 2. Conga Figure 1.4. luci cluster Tab...

  • Page 15: System-Config-Cluster Cluster Administration Gui

    3. system-config-cluster Cluster Administration GUI 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 — . The GUI is for use with the system-config-cluster cluster infrastructure and the high-availability service management components.
  • Page 16 3.1. Cluster Configuration Tool Figure 1.6. Cluster Configuration Tool The Cluster Configuration Tool represents cluster configuration components in the configura- tion file ( ) with a hierarchical graphical display in the left panel. A tri- /etc/cluster/cluster.conf angle icon to the left of a component name indicates that the component has one or more sub- ordinate components assigned to it.

  • Page 17: Cluster Status Tool

    3.2. Cluster Status Tool 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 Man- age Fencing For This Node button) for each node.

  • Page 18: Command Line Administration Tools

    4. 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 ( ). You can use the Cluster Status Tool to enable, /etc/cluster/cluster.conf disable, restart, or relocate a high-availability service. 4.

  • Page 19: Configuration Considerations

    5. Configuration Considerations Command Line Used With Purpose Tool — Cluster Infra- is a program for making online updates to the ccs_tool ccs_tool Cluster Configur- structure cluster configuration file. It provides the capability to ation System create and modify cluster infrastructure components Tool (for example, creating a cluster, adding and removing a node).
  • Page 20 5. Configuration Considerations Certain low-cost alternatives, such as host RAID controllers, software RAID without cluster support, and multi-initiator parallel SCSI configurations are not compatible or appropriate for use as shared cluster storage. Data integrity assurance To ensure data integrity, only one node can run a cluster service and access cluster-service data at a time.

  • Page 21: Configuring Red Hat Cluster With Conga

    Chapter 2. 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 22 2. Starting luci and ricci To administer Red Hat Clusters with Conga, install and run luci and ricci as follows: At each node to be administered by Conga, install the ricci agent. For example: # yum install ricci At each node to be administered by Conga, start ricci. For example: # service ricci start Starting ricci: Select a computer to host luci and install the luci software on that computer.

  • Page 23: Creating A Cluster

    3. Creating A Cluster (or the equivalent). The URL syntax for the luci server is . The first time you access luci, two SSL certificate dia- https://luci_server_hostname:8084 log boxes are displayed. Upon acknowledging the dialog boxes, your Web browser displays the luci login page.
  • Page 24 4. Global Cluster Properties • The Cluster Name text box displays the cluster name; it does not accept a cluster name change. You cannot change the cluster name. The only way to change the name of a Red Hat cluster is to create a new cluster configuration with the new name. •...

  • Page 25: Configuring Fence Devices

    5. Configuring Fence Devices Note For more information about setting Quorum Partition parameters, refer to the qdisk(8) man page. 5. Configuring Fence Devices Configuring fence devices consists of creating, modifying, and deleting fence devices. Creating a fence device consists of selecting a fence device type and entering parameters for that fence device (for example, name, IP address, login, and password).

  • Page 26: Creating A Shared Fence Device

    5.1. Creating a Shared Fence Device • Dell DRAC • HP iLO • IBM RSA II • IPMI LAN • RPS10 Serial Switch This section provides procedures for the following tasks: • Creating shared fence devices — Refer to Section 5.1, “Creating a Shared Fence Device”. The procedures apply only to creating shared fence devices.

  • Page 27: Modifying Or Deleting A Fence Device

    5.2. Modifying or Deleting a Fence Device Figure 2.1. Fence Device Configuration 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. Specify the information in the Fencing Type dialog box according to the type of fence device.

  • Page 28: Configuring Cluster Members

    6. Configuring Cluster Members 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 29: Adding A Member To A Running Cluster

    6.2. Adding a Member to a Running Cluster 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. Click a link for a node at either the list in the center of the page or in the list in the detailed menu under the clusters menu.

  • Page 30: Deleting A Member From A Cluster

    6.3. Deleting a Member from a Cluster Joining the added node to cluster. A progress page shows the progress of those actions for each added node. When the process of adding a node is complete, a page is displayed providing a configura- tion interface for the cluster.

  • Page 31: Configuring A Failover Domain

    7. Configuring a Failover Domain Disable or relocate each service that is running on the node to be deleted: Note Repeat this step for each service that needs to be disabled or started on an- other node. Under Services on this Node, click the link for a service. Clicking that link cause a configuration page for that service to be displayed.

  • Page 32: Adding A Failover Domain

    7.1. Adding a Failover Domain Note Changing a failover domain configuration has no effect on currently running ser- vices. Note Failover domains are not required for operation. By default, failover domains are unrestricted and unordered. In a cluster with several members, using a restricted failover domain can minimize the work to set up the cluster to run a cluster service (such as ), which requires you to set up the con- httpd...

  • Page 33: Modifying A Failover Domain

    7.2. Modifying a Failover Domain At the Add a Failover Domain page, specify a failover domain name at the Failover Do- main Name text box. Note The name should be descriptive enough to distinguish its purpose relative to other names used in your cluster. To enable setting failover priority of the members in the failover domain, click the Priorit- ized checkbox.

  • Page 34: Adding Cluster Resources

    8. Adding Cluster Resources Modifying failover name — To change the failover domain name, modify the text at the Fail- over Domain Name text box. Note The name should be descriptive enough to distinguish its purpose relative to other names used in your cluster. Failover priority —...
  • Page 35 8. Adding Cluster Resources select the type of resource to configure. The resource options are described as follows: Name — Create a name for the file system resource. Mount Point — Choose the path to which the file system resource is mounted. Device —...
  • Page 36 8. Adding Cluster Resources Monitor Link checkbox — Check the box to enable or disable link status monitoring of the IP address resource NFS Mount Name — Create a symbolic name for the NFS mount. Mount Point — Choose the path to which the file system resource is mounted. Host —...

  • Page 37: Adding A Cluster Service To The Cluster

    9. Adding a Cluster Service to the Cluster directly to service, not to a resource within a service. Click Submit. Clicking Submit causes a progress page to be displayed followed by the dis- play of Resources for page. That page displays the added resource (and oth- cluster name er resources).

  • Page 38: Configuring Cluster Storage

    10. Configuring Cluster Storage Note If you are adding a Samba-service resource, connect a Samba-service re- source directly to the service, not to a resource within a service. 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 39 10. Configuring Cluster Storage forms throughout the storage user interface. This general choice allows you to avoid difficult decimal representations of storage size (for 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.

  • Page 40: Managing Red Hat Cluster With Conga

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

  • Page 41: Managing Cluster Nodes

    2. Managing Cluster Nodes 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. Select one of the functions and click Go. Clicking Go causes a progress page to be displayed. When the action is complete, a page is displayed showing either of the following pages according to the action selected: •...

  • Page 42: Managing High-Availability Services

    3. Managing High-Availability Services Selecting Have node join cluster starts cluster software and makes the node join the cluster. Making a node join a cluster allows the node to automatically join the cluster when it is rebooted. • Fence this node — Selecting this action causes the node to be fenced according to how the node is configured to be fenced.

  • Page 43: Diagnosing And Correcting Problems In A Cluster

    4. Diagnosing and Correcting Problems in a Cluster • Configure this service — Configure this service is available when the service is run- ning or not running. Selecting Configure this service causes the services configuration page for the service to be displayed. On that page, you can change the configuration of the service.

  • Page 44: Configuring Red Hat Cluster With System-Config-Cluster

    Chapter 4. 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 1, “Configuration Tasks” • Section 2, “Starting the Cluster Configuration Tool” • Section 3, “Naming The Cluster”...

  • Page 45: Starting The Cluster Configuration Tool

    2. Starting the Cluster Configuration Tool Starting the cluster software. Refer to Section 10, “Starting the Cluster Software”. 2. Starting the Cluster Configuration Tool You can start the Cluster Configuration Tool by logging in to a cluster node as root with the command and issuing the command.
  • Page 46 2. Starting the Cluster Configuration Tool Clicking Create New Configuration causes the New Configuration dialog box to be dis- played (refer to Figure 4.2, “Creating A New Configuration”). The New Configuration dia- log box provides a text box for cluster name and the following checkboxes: Custom Con- figure Multicast and Use a Quorum disk.

  • Page 47: Naming The Cluster

    3. Naming The Cluster Figure 4.2. Creating A New Configuration 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 4.3, “The Cluster Config- uration Tool”).

  • Page 48: Configuring Fence Devices

    4. Configuring Fence Devices Cluster Properties dialog box presents text boxes for Name, Config Version, and two Fence Daemon Properties parameters: Post-Join Delay and Post-Fail Delay. At the Cluster Alias text box, specify a name for the cluster. The name should be descript- ive enough to distinguish it from other clusters and systems on your network (for example, ).

  • Page 49: Adding And Deleting Members

    5. Adding and Deleting Members Fence Device button. Clicking Add a Fence Device causes the Fence Device Configura- tion dialog box to be displayed (refer to Figure 4.4, “Fence Device Configuration”). Figure 4.4. Fence Device Configuration 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.
  • Page 50 5.1. Adding a Member to a Cluster 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 4.5, “Adding a Member to a New Cluster”).

  • Page 51: Adding A Member To A Running Cluster

    5.2. Adding a Member to a Running Cluster 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 be- low the node in the left frame of the Fence Configuration dialog box.
  • Page 52 5.2. Adding a Member to a Running Cluster Section 5.1, “Adding a Member to a Cluster”. Click Send to Cluster to propagate the updated configuration to other running nodes in the cluster. Use the command to send the updated file from one of the /etc/cluster/cluster.conf existing cluster nodes to the new node.

  • Page 53: Deleting A Member From A Cluster

    5.3. Deleting a Member from a Cluster Start cluster services on the new node by running the following commands in this order: service cman start service clvmd start , if you are using Red Hat GFS service gfs start service rgmanager start Start the Red Hat Cluster Suite management GUI.

  • Page 54: Configuring A Failover Domain

    6. Configuring a Failover Domain Figure 4.6. Confirm Deleting a Member At that dialog box, click Yes to confirm deletion. Propagate the updated configuration by clicking the Send to Cluster button. (Propagating the updated configuration automatically saves the configuration.) Stop the cluster software on the remaining running nodes by running the following com- mands at each node in this order: service rgmanager stop , if you are using Red Hat GFS...

  • Page 55: Adding A Failover Domain

    6.1. Adding a Failover Domain • Ordered — Allows you to specify a preference order among the members of a failover do- main. The member at the top of the list is the most preferred, followed by the second mem- ber in the list, and so on.
  • Page 56 6.1. Adding a Failover Domain 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. At the Add Failover Domain dialog box, specify a failover domain name at the Name for new Failover Domain text box and click OK.
  • Page 57 6.1. Adding a Failover Domain over domain.) To prioritize the order in which the members in the failover domain assume control of a failed cluster service, follow these steps: Click (check) the Prioritized List checkbox (Figure 4.8, “Failover Domain Configura- tion: Adjusting Priority”).

  • Page 58: Removing A Failover Domain

    6.2. Removing a Failover Domain • Running cluster — If this cluster is operational and running, and you want to propagate the change immediately, click the Send to Cluster button. Clicking Send to Cluster automatically saves the configuration change. If you do not want to propagate the change immediately, choose File =>...

  • Page 59: Adding Cluster Resources

    7. Adding Cluster Resources When finished, click Close. 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 — If this is a new cluster, choose File => Save to save the changes to the cluster configuration.
  • Page 60 7. Adding Cluster Resources Device — Specify the device file associated with the file system resource. 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 61: Adding A Cluster Service To The Cluster

    8. Adding a Cluster Service to the 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 62 8. Adding a Cluster Service to the Cluster 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. At the Add a Service dialog box, type the name of the service in the Name text box and click OK.
  • Page 63 8. Adding a Cluster Service to the Cluster 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. Run Exclusive checkbox —...

  • Page 64: Propagating The Configuration File: New Cluster

    9. Propagating The Configuration File: New Cluster ton. The process is the same as creating a shared resource described in Section 7, “Adding Cluster Resources”. The private resource will appear as a child to the shared resource to which you associated with the shared resource. Click the triangle icon next to the shared resource to display any private resources associated.

  • Page 65: Starting The Cluster Software

    10. Starting the Cluster Software 10. Starting the Cluster Software After you have propagated the cluster configuration to the cluster nodes you can either reboot each node or start the cluster software on each cluster node by running the following com- mands at each node in this order: service cman start service clvmd start...

  • Page 66: Managing Red Hat Cluster With System-Config-Cluster

    Chapter 5. Managing Red Hat Cluster With system-config-cluster This chapter describes various administrative tasks for managing a Red Hat Cluster and con- sists of the following sections: • Section 1, “Starting and Stopping the Cluster Software” • Section 2, “Managing High-Availability Services” •...
  • Page 67 2. Managing High-Availability Services Figure 5.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. To enable a service, you can select the service in the Services area and click Enable.

  • Page 68: Modifying The Cluster Configuration

    3. 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 rgman- is not running on the node, but all other cluster software compon- ager...

  • Page 69: Backing Up And Restoring The Cluster Database

    4. Backing Up and Restoring the Cluster Database 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. Furthermore, it is recommended that you retain the default Quorum Votes value of .
  • Page 70 4. Backing Up and Restoring the Cluster Database Each time you save a configuration file, the Cluster Configuration Tool saves backup copies of the three most recently used configuration files as /etc/cluster/cluster.conf.bak.1 , and . The backup file etc/cluster/cluster.conf.bak.2 /etc/cluster/cluster.conf.bak.3 is the newest backup, is the etc/cluster/cluster.conf.bak.1...

  • Page 71: Disabling The Cluster Software

    5. Disabling the Cluster Software 11. Click the Cluster Management tab and verify that the changes have been propagated to the cluster members. 5. Disabling the Cluster Software It may become necessary to temporarily disable the cluster software on a cluster member. For example, if a cluster member experiences a hardware failure, you may want to reboot that mem- ber, but prevent it from rejoining the cluster to perform maintenance on the system.

  • Page 72: 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 73: Configuring Shared Storage

    3. Installing and Configuring the Apache HTTP Server 2. Configuring Shared Storage To set up the shared file system resource, perform the following tasks as root on one cluster system: On one cluster node, use the interactive utility to create a partition to use for the parted document root directory.
  • Page 74 3. Installing and Configuring the Apache HTTP Server DocumentRoot "/mnt/httpdservice/html" • Specify a unique IP address to which the service will listen for requests. For example: 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 75 3. Installing and Configuring the Apache HTTP Server • Enter a Name to be associated with the Apache HTTP Server service. • Specify the path to the Apache HTTP Server init script (for example, ) in the File (with path) field. etc/rc.d/init.d/httpd •...

  • Page 76: 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 Pass- word 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 77 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. Using this Script supersedes the Password parameter.
  • Page 78 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 79 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. Password The script that supplies a password for access to the fence device.
  • Page 80 Field Description Name A name for the WTI RPS-10 power switch connected to the cluster. Device The device the switch is connected to on the controlling host (for example, dev/ttys2 Port The switch outlet number. Table B.13. RPS-10 Power Switch (two-node clusters only) Field Description Name...
  • Page 81 Field Description (optional) Table B.17. Vixel SAN Switch 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 82: 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 informa- tion about Red Hat GFS, refer to Global File System: Configuration and Administration.
  • Page 83 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 # chkconfig --level 2345 ccsd off Edit the cluster configuration file as follows: At a cluster node, open...
  • Page 84 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. lvmconf --enable-cluster Enable cluster software to start upon reboot.

  • Page 85: Index

    cluster software Index configuration, 13 disabling, 63 installation and configuration, 36 starting and stopping, 58 cluster software installation and configuration, Apache HTTP Server httpd.conf, 65 cluster storage setting up service, 64 configuration, 30 command line tools table, 10 configuration file cluster propagation of, 56 administration, 32, 58...
  • Page 86 cluster, 35, 63 upgrading, RHEL 4 to RHEL 5, 74...

Table of Contents