3.0 config: replication administration - add diagrams

Author: andreyaksenov

doc/book/admin/replication/_images/box_info_replication_instance001.png

@@ -202,6 +202,9 @@ Checking a replica set status
               lag: 0
         ...
 
+    To see the diagrams that illustrate how the ``upstream`` and ``downstream`` connections look,
+    refer to :ref:`Monitoring a replica set <replication-monitoring>`.
+
 
 .. _replication-master_replica_add_data:
 

doc/book/admin/replication/_images/box_info_replication_instance002.png

@@ -223,6 +223,8 @@ Checking a replica set status
               lag: 0
         ...
 
+    To see the diagrams that illustrate how the ``upstream`` and ``downstream`` connections look,
+    refer to :ref:`Monitoring a replica set <replication-monitoring>`.
 
 .. _replication-automated-failover-add-data:
 
@@ -360,6 +362,13 @@ To test how automated failover works if the current master is stopped, follow th
 
     .. box_info_replication_auto_leader_disconnected_end
 
+    The diagram below illustrates how the ``upstream`` and ``downstream`` connections look like:
+
+    ..  image:: box_info_replication_instance002_disconnected.png
+        :width: 600
+        :align: center
+        :alt: replication status on a new master
+
 
 4.  Start ``instance002`` back using ``tt start``:
 

doc/how-to/replication/box_info_replication_instance002_disconnected.png

@@ -209,6 +209,9 @@ Checking a replica set status
             name: instance001
         ...
 
+    To see the diagrams that illustrate how the ``upstream`` and ``downstream`` connections look,
+    refer to :ref:`Monitoring a replica set <replication-monitoring>`.
+
 ..  include:: /how-to/replication/repl_bootstrap.rst
     :start-after: vclock_0th_component_note_start
     :end-before: vclock_0th_component_note_end
@@ -366,6 +369,13 @@ To insert conflicting records to ``instance001`` and ``instance002``, follow the
             name: instance001
         ...
 
+    The diagram below illustrates how the ``upstream`` and ``downstream`` connections look like:
+
+    ..  image:: box_info_replication_master_master_stopped.png
+        :width: 600
+        :align: center
+        :alt: replication status on a new master
+
 
 .. _replication-master-master-reseed-replica:
 
@@ -467,6 +477,13 @@ After :ref:`reseeding a replica <replication-master-master-reseed-replica>`, you
             name: instance001
         ...
 
+    The diagram below illustrates how the ``upstream`` and ``downstream`` connections look like:
+
+    ..  image:: box_info_replication_master_master_follow_stopped.png
+        :width: 600
+        :align: center
+        :alt: replication status after reseeding a replica
+
 
 2.  In the ``config.yaml`` file, clear the ``iproto`` option for ``instance001`` by setting its value to ``{}`` to disconnect this instance from ``instance002``.
     Set ``database.mode`` to ``ro``: