Arista Portal

  • Tag : EVPN

 
 

Spanning tree network super root

Posted on December 22, 2020 by   |   66 Views

Description Arista MLAG supports STP for Layer-2 loop detection. In fact, most customers enable STP in their MLAG(s) to ensure no downstream Layer-2 loops due to mis-cabling or mis-configuration. Pre 4.25.1F EVPN All-Active multihoming mechanism did not support STP downstream because of the following reasons: Unlike MLAG, EVPN multihoming peers run STP independently. Hence, all EVPN multihoming PEs send BPDUs independently on port-channel links. STP BPDUs will have Bridge ID derived from the local system MAC address, so the BPDUs generated by each multihoming PE are different.  Hence, the downstream multihomed switch/server receives different BPDUs from different PEs, so STP...
Continue reading →

Deploying EVPN with IPv6 Fabric using RFC5549

Posted on November 23, 2020 by   |   125 Views

Introduction To use IPv6 addresses for VXLAN underlay, there are two different approaches.  The first approach is to make use of IPv6 VXLAN tunnel (i.e. IPV6 tunnel encapsulation) for all VTEPs to VTEPs communication.  This approach is suitable for a Greenfield deployment environment where all the VTEPs are capable of supporting IPV6 VXLAN tunnels. The second approach is to use IPV4 VXLAN Tunnels while using IPv6 addresses in the Data center fabric.  In this approach, all VTEPs advertise the IPV4 VXLAN Tunnels VTEP IP with a IPv6 nexthop using RFC5549.  Because VTEPs to VTEPs are using IPV4 VXLAN Tunnels and...
Continue reading →

EVPN L3 Gateway

Posted on October 28, 2020 by   |   425 Views

Description This feature adds control plane support for inter-subnet forwarding between EVPN networks. This support is achieved by advertising received EVPN IP Prefix routes (Type-5) with next-hop self. VXLAN and MPLS encapsulation are supported, and the encapsulation type used for advertised routes is dependent on the encapsulation type configured for EVPN peering. The following diagram shows an example topology where an EVPN VXLAN network exchanges Type-5 routes with an EVPN MPLS network.   Within the EVPN VXLAN and EVPN MPLS network, EVPN routes are exchanged as normal. The L3 gateway functionality is achieved by GW1/2 and GW3/4 advertising received type-5...
Continue reading →

EVPN VXLAN single-gateway centralized routing

Posted on October 28, 2020 by   |   303 Views

Description In a traditional EVPN VXLAN centralized anycast gateway deployment, multiple L3 VTEPs serve the role of the centralized anycast gateway.  In order for hosts to have a consistent ARP binding for any of the individual centralized gateway VTEPs, each VTEP operating as a centralized gateway is configured with a virtual router MAC (VARP MAC), and a virtual VTEP IP (VARP VTEP IP), that is shared between all of the L3 VTEPs operating as centralized gateways.  Each centralized gateway VTEP also advertises an EVPN type-3 route for both its primary VTEP IP and VARP VTEP IP, so both IPs end...
Continue reading →

EVPN VXLAN Support for Wireless APs

Posted on August 24, 2020 by   |   106 Views

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

Posted on August 24, 2020 by   |   214 Views

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 →

EVPN MPLS Virtual Private Wire Service (VPWS)

Posted on August 24, 2020 by   |   496 Views

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 DCS-7800R3 DCS-7500R3 DCS-7280R3 Configuration VPWS configuration is made up of two main components on each participating router.  The first...
Continue reading →

Discard unimportable VPN paths

Posted on August 20, 2020 by   |   86 Views

Description In a Service Provider network, a Provider Edge (PE) device learns VPN paths from remote PEs and uses the Route Target extended communities carried by those paths to determine which customer VRF(s) the paths should be imported into (from where they can be subsequently advertised to Customer Edge (CE) devices). In large Service Provider networks, each PE device may learn a significant number of VPN paths even though it might only handle a relatively small number of customer VRFs. As a result, such PE devices are really only interested in a subset of the VPN paths that they receive...
Continue reading →

EVPN route type 5 imported

Posted on August 18, 2020 by   |   0 Views

Hi, We are configuring L3 VPN service using EVPN route type 5. I can see the route in the bgp table of the VRF but in the route table, the destination of the learned prefix is null0. Can someone explain why and how to fix it? I am running vEOS 4.24.0F in our lab. Here is the output of the bgp table in the VRF: AT1-R1#show ip bgp 10.37.4.0/23 vrf CORE BGP routing table information for VRF CORE Router identifier 10.32.25.2, local AS number 65032 BGP routing table entry for 10.37.4.0/23 Paths: 1 available 65037 65370 2.2.2.3 from 1.1.1.103 (2.2.2.3),...
Continue reading →

EVPN route type 5 imported

Posted on August 18, 2020 by   |   0 Views

Hi, We are configuring L3 VPN service using EVPN route type 5. I can see the route in the bgp table of the VRF but in the route table, the destination of the learned prefix is null0. Can someone explain why and how to fix it? I am running vEOS 4.24.0F in our lab. Here is the output of the bgp table in the VRF: AT1-R1#show ip bgp 10.37.4.0/23 vrf CORE BGP routing table information for VRF CORE Router identifier 10.32.25.2, local AS number 65032 BGP routing table entry for 10.37.4.0/23 Paths: 1 available 65037 65370 2.2.2.3 from 1.1.1.103 (2.2.2.3),...
Continue reading →

EVPN route null0

Posted on July 27, 2020 by   |   0 Views

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 10.24.4.0/23 [0/0] via Vlan2404, directly connected B E 10.27.4.0/27 [20/0] Null0 B E 10.224.4.0/23 [20/0] Null0 #show ip bgp 10.27.4.0/27 vrf CORE BGP routing table information for VRF CORE Router identifier 10.24.5.251, local AS number 65024 BGP routing table entry for 10.27.4.0/27 Paths: 2 available 65002 65000 65001 2.2.2.1 from 1.1.1.101 (192.168.2.0), imported EVPN route, RD 1.1.1.101:50002...
Continue reading →

EVPN border leaf configured as PE in MPLS network

Posted on July 16, 2020 by   |   0 Views

Hello, I am testing EVPN and MPLS VPN feature of vEOS(4.24.1.1F) in EVE-NG. I created two networks, one is EVPN, the other one is MPLS VPN network. I would like to know if the border leaf in EVPN network could be configured as PE router in MPLS network. Basically I would like to combine border leaf and PE router as one node. I did not see any documentation describe if this is supported?

BFD support in vEOS lab

Posted on July 15, 2020 by   |   0 Views

When I tried to run the following BFD interval command under global scope in vEOS, I got error: bfd interval 1200 min_rx 1200 multiplier 3 % Incomplete command Can you give me hint what the correct syntax is?   Thanks  

What is the meaning of this command?

Posted on July 15, 2020 by   |   0 Views

In EVPN configuration guide, I read the following command has been used: ip address virtual source-nat vrf A address 10.10.10.10 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

Posted on June 21, 2020 by   |   163 Views

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 

Posted on June 10, 2020 by   |   233 Views

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

Posted on June 3, 2020 by   |   0 Views

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

Posted on April 27, 2020 by   |   456 Views

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)

Posted on April 24, 2020 by   |   548 Views

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

Posted on April 23, 2020 by   |   164 Views

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 →

« Older posts
Follow

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

Join other followers: