• Tag : VXLAN

 
 

EVPN VXLAN Design Guide

EVPN VXLAN Design Guide   A Detailed Overview of the EVPN & VxLAN Protocols, Route Types, Use-Cases and Architectures   1. Introduction This document describes the operation and configuration of BGP EVPN Services over a VXLAN (Virtual eXtensible LAN) overlay on Arista platforms. The focus in this design guide is VxLAN as the protocol for the data-plane encapsulation for the overlay tunnels, and the functionality of the Multiprotocol BGP (MP-BGP) EVPN address-family for control plane signaling in the overlay.  MP-BGP EVPN is not only used for advertising MAC addresses, MAC and IP bindings and IP prefixes across the overlay; it...
Continue reading →

Arista Layer 2 VTEP EVPN VxLAN Route Type-1 Support

Arista Layer 2 VTEP EVPN Route Type-1 Support   Arista Layer 2 EVPN VTEP Inter-Operation With A/A Multi-homed Third-Party Layer 3 EVPN VXLAN VTEPs   Introduction   This document will explain the configurations required to support inter-working with EVPN VXLAN A/A multi-homed VTEPs, also known as L2 ECMP in VxLAN EVPN.   Currently, EOS uses MLAG is used to achieve Multi-homing in EVPN VxLAN Topologies, with an any-cast VxLAN VTEP configured on the MLAG pair, and as such does not need to support EVPN Multihoming Tx (Type-1 route generation). EOS can however install received Type-1 routes and can...
Continue reading →

Multi-Tenant EVPN VXLAN IRB Configuration & Verification Guide (iBGP Overlay eBGP Underlay)

Multi-Tenant EVPN VXLAN IRB Configuration & Verification Guide   Symmetric and Asymmetric IRB With VLAN Based and VLAN Aware Bundle Services Using an iBGP Overlay and eBGP Underlay Topology Logical Diagrams Tenant-A: Symmetric IRB Tenant-B: Asymmetric IRB Platform Support: https://www.arista.com/en/support/product-documentation/supported-features Topology Overview   In the symmetric and asymmetric IRB setups illustrated in the figures above;  for tenant-a four subnets are stretched across the two MLAG domains; with two subnets (vlan 10 – 10.10.10.0/24 and vlan 11 – 10.10.11.0/24) configured as a VLAN based service, and two other subnets (vlan 12 – 10.10.12.0/24 and vlan 13 – 10.10.13.0/24) as a vlan-aware...
Continue reading →

Multi-Tenant EVPN VXLAN IRB Configuration & Verification Guide (eBGP Overlay & Underlay)

Multi-Tenant EVPN VXLAN IRB Configuration & Verification Guide   Symmetric and Asymmetric IRB With VLAN Based and VLAN Aware Bundle Services Using an eBGP Overlay and eBGP Underlay Topology Logical Diagrams Tenant-A: Symmetric IRB Tenant-B: Asymmetric IRB Platform Support: https://www.arista.com/en/support/product-documentation/supported-features Topology Overview   In the symmetric and asymmetric IRB setups illustrated in the figures above;  for tenant-a four subnets are stretched across the two MLAG domains; with two subnets (vlan 10 – 10.10.10.0/24 and vlan 11 – 10.10.11.0/24) configured as a VLAN based service, and two other subnets (vlan 12 – 10.10.12.0/24 and vlan 13 – 10.10.13.0/24) as a vlan-aware...
Continue reading →

L3 EVPN VXLAN Configuration Guide

L3 EVPN VXLAN Configuration Guide   EVPN VXLAN Type-5 Layer 3 VPN  (With Dual-Homed Layer 2 and Layer 3 Sites) Overview Ethernet VPN (EVPN) is an extension of the BGP protocol introducing a new address family: L2VPN (address family number 25) / EVPN (subsequent address family number 70). It is used to exchange overlay MAC and IP address reachability information between BGP peers using type-2 routes, but additionally,  EVPN supports the exchange of layer 3 IPv4 and IPv6 overlay routes through the extensions described in (type 5 EVPN routes). An IP VRF is used on a VTEP router for...
Continue reading →

How does vxlan traffic flow from outside into the vxlan

Hi I understand how vxlan direct routing works from the vxlan perspective. The only thing I cannot grasp my head around is how does the traffic flow from ping for 172.10.10.50 from OUTSIDE DATACENTER -> SPINE eBGP-> multiple different LEAF MLAG VXLAN PAIR with different VTEP ex: 172.0.0.200 vtep 1, 172.0.0.201 vtep 2 -> server 172.10.10.50 connected to vtep 1 pair. vARP on all pairs advertising 172.10.10.1 as the default gateway. Once it comes into the spine how does the spine forward traffic to the get to the server ip addresses? Does it go through one of the vtep ip’s...
Continue reading →

Spine-Leaf BGP EVPN Best Practice

Hello I’m seeking for a white paper\best practice document that can cover deploying a topology of spine-leaf data center. The points i’m seeking clarifications are 1. underlay L3 connectivity – is IGP required to be configured between spine and leafs. 2. is multicast a must between spine and leaf for control plan operation? (forwarding BUM packets?) 3. with vxlan, are there any problems using mlags? how can i advertise a certain MAC address is available from two different VTEPs and encapsulate into vxlan from both connections? 4. in terms of configuration, how can i deploy such a scenario? 5. unconventional as it...
Continue reading →

vEOS on ESXi – Jumbo MTU Problem

Hi, I run couples of latest vEOS switches on ESXi, trying to build a VXLAN lab to test. Between vEOS switches, I used standard virtual switch as a virtual cable for each individual connection.  In vSwitch settings, I’ve set the MTU to 9000. MTU1500 works OK. But ping test over 1500 bytes all failed. PING 172.16.11.0 (172.16.11.0) 1473(1501) bytes of data. ping: sendmsg: Network is unreachable ping: sendmsg: Network is unreachable ping: sendmsg: Network is unreachable Searching over Internet came up no result…. Any thought?  

How to recover flood-list and mac address learning when using OVSDB management

Hi, I am a beginner of Arista switch. I have two questions on that. <Information of the switch>model:Arista DCS-7150S-64-CLversion:EOS-4.15.7M 1) The flood-list and the mac address  learning disappears when the switch restarts. Why? I set the infomation that “HER flood-list and mac address learning” on the Arista switch that using the OVSDB management. Example of setting  is as follows.(The following command executed on CVX.)-bash-4.1# vtep-ctl add-mcast-remote <LS-name> unknown-dst vxlan_over_ipv4 <vtep-ip>-bash-4.1# vtep-ctl add-ucast-remote  <LS-name>  <MAC-address> vxlan_over_ipv4 <vtep-ip> One day, I stopped the Arista switch and started it.Then, the information(HER flood-list and mac address  learning) disappeared from Arista switch…Note: I confirmed it by...
Continue reading →

Multicast in VXLAN with BGP EVPN control-plane

 Hello, We are trying to run multicast in data center overlay network. In our data centers we are using L3 leaf-spine topology with VXLAN. For the control plane BGP EVPN is used.  Leaf switches are deployed in an MLAG configuration. We want to run multicast between hosts that are on same vlan across switches in different MLAG domains. Multiple multicast receivers, as well as multiple senders are connected to different MLAG domains and are all in the same VLAN. Multicast receiver can receive m-c stream from the sender if both of them are in the same MLAG domain. But if receiver is connected to...
Continue reading →

EVPN Configuration – Layer 2 EVPN design with Type-2 routes

Introduction This document describes the operation and configuration of BGP EVPN with a VXLAN forwarding plane, for the construction of multi-tenant Layer 2 networks, termed L2VPNs within this document, over a layer 3 leaf-spine network. The configuration and guidance within the document unless specifically noted are based on the platforms and EOS releases noted in the table below Platform Software Release 7050X Series EOS release 4.18.1 7050X2 series EOS release 4.18.1 7060X Series EOS release 4.18.1 7160 series EOS release 4.18.1 7280R/7500R EOS release 4.18.1   Leaf spine underlay architecture EVPN with a VXLAN forwarding plane provides the ability to...
Continue reading →

VXLAN on 7150 EOS version 4.16.7M

Hi, I’m trying to get VXLAN to work between 2 back to Arista 7150S. But it does not work.   SW1 and SW2 are directly connected via a l3 interco. Traffic is being generated from SW1- eth1 On both switch I have version 4.16.7M Here is my config : SW1 config : SW1(config)#sh run int e2,1interface Ethernet1   load-interval 5   switchport trunk allowed vlan 777   switchport mode trunk   no lldp transmit   spanning-tree bpdufilter disableinterface Ethernet2   load-interval 5   switchport mode dot1q-tunnel   no switchport   ip address 7.7.7.1/30   ip igmp version 2   ip pim sparse-mode   spanning-tree bpdufilter disableSW1(config)#sh run int vxlan 1interface Vxlan1   vxlan...
Continue reading →

VXLAN on 7150 EOS version 4.16.7M

Hi, I’m trying to get VXLAN to work between 2 back to Arista 7150S. But it does not work.   SW1 and SW2 are directly connected via a l3 interco. Traffic is being generated from SW1- eth1 On both switch I have version 4.16.7M Here is my config : SW1 config : SW1(config)#sh run int e2,1interface Ethernet1   load-interval 5   switchport trunk allowed vlan 777   switchport mode trunk   no lldp transmit   spanning-tree bpdufilter disableinterface Ethernet2   load-interval 5   switchport mode dot1q-tunnel   no switchport   ip address 7.7.7.1/30   ip igmp version 2   ip pim sparse-mode   spanning-tree bpdufilter disableSW1(config)#sh run int vxlan 1interface Vxlan1   vxlan...
Continue reading →

vEOS – Logical VTEP with MLAG – VXLAN interpreted on MLAG Peer

Hello all, Please see attached picture for network topolgy. I try to use VXLAN with HER for DCI, together with BGP&BFD as routing protocol (for underlay) between Site A and Site B.– Site A: VLAN100 mapped to DCI VNI 10100– Site B: VLAN1100 mapped to DCI VNI 10100– spine1&spine2 as mlag peers with logical VTEP– spine3 as single VTEP– ports for DCI configured as L3 routed (no switchport)– EBGP between spine1 and spine3 as well as spine2 and spine3– VLAN4093 between spine1 (10.0.1.1) and spine2 (10.0.1.2) for re-routing in case one DCI is down– IBGP between spine1 and spine2– target...
Continue reading →

Access to manuals

Hi there! Currently I’m doing some research in new data center networking technologies. I downloaded vEOS image and built basic topology using Unetlab. Now I want to configure EVPN, but I couldn’t find any manuals on it. For some reason this one – https://eos.arista.com/eos-4-18-1f/evpn-vxlan/ is protected. How can I get it?

VXLAN Indirect Routing on 7280E, 7280R and 7500R series

In EOS-4.18.0F, VXLAN direct routing was introduced on the 7500R and 7280E/R series platforms. VXLAN routing provides the capability to route between VXLAN Layer 2 domains. In EOS-4.18.1, support for VXLAN Indirect Routing model is added to the 7500R and 7280E/R series platforms. In the Indirect routing model, the destination host is not directly attached to the VTEP(s) where the default gateway functionality is present. This model is called “indirect” because, in this model,  the packet possibly needs to go through multiple hops in the overlay to reach the final destination. It typically involves running routing protocols in the overlay...
Continue reading →

Overlay IPv6 routing over VXLAN

Overlay IPv6 routing over VXLAN Tunnel is simply routing IPv6 packets in and out of VXLAN Tunnels, similar to VXLAN overlay IPv4 routing. Underlay ( Outer IP Header ) in VXLAN still uses IPv4, and common for both overlay IPv4 and IPv6 . Hence VXLAN configuration remains exactly same for both IPv4 and IPv6 overlay routing support. This feature enables IPv6 networks/hosts get connected through VXLAN Tunnels. Following figure illustrates IPv6 routing followed by VXLAN encapsulation to reach a remote host across the VXLAN tunnel.   Following figure illustrates VXLAN decapsulation and routing of an IPv6 packet. Platform compatibility DCS-7050X DCS-7060X DCS7260X DCS-7050X2 DCS-7250X DCS-7304 / DCS-7308 /...
Continue reading →

EVPN extension to BGP using VXLAN

Ethernet VPN (EVPN) is an extension of the BGP protocol introducing a new address family: L2VPN (address family number 25) / EVPN (subsequent address family number 70). It is used to exchange overlay MAC and IP address reachability information between BGP peers within a tunnel [1]. In EOS 4.18.1F VXLAN tunnel support was introduced [2]. The available features are: Single-homing L2 routes (EVPN type 2 and type 3), with MLAG used as the L2 multi-homing solution. Multi-homing L2 routes (EVPN type 1 and type 2) are received and installed, with up to two all-active remote paths per destination (additional paths...
Continue reading →

OVSDB Hardware-VTEP L3 Integration

EOS currently supports VXLAN L2 integration with external controllers using the Arista OVSDB HW VTEP schema ([HW-VTEP]) implementation. External controllers can read and write the tables specified in OVSDB to orchestrate a VXLAN L2 overlay network. EOS-4.18.0F  introduces  support for L3 functionality in VXLAN Overlay Networks. The functionality,  implemented in Arista’s Cloudvision Controller (CVX) and switches, will be used to orchestrate L3 VXLAN Overlay in a physical network of Arista switches. External controllers (e.g., VMWare NSX or Nuage VSP) can interact with the OVSDB server running on CVX/EOS. CVX/EOS reads all the information from OVSDB and communicates with the appropriate Arista...
Continue reading →