Appendix E. Upgrading A Red Hat Cluster from RHEL 4 to RHEL 5106# chkconfig --level 2345 gfs off# chkconfig --level 2345 clvmd off# chkconfig --level 2345 fenced off# chkconfig --level 2345 cman off# chkconfig --level 2345 ccsd off4. Edit the cluster configuration file as follows:a. At a cluster node, open /etc/cluster/cluster.conf with a text editor.b. If your cluster is configured with GULM as the cluster manager, remove the GULMXML elements — and — and their content from /etc/cluster/cluster.conf. GULM is not supported in Red Hat Cluster Suite for RHEL 5. Example E.1,“GULM XML Elements and Content” shows an example of GULM XML elements and content.c. At the element for each node in the configuration file, insertnodeid="number" after name="name". Use a number value unique to that node. Insertingit there follows the format convention of the element in a RHEL 5 clusterconfiguration file.NoteThe nodeid parameter is required in Red Hat Cluster Suite for RHEL 5. Theparameter is optional in Red Hat Cluster Suite for RHEL 4. If your configurationfile already contains nodeid parameters, skip this step.d. When you have completed editing /etc/cluster/cluster.conf, save the file and copy itto the other nodes in the cluster (for example, using the scp command).5. If your cluster is a GULM cluster and uses Red Hat GFS, change the superblock of each GFS filesystem to use the DLM locking protocol. Use the gfs_tool command with the sb and protooptions, specifying lock_dlm for the DLM locking protocol:gfs_tool sb device proto lock_dlmFor example:# gfs_tool sb /dev/my_vg/gfs1 proto lock_dlmYou shouldn't change any of these values if the filesystem is mounted.Are you sure? [y/n] ycurrent lock protocol name = "lock_gulm"new lock protocol name = "lock_dlm"Done6. Update the software in the cluster nodes to RHEL 5 and Red Hat Cluster Suite for RHEL 5. Youcan acquire and update software through Red Hat Network channels for RHEL 5 and Red HatCluster Suite for RHEL 5.
