• Tag : VXLAN


Mss fortigate, cvx, cvp and Arista L3LS

Hi master. My customer has infrastructure Arista 2spine and 4leaf. They want to deploy new firewall Fortigate HA = 2 unit and Cloudvison appliance with MSS features. I’m reading and learn concept mss configuration on cvx and Fortigate, but there is something I’m not understanding about config mss on cvx. Arista Macro Segmentation Service integration with Fortinet Firewalls The link at the top, define command on cvx “type Fortinet fortimanager”My customer asks for me, how about not used /without the fortimanager? It is can used mss features, configuration or not?   Please advise and share your experience and link recommended.     Thanks   Robma bayu    

EVPN VXLAN Support for Wireless APs

Description Typical WiFi networks utilize a single, central Wireless LAN Controller (WLC) to act as a gateway between the wireless APs and the wired network. Arista differentiates itself by allowing the wireless network to utilize a distributed set of aggregation switches to connect APs to the wired network. This feature allows a decentralized and distributed set of aggregation switches to bridge wireless traffic on behalf of the set of APs configured to VXLAN tunnel all traffic to those aggregation switches, or their “local” APs. This is an extension of the VXLAN VTEP to VTEP bridging feature (https://eos.arista.com/eos-4-22-1f/vxlan-vtep-to-vtep-bridging/) which supports only...
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.   There are two options for pairing MSS and EVPN: Option 1: MSS + EVPN asymmetric IRB Option 2: MSS + EVPN symmetric IRB with VXLAN bridging to firewall (see https://eos.arista.com/eos-4-20-1f/evpn-irb-with-vxlan-underlay/ for...
Continue reading →

VxLAN VTEP counters on 7020R, 7280R, 7280R2, 7500R, and 7500R2 series

Description The VxLAN VTEP counters feature allows the device to count VxLAN packets received and sent by the device on a per VTEP basis. Specifically, it enables the device to count bytes and packets that are encapsulated and decapsulated as they are passing through. The counters are logically split up in the two VxLAN directions: “encap” counters count packets coming from the edge, encapsulated on the device and directed to the core “decap” counters count packets coming from the core, decapsulated on the device and heading towards the edge. To be able to count VxLAN packets the device has to...
Continue reading →

EVPN route null0

Hi, I am trying to configure BGP EVPN using route-type 5. I am run into issue that route table show learned route via Null0. However my control plane show the correct prefix is imported to BGP table. #show ip route vrf CORE C [0/0] via Vlan2404, directly connected B E [20/0] Null0 B E [20/0] Null0 #show ip bgp vrf CORE BGP routing table information for VRF CORE Router identifier, local AS number 65024 BGP routing table entry for Paths: 2 available 65002 65000 65001 from (, imported EVPN route, RD
Continue reading →

What is the meaning of this command?

In EVPN configuration guide, I read the following command has been used: ip address virtual source-nat vrf A address But I could not find any documentation to explain this command. What is used for? and How to use it? Please give some hint about this command. Thanks.

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

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 →


G’day, I am looking for some guidance as well as real life experience, gotchas, etc (if someone has done something similar it will be great to hear some thoughts). I am working on a design of 50+ DCs, meaning I’ll have 50+ fabrics across the globe. The requirement is to support multi-tenancy across all the sites and the only “relief” here is I only need to support layer3! That being said, I am considering multi-site, multi-pod architecture running route-servers within and between all sites. My current idea is to have three major sites (regions) – US, EMEA & APAC. In...
Continue reading →

RACL on inner IP fields for VXLAN decapsulated packets

Description This feature introduces the support for ACL configuration on VxLAN decapsulated packets. The configured ACL rules will be applied to the inner packet header after Vxlan header decapsulation. The ingress RACLs for VxLAN decap packets can be configured on SVIs or under Vxlan tunnel interface. Platform Compatibility DCS-7280R/R2 DCS-7500R/R2 Configuration No special configuration needed to enable RACLs on SVIs to match inner header fields for VxLAN decapsulated packets. interface Vlan100 ip address ip access-group vxlanAclIpv4CoreToEdge in ! interface Vxlan1 vxlan source-interface Loopback0 vxlan udp-port 4789 vxlan vlan 100 vni 20000 vxlan flood vtep ! ip...
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 →

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 →


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, 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 →


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 →

VXLAN Auto Flood-List Construction

Description VXLAN flood-lists are typically configured via CLI or learned via control plane sources such as EVPN. The introduction of wireless access points (APs) into the VXLAN data-plane and the desire to minimize AP configuration led to the introduction of a new feature to learn VXLAN flood-lists via the data-plane. When a VXLAN packet is received from a remote VTEP on a new VNI, that remote VTEP is added to the flood-list for that VNI. When all of the MACs behind a remote VTEP have aged out or been removed, that remote VTEP is no longer considered active and it...
Continue reading →


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

Join other followers: