Chapter 9. Managing Red Hat High Availability Add-On With Command Line Tools
This chapter describes various administrative tasks for managing Red Hat High Availability Add-On and consists of the following sections:
Important
Make sure that your deployment of Red Hat High Availability Add-On meets your needs and can be supported. Consult with an authorized Red Hat representative to verify your configuration prior to deployment. In addition, allow time for a configuration burn-in period to test failure modes.
Important
This chapter references commonly used
cluster.conf elements and attributes. For a comprehensive list and description of cluster.conf elements and attributes, see the cluster schema at /usr/share/cluster/cluster.rng, and the annotated schema at /usr/share/doc/cman-X.Y.ZZ/cluster_conf.html (for example /usr/share/doc/cman-3.0.12/cluster_conf.html).
Important
Certain procedure in this chapter call for using the
cman_tool version -r command to propagate a cluster configuration throughout a cluster. Using that command requires that ricci is running.
Note
Procedures in this chapter, may include specific commands for some of the command-line tools listed in Appendix E, Command Line Tools Summary. For more information about all commands and variables, see the man page for each command-line tool.
9.1. Starting and Stopping the Cluster Software
You can start or stop cluster software on a node according to Section 9.1.1, “Starting Cluster Software” and Section 9.1.2, “Stopping Cluster Software”. Starting cluster software on a node causes it to join the cluster; stopping the cluster software on a node causes it to leave the cluster.
9.1.1. Starting Cluster Software
To start the cluster software on a node, type the following commands in this order:
service cman startservice clvmd start, if CLVM has been used to create clustered volumesservice gfs2 start, if you are using Red Hat GFS2service rgmanager start, if you using high-availability (HA) services (rgmanager).
For example:
[root@example-01 ~]#service cman startStarting cluster: Checking Network Manager... [ OK ] Global setup... [ OK ] Loading kernel modules... [ OK ] Mounting configfs... [ OK ] Starting cman... [ OK ] Waiting for quorum... [ OK ] Starting fenced... [ OK ] Starting dlm_controld... [ OK ] Starting gfs_controld... [ OK ] Unfencing self... [ OK ] Joining fence domain... [ OK ] [root@example-01 ~]#service clvmd startStarting clvmd: [ OK ] Activating VG(s): 2 logical volume(s) in volume group "vg_example" now active [ OK ] [root@example-01 ~]#service gfs2 startMounting GFS2 filesystem (/mnt/gfsA): [ OK ] Mounting GFS2 filesystem (/mnt/gfsB): [ OK ] [root@example-01 ~]#service rgmanager startStarting Cluster Service Manager: [ OK ] [root@example-01 ~]#
9.1.2. Stopping Cluster Software
To stop the cluster software on a node, type the following commands in this order:
service rgmanager stop, if you using high-availability (HA) services (rgmanager).service gfs2 stop, if you are using Red Hat GFS2umount -at gfs2, if you are using Red Hat GFS2 in conjunction withrgmanager, to ensure that any GFS2 files mounted duringrgmanagerstartup (but not unmounted during shutdown) were also unmounted.service clvmd stop, if CLVM has been used to create clustered volumesservice cman stop
For example:
[root@example-01 ~]#service rgmanager stopStopping Cluster Service Manager: [ OK ] [root@example-01 ~]#service gfs2 stopUnmounting GFS2 filesystem (/mnt/gfsA): [ OK ] Unmounting GFS2 filesystem (/mnt/gfsB): [ OK ] [root@example-01 ~]#umount -at gfs2[root@example-01 ~]#service clvmd stopSignaling clvmd to exit [ OK ] clvmd terminated [ OK ] [root@example-01 ~]#service cman stopStopping cluster: Leaving fence domain... [ OK ] Stopping gfs_controld... [ OK ] Stopping dlm_controld... [ OK ] Stopping fenced... [ OK ] Stopping cman... [ OK ] Waiting for corosync to shutdown: [ OK ] Unloading kernel modules... [ OK ] Unmounting configfs... [ OK ] [root@example-01 ~]#
Note
Stopping cluster software on a node causes its HA services to fail over to another node. As an alternative to that, consider relocating or migrating HA services to another node before stopping cluster software. For information about managing HA services, see Section 9.3, “Managing High-Availability Services”.
