• Tag : Port Channel


Mixed speed port channel

Description Starting with the 4.26.1F release, EOS supports active mixed speed members in a port-channel, allowing different speed ports to aggregate. Mixed speed port-channels can be enabled using a CLI configuration command. By default the feature is disabled. The mixed speed port-channel feature introduces the concept of ”weight” associated with a port-channel member. The weight of a member port is directly proportional to the other members’ speeds and it determines the ratio of packets sent over that member port if it becomes active. For same speed port-channels, all members have a weight of 1. The ”weight” value has been added...
Continue reading →

Port-channel Minimum Speed Review and Retry Mechanism

Description Starting from 4.26.10F release, for LACP and static port-channels, EOS will support minimum speed configuration, along with review timer and retry timer. Minimum speed is the total speed of all the interfaces configured in the port-channel which is needed to bring the port-channel link up. If both min-links and minimum speed are configured for a port-channel, minimum speed takes precedence over min-links. Min-links feature is only applicable on the port-channel with all member interfaces having the same speed. Minimum speed feature is applicable for both: port-channel with all member interfaces having same speed; port-channel with member interfaces having different/mixed...
Continue reading →

Port channel LACP to self issue

Hello All I have a question regarding the Port-channel (LACP), on Arista DCS-7050TX3-48C8-R with EOS: When I configure 2x different LACP port channels on same device, and connect them with Breakout Cable, the port-channel is not coming UP and give following logging info: Lag: %LACP-4-ACTOR_CHURN: LACP Actor Churn Detected on Ethernet But if it will be connected to other Switch it work just normal. Is it a Bug, or I need to change any configuration to support self connection with LACP? Thanks!

LACP on Arsta 7050S

Hello Together   I try to set up LACP From the 7050S to the ESXI hosts. Way is the LACP not working ? ESXI is set to Rout based on IP Hash. This is my settings: vlan 10 name temp_10 ! interface Port-Channel10 switchport access vlan 10 switchport mode trunk ! interface Ethernet1 switchport mode trunk   interface Ethernet17 switchport mode trunk channel-group 10 mode active ! interface Ethernet18 switchport mode trunk channel-group 10 mode active   Thanks in advance. Tim

Etherchannel detailed error

show etherchannel detailed =============== Exception raised in ‘Cli [interac -d -i –dlopen -p -f -l li bLoadDynamicLibs.so procmgr libProcMgrSetup.so –daemonize ‘ (PID 19146; PPID 19 142) =============== Local variables by frame (innermost frame last): File “/usr/lib/python2.7/site-packages/CliPlugin/LagCli.py”, line 1059, in doS howPortChannel activeMembers = [‘Ethernet17’, ‘PeerEthernet17’] allPorts = True brief = False cfg = channelGroupIdList = None channels = [‘Port-Channel2’, ‘Port-Channel3’, ‘Port-Channel4’, ‘ Port-Channel5’, ‘Port-Channel6’, ‘Port-Channel7’, ‘Port-Channel8’, ‘Port-Channel 9’, ‘Port-Channel10’, ‘Port-Channel11’, ‘Port-Channel12’, ‘Port-Channel13’, ‘Por t-Channel14’, ‘Port-Channel15’, ‘Port-Channel16’, ‘Port-Channel17’, ‘Port-Channe l18’, ‘Port-Channel19’, ‘Port-Channel20’] elic = elicd = <LazyMount._Proxy for entity(‘/ar/Sysdb/interface/con –More– Command: show etherchannel detailed =============== Exception raised in ‘Cli [interac -d...
Continue reading →

40G port-channel/LAG flatlining around 10 Gbps

We have two Arista 7504’s, each with a downstream-facing LAG into the same Cisco 7600-series router. Both were flat-lining around 10 Gbps, so thinking that perhaps it was the downstream router, we spread the traffic around by adding a fourth 10G to each LAG. Yet we’re flat-lining around the same value — adding that fourth LAG member made no perceptible difference. There are no deferred or output discards on the port-channel or individual ports, so my remaining thought is that there is some kind of rate-limiting going on in the Aristas that we can’t see. Is there anything that needs...
Continue reading →

Can I configure VARP on port-channel subinterface of two 7500E switch?

Such as SW1interface Po10.100 encapsulation dot1q vlan 100 no switchport ip add ip virtual-router address!ip virtual-router mac-address 00:1c:73:00:00:99 SW2interface Po10.100 encapsulation dot1q vlan 100 no switchport ip add ip virtual-router address!ip virtual-router mac-address 00:1c:73:00:00:99  

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 →

Configuring LACP Fallback in EOS

The LACP Fallback mode in Arista switches allows an active LACP interface to establish a port-channel (LAG) before it receives LACP PDUs from its peer. This feature is useful in environments where customers have Preboot Execution Environment (PXE) Servers connected with a LACP Port Channel to the switch.  Since PXE images are very small, many operating systems are unable to leverage LACP during the preboot process.  The server’s NICs do not have the capability to run LACP without the assistance of a fully functional OS; during the PXE process, they are unaware of the other NIC and don’t have a...
Continue reading →


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

Join other followers: