Documentation/faq/vxlan.rst

   1 ..
   2       Licensed under the Apache License, Version 2.0 (the "License"); you may
   3       not use this file except in compliance with the License. You may obtain
   4       a copy of the License at
   5
   6           http://www.apache.org/licenses/LICENSE-2.0
   7
   8       Unless required by applicable law or agreed to in writing, software
   9       distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
  10       WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
  11       License for the specific language governing permissions and limitations
  12       under the License.
  13
  14       Convention for heading levels in Open vSwitch documentation:
  15
  16       =======  Heading 0 (reserved for the title in a document)
  17       -------  Heading 1
  18       ~~~~~~~  Heading 2
  19       +++++++  Heading 3
  20       '''''''  Heading 4
  21
  22       Avoid deeper levels because they do not render well.
  23
  24 ======
  25 VXLANs
  26 ======
  27
  28 Q: What's a VXLAN?
  29
  30     A: VXLAN stands for Virtual eXtensible Local Area Network, and is a means
  31     to solve the scaling challenges of VLAN networks in a multi-tenant
  32     environment. VXLAN is an overlay network which transports an L2 network
  33     over an existing L3 network. For more information on VXLAN, please see `RFC
  34     7348 <https://tools.ietf.org/html/rfc7348>`__.
  35
  36 Q: How much of the VXLAN protocol does Open vSwitch currently support?
  37
  38     A: Open vSwitch currently supports the framing format for packets on the
  39     wire. There is currently no support for the multicast aspects of VXLAN.  To
  40     get around the lack of multicast support, it is possible to pre-provision
  41     MAC to IP address mappings either manually or from a controller.
  42
  43 Q: What destination UDP port does the VXLAN implementation in Open vSwitch
  44 use?
  45
  46     A: By default, Open vSwitch will use the assigned IANA port for VXLAN,
  47     which is 4789. However, it is possible to configure the destination UDP
  48     port manually on a per-VXLAN tunnel basis. An example of this configuration
  49     is provided below.::
  50
  51         $ ovs-vsctl add-br br0
  52         $ ovs-vsctl add-port br0 vxlan1 -- set interface vxlan1 type=vxlan \
  53             options:remote_ip=192.168.1.2 options:key=flow options:dst_port=8472