Disabling the Cluster Software734. Increment the configuration version beyond the current working version number as follows:a. Click Cluster => Edit Cluster Properties.b. At the Cluster Properties dialog box, change the Config Version value and click OK.5. Click File => Save As.6. Clicking File => Save As causes the system-config-cluster dialog box to be displayed.7. At the the system-config-cluster dialog box, select /etc/cluster/cluster.conf and clickOK. (Verify the file selection in the Selection box.)8. Clicking OK causes an Information dialog box to be displayed. At that dialog box, click OK.9. Propagate the updated configuration file throughout the cluster by clicking Send to Cluster.NoteThe Cluster Configuration Tool does not display the Send to Cluster button ifthe cluster is new and has not been started yet, or if the node from which you arerunning the Cluster Configuration Tool is not a member of the cluster. If the Sendto Cluster button is not displayed, you can still use the Cluster Configuration Tool;however, you cannot propagate the configuration. You can still save the configurationfile. For information about using the Cluster Configuration Tool for a new clusterconfiguration, refer to Chapter 5, Configuring Red Hat Cluster With system-config-cluster.10. Clicking Send to Cluster causes a Warning dialog box to be displayed. Click Yes to propagatethe configuration.11. Click the Cluster Management tab and verify that the changes have been propagated to thecluster members.6.5. Disabling the Cluster SoftwareIt may become necessary to temporarily disable the cluster software on a cluster member. Forexample, 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 asfollows:# chkconfig --level 2345 rgmanager off# chkconfig --level 2345 gfs off# chkconfig --level 2345 clvmd off# chkconfig --level 2345 cman offOnce the problems with the disabled cluster member have been resolved, use the followingcommands to allow the member to rejoin the cluster: