This chapter provides an overview of Virtual eXtensible Local Area Network (VxLAN) and its implementation with OcNOS. VxLAN creates LAN segments using a MAC in IP encapsulation. The encapsulation carries the original L2 frame received from a host to the destination in another server using IP tunnels. The endpoints of the virtualized tunnel formed using VxLAN are called VTEPs (VxLAN Tunnel EndPoints). This technology allows the network to support several tenants with minimum changes in the network. The VTEPs carry tenant data in L3 tunnels over the network. The tenant data is not used in routing or switching. This aids in tenant machine movement and allows the tenants to have the same IP or MAC addresses on end devices, hosts/VM’s.

OcNOS supports VxLAN IPv4 tunnels, but both IPv4 and IPv6 hosts are supported.

Terms related to VxLAN configuration are defined in the table below.

VxLAN runs over the existing networking infrastructure. It provides a means to “stretch” a Layer 2 network. In short, VxLAN is a Layer 2 overlay scheme on a Layer 3 network.

Each overlay is termed as a VxLAN segment. Only VMs within the same VxLAN segment can communicate with each other. Each VxLAN segment is identified through a 24-bit segment ID termed the “VxLAN Network Identifier (VNI)”. This allows up to 16 million VxLAN segments to coexist within the same administrative domain.

VNI identifies the scope of the inner MAC frame originated by the individual VM. Hence, we can have overlapping MAC addresses across segments but never have traffic “cross over” since the traffic is isolated using the VNI. The VNI is in an outer header that encapsulates the inner MAC frame originated by the VM.

Any packets (including ARP-ND) that are uplifted to the VxLAN CPU queue from any port are rate limited to 500 packets/second. This is done to protect the system and CPU during an ARP storm.