Installation guide

Important
Certain procedure in this chapter call for using the cman_to o l versio n -r command to
propagate a cluster configuration throughout a cluster. Using that command requires that
ri cci is running. Using ricci requires a password the first time you interact with ricci from
any specific machine. For information on the ri cci service, refer to Section 2.13,
“ Considerations for ricci ” .
Note
Procedures in this chapter may include specific commands for some of the command-line
tools listed in Appendix E, Command Line Tools Summary. For more information about all
commands and variables, refer to the man page for each command-line tool.
7.1. Configurat ion T asks
Configuring Red Hat High Availability Add-On software with command-line tools consists of the
following steps:
1. Creating a cluster. Refer to Section 7.2, “Creating a Basic Cluster Configuration File” .
2. Configuring fencing. Refer to Section 7.3, “ Configuring Fencing” .
3. Configuring failover domains. Refer to Section 7.4, “Configuring Failover Domains” .
4. Configuring HA services. Refer to Section 7.5, “ Configuring HA Services”.
5. Verifying a configuration. Refer to Section 7.9, “ Verifying a Configuration” .
7.2. Creat ing a Basic Clust er Configurat ion File
Provided that cluster hardware, Red Hat Enterprise Linux, and High Availability Add-On software are
installed, you can create a cluster configuration file (/etc/cl uster/cl uster.co nf) and start
running the High Availability Add-On. As a starting point only, this section describes how to create a
skeleton cluster configuration file without fencing, failover domains, and HA services. Subsequent
sections describe how to configure those parts of the configuration file.
Important
This is just an interim step to create a cluster configuration file; the resultant file does not have
any fencing and is not considered to be a supported configuration.
The following steps describe how to create and configure a skeleton cluster configuration file.
Ultimately, the configuration file for your cluster will vary according to the number of nodes, the type
of fencing, the type and number of HA services, and other site-specific requirements.
1. At any node in the cluster, create /etc/cl uster/cluster. co nf, using the template of the
example in Example 7.1, “cl uster. co nf Sample: Basic Configuration” .
⁠Chapt er 7 . Configu ring Red Hat High Availabilit y Manually
105