Clarify the different utility of Corosync version 1 and 2
Change-Id: I05ce8c9c542f355a0820e24ac01f3526e90b7ea1 Closes-Bug: #1762882
This commit is contained in:
parent
aefe1a1029
commit
a2acb21bcd
|
@ -499,6 +499,11 @@ to get a summary of the health of the communication rings:
|
|||
Use the :command:`corosync-objctl` utility to dump the Corosync cluster
|
||||
member list:
|
||||
|
||||
.. note::
|
||||
|
||||
If you are using Corosync version 2, use the :command:`corosync-cmapctl`
|
||||
utility instead of :command:`corosync-objctl`; it is a direct replacement.
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
# corosync-objctl runtime.totem.pg.mrp.srp.members
|
||||
|
@ -512,11 +517,6 @@ member list:
|
|||
You should see a ``status=joined`` entry for each of your constituent
|
||||
cluster nodes.
|
||||
|
||||
.. note::
|
||||
|
||||
If you are using Corosync version 2, use the :command:`corosync-cmapctl`
|
||||
utility instead of :command:`corosync-objctl`; it is a direct replacement.
|
||||
|
||||
.. _pacemaker-start:
|
||||
|
||||
Start Pacemaker
|
||||
|
|
Loading…
Reference in New Issue