EOS 4.22.0F TOI

This feature increases the number of routes that can be forwarded using hardware on platforms based on ASIC that

This feature allows a user to configure Autonomous System Number (ASN) in Asdot notation and get the ASN in output of

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)

ASU, or Accelerated Software Upgrade, is a feature to minimize traffic loss when upgrading from one ASU supported EOS

A common way of configuring a switch is with config session or with config replace. In a config session, if the

ACL counters can be displayed on a per chip basis by passing an additional option in the ACL show command. The output of

This feature adds support for 10Gb, 25Gb, and 50Gb speeds on additional ports of the 7280QRA C36S and 7280QR C72:

When a switchport receives its own STP BPDU, the port goes into role ‘Backup’ and state ‘Discarding’. The

BFD (Bidirectional Forwarding Detection) authentication is used to validate the identity of BFD peers.

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.

This feature implements RFC3107 that allows carrying a label stack with BGP route updates, using multi protocol BGP.

This feature adds support for user-configured BGP Nexthop Resolution RIB profiles for various BGP-based services e.g. IP unicast, L3 VPN, EVPN, etc. The feature allows an administrator to customize the next hop resolution semantics of BGP routes with an ordered list, or profile, of resolution RIB domains (i.e., either tunnel or IP domain). This allows EOS to direct specific services over the specified RIB domains, overriding the default behavior.

The replace remote AS feature allows a provider edge (PE) router to change the autonomous system (AS) number used by a

The “set as path prepend” clause in route map configuration mode has been enhanced with the addition of

This feature extends the BGP Layer 3 VPN Import/Export and VRF Route Leaking functionality to “default” VRF.

Coherent systems connect data centers over distances of hundreds, even thousands of miles. In some cases, the fiber

This feature allows the user to reset the forward error correction (FEC) statistics counters shown in the output of

The feature allows a simulated transceiver removal, without physically touching the module. This can be used for

This feature can be divided into 3 parts. Enable support for different threshold per Color per TX queue  We

This article describes the support for IP ACLs on the egress ports for filtering Bridged IPv4 traffic. The users will

The base kernel for EOS was upgraded to use newer maintenance version 4.9.122 from version 4.9.108, bringing many

This feature extends the capabilities of event monitor to include IPv6 Route and IPv6 Neighbor event logging.

This feature provides a mechanism to export default VRF routes into EVPN and advertise them as EVPN type 5 IP Prefix

Ethernet VPN (EVPN) networks normally require some measure of redundancy to reduce or eliminate the impact of outages and maintenance. RFC7432 describes four types of route to be exchanged through EVPN, with a built-in multihoming mechanism for redundancy. Prior to EOS 4.22.0F, MLAG was available as a redundancy option for EVPN with VXLAN, but not multihoming. EVPN multihoming is a multi-vendor standards-based redundancy solution that does not require a dedicated peer link and allows for more flexible configurations than MLAG, supporting peering on a per interface level rather than a per device level. It also supports a mass withdrawal mechanism to minimize traffic loss when a link goes down.

Starting with EOS release 4.22.0F, the EVPN VXLAN L3 Gateway using EVPN IRB supports routing traffic from IPV6 host to

Fair Adaptive Dynamic thresholds (FADT) provides efficient allocation of shared packet buffer resources amongst various virtual output queues. FADT is useful when queues are getting congested and buffer resources should be allocated in a way tdat prioritizes certain queues while avoiding starvation of lower priority queues. the scheme works on each incoming packet by calculating instantaneous queue threshold based on available free resources. Queue buffer threshold is calculated as:

This feature introduces the hardware forwarding support for IPv4 over IPv4, GRE-Tunnel interfaces on Arista Switches. A GRE-Tunnel interface acts as a logical interface which performs the GRE encapsulation or decapsulation. IPv6 payload over IPv4 GRE-Tunnel interfaces is supported with limitations (see Limitation section).

This feature involves the use of packet’s Time to Live (TTL) (IPv4) or Hop Limit (IPv6) attributes to protect

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

This feature allows inter VRF route leaking locally from one VRF into another on the same device. Inter VRF routes can

In a typical switch deployment, multiple ports can have the same configuration, such as description and access VLAN.

The Interface Reflector feature allows performing certain actions (such as source/destination MAC address swap) on bridged packets that are reflected back from the interface. It is useful to test properties and SLAs before deploying the service for a customer.

IPv4 traffic can be encrypted and carried over IPSec tunnels originating or terminating on EOS dut. 

This feature makes a switch act as a neighbor discovery proxy for an IPv6 subnets. It can be used in conjunction with BUM

This configuration command features an IPv6 Neighbor Discovery (ND) option (called Boot File URL (BFURL) option)

This feature adds support for PIM SSM (Source Specific Multicast) for IPv6 Multicast Routing on platforms listed

This feature implements RFC6119, which allows the extension of IS IS protocol to carry IPv6 Traffic Engineering

This feature allows a user to configure multiple static adjacency SIDs for an IS IS adjacency. This feature is an

L2 protocol frames - LLDP, LACP and STP are trapped to the CPU by default. This feature allows for disabling the per protocol trap on a given set of interfaces. Starting from 4.32.1F, forwarding of MACsec EAPoL frames is also supported on a per interface basis on certain platforms. Starting from 4.35.0F, specific platforms support forwarding LLDP VXLAN encapsulated frames while continuing to trap regular/local LLDP frames to the CPU per interface.

This feature allows customers to run Label Distribution Protocol (LDP) on a subset of the interfaces that run Multi

The main motivation for the feature is to provide high availability to the ManagementActive interface (Management0) via multiple redundant paths in the modular system. The ManagementActive interface(Management0) is a virtual interface pointing to the active supervisor.

Enhancement of QOS class maps to match on nexthop groups along with dscp (dscp being optional) to set any QOS actions

The objective of Maintenance Mode on MLAG is to gracefully drain away the traffic (L2 and BGP) flowing through a switch

A new configuration model for the BFD (Bidirectional Forwarding Detection) agent was added in order to more

The "set metric" clause in a route map sequence has been enhanced with the addition of the "igp nexthop cost" keyword.

Normally, Multiprotocol Label Switching (MPLS) determines the packet forwarding destination based on the top most

IP traceroute and path MTU (PMTU) discovery both require that routers send ICMP reply messages to the host that invokes each network function. When the route to the destination host traverses an MPLS label-switched path (LSP), the label switching routers (LSRs) will also need to send ICMP reply messages to the originating host.

Add support for dynamic prefix list based matching in multi agent model. Please refer the TOI for rib

The PIM routing protocol builds multicast routing state based on control packets and multicast data events. In our

An introduction to Nexthop-groups can be seen in the Nexthop-Group section of EOS. With this feature, IP packets matching a static Nexthop-Group route can be encapsulated with a GRE tunnel and forwarded.