aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/progressivevpp/twovppinstances.rst
diff options
context:
space:
mode:
authorJohn DeNisco <jdenisco@cisco.com>2018-08-03 11:02:24 -0400
committerDave Barach <openvpp@barachs.net>2018-08-03 17:38:40 +0000
commitc8e7f419fed65f2a9d055a5c9850e5fb213d9152 (patch)
treee7ef53d1113bbea129de6a1b4b709fa35ca2f2a7 /docs/guides/progressivevpp/twovppinstances.rst
parentb199e98fef4256795db7fb055b180a07ce84de5c (diff)
Added missing file
docs: Incorporate Javier's progressive VPP tutorial Change-Id: Iecee041039c7ed81713bc0530fc536e989c71497 Signed-off-by: John DeNisco <jdenisco@cisco.com>
Diffstat (limited to 'docs/guides/progressivevpp/twovppinstances.rst')
-rw-r--r--docs/guides/progressivevpp/twovppinstances.rst114
1 files changed, 114 insertions, 0 deletions
diff --git a/docs/guides/progressivevpp/twovppinstances.rst b/docs/guides/progressivevpp/twovppinstances.rst
new file mode 100644
index 00000000000..13447b5ea8b
--- /dev/null
+++ b/docs/guides/progressivevpp/twovppinstances.rst
@@ -0,0 +1,114 @@
+.. _twovppinstances:
+
+.. toctree::
+
+Connecting two FD.io VPP Instances
+----------------------------------
+
+.. _background-1:
+
+memif is a very high performance, direct memory interface type which can
+be used between FD.io VPP instances to form a topology. It uses a file socket
+for a control channel to set up that shared memory.
+
+.. _skills-to-be-learned-1:
+
+Skills to be Learned
+^^^^^^^^^^^^^^^^^^^^
+
+You will learn the following new skill in this exercise:
+
+#. Create a memif interface between two FD.io VPP instances
+
+You should be able to perform this exercise with the following skills
+learned in previous exercises:
+
+#. Run a second FD.io VPP instance
+#. Add an ip address to a FD.io VPP interface
+#. Ping from FD.io VPP
+
+.. _topology-1:
+
+Topology
+^^^^^^^^
+
+.. figure:: /_images/Connecting_two_vpp_instances_with_memif.png
+ :alt: Connect two FD.io VPP topology
+
+ Connect two FD.io VPP topology
+
+.. _initial-state-1:
+
+Initial state
+^^^^^^^^^^^^^
+
+The initial state here is presumed to be the final state from the
+exercise `Create an
+Interface <VPP/Progressive_VPP_Tutorial#Exercise:_Create_an_Interface>`__
+
+.. _action-running-a-second-vpp-instances-1:
+
+Running a second FD.io VPP instances
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+You should already have a FD.io VPP instance running named: vpp1.
+
+Run a second FD.io VPP instance named: vpp2.
+
+.. _action-create-memif-interface-on-vpp1-1:
+
+Create memif interface on vpp1
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Create a memif interface on vpp1:
+
+.. code-block:: console
+
+ vpp# create interface memif id 0 master
+
+This will create an interface on vpp1 memif0/0 using /run/vpp/memif as
+its socket file. The role of vpp1 for this memif inteface is 'master'.
+
+Use your previously used skills to:
+
+#. Set the memif0/0 state to up.
+#. Assign IP address 10.10.2.1/24 to memif0/0
+#. Examine memif0/0 via show commands
+
+.. _action-create-memif-interface-on-vpp2-1:
+
+Create memif interface on vpp2
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+We want vpp2 to pick up the 'slave' role using the same
+run/vpp/memif-vpp1vpp2 socket file
+
+.. code-block:: console
+
+ vpp# create interface memif id 0 slave
+
+This will create an interface on vpp2 memif0/0 using /run/vpp/memif as
+its socket file. The role of vpp1 for this memif inteface is 'slave'.
+
+Use your previously used skills to:
+
+#. Set the memif0/0 state to up.
+#. Assign IP address 10.10.2.2/24 to memif0/0
+#. Examine memif0/0 via show commands
+
+.. _action-ping-from-vpp1-to-vpp2-1:
+
+Ping from vpp1 to vpp2
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Ping 10.10.2.2 from vpp1
+
+.. code-block:: console
+
+ $ ping 10.10.2.2
+
+Ping 10.10.2.1 from vpp2
+
+.. code-block:: console
+
+ $ ping 10.10.2.1 \ No newline at end of file