summaryrefslogtreecommitdiff
path: root/docs/interfaces/geneve.rst
diff options
context:
space:
mode:
authorrebortg <github@ghlr.de>2020-11-29 21:52:28 +0100
committerrebortg <github@ghlr.de>2020-11-29 21:52:28 +0100
commit4abded8025a47990e58cd0a5fe9b96e38f4a3715 (patch)
tree2a6ebaa9dcf96a10e95577ae446c3897b0938fd4 /docs/interfaces/geneve.rst
parente7f01e6efc8578603592ff86c031d46f1f1f9d82 (diff)
downloadvyos-documentation-4abded8025a47990e58cd0a5fe9b96e38f4a3715.tar.gz
vyos-documentation-4abded8025a47990e58cd0a5fe9b96e38f4a3715.zip
arrange: interfaces
Diffstat (limited to 'docs/interfaces/geneve.rst')
-rw-r--r--docs/interfaces/geneve.rst61
1 files changed, 0 insertions, 61 deletions
diff --git a/docs/interfaces/geneve.rst b/docs/interfaces/geneve.rst
deleted file mode 100644
index 47068687..00000000
--- a/docs/interfaces/geneve.rst
+++ /dev/null
@@ -1,61 +0,0 @@
-.. _geneve-interface:
-
-######
-GENEVE
-######
-
-:abbr:`GENEVE (Generic Network Virtualization Encapsulation)` supports all of
-the capabilities of :abbr:`VXLAN (Virtual Extensible LAN)`, :abbr:`NVGRE
-(Network Virtualization using Generic Routing Encapsulation)`, and :abbr:`STT
-(Stateless Transport Tunneling)` and was designed to overcome their perceived
-limitations. Many believe GENEVE could eventually replace these earlier formats
-entirely.
-
-GENEVE is designed to support network virtualization use cases, where tunnels
-are typically established to act as a backplane between the virtual switches
-residing in hypervisors, physical switches, or middleboxes or other appliances.
-An arbitrary IP network can be used as an underlay although Clos networks - A
-technique for composing network fabrics larger than a single switch while
-maintaining non-blocking bandwidth across connection points. ECMP is used to
-divide traffic across the multiple links and switches that constitute the
-fabric. Sometimes termed "leaf and spine" or "fat tree" topologies.
-
-Geneve Header:
-
-.. code-block:: none
-
- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- |Ver| Opt Len |O|C| Rsvd. | Protocol Type |
- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- | Virtual Network Identifier (VNI) | Reserved |
- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- | Variable Length Options |
- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
-
-*************
-Configuration
-*************
-
-Common interface configuration
-==============================
-
-.. cmdinclude:: ../_include/interface-common-without-dhcp.txt
- :var0: geneve
- :var1: gnv0
-
-GENEVE options
-==============
-
-.. cfgcmd:: set interfaces geneve gnv0 remote <address>
-
- Configure GENEVE tunnel far end/remote tunnel endpoint.
-
-.. cfgcmd:: set interfaces geneve gnv0 vni <vni>
-
- :abbr:`VNI (Virtual Network Identifier)` is an identifier for a unique
- element of a virtual network. In many situations this may represent an L2
- segment, however, the control plane defines the forwarding semantics of
- decapsulated packets. The VNI MAY be used as part of ECMP forwarding
- decisions or MAY be used as a mechanism to distinguish between overlapping
- address spaces contained in the encapsulated packet when load balancing
- across CPUs.