Tag :: EOS 4.22.1F

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 adds support for BGP peering over IPv6 link local addresses. This feature is available with the with the

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

This feature allows failover to the backup path to occur in constant time per interface going down for features such as RSVP link protection, RSVP node protection, TI-LFA link protection, and BGP PIC. Without this feature enabled, it would take time proportional to the number of paths going over the interface experiencing the link down event to failover to the backup path. With this feature enabled, the failover time would be constant regardless of the number of paths.

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.

Dynamic NAT connection limit is a feature that provides the functionality to limit the number of dynamic NAT connections.

As of 4.22.1F Load Balance Profiles can be used to explicitly configure ECMP Load Balance parameters. In addition,

This feature supports counting ECN-marked packets (ECN = Explicit Congestion Notification) on a per egress port per tx-queue basis. The feature can be used to gather these packet counts via CLI or SNMP. There are two cases when an ECN-marked (congestion) packet is counted on the egress port/queue:

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.

Forwarding destination prediction enables visibility into how a packet is forwarded through the switch, allowing you to determine which interfaces a packet would egress out of. Typical use cases include, but are not limited to, determining egress members for Port-Channels and ECMPs.

The General Router ID configuration provides the ability to configure a common Router ID for all routing protocols

Lanz Mirroring feature allows users to automatically mirror traffic queued as a result of congestion to either CPU or a different interface.

This feature allows classification of packets on QoS policy-maps based on the Class of Service (CoS), VLAN, Drop Eligible Indicator (DEI) in the 802.1q header of the packet. CoS (Class of Service) corresponds to the Priority code point (PCP) bits in the 802.1q header.

In campus network deployments, classification of the devices connected to a switch port is required. Based on the

SSH certificates (as implemented by OpenSSH, introduced in version 5.4) allow for easy management of user authentication and authorization for passwordless logins, as well as host verification.

EOS 4.22.1F release adds support for secure In band connection between CVX and Arista switches. Prior to this

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.

Add the ability to generate SYSLOG messages when a transceiver's digital optical monitoring threshold is crossed.