summaryrefslogtreecommitdiff
path: root/docs/interfaces/geneve.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/interfaces/geneve.rst')
-rw-r--r--docs/interfaces/geneve.rst70
1 files changed, 0 insertions, 70 deletions
diff --git a/docs/interfaces/geneve.rst b/docs/interfaces/geneve.rst
deleted file mode 100644
index a4bc22aa..00000000
--- a/docs/interfaces/geneve.rst
+++ /dev/null
@@ -1,70 +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
-=============
-
-.. cfgcmd:: set interfaces geneve gnv0 address <address>
-
- Configure interface `<interface>` with one or more interface addresses.
-
- **address** can be specified multiple times as IPv4 and/or IPv6 address,
- e.g. 192.0.2.1/24 and/or 2001:db8::1/64
-
- Example:
-
- .. code-block:: none
-
- set interfaces geneve gnv0 address 192.0.2.1/24
- set interfaces geneve gnv0 address 192.0.2.2/24
- set interfaces geneve gnv0 address 2001:db8::ffff/64
- set interfaces geneve gnv0 address 2001:db8:100::ffff/64
-
-.. 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.
-
-.. cfgcmd:: set interfaces geneve gnv0 mtu <mtu>
-
- Set interface :abbr:`MTU (Maximum Transfer Unit)` size.