Installation guide

You can now configure an independent subtree as non-critical, indicating that if the resource fails
then only that resource is disabled. For information on this feature see Section 3.10, “ Adding a
Cluster Service to the Cluster” and Section C.4, “Failure Recovery and Independent Subtrees” .
This document now includes the new chapter Chapter 9, Diagnosing and Correcting Problems in a
Cluster.
In addition, small corrections and clarifications have been made throughout the document.
1.1.2. New and Changed Feat ures for Red Hat Ent erprise Linux 6.2
Red Hat Enterprise Linux 6.2 includes the following documentation and feature updates and
changes.
Red Hat Enterprise Linux now provides support for running Clustered Samba in an active/active
configuration. For information on clustered Samba configuration, refer to Chapter 11, Clustered
Samba Configuration.
Any user able to authenticate on the system that is hosting lu ci can log in to lu ci. As of Red Hat
Enterprise Linux 6.2, only the root user on the system that is running lu ci can access any of the
lu ci components until an administrator (the root user or a user with administrator permission)
sets permissions for that user. For information on setting lu ci permissions for users, refer to
Section 3.3, “ Controlling Access to luci” .
The nodes in a cluster can communicate with each other using the UDP unicast transport
mechanism. For information on configuring UD P unicast, refer to Section 2.12, “ UDP Unicast
Traffic” .
You can now configure some aspects of lu ci's behavior by means of the
/etc/sysco nfi g /l uci file. For example, you can specifically configure the only IP address
lu ci is being served at. For information on configuring the only IP address lu ci is being served
at, refer to Table 2.2, “ Enabled IP Port on a Computer That Runs luci” . For information on the
/etc/sysco nfi g /l uci file in general, refer to Section 2.4, “ Configuring lu ci with
/etc/sysco nfi g /l uci ” .
The ccs command now includes the --lsfenceopts option, which prints a list of available
fence devices, and the --l sfenceo pts fence_type option, which prints each available fence
type. For information on these options, refer to Section 5.6, “ Listing Fence Devices and Fence
Device Options” .
The ccs command now includes the --lsservi ceo pts option, which prints a list of cluster
services currently available for your cluster, and the --l sservi ceo pts service_type option,
which prints a list of the options you can specify for a particular service type. For information on
these options, refer to Section 5.11, “Listing Available Cluster Services and Resources”.
The Red Hat Enterprise Linux 6.2 release provides support for the VMware (SOAP Interface) fence
agent. For information on fence device parameters, refer to Appendix A, Fence Device Parameters.
The Red Hat Enterprise Linux 6.2 release provides support for the RHEV-M REST API fence agent,
against RHEV 3.0 and later. For information on fence device parameters, refer to Appendix A,
Fence Device Parameters.
As of the Red Hat Enterprise Linux 6.2 release, when you configure a virtual machine in a cluster
with the ccs command you can use the --add vm option (rather than the ad d servi ce option).
This ensures that the vm resource is defined directly under the rm configuration node in the cluster
configuration file. For information on configuring virtual machine resources with the ccs
command, refer to Section 5.12, “ Virtual Machine Resources” .
⁠Chapt er 1 . Red Hat High Availabilit y Ad d- O n Co nfigurat ion an d Management Overview
11