EOS 4.24.1F TOI

As of EOS 4.22.0F, EVPN all active multihoming is supported as a standardized redundancy solution.  Redundancy

802.1X is an IEEE standard protocol that prevents unauthorized devices from gaining access to the network.

Accumulated IGP Metric (AIGP) is an optional non-transitive BGP attribute used to carry an IGP metric with BGP route advertisements. The AIGP attribute is useful for tie-breaking in BGP bestpath selection so that routing decisions can be made on the basis of shortest path/lowest IGP cost path amongst multiple BGP paths. This is particularly applicable in scenarios where a single administration is subdivided into multiple Autonomous Systems (AS) each with similar routing policies and the same IGP in use such that the IGP metric for a route can be propagated usefully between the ASes so as to let receiving BGP speakers make routing decisions based on the cumulative IGP cost of the route. This set of ASes in a common administrative domain in the context of advertising and receiving the AIGP attribute are referred to as an AIGP administrative domain.

The “set as path prepend” and “set as path match all replacement” route map configuration

It is often useful to know on a per AFI/SAFI basis, the number of paths that have been selected from a peer as best paths.

EOS 4.21.3F introduces support for BGP Flowspec, as defined in RFC5575 and RFC7674. The typical use case is to filter or redirect DDoS traffic on edge routers.

The goal of IAR operation is to minimize the CPU processing and churn in hardware by identifying a set of nexthop adjacencies such that updating those adjacencies in-place is sufficient to correctly forward the traffic quickly for all the affected routes.

Neighbor default originate feature is used to advertise a default route to the neighbor (peer or peer group) even when

BGP Non Stop Forwarding (NSF) aims to minimize the traffic loss when the the following scenarios occur:

RPKI provides a mechanism to validate the originating AS of an advertised prefix. Using the result of the validation to apply inbound policy in a route map.

This feature adds support for BGP UCMP in the multi agent routing protocol model. The TOI for BGP UCMP in the ribd

Segment Routing Traffic Engineering Policy (SR TE) aka SR Policy makes use of Segment Routing (SR) to allow a headend

On most PHYs, we run a sequence of steps in order to bring the links up reliably, because of it’s conservative

EOS 4.24.1 introduces Linecard management changes in the DCS 7368X4 series. In this release, the DCS 7368 is

Support for DHCPv4 (RFC 2131)  and DHCPv6 Server (RFC 8415) was added to EOS-4.22.1 and EOS-4.23.0 respectively. EOS DHCP server leverages ISC Kea as backend. The router with DHCP Server enabled acts as a server that allocates and delivers network addresses with desired configuration parameters to its hosts.

This article describes the support for specifying DSCP mask in IPv4 and IPv6 access lists. DSCP mask can be used to

Egress Sflow sampling feature allows to sample unicast packets based on the egress interface. The

Fast poll counters allow for rapid collection of a basic set of MAC counters on supported platforms at a very high

Starting from EOS 4.24.0F and EOS 4.24.0FX, RADIUS Attribute 8 (Framed IP Address) is included in Accounting Start,

This feature adds support for offloading BFD Transmit path to hardware (ASIC) for specific types of BFD sessions. This will improve accuracy of transmit timer implementations for BFD (especially with fast timers like 50 ms) and relieve pressure on the main CPU in scenarios of scale.

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.

Hardware counter feature allows enabling counters for features using programmable hardware counter resources.

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.

CALEA is the Communications Assistance for Law Enforcement Act which was passed into United States law

This feature implements RFC 3478. It allows devices to preserve the MPLS LDP LFIB entries in the forwarding plane if

On a MLAG chassis, MAC addresses learned on individual peers are synced and appropriate interfaces are mapped to these MAC addresses. In case of unexpected events like reloading of one of the peers in the MLAG chassis or flapping of one or more MLAG interfaces, some loss of traffic may be observed.

EOS version 4.24.1F introduces support for specifying multiple vias to form ECMP in MPLS static tunnels. A new

Multiprotocol Label Switching (MPLS) is a networking process that replaces complete network addresses with short

EOS supports reading and streaming various OpenConfig configuration and state models over gNMI (gRPC Network Management Interface), RESTCONF, and NETCONF transports. A subset of the configuration models may also be modified over these transports

Current EOS PIM sparse mode implementation installs an (S, G) route in the hardware whenever it receives an (S, G) join

This feature introduces the support for OSPF routes over GRE tunnels under default as well as non-default VRFs. The feature is disabled by default. 

VRF Route leaking can be used when routes from one VRF are required in another VRF (e.g. in case of shared services). If VrfLeak Agent is being used to leak routes, the leaked routes (in destination VRF) can be redistributed into IGPs.

Bidirectional Forwarding Detection (BFD) is a protocol that provides low-overhead, short-duration detection of failures of arbitrary paths between two systems.

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.

Segment Routing Traffic Engineering Policy (SR TE) aka SR Policy makes use of Segment Routing (SR) to allow a headend

This feature introduces a metric for static routes so that the user can configure both administrative distance and

Due to hardware constraints on specific platforms, Ethernet interfaces are grouped together, within which their

The IPv6 multicast route counters count packets and bytes per group, source and vrf . Every IPv6

GRE ( Generic Routing Encapsulation ) packet header has a Key extension which is used by Arista to carry packet metadata. Currently packets mirrored at egress to a GRE tunnel destination do not have this information. This feature could be used to enable metadata in egress mirrored packets to GRE destinations.

The CLI command “show rib route ip[ipv6]” and its sub commands (e.g. “show rib route ip

Static NAT rules may optionally include an access list to filter the packets to be translated.

EOS provides a way to extend its capabilities through the installation of extensions. An extension is a pre packaged

Topology Independent Fast Reroute, or TI-LFA, uses IS-IS SR to build loop-free alternate paths along the post-convergence path. These loop-free alternates provide fast convergence.

Some users need to configure the source MAC on routed ports, in some cases.To achieve this,a new CLI configuration

TAP Aggregation support for the DCS 7280R3 and DCS 7500R3 series is documented below, including the release in which a

In TAP Aggregation mode, configuration options are provided to handle special packet types. When receiving a packet whose Frame Check Sequence (FCS) is corrupted, the default behavior is to replace the bad FCS with the correct value and forward it. Configuration options are available to control the FCS behavior, such as to discard errors, pass through the bad FCS, or append a new FCS.

BGP routing information often contains more than one path to the same destination network. The BGP best-path selection algorithm determines which of these paths should be considered as the best path to that network.

TCB provides a mechanism to capture information around a MMU(Memory management unit) drop event.

Two rate three color marker (TrTCM) meters an incoming packet stream and marks the packets based on two rates, PIR

This article describes a set of CLI commands to create TCAM profiles. The profile is composed of a set of TCAM features, with each feature having customized lookup key, actions and packet types to hit.