(2) Virtual Network Identifier (VNI): identify a VXLAN segment. Used to perform VXLAN encapsulation/de-encapsulation. (1) VXLAN Tunnel Endpoint (VTEP): Map tenants’ end devices to VXLAN segments. My focus is more towards the Nexus 7k, Nexus 9k, Nexus 1k and CSR1000v.Įach control plane may have a series of caveats in their own, but those are not covered by this blog entry. This post tries to summarize the three (3) control planes currently supported by some of the Cisco NX-OS/IOS-XR. It is implemented and supported by multiple vendors and it is even natively supported in server OS like the Linux Kernel. The most commonly use VXLAN control plane is multicast. There are several drafts describing the use of different control planes.
The standard does not define a “standard” control plane for VXLAN. That is where the evolution of VXLAN control plane comes into play. Now, as with any other overlay network protocol, its scalability is tied into how well it can handle the Broadcast, Unknown unicast and Multicast (BUM). One of the Layer2 over Layer3 (or Layer2 over UDP) protocols adopted by the industry is VXLAN.
With the adoption of overlay networks as the standard deployment for multi-tenant network, Layer2 over Layer3 protocols have been the favorite among network engineers.
