Installation guide

h. T o create additional fence devices at this fence level, return to step 6d. Otherwise, proceed

to the next step.

i. T o create additional fence levels, return to step 6c. Otherwise, proceed to the next step.

j. If you have configured all the fence levels and fence devices for this node, click Close.

7. Choose File => Save to save the changes to the cluster configuration.

To continue configuring a new cluster, proceed to Section 5.6, “Configuring a Failover Domain”.

5.5.2. Adding a Member to a Running DLM Cluster

The procedure for adding a member to a running DLM cluster depends on whether the cluster contains

only two nodes or more than two nodes. T o add a member to a running DLM cluster, follow the steps in

one of the following sections according to the number of nodes in the cluster:

For clusters with only two nodes —

Section 5.5.2.1, “Adding a Member to a Running DLM Cluster T hat Contains Only Two Nodes”

For clusters with more than two nodes —

Section 5.5.2.2, “Adding a Member to a Running DLM Cluster T hat Contains More Than Two Nodes”

5.5.2.1. Adding a Member to a Running DLM Cluster That Contains Only Two Nodes

To add a member to an existing DLM cluster that is currently in operation, and contains only two nodes,

follow these steps:

1. Add the node and configure fencing for it as in Section 5.5.1, “Adding a Member to a New Cluster”.

2. Click Send to Cluster to propagate the updated configuration to other running nodes in the

cluster.

3. Use the scp command to send the updated /etc/cluster/cluster.conf file from one of the

existing cluster nodes to the new node.

4. At system-config-cluster, in the Cluster Status T ool tab, disable each service listed

under Services.

5. Stop the cluster software on the two running nodes by running the following commands at each

node in this order:

a. service rgm anager stop, if the cluster is running high-availability services

(rgm anager)

b. service gfs stop, if you are using Red Hat GFS

c. service clvm d stop, if CLVM has been used to create clustered volumes

d. service fenced stop

e. service cman stop

f. service ccsd stop

6. Start cluster software on all cluster nodes (including the added one) by running the following

commands in this order:

a. service ccsd start

b. service cman start

c. service fenced start

d. service clvmd start, if CLVM has been used to create clustered volumes

e. service gfs start, if you are using Red Hat GFS

f. service rgmanager start, if the cluster is running high-availability services

(rgm anager)

Chapter 5. Configuring Red Hat Cluster With system-config-cluster