![]() ![]() (7) VTEP1 will receive and de-encapsulate the packet and deliver it to SRV-A VTEP2 encapsulates the ARP reply with a VXLAN header and will unicast it to VTEP1. When SW2 VTEP2 receives it, it will lookup its local table and will find and entry with the information that traffic destined to SRV-A must be sent to VTEP1 address. (5) Each VTEP forwards the ARP request to its local destinations. (4) Each VTEP will receive and de-encapsulate the packet VXLAN packet and learn SRV-A Mac Address pointing to the remote VTEP address. (3) The multicast RP receive the packet and it will forward a copy to every VTEP that has joined the multicast group. (2) When the ARP request arrives to SW1 it will lookup its local table and if an entry is not found, it will encapsulate the ARP request over VXLAN and send it over the Multicast group configured for the specific VNI. ![]() SRV-A will generate an ARP request trying to discover SRV-B Mac Address. (1) Lets say SRV-A want to talk to SRV-B. Remote Mac Addresses are learn by a conversational Mac Address learning technique as follows (as per diagram): Initially, the switch will only learn the Mac Addresses of devices directly connected to them. Multicast configuration must support Any-Source Multicast (ASM).Every node configured with a VTEP for a VXLAN with certain VNI will join the same multicast group.When configuring VXLAN with multicast control plane:.(3) Network Virtualization Endpoint or Network Virtualization Edge (NVE): overlay interface configured in Cisco devices to define a VTEP Each segment can transport 802.1q-encapsulated packets, theoretically giving us 212 or 4096 VLANs over a single VNI. It hast up to 224 IDs theoretically giving us 16,777,216 segments. (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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |