EOS 4.26.0F TOI

This TOI details the following feature additions:. Support of 4x100G mode for the 400GBASE ZR transceivers

The L2 EVPN MPLS feature is available when configuring BGP in the multi-agent routing protocol model. Ethernet VPN (EVPN) is an extension of the BGP protocol introducing a new address family: L2VPN (address family number 25) / EVPN (subsequent address family number 70). It is used to exchange overlay MAC and IP address reachability information between BGP peers.

802.1X is an IEEE standard protocol that prevents unauthorized devices from gaining access to the network. We support dot1x protocol standard 802.1X-2004 (version=2)

This feature supports to upgrade Aboot firmware via an Aboot Update File (AUF). The aim is to be able to provide a signed

The following table describes the advanced mirroring features that are currently supported with links to their respective TOIs.

This feature allows for the configuration of the VRF that the BfRuntime server is configured to listen on.

BGP Add Path TX, or send, allows for a BGP speaker to advertise multiple paths (instead of a single best path) for a

The default policy behavior is to permit/accept all routes when a BGP neighbor or peer group is configured with a route

This feature provides the ability to configure the MTU value of fwd devices in a specific vrf or across vrfs. A default

QSFP+ transceiver supports 40G and 4x10G. This feature provides support for changing the default QSFP mode between

This feature detects duplicate IP addresses configured on the switch already owned by hosts the switch has already learned. When the duplicate IP address is detected, a syslog message will be generated. It can help the network operator to identify IP address misconfiguration.

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

This feature allows a Data Center (DC) operator to incrementally migrate their VXLAN network from IPv4 to IPv6

ALPM (Algorithmic Longest Prefix Management) is a scheme in which the route prefix is split and stored across DEFIP

The document captures the default preference value (between and 255) for routes from various supported protocols.

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.

Multihoming in EVPN allows a single customer edge (CE) to connect to multiple provider edges (PE or tunnel endpoint). The default mode of operation is all-active, in which the CE connects using link aggregation and can send traffic to either PE by hashing (or any other means) and expect the traffic to be successfully delivered.

EOS supports the ability to match on a single VLAN tag (example: encapsulation dot1q vlan 10)  or a VLAN tag pair (example: encapsulation dot1q vlan 10 inner 20) to map matching packets to an interface. In this case, the encapsulation string is considered consumed by the mapped interface before forwarding, which means that the tags are effectively removed from the incoming packet for the purposes of any downstream forwarding.

Disabling the flooding of broadcast, multicast, and unknown unicast traffic into the VXLAN fabric can significantly reduce bandwidth consumption in the VXLAN underlay. This is particularly beneficial in use cases where such traffic is unnecessary. This feature, exclusively supported with EVPN, allows for the selective flooding of ARP and/or ND traffic, offering further control over bandwidth usage.

EOS-4.24.0 adds support for hardware-accelerated sFlow on R3 systems. Without hardware acceleration, all sFlow processing is done in software, which means performance is heavily dependent on the capabilities of the host CPU. Aggressive sampling rates also decrease the amount of processing time available for other EOS applications.

IGP shortcuts enable traffic to get forwarded along traffic engineered paths computed by RSVP using a modified SPF

The  Inband Network Telemetry eXport Data (INT XD) feature is used to gather flow, queue, drop telemetry

IPv4 routes of certain prefix lengths can be optimized for enhanced route scale. This document describes the enhancements done to IPv4 route scale in subsequent EOS releases.

The IS IS maximum LSP size feature provides the ability to configure the maximum LSP size that the IS IS protocol will

4.26.0F adds Latency ANalyZer (LANZ) support to the Arista 7170 series. LANZ monitors the egress queue usage through

This solution allows the delivery of customer BUM (Broadcast, Unknown unicast and Multicast) traffic in a VLAN using

If a network device uses deep packet inspection for load balancing, RFC6790 recommends deployments to use entropy label in LDP to improve load balancing in MPLS networks by providing sufficient entropy in the label stack itself.

The MPLS ping/traceroute utilities were extended in EOS version 4.26.0F to support connectivity checking of BGP

Media Access Control Security (MACsec) is an industry standard encryption mechanism that protects all traffic

Media Access Control Security (MACsec) is an industry standard encryption mechanism that protects all traffic

MLDv2 Snooping optimizes the transmission of multicast packets in Layer 2 by using Layer 3 information contained in

The TCP MSS clamping feature involves clamping the maximum segment size (MSS) in the TCP header of TCP SYN packets if it exceeds the configured MSS ceiling limit for the interface. Clamping MSS value helps in avoiding IP fragmentation in tunnel scenarios by ensuring that MSS is small enough to accommodate the extra overhead of GRE and tunnel outer IP headers. One of the most common use cases for this feature is connectivity towards Cloud providers via GRE which require asymmetric routing (for example DDoS protection).

A mDNS Gateway extends the link-local scope of mDNS messages to additional subnets to provide service discovery and domain name resolution over an extended link-local multicast domain. A mDNS gateway can also peer with additional mDNS gateways to extend the logical link-local multicast domain to include directly connected subnets on a mDNS gateway peer.

E-Tree is an L2 EVPN service (defined in RFC8317) in which each attachment circuit (AC) is assigned the role of Root or Leaf. 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).

This TOI describes a set of enhancements made to the existing Port Security: Protect Mode (PortSec-Protect) feature. Please see the existing TOI for this feature here:Port Security: Protect Mode

The postcard telemetry (GreenT - GRE Encapsulated Telemetry) feature is used to gather per flow telemetry information like path and per hop latency. For network monitoring and troubleshooting flow related issues, it is desirable to know the path, latency and congestion information for flows at different times.

Power over Ethernet (PoE) is a way of delivering power and data over the same Ethernet wires. There have been multiple

The`ptp forward-v1` command configures the switch to forward Precision Time Protocol version 1 packets as regular multicast traffic. By default, when PTP is enabled and PTPv1 packets are received on the PTP enabled interfaces, these packets are trapped by the CPU, logged and discarded. The feature is already supported on various Arista platforms, this article highlights added support on the 7280R/7280R2/7020R/7500R/7500R2 platforms in EOS 4.26.0F and on the 7280R3/7500R3/7800R3/7289 platforms in EOS 4.29.0F. It highlights some differences in support for 7280/7500/7800 R/R2 platforms versus 7280/7500/7800 R3 platforms.

IS IS adjacency is not formed between devices with different address families configured. For example,  a router

This article describes the support for Filtered Mirroring using security ACL. The user can selectively mirror packets based on the statement in the configured IPv4, IPv6 or MAC ACL.

In EOS, BGP creates different update groups based on the outbound configuration. Different route maps or Routing

All electronic devices are subject to interference from cosmic radiation. Arista products use a combination of

When an interface is overloaded with packets and goes beyond its buffering capabilities, packet drops become

This feature adds support for streaming the output of the following show command in Octa:. The

RFC4191 describes an optional extension to Router Advertisement messages for communicating default router

This feature adds TLS support to the existing syslog logging mechanism. With the new added CLI commands, the user can

This article describes how to customize TCAM ( Ternary Content Addressable Memory ) lookup for each feature which uses TCAM. The lookup is composed of fields, in the packet header / forwarding chip pipeline decisions, that are of interest to a feature. Size of the lookup determines the number of banks to be used by a feature. Traditionally, any feature uses a predefined TCAM lookup.

This feature allows selecting Differentiated Services Code Point (DSCP) and Traffic Class (TC) values for packets at VTEPs along VXLAN encapsulation and decapsulation directions respectively. DSCP is a field in IP Header and TC is a tag associated with a packet within the switch, both influence the Quality of Service the packet receives. This feature can be enabled via configuration as explained later in this document.

This feature allows remote VTEP Tunnels to be routed over L3 SubInterfaces. DCS 7050SX3. Release.