Installation guide

file /etc/cluster/cluster.conf.bak.1 is the newest backup,
/etc/cluster/cluster.conf.bak.2 is the second newest backup, and
/etc/cluster/cluster.conf.bak.3 is the third newest backup.
If a cluster member becomes inoperable because of misconfiguration, restore the configuration file
according to the following steps:
1. At the Cluster Configurat ion Tool tab of the Red Hat Cluster Suite management GUI, click File
=> Open.
2. Clicking File => Open causes the system-config-cluster dialog box to be displayed.
3. At the the system -config-cluster dialog box, select a backup file (for example,
/etc/cluster/cluster.conf.bak.1). Verify the file selection in the Select ion box and click
OK.
4. Click File => Save As.
5. Clicking File => Save As causes the system -config-cluster dialog box to be displayed.
6. At the the system -config-cluster dialog box, select /etc/cluster/cluster.conf and
click OK. (Verify the file selection in the Selection box.)
7. Clicking OK causes an Information dialog box to be displayed. At that dialog box, click OK.
8. Propagate the updated configuration file throughout the cluster by clicking Send to Cluster.
Note
The Cluster Configurat ion T ool does not display the Send to Cluster button if the
cluster is new and has not been started yet, or if the node from which you are running the
Cluster Configurat ion Tool is not a member of the cluster. If the Send to Cluster
button is not displayed, you can still use the Cluster Configuration Tool; however, you
cannot propagate the configuration. You can still save the configuration file. For information
about using the Cluster Configuration Tool for a new cluster configuration, refer to
Chapter 5, Configuring Red Hat Cluster With system-config-cluster.
9. Clicking Send to Cluster causes a Warning dialog box to be displayed. Click Yes to
propagate the configuration.
10. Click the Cluster Management tab and verify that the changes have been propagated to the
cluster members.
6.5. Disabling the Cluster Software
It may become necessary to temporarily disable the cluster software on a cluster member. For example,
if a cluster member experiences a hardware failure, you may want to reboot that member, but prevent it
from rejoining the cluster to perform maintenance on the system.
Use the /sbin/chkconfig command to stop the member from joining the cluster at boot-up as
follows:
Chapter 6. Managing Red Hat Cluster With system-config-cluster
79