Configuring A Failover Domain - Red Hat ENTERPRISE LINUX 5 - ADMINISTRATION Manual

e. Propagate the updated configuration by clicking the Send to Cluster button. (Propagating the
updated configuration automatically saves the configuration.)
4. Stop the cluster software on the remaining running nodes by running the following commands at
each node in this order:
a. service rgmanager stop
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 cman stop
5. Start cluster software on all remaining cluster nodes by running the following commands in this
order:
a. service cman start
b. service clvmd start, if CLVM has been used to create clustered volumes
c. service gfs start, if you are using Red Hat GFS
d. service rgmanager start
6. Start the Red Hat Cluster Suite management GUI. At the Cluster Configuration Tool tab, verify
that the configuration is correct. At the Cluster Status Tool tab verify that the nodes and services
are running as expected.

5.6. Configuring a Failover Domain

A failover domain is a named subset of cluster nodes that are eligible to run a cluster service in the
event of a node failure. A failover domain can have the following characteristics:
• Unrestricted — Allows you to specify that a subset of members are preferred, but that a cluster
service assigned to this domain can run on any available member.
• Restricted — Allows you to restrict the members that can run a particular cluster service. If none
of the members in a restricted failover domain are available, the cluster service cannot be started
(either manually or by the cluster software).
• Unordered — When a cluster service is assigned to an unordered failover domain, the member on
which the cluster service runs is chosen from the available failover domain members with no priority
ordering.
• 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
on.
Note
Changing a failover domain configuration has no effect on currently running services.
Configuring a Failover Domain
59