User's Guide

VxLAN can add up to a 50-byte header to the tenant VM frame. For VxLAN to work correctly, this
requires that the IP MTU be set to at least 1550 bytes on the network-side interfaces. IP MTU of 1550
should also be set on all transit nodes which carry VxLAN trac. The point at which a tenant frame is
encapsulated (or decapsulated) is referred to as a VxLAN Tunnel Endpoint (or VTEP). VTEPs are
typically located on hypervisors but may also be located on physical network switches. Network
switches that act as a VTEP are referred to as VxLAN gateways.
The role to encapsulate/decapsulate a frame is performed by a VxLAN Tunnel Endpoint (VTEP), also
referred to as a VxLAN gateway. A VxLAN gateway can be a Layer 2 gateway or Layer 3 gateway
depending on its capacity. A Layer 2 gateway acts as a bridge connecting VxLAN segments to VLAN
segments. A Layer 3 gateway performs much like a Layer 2 gateway, but it is also capable of routing
trac between tenant VLANs.
Figure 73: VxLAN Topology
Related Topics
Configuring a VxLAN in Extreme Campus Controller on page 276
Configuring VLANS on page 270
VxLAN ExtremeXOS Considerations on page 277
Configuring a VxLAN in Extreme Campus Controller
A VxLAN topology in Extreme Campus Controller can be supported in the following configurations:
• A default VLAN for policy roles
• Contain to VLAN action for policy rules
• A default VLAN for network configuration
VxLAN is supported on a Centralized network with Jumbo-Frame support. You are not required to
explicitly enable Jumbo Support on the AP. The network path that the tunnel will traverse, from AP to
VTEP switch must be provisioned for Jumbo Frame support for at least 1550 byte packets. The AP does
not require a special setting for handling larger frames towards the clients. The AP and switches must
VLANS
Configure
276 Extreme Campus Controller User Guide for version 5.46.03