Installation guide

54 Chapter 3. Installing and Configuring Red Hat Cluster Suite Software
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 all remaining running nodes (including GULM lock-
server nodes for GULM clusters) 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
d. service fenced stop (DLM clusters only)
e. service lock_gulmd stop or service cman stop according to the
type of lock manager used
f. service ccsd stop
5. Start cluster software on all remaining cluster nodes (including the GULM lock-
server nodes for a GULM cluster) by running the following commands in this order:
a. service ccsd start
b. service lock_gulmd start or service cman start according to the
type of lock manager used
c. service fenced start (DLM clusters only)
d. service clvmd start
e. service gfs start, if you are using Red Hat GFS
f. 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.
3.8. 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: