Red Hat CLUSTER FOR ENTERPRISE LINUX 5.0 Configuration Manual page 110

Appendix C. Upgrading A Red Hat Cluster from RHEL 4 to RHEL 5
f. Run
service ccsd stop
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 —
<gulm>
/etc/cluster/cluster.conf
5. Example C.1, "GULM XML Elements and Content"
elements and content.
c. At the
<clusternode>
nodeid="number"
there follows the format convention of the
configuration file.
Note
The
nodeid
parameter is optional in Red Hat Cluster Suite for RHEL 4. If your configuration
file already contains
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
100
.
/etc/cluster/cluster.conf
and — and their content from
</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"
parameter is required in Red Hat Cluster Suite for RHEL 5. The
parameters, skip this step.
nodeid
/etc/cluster/cluster.conf
for the DLM locking protocol:
lock_dlm
with a text editor.
shows an example of GULM XML
value unique to that node. Inserting it
number
element in a RHEL 5 cluster
<clusternode>
command).
scp
gfs_tool
/sbin/chkconfig
, save the file and copy it
command with the
sb
as