• Author : Madhu Sudan


Dual Stack Underlay Support for VXLAN with EVPN Control Plane

Description This feature allows a Data Center (DC) operator to incrementally migrate their VXLAN network from IPv4 to IPv6 underlay when using the EVPN control plane. It is meant for brownfield deployments where operators are considering transitioning their VXLAN network to IPv6 underlay but do not want to migrate their whole network at the same time. This feature allows them to migrate parts of their network to IPv6 and leave the rest of the network untouched, without any overlay network partitioning. The incremental transition is achieved using the concept of a dual-stack VTEP.  Dual Stack VTEPs and incremental migration A...
Continue reading →

IPv6 Underlay Support for VXLAN With EVPN Control Plane

Description Several customers have expressed interest in using IPv6 addresses for VXLAN underlay in their Data Centers (DC). Prior to 4.24.1F, EOS only supported IPv4 addresses for VXLAN underlay, i.e., VTEPs were reachable via IPv4 addresses only. This feature enables a VTEP to send VXLAN Encapsulated packets using IPv6 underlay. The following list describes the capabilities of this feature. The feature is designed for a Greenfield deployment environment, i.e., an environment where all VTEPs communicate using IPv6 underlay only. In such deployments, the VTEPs must be configured with an IPv6 address on the VXLAN source interface. And all VTEP-VTEP VXLAN...
Continue reading →

Federating CVX across multiple Data Centers using BGP-EVPN

Description Many Layer 2 VXLAN deployments span more than one physical data center (DC) location. Typically, each DC has several (10’s to 100’s) VTEPs. Each VTEP typically connects a number of servers/hosts. When using VCS, each VTEP also connects to a network controller (CVX), and shares with it the L2 reachability information about its locally attached hosts. VXLAN control service (VCS), running on the CVX is used to distribute L2 reachability information (MAC-VTEP bindings) amongst all the VTEPs. This is used to orchestrate a L2 overlay network in the DC. Typically, each DC functions as a separate island with its...
Continue reading →

HSC support for multiple standalone external controllers

External controllers can communicate with HSC (Hardware Switch Controller) running on CVX/EOS using the OVSDB management protocol (RFC 7047) in order to orchestrate a VXLAN L2/L3 overlay network over a physical network of Arista switches. To enable communication with an external controller, its IP address (and, optionally, port number) needs to be configured via the “manager” command in the HSC configuration mode on CVX. Arista# cvx Arista(config-cvx)# service hsc Arista(config-cvx-hsc)#manager <ip> [ port ] Arista(config-cvx-hsc)#no shutdown Prior to EOS 4.18.1F, only a single controller IP was allowed to be configured in the above CLI. If a new controller was configured via...
Continue reading →


Get every new post on this blog delivered to your Inbox.

Join other followers: