Red Hat Cluster for Enterprise Linux 5 Configuration page 83

3. Disable cluster software from starting during reboot. At each node, run
follows:
# chkconfig --level 2345 rgmanager off
# chkconfig --level 2345 gfs off
# chkconfig --level 2345 clvmd off
# chkconfig --level 2345 fenced off
# chkconfig --level 2345 cman off
# chkconfig --level 2345 ccsd off
4. Edit the cluster configuration file as follows:
a. At a cluster node, open
b. If your cluster is configured with GULM as the cluster manager, remove the GULM
XML elements —
etc/cluster/cluster.conf
5. Example C.1, "GULM XML Elements and Content" shows an example of GULM
XML elements and content.
c. At the
<clusternode>
nodeid="number"
there follows the format convention of the
configuration file.
d. When you have completed editing
to the other nodes in the cluster (for example, using the
5. If your cluster is a GULM cluster and uses Red Hat GFS, change the superblock of each
GFS file system to use the DLM locking protocol. Use the
and options, specifying
proto
gfs_tool sb device proto lock_dlm
For example:
# gfs_tool sb /dev/my_vg/gfs1 proto lock_dlm
You shouldn't change any of these values if the filesystem is mounted.
Are you sure? [y/n] y
current lock protocol name = "lock_gulm"
new lock protocol name = "lock_dlm"
Done
/etc/cluster/cluster.conf
and
<gulm> </gulm>
. GULM is not supported in Red Hat Cluster Suite for RHEL
element for each node in the configuration file, insert
after . Use a
name="name"
Note
The parameter is required in Red Hat Cluster Suite for RHEL 5.
nodeid
The parameter is optional in Red Hat Cluster Suite for RHEL 4. If your
configuration file already contains
lock_dlm
with a text editor.
— and their content from
value unique to that node. Inserting it
number
<clusternode>
parameters, skip this step.
nodeid
/etc/cluster/cluster.conf
gfs_tool
for the DLM locking protocol:
75
/sbin/chkconfig
/
element in a RHEL 5 cluster
, save the file and copy it
command).
scp
command with the
as
sb