Tag :: LAG

This document describes BFD RFC7130 mode on EOS. RFC7130 defines a mechanism to run BFD protocol over port channels with an independent asynchronous BFD session on every port channel member link. With RFC7130 support, the port channel member link will be removed from forwarding if the BFD session state transitions from UP to DOWN on the member link. This is useful for quickly detecting failures where L1 stays connected but the interface is unable to forward traffic.

In older EOS releases the ingress interface was always included in LAG hash calculations input together with other

Users can now define a global LAG hashing profile. The global LAG hashing profile will be applied to all linecards

Introduced in EOS-4.20.1F, “selectable hashing fields” feature controls whether a certain header’s field is used in the hash calculation for LAG and ECMP.

This feature supports Link Aggregation Group (LAG) use in the tunnel endpoint configuration.

Previously, the maximum valid port channel ID was equal to the maximum number of port channels configurable on the

When some LAG member links go down, it may be preferable to isolate the filter switch by bringing down the entire LAG interface rather than delivering unreliable data to tools and devices. Two new commands are now part of the DANZ Monitoring Fabric (DMF) lag-interface configuration to aid in managing the LAG interface when a specified number of links go down.

On supported devices, a port-channel can be configured as a mirroring destination for both ingress and egress source directions. Traffic mirrored to a port-channel is load-balanced based on the global port-channel load-balance configuration, which is the same for other port-channels.

A Link Aggregation Group (LAG) is used to aggregate/gather together multiple physical links into a single logical

Starting from 4.26.10F release, for LACP and static port channels, EOS will support minimum speed configuration,