Configuring A Failover Domain - Red Hat Cluster for Enterprise Linux 5 Configuration

Figure 4.6. Confirm Deleting a Member
d. At that dialog box, click Yes to confirm deletion.
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 com-
mands at each node in this order:
a.
service rgmanager stop
b.
service gfs stop
c.
service clvmd stop
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
c.
service gfs start
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.

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 mem-
ber on which the cluster service runs is chosen from the available failover domain members
with no priority ordering.
6. Configuring a Failover Domain
, if you are using Red Hat GFS
, if you are using Red Hat GFS
46