Installation guide

Note
Make sure to configure other parameters that may be affected by changes in this section. Refer
to Section 5.1, “Configuration Tasks”.
5.5.4. Adding a GULM Client-only Member
The procedure for adding a member to a running GULM cluster depends on the type of GULM node:
either a node that functions only as a GULM client (a cluster member capable of running applications, but
not eligible to function as a GULM lock server) or a node that functions as a GULM lock server. T his
procedure describes how to add a member that functions only as a GULM client. T o add a member that
functions as a GULM lock server, refer to Section 5.5.6, “Adding or Deleting a GULM Lock Server
Member”.
To add a member that functions only as a GULM client to an existing cluster that is currently in
operation, follow these steps:
1. At one of the running members, start system-config-cluster (refer to Section 5.2, “Starting
the Cluster Configuration Tool”). At the Cluster Configurat ion T ool tab, 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. Start cluster services on the new node by running the following commands in this order:
a. service ccsd start
b. service lock_gulm d start
c. service clvm d start, if CLVM has been used to create clustered volumes
d. service gfs start, if you are using Red Hat GFS
e. service rgm anager start, if the cluster is running high-availability services
(rgm anager)
5. At system-config-cluster, in the Cluster Configuration Tool tab, verify that the
configuration is correct. At the Cluster Status T ool tab verify that the nodes and services are
running as expected.
Note
Make sure to configure other parameters that may be affected by changes in this section. Refer
to Section 5.1, “Configuration Tasks”.
5.5.5. Deleting a GULM Client-only Member
The procedure for deleting a member from a running GULM cluster depends on the type of member to
be removed: either a node that functions only as a GULM client (a cluster member capable of running
applications, but not eligible to function as a GULM lock server) or a node that functions as a GULM lock
server. T he procedure in this section describes how to delete a member that functions only as a GULM
client. To remove a member that functions as a GULM lock server, refer to Section 5.5.6, “Adding or
Deleting a GULM Lock Server Member”.
Red Hat Enterprise Linux 4 Cluster Administration
62