Installation guide

3. Disable cluster software from starting during reboot. At each node, run /sbin/chkconfig as

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 /etc/cluster/cluster.conf with a text editor.

b. If your cluster is configured with GULM as the cluster manager, remove the GULM

XML elements — <gulm> and </gulm> — and their content from /

etc/cluster/cluster.conf. GULM is not supported in Red Hat Cluster Suite for RHEL

5. Example C.1, “GULM XML Elements and Content” shows an example of GULM

XML elements and content.

c. At the <clusternode> element for each node in the configuration file, insert

nodeid="number" after name="name". Use a number value unique to that node. Inserting it

there follows the format convention of the <clusternode> element in a RHEL 5 cluster

configuration file.

Note

The nodeid parameter is required in Red Hat Cluster Suite for RHEL 5.

The parameter is optional in Red Hat Cluster Suite for RHEL 4. If your

configuration file already contains nodeid parameters, skip this step.

d. When you have completed editing /etc/cluster/cluster.conf, save the file and copy it

to 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 file system to use the DLM locking protocol. Use the gfs_tool command with the sb

and proto options, specifying lock_dlm for the DLM locking protocol:

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