• Tag : EVPN

 
 

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 →

4-way L2 ECMP support for EVPN VXLAN All-Active Multihoming 

Description As of EOS 4.22.0F, EVPN all-active multihoming is supported as a standardized redundancy solution.  Redundancy provides not only better fault tolerance but also a way to load balance unicast traffic for better efficiency.  The EVPN VXLAN 4-way L2 ECMP feature allows a Customer Edge (CE) to perform Equal Cost Multi-Path (ECMP) unicast VXLAN switching to a remote CE that is multihomed to at most four Provider Edges (PE).  This feature overcomes the existing 2-way ECMP limitation by providing up to 4-way ECMP. Platform compatibility Platform Independent. (Subject to any and all platform compatibility limitations listed in EVPN Extension to...
Continue reading →

VXLAN Unresolved ARPs to 172.16.1.1

We have stand for test VXLAN between different DCs (schema in attachment). All Leafs connected to CVX server on each DC. And each CVX connected between themeslaves via BGP EVPN. For test in each leaf was connect server with linux and configured port on access VLAN100. Next step I configure assotiation VLAN100 and VNI25100. MAC Lerning good work and on both leaf I see mac-addreses. Connection for vxlan configured in GRE tunnel and has good L3 connectevless. But traffic has no on VNI 25100. I tried to debug this problem and discovered: show vxlan config-sanity category result detail ———————————- ——–...
Continue reading →

EVPN Transit Route VRF Leaking

Description As described in the L3 EVPN VXLAN Configuration Guide, it is common practice to use Layer 3 EVPN to provide multi-tenancy within a datacenter. This is achieved by keeping each tenant’s prefixes in separate VRFs.   In order to allow hosts from different VRFs to communicate with each other, a new mechanism lets the Spine act as a VTEP to which cross-VRF traffic will be directed for leaking.   The Spine will: Import specific learned IP or IPv6 prefixes belonging to one VRF into another Advertise these leaked routes to relevant EVPN neighbors (Leafs) with itself as next-hop. Furthermore,...
Continue reading →

EVPN MPLS Virtual Private Wire Service (VPWS)

Description EVPN MPLS VPWS (RFC 8214) provides the ability to forward customer traffic to / from a given attachment circuit (AC) without any MAC lookup / learning.  The basic advantage of VPWS over an L2 EVPN is the reduced control plane signalling due to not exchanging MAC address information.  In contrast to LDP pseudowires, EVPN MPLS VPWS uses BGP for signalling.  Port based and VLAN based services are supported. VLAN Based Service Port Based Service Platform compatibility DCS-7280R DCS-7280R2 DCS-7500R DCS-7500R2 Configuration VPWS configuration is made up of two main components on each participating router.  The first is the patch...
Continue reading →

EVPN E-Tree for MPLS

Description E-Tree is an L2 EVPN service (defined in RFC8317) in which each attachment circuit (AC) is assigned a role of Root or Leaf.  Once roles are assigned, forwarding rules are enforced such that: Root ACs can communicate with leaf ACs and other root ACs Leaf ACs can only communicate with root ACs.  Leaf AC to leaf AC traffic is blocked In this implementation, ACs are configured at the VLAN level, and the forwarding rules are enforced using a combination of local configuration of leaf VLANs (for local hosts), and  asymmetric route targets (for remote hosts). Platform compatibility DCS-7280R DCS-7280R2...
Continue reading →

EVPN Centralized Anycast Gateway

Description In the Centralized Anycast Gateway configuration, the Spines are configured with EVPN-IRB and are used as the IP Default Gateway(DWG), whereas the Top of rack switches perform L2 EVPN Routing. EVPN-IRB  supports both Virtual eXtensible Local Area Network (VXLAN) Bridging and IP Routing on the top of rack (TOR) switch.  In a typical EVPN IRB deployment, the IP Default Gateway(DGW) for a host (or VM) is the IP address configured on the IRB interface (check out the EVPN IRB TOI for more detail).   Platform compatibility DCS-7050X* DCS-7050X2 DCS-7050X3 DCS-7300/DCS-7320 DCS-7300X3 DCS-7260X* (DCS-7260X, DCS-7260X2, DCS-7260X3) DCS-7280R, DCS-7280R2, DCS-7280R3 DCS-7500R, DCS-7500R2,...
Continue reading →

Migrating from legacy DC design to EVPN VXLAN Fabric

Introduction This document is intended to provide a reference of steps and sequence followed for:  (1) migrating a legacy 3-tier L2 network to EVPN based VXLAN environment using Leaf & Spine design (2) migrating an L2 Leaf & Spine network with VXLAN using CVX as the control plane to EVPN based control plane (3) migrating an L2 Leaf & Spine network with VXLAN using static VXLAN as the control plane to EVPN based control plane. Scope The key objective of this report is to migrate a Layer 2 datacenter to EVPN based VXLAN using Leaf & Spine (L3LS) solution for...
Continue reading →

EVPN Internetworking with IPVPN

Description This feature adds control-plane support for inter-subnet forwarding between EVPN and IPVPN networks. It also introduces a new BGP path-attribute, D-PATH, that may be used for loop prevention when internetworking between EVPN and IPVPN domains. The supported transport type for IPVPN networks is MPLS, while EVPN networks may use MPLS or VXLAN. The following diagram shows an example topology where a DC EVPN-VXLAN cloud is connected to an MPLS-VPN cloud via border leaf nodes peering with both EVPN and IPVPN. The MPLS-VPN cloud is then connected to a DC EVPN-MPLS cloud, where the border leaf nodes peer with both...
Continue reading →

EVPN VxLAN control plane support for OpenStack

Description This feature enables support for an EVPN VxLAN control plane in conjunction with Arista’s OpenStack ML2 plugin for automated network provisioning. When utilizing this feature: VCS (Vxlan Controller Service) on CVX (CloudVision eXchange) will be responsible for dynamically provisioning VLAN to VNI mappings on switches based on OpenStack configuration The OpenStack service on CVX will be responsible for dynamically provisioning VLANs and allowing them on applicable trunk switchports on switches EVPN will be responsible for distributing and configuring flood lists based on  EVPN type 3 IMET routes and host reachability based on type 2 MAC-IP routes This feature is...
Continue reading →

VCS to EVPN hitless migration

Description This feature enables support for migrating from only using VCS as the control plane to only using EVPN as a control plane in a hitless manner with respect to L2 reachability information. Platform compatibility Platform Independent (Subject to any and all platform compatibility limitations of both VCS and EVPN) Configuration Assume that initially only VCS is configured as the control plane.  The step-by-step migration process is as follows: Check VCS L2 reachability information in L2Rib: Use the following show commands to verify that L2 reachability information is in L2Rib’s input and output: show l2Rib input vxlan-control-service show l2rib input...
Continue reading →

EVPN VxLAN IPV6 Overlay

Description Starting with EOS release 4.22.0F, the EVPN VXLAN L3 Gateway using EVPN IRB supports routing traffic from one IPV6 host to another IPV6 host on a stretched VXLAN VLAN. This TOI explains the EOS configuration and show commands. Platform Compatibility Platform supporting ND Proxy and ND Suppression DCS-7280R/7280R2 DCS-7050CX3-32S-F DCS-7050SX3-48YC12-F (Starting in 4.22.1F) DCS-7050SX3-48YC8 (Starting in 4.22.1F) DCS-7050/7050X/7050X2 (Starting in 4.22.1F) DCS-7260X/7260X3 (Starting in 4.22.1F) DCS-7060X/7060X2 (Starting in 4.21.1F) DCS-7250 (Starting in 4.22.1F) DCS-7300/DCS-7320 (Starting in 4.22.1F) Platform not supporting ND Proxy, No ND Suppression  DCS-7020R DCS-7160 DCS-7500R/7500R2/7500E Configuration Enable IPv6 Routing Enable global IPv6 unicast routing and IPv6...
Continue reading →

Problem with EVPN type-5 packet forwarding on vEOS

Hello, I am testing a solution based on VXLAN EVPN, with Type-5 routes, with vEOS 4.23.0.1, but I am having some issues in packet forwarding. The routes are correctly propagated, but when I try to ping from a device connected to one node, on a device connected to another node, the ping does not work. I also tried a ping, with a forced source IP, from the vEOS machine itself, but it has problems too. LEAF-2 LEAF-2#sh ip route vrf gold VRF: gold Codes: C – connected, S – static, K – kernel, O – OSPF, IA – OSPF inter...
Continue reading →

EVPN VxLAN IPV6 Overlay TOI

Description Starting with EOS release 4.22.0F, the EVPN VXLAN L3 Gateway using EVPN IRB supports routing traffic from IPV6 host to another IPV6 host on a stretched Vxlan VLAN. This TOI explains the EOS configuration and show commands. Platform Compatibility Platform supporting ND Proxy and ND Suppression DCS-7280R/7280R2 DCS-7050CX3-32S-F DCS-7050SX3-48YC12-F ( Starting in 4.22.1F ) DCS-7050SX3-48YC8 ( Starting in 4.22.1F ) DCS-7050/7050X/7050X2 ( Starting in 4.22.1F ) DCS-7260X/7260X3 ( Starting in 4.22.1F ) DCS-7060X/7060X2 ( Starting in 4.21.1F ) DCS-7250 ( Starting in 4.22.1F ) DCS-7300/DCS-7320 ( Starting in 4.22.1F ) Platform not supporting ND Proxy, No ND Suppression  DCS-7020R...
Continue reading →

VLAN-aware bundle Addition/Removal of VLANs from VLAN set

Description In EVPN, when configuring the member VLANs for a VLAN-aware bundle, the existing configuration command only allows the specification of a VLAN range string, which replaces the previously configured VLAN range string.  This enhancement adds new syntax to add or remove additional VLANs from the currently configured VLAN-aware bundle VLAN list. Platform Compatibility Platform independent Configuration The existing configuration CLI for configuring the member VLANs in a VLAN-aware bundle is: vlan <range>   This takes a VLAN range-string and uses it to replace the currently configured VLAN range-string.  The updated CLI syntax is now: vlan [ add | remove...
Continue reading →

EVPN Control Plane Support for MSS

Description This feature enables support for Macro Segmentation Service (MSS) to insert security devices into the traffic path for VXLAN networks using an EVPN control plane. With this feature enabled, CVX will continue to monitor the network via NetDB state and will initiate intercept and offload rules. With this feature enabled, MAC and IP reachability information will be learned and distributed in user configured L2 domains via EVPN.   CVX will continue to use the Vxlan Controller Service to discover network state and distribute MAC reachability information in service L2 domains (MSS L2 only.) Platform Compatibility Platform Independent (Subject to...
Continue reading →

EVPN – MLAG single homed hosts

Description As described in the Multi-VTEP MLAG TOI, singly connected hosts can lead to suboptimal peer-link utilisation. By adding a local VTEP to each MLAG peer, the control plane is able to advertise singly connected hosts as being directly behind a specific local VTEP / MLAG peer. The multi-VTEP MLAG feature has been extended to add EVPN control plane support. VXLAN bridging (EVPN Type-2 and Type-3 routes) and routing (EVPN Type-5 routes and IRB) are supported by this feature. When multi-VTEP MLAG mode is enabled, outgoing EVPN route advertisements will contain a nexthop and router MAC extended community as summarized...
Continue reading →

EVPN peering not being established

I’m building an EVPN test network using GNS3 (v2.2.0) and vEOS-lab images (4.22.2.1F) basing the configuration on the EVPN Deployment guide. I’ve built a network with 2 pairs of leaf switches & a pair of spine switches (see image). The Underlay BGP network is established fine, and I can reach the endpoints correctly. However when I try and establish the eVPN overlay peerings between the leaf switches and the spines some links never proceed beyond ‘OpenConfirm’ state. spine1(config-router-bgp)#show bgp evpn summary BGP summary information for VRF default Router identifier 192.168.31.129, local AS number 65000.0 Neighbor Status Codes: m - Under...
Continue reading →

SSU support for L2 EVPN with VXLAN

Description Smart System Upgrade (SSU) aims to minimize traffic loss during a software upgrade. The Smart System Upgrade (SSU) process includes the core functionality of Accelerated Software Upgrade, plus additional optimizations that permit a hitless restart of several features. SSU leverages protocols capable of graceful restart to minimize traffic loss during upgrade. For protocols not capable of graceful restart, SSU generates control plane messages and buffers them in hardware to be slowly released when the control plane is offline. Additionally, under SSU, the forwarding ASIC does not get reset and ports do not flap. Starting EOS 4.22.1F SSU is now...
Continue reading →

EVPN mutlihoming w/ ESI

I stumbled upon this archived [post](https://www.reddit.com/r/Arista/comments/azubnz/mlag_or_esi/) while researching EVPN support specifically on the EVPN multihoming side using common ESIs to extend beyond 2 switches in a LAG. Also this is the only post I’ve found mentioning EVPN Multihoming – https://eos.arista.com/arista-layer-2-vtep-evpn-vxlan-route-type-1-support/ but is limited to using mlag only. Does anyone have any information on when there will be support for the EVPN ESI LAGs?

Follow

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

Join other followers: