Disabling The Cluster Software - Red Hat CLUSTER SUITE FOR ENTERPRISE LINUX 5.1 Configuration Manual

Hide thumbs Also See for CLUSTER SUITE FOR ENTERPRISE LINUX 5.1:
Table of Contents

Advertisement

Chapter 6. Managing Red Hat Cluster With
9. Propagate the updated configuration file throughout the cluster by clicking Send to Cluster.
Note
The Cluster Configuration Tool 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 Configuration 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
Configuring Red Hat Cluster With
10. C licking Send to Cluster causes a Warning dialog box to be displayed. Click Yes to
propagate the configuration.
11. C lick the Cluster Management tab and verify that the changes have been propagated to the
cluster members.

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
follows:
# chkconfig --level 2345 rgmanager off
# chkconfig --level 2345 gfs off
# chkconfig --level 2345 clvmd off
# chkconfig --level 2345 cman off
Once the problems with the disabled cluster member have been resolved, use the following
commands to allow the member to rejoin the cluster:
# chkconfig --level 2345 rgmanager on
# chkconfig --level 2345 gfs on
# chkconfig --level 2345 clvmd on
# chkconfig --level 2345 cman on
You can then reboot the member for the changes to take effect or run the following commands
84
system-config-cluster
system-config-cluster
command to stop the member from joining the cluster at boot-up as
Chapter 5,
.

Advertisement

Table of Contents
loading

Table of Contents