- Written by Eddie Xie
- Posted on January 31, 2024
- Updated on July 15, 2024
- 1592 Views
This TOI supplements the Ingress Traffic Policy applied on ingress port interfaces. Please refer to that document for a description of Traffic Policies and field-sets. This TOI explains the Traffic Policies as applied in the ingress direction on VLAN interfaces.
- Written by Michael Wang
- Posted on July 2, 2024
- Updated on July 2, 2024
- 513 Views
This feature introduces the ability to define matching rules to configure transceiver tuning on a switch. This is useful when a particular collection of transceivers are known to require tuning values which differ from EOS defaults.
- Written by Rajesh Thakur
- Posted on June 28, 2024
- Updated on July 3, 2024
- 613 Views
This feature is only applicable to shaped port-channel subinterfaces. Traffic destined to a shaped port-channel subinterface would be load-balanced across all members of the port-channel. Shaping configured on the port-channel subinterface will be directly used across all the members of port-channel. Load-balancing criterion for flows destined to a shaped port-channel subinterface is the same as parent port-channel load-balancing criterion. Each shaped port-channel subinterface consumes as many SPPID (System physical port identifier) as the number of members added to the port-channel along with one extra port-channel resource (LAG ID) to combine all these SPPID. Anchor based approach is default behavior and we explicitly need to enable and reload the system for this feature to work.
- Written by Prasanna Parthasarathy
- Posted on December 23, 2021
- Updated on July 12, 2024
- 12300 Views
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.
- Written by Charlotte Fedderly
- Posted on June 20, 2022
- Updated on July 19, 2024
- 5330 Views
Synchronous Ethernet (SyncE) provides support for frequency synchronization over Ethernet between devices traceable to an external frequency reference, like a primary reference clock, as specified in ITU G.8261.
- Written by Stefan Kheraj
- Posted on July 2, 2024
- Updated on July 10, 2024
- 491 Views
Tap aggregation traffic steering allows users to redirect traffic flows received on TAP interfaces based on configurable policy-map rules. This feature enables the ability to define policy-map rules that filter on IP header fields on the following Ethernet-over-MPLS packet types.
- Written by Bidong Chen
- Posted on July 5, 2024
- Updated on July 5, 2024
- 495 Views
This feature comprises two parts:
To extend Traffic Steering to Nexthop Groups (GRE) by allowing us to specify one or more nexthop groups of type DzGRE (DANZ GRE) as the destination for a TAP aggregation steering policy. A DzGRE header will be encapsulated to the packets sending out a nexthop group of type DZGRE.
To extend GRE Tunnel Termination by allowing decapsulation of traffic received from nexthop groups of type DZGRE and adding VLAN tags based on DZGRE metadata.
- Written by Gowtham Rameshkumar
- Posted on September 15, 2023
- Updated on July 29, 2024
- 2762 Views
The Unified Forwarding Table (UFT) is memory that is shared between Layer2 and Layer3 lookup tables with capabilities for variable partitions. Rather than separate Layer2 and Layer3 lookup tables of fixed size, the UFT may be partitioned to support user-requested combinations of Layer2 and Layer3 lookup table sizes.
- Written by Pierre Desvallons
- Posted on May 30, 2024
- Updated on July 10, 2024
- 913 Views
User-defined recovery policy is a type of reset that allows the customer to rollback a device to a previously saved state. A state can be saved by taking a snapshot of the configuration files that the customer wants to save. Once a snapshot has been taken, the device can be reset either through push-button or through the command line interface. This feature provides a trivial way to get back to a tested and working version of EOS.swi with user-defined configs in case of failure.
- Written by Deepanshu Shukla
- Posted on January 31, 2024
- Updated on July 19, 2024
- 2261 Views
This article describes how to configure a TCAM ( Ternary Content Addressable Memory ) profile for ingress filtered mirroring sessions. This profile allows mirroring sessions to use less TCAM resources by individually selecting the allowable match criteria.
- Written by Anirudh Ramesh Iyer
- Posted on May 5, 2021
- Updated on July 19, 2024
- 15814 Views
This article describes how to customize TCAM ( Ternary Content Addressable Memory ) lookup for each feature which uses TCAM.
- Written by Travis Hammond
- Posted on July 29, 2024
- Updated on July 29, 2024
- 201 Views
Arista’s DCS-7130LBR series of switches are capable of supporting SwitchApp, which is an FPGA-based L2/L3 switch. However, as the switch would then contain two switch ASICs (one traditional switch ASIC, and one FPGA-based switch) physically upon loading the SwitchApp application, there are certain limitations and nuances along with its usage. This document intends to explain some of the details.
- Written by Isidor Kouvelas
- Posted on February 28, 2022
- Updated on July 29, 2024
- 13244 Views
Virtual Private LAN Service (VPLS) appears in (almost) all respects as an Ethernet type service to customers of a Service Provider (SP). A VPLS glues together several individual LANs across a packet switched network to appear and function as a single bridged LAN. This is accomplished by incorporating MAC address learning, flooding, and forwarding functions in the context of pseudowires that connect these individual LANs across the packet switched network. LDP signaling is used for the setup and teardown of the mesh of pseudowires that constitute a given VPLS instance.
- Written by Aurora Desmarais
- Posted on June 20, 2022
- Updated on July 9, 2024
- 6619 Views
This feature allows traffic ingressing a VLAN to be mirrored. It mirrors based on the VLAN tag in the Ethernet header, so it is not port based.