Tag :: 4.24.1F

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

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

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.

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

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

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

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

This priority drop feature provides a way to drop packets according to QOS priority when the device ingress maximum packet rate is oversubscribed.

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

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