Tag :: EOS 4.27.1F

Multiple dynamic counter features may be enabled simultaneously, primarily configured using the [no] hardware counter feature [feature] CLI commands. Compatibility of these features has been enhanced to allow for greater flexibility in simultaneously enabled counter features. Changes in counter feature compatibility across EOS releases is detailed below.

As Ethernet technologies made their way into the Metropolitan Area Networks (MAN) and the Wide Area Networks (WAN), from the conventional enterprise level usage, they are now widely being used by service providers to provide end-to-end connectivity to customers. Such service provider networks are typically spread across large geographical areas. Additionally, the service providers themselves may be relying on certain internet backbone providers, referred to as “operators”, to provide connectivity in case the geographical area to be covered is too huge. This mode of operation makes the task of Operations, Administration and Maintenance (OAM) of such networks to be far more challenging, and the ability of service providers to respond to such network faults swiftly directly impacts their competitiveness.

For MPLS forwarded traffic the tunnel destination needs to know the address-family of the payload IP/IPv6 packet to correctly parse the header. On some platforms this address-family is deduced from the address family of the Bottom of stack( BOS ) MPLS label seen by the router or by relying on the Ether Type in the Ethernet header.

This feature introduces the support for IPv4 ACL configuration under GRE and IPsec tunnel interfaces and IPv6 ACL configuration under GRE tunnel interfaces. The configured ACL rules are applied to a tunnel terminated GRE packet i.e. any IPv4/v6-over-GRE-over-IPv4 that is decapsulated by the GRE tunnel-interface on which the ACL is applied, or a packet terminated on IPsec tunnel i.e, IPv4-over-ESP-over-encrypted-IPv4 packet that is decapsulated and decrypted by the IPsec tunnel interface on which the ACL is applied.

IPSec tunnel mode support allows the customer to encrypt traffic transiting between two tunnel endpoints.

Arista's 7130 Connect Series of Layer 1+ switches are powerful network devices designed for ultra low latency and offer a wealth of integrated management features and functionalities.

MetaWatch is an FPGA-based feature available for Arista 7130 Series platforms. It provides precise timestamping of packets, aggregation and deep buffering for Ethernet links. Timestamp information and other metadata such as device and port identifiers are appended to the end of the packet as a trailer.

This feature adds support for CPU traffic policy capable of matching and acting on IP traffic which would otherwise

SwitchApp is an FPGA-based feature available on Arista’s 7130LB-Series and 7132LB-Series platforms. It performs ultra low latency Ethernet packet switching. Its packet switching feature set, port count, and port to port latency are a function of the selected SwitchApp profile. Detailed latency measurements are available in the userguide on the Arista Support site.

This feature introduces the possibility of creating Tap Aggregation PMF profiles consisting of 80 bit keys, to make a more efficient use of TCAM resources. Previously, we could only have key sizes of 160 or 320 bits. 

This article describes the TAP Aggregation 802.1Q (VLAN) tag stripping feature. This feature allows up to two of the outermost incoming 802.1Q tags to be stripped, and can be configured on a traffic steering policy or a tool port.

Identity tagging is an existing Tap Aggregation feature that allows a 802.1Q header to be added to packets sent by tool ports with a configurable identity value.

This document describes the truncation capability for Tap Aggregation, which allows tapped traffic to be truncated to a smaller size before being transmitted.