• Tag : mlag

 
 

MLAG “Orphan Ports”

Hi, I wanted to know if MLAG has the same issue as Cisco’s VPC. Specially regarding “Orphan Ports”? If so how do the Arista switches deal with this?   Thank you, Victor

MLAG switches connecting Physical server without LACP

Hi, i have a setup with two 7050X in MLAG Domain. I have most of my Physical servers connected to the two Switches 10G interfaces with LACP and LAG and everything works great. However, i have a few specific servers that needs to be connected to the two switches( one server port to first switch and second server port to the second switch) but without LACP(the servers will be in a Hyper-v Cluster with software defined nic teaming). The question is, do i need to create a LAG without LACP in order to connect the server to the switches or...
Continue reading →

VXLAN bridging with MLAG

VXLAN bridging with MLAG Introduction This document describes the operation and configuration of VXLAN within an Multi-Chassis LAG (MLAG) deployment. The configuration and guidance within the document is based on the platforms and EOS release of table 1.0 Arista MLAG technologyTable 1.0 Arista’s Multi-Chassis LAG (MLAG) technology provides the ability to build a loop free active-active layer 2 topology. The technology operates by allowing two physical Arista switches to appear as a single logical switch (MLAG domain), third-party switches, servers or neighbouring Arista switches connect to the logical switch via a standard port-channel (static, passive or active) with the physical links...
Continue reading →

MLAG Priorities

Hi, How does the Arista switches decide which switch will be the primary switch of the MLAG domain? Also, is there anyway to change which one is primary and which one is secondary within the MLAG domain? Thank you

MLAG – basic configuration

MLAG overview LAG or link aggregation is a way of bonding multiple physical links into a combined logical link. MLAG or multi-chassis link aggregation extends this capability allowing a downstream switch or host to connect to two switches configured as an MLAG domain. This provides redundancy by giving the downstream switch or host two uplink paths as well as full bandwidth utilization since the MLAG domain appears to be a single switch to Spanning Tree (STP). Because the MLAG domain appears to STP as a single switch there are no blocked ports. Configuration The following will provide instructions on how...
Continue reading →

Active-active router redundancy using VARP

In most of Leaf-Spine deployments, redundancy in Spine layer is required to achieve high availability and to prevent network service disruption. Modern layer 2 networks adopted loop-free and balanced path networks using Multi Chassis Link Aggregation topologies with LACP port channels, leaving loop control methods (STP) as second protection layer. Spines also supports layer 3 networks, using ECMP in a scalable network topology. For unicast redundancy in layer 3, a common method is use First Hop Router Redundancy (FHRR) to provide a simple and unique gateway for Leaf level. VRRP and HRSP are popular FHRR protocols and supported in most...
Continue reading →

In the output of sh vlan brief command output what are ‘PEt’ interfaces

When I execute the command “sh vlan brief” in the output I see a few interfaces with “PEt” (see below). What exactly are these interfaces where are they coming from?   Core_Router# sh vlan brief VLAN  Name                             Status    Ports ----- -------------------------------- --------- ------------------------------- 1     default                          active 563   User_Segment1           active    Cpu, Et9, Et10, Et11, Et12 Et13, Et14, Et15, Et16, Et17 PEt9, PEt10, PEt11, PEt12 PEt13, PEt14, PEt15, PEt16 PEt17, Po100

Follow

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

Join other followers: