Installation guide

1.1.6. New and Changed Feat ures for Red Hat Ent erprise Linux 6.6
Red Hat Enterprise Linux 6.6 includes the following documentation and feature updates and
changes.
The tables of fence device parameters in Appendix A, Fence Device Parameters have been updated
to reflect small updates to the lu ci interface.
The tables of resource agent parameters in Appendix B, HA Resource Parameters have been
updated to reflect small updates to the lu ci interface.
Table B.3, “ Bind Mount (bi nd -mo unt Resource) (Red Hat Enterprise Linux 6.6 and later)
documents the parameters for the Bind Mount resource agent.
As of Red Hat Enterprise Linux 6.6 release, you can use the --no enabl e option of the ccs --
startall command to prevent cluster services from being enabled, as documented in
Section 6.2, “ Starting and Stopping a Cluster
Table A.11, “ Fence kdump documents the parameters for the kdump fence agent.
As of the Red Hat Enterprise Linux 6.6 release, you can sort the columns in a resource list on the
lu ci display by clicking on the header for the sort category, as described in Section 3.9,
Configuring Global Cluster Resources.
In addition, many small corrections and clarifications have been made throughout the document.
1.2. Configurat ion Basics
To set up a cluster, you must connect the nodes to certain cluster hardware and configure the nodes
into the cluster environment. Configuring and managing the Red Hat High Availability Add-On
consists of the following basic steps:
1. Setting up hardware. Refer to Section 1.3, “ Setting Up Hardware” .
2. Installing Red Hat High Availability Add-On software. Refer to Section 1.4, Installing Red Hat
High Availability Add-On software” .
3. Configuring Red Hat High Availability Add-On Software. Refer to Section 1.5, “ Configuring
Red Hat High Availability Add-On Software” .
1.3. Set t ing Up Hardware
Setting up hardware consists of connecting cluster nodes to other hardware required to run the Red
Hat High Availability Add-On. The amount and type of hardware varies according to the purpose and
availability requirements of the cluster. Typically, an enterprise-level cluster requires the following
type of hardware (refer to Figure 1.1, “ Red Hat High Availability Add-On Hardware Overview”). For
considerations about hardware and other cluster configuration concerns, refer to Chapter 2, Before
Configuring the Red Hat High Availability Add-On or check with an authorized Red Hat representative.
Cluster nodes — Computers that are capable of running Red Hat Enterprise Linux 6 software, with
at least 1GB of RAM.
Network switches for public network — This is required for client access to the cluster.
Network switches for private network — This is required for communication among the cluster
nodes and other cluster hardware such as network power switches and Fibre Channel switches.
Red Hat Ent erprise Linux 6 Clust er Administ rat ion
14