- Written by Tarun Jaswanth LNU
- Posted on 8月 24, 2020
- Updated on 7月 3, 2024
- 22535 Views
802.1X is an IEEE standard protocol that prevents unauthorized devices from gaining access to the network.
- Written by Subhash S
- Posted on 7月 2, 2024
- Updated on 7月 2, 2024
- 226 Views
This feature adds support for associating a WAN interface with multiple Dynamic Path Selection (DPS) path groups to allow paths originating from the same interface to have different priorities.
- Written by Manoj Agiwal
- Posted on 9月 30, 2015
- Updated on 7月 12, 2024
- 15658 Views
BGP Non Stop Forwarding (NSF) aims to minimize the traffic loss when the the following scenarios occur:
- Written by Jesper Skriver
- Posted on 4月 25, 2022
- Updated on 7月 10, 2024
- 6005 Views
Route reflectors are commonly used to distribute routes between BGP peers belonging to the same autonomous system. However, this can lead to non-optimal path selection. The reason for this is that the route reflector chooses the optimal route based on IGP cost from its perspective. This may not be optimal from the perspective of the client as its location may be different from the RR
- Written by Keon Vafai
- Posted on 6月 22, 2020
- Updated on 7月 12, 2024
- 11786 Views
This feature adds support for BGP UCMP in the multi agent routing protocol model. The TOI for BGP UCMP in the ribd
- Written by Adrian Fettes
- Posted on 7月 2, 2024
- Updated on 7月 12, 2024
- 106 Views
MPLS speculative parsing is the parsing of the headers following the MPLS header. Because there is no ethertype following the MPLS header, it can be difficult to discern the following header type(s). Some headers can be misparsed, so certain configurations are provided to allow customization of the parsing behaviour.
- Written by Vikas Hegde
- Posted on 11月 22, 2017
- Updated on 7月 9, 2024
- 14021 Views
Connectivity Monitor is an EOS feature that allows users to monitor their network resources from their Arista switches. The resources being monitored may or may not be Arista devices. Connectivity monitoring is unidirectional in nature.
- Written by Michael Wang
- Posted on 6月 28, 2024
- Updated on 6月 28, 2024
- 312 Views
This document describes the configuration and behavior of physical interfaces on the DCS-7280SR3A-series switches including: Speed, Forward Error Correction (FEC), Logical ports, Precoding, Transceiver Online Insertion and Removal (OIR).
- Written by Devon McAvoy
- Posted on 10月 4, 2019
- Updated on 7月 18, 2024
- 9211 Views
DirectFlow runs alongside the existing layer 2/3 forwarding plane, enabling a network architecture that incorporates new capabilities, such as TAP aggregation and custom traffic engineering, alongside traditional forwarding models. DirectFlow allows users to define flows that consist of match conditions and actions to perform that are a superset of the OpenFlow 1.0 specification. DirectFlow does not require a controller or any third party integration as flows can be installed via the CLI.
- Written by Yongguang Xu
- Posted on 2月 17, 2021
- Updated on 7月 10, 2024
- 5796 Views
The Dot1x Dropped Counters count the packets that get dropped for dot1x interfaces. The following
- Written by Rabi Narayan
- Posted on 6月 28, 2024
- Updated on 6月 28, 2024
- 301 Views
EOS allows users to statically configure link min-delay and max-delay used for IS-IS FlexAlgo until EOS release 4.32.0. This feature adds support for dynamic measurement of link delay using the TWAMP Light protocol described in RFC8186 and provides it to IS-IS FlexAlgo dynamically.
- Written by Vivek Ilangovan
- Posted on 7月 2, 2024
- Updated on 7月 3, 2024
- 212 Views
Segment Routing Traffic Engineering Policy (SR-TE) aka SR Policy makes use of Segment Routing (SR) to allow a headend to steer traffic along any path without maintaining per flow state in every node. A headend steers traffic into an SR Policy. SR-TE policies allow creating segment lists using segments along the shortest path or along a flex algo path. These policies can be traffic engineered to avoid the shortest or flex-algo paths.
- Written by Richard
- Posted on 6月 28, 2024
- Updated on 7月 3, 2024
- 276 Views
This feature introduces a new configurable attribute, weight, for vias through EosSdk and EosSdkRpc. The attribute is supported in both forward and nexthop_group type vias. A value of 0 indicates a via does not have a weight value and this is the default value for the attribute. Despite the attribute being type uint32, the maximum value it can support is 2^24 - 1
- Written by Wade Carpenter
- Posted on 4月 24, 2020
- Updated on 7月 15, 2024
- 13829 Views
EVPN MPLS VPWS (RFC 8214) provides the ability to forward customer traffic to / from a given attachment circuit (AC) without any MAC lookup / learning. The basic advantage of VPWS over an L2 EVPN is the reduced control plane signalling due to not exchanging MAC address information. In contrast to LDP pseudowires, EVPN MPLS VPWS uses BGP for signalling. Port based and VLAN based services are supported.
- Written by Pierre
- Posted on 6月 5, 2024
- Updated on 6月 27, 2024
- 332 Views
Factory reset will reset the device back to the EOS.swi image and configs that the device came with from the factory saved on a different partition. The device can be reset either through push-button or through the command line interface. Once the factory reset is requested, the device will reboot and will delete all files on the normal partition to be replaced with the swi image and config files that were saved in the recovery partition during manufacturing.
- Written by Edwin Tambi
- Posted on 8月 19, 2020
- Updated on 7月 3, 2024
- 17444 Views
EOS supports the ability to match on a single VLAN tag (example: encapsulation dot1q vlan 10) or a VLAN tag pair (example: encapsulation dot1q vlan 10 inner 20) to map matching packets to an interface. In this case, the encapsulation string is considered consumed by the mapped interface before forwarding, which means that the tags are effectively removed from the incoming packet for the purposes of any downstream forwarding.
- Written by Feng Zhu
- Posted on 5月 7, 2024
- Updated on 7月 18, 2024
- 932 Views
A forwarding equivalence class (FEC) entry is the data structure that holds all reachable vias where the packets should be sent to, for certain routes. Before this feature, a FEC could not contain both IPv4 next hop vias and IPv6 next hop vias. This feature starts supporting FECs that have both IPv4 next hop vias and IPv6 next hop vias. In an Equal Cost Multi-Path (ECMP) FEC, some of the vias may have IPv4 next hop and others may have IPv6 next hop.
- Written by Gowtham Rameshkumar
- Posted on 3月 11, 2020
- Updated on 7月 3, 2024
- 9641 Views
This feature introduces hardware forwarding support for IPv4-over-IPv4 GRE tunnel interfaces on selected Arista
- Written by Jonathan Ho
- Posted on 6月 28, 2024
- Updated on 7月 1, 2024
- 307 Views
The ip address virtual command is generally used to conserve IP addresses in VXLAN deployments and can be used to provide an Anycast gateway. On a VLAN, the same IP address can be configured using this command on multiple VTEPS or on both MLAG devices. Release 4.22.1F introduced [ip address virtual support for PIM and IGMP]. Using that solution, users are required to configure pim ipv4 local-interface on the VLAN interface. PIM and IGMP then borrow the IP address from the local interface specified. Using this configuration, IGMP skips subnet checks for received control messages.
- Written by Subham Burnwal
- Posted on 6月 28, 2024
- Updated on 6月 28, 2024
- 264 Views
EOS IS-IS implementation advertises interface-address TLVs for both passive and non-passive interfaces. IS-IS “advertise interface-address passive-only” feature is used to control the advertisement of interface address TLVs in LSP Advertisement. Once this feature is enabled on the device, IS-IS advertises interface address TLVs i,e. IP Interface Address TLV #132 and IPv6 Interface Address TLV #232 only for passive interfaces in the LSP Advertisement and stops advertising these TLVs for active or non-passive interfaces.
- Written by Zetang Lei
- Posted on 7月 2, 2024
- Updated on 7月 3, 2024
- 224 Views
This feature introduces a way for IS-IS to advertise its IP reachability and SID for loopback interfaces only when routes matching an RCF function are present. One example use-case is to use IS-IS Segment Routing to attract traffic to a router only when routes towards the ultimate destination are present.
- Written by Prakrati Vidyarthi
- Posted on 8月 16, 2018
- Updated on 7月 15, 2024
- 13072 Views
L2 protocol packets - 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.
- Written by Dawon Lee
- Posted on 8月 17, 2018
- Updated on 7月 5, 2024
- 7181 Views
Lanz Mirroring feature allows users to automatically mirror traffic queued as a result of congestion to either CPU or a different interface.
- Written by Tanuj Kumar Jhamb
- Posted on 7月 2, 2024
- Updated on 7月 3, 2024
- 213 Views
ECN (Explicit Congestion Notification) is a mechanism of notifying network congestion without dropping the packets.The ECN based network congestion notification can be done in two ways: queue-length based ECN, latency based ECN. The queue-length based ECN marks the ECT packets when the average VOQ length exceeds the configured ECN threshold value whereas latency based
- Written by John Li
- Posted on 2月 16, 2022
- Updated on 7月 18, 2024
- 6443 Views
This TOI describes the MAC limit per VLAN feature which can be used to limit the number of locally learned MAC addresses per VLAN.
- Written by Dawid Smalcuga
- Posted on 6月 28, 2024
- Updated on 6月 28, 2024
- 288 Views
This feature adds support for specifying Resolution Rib Profile as system-connected per-via (next-hop) for static routes. System-connected means that a static route is only resolved if the next-hop is reachable over a connected route. If system-connected is not specified, it means that the static route is resolved if the next-hop is reachable over any kind of route in the routing FIB, including a connected route as well as a tunnel rib.
- Written by Bhargav Jethwa
- Posted on 6月 27, 2024
- Updated on 6月 27, 2024
- 283 Views
In some situations, packets received by an ASIC need to be redirected to the control plane: packets that have the destination address of the router or packets that need special handling from the CPU for example. The control plane cannot handle as many packets as the ASIC. A system that protects the control plane against DOS and prioritizes packets to send to the CPU is needed. This is accomplished by CoPP (control-plane policing). CoPP is already functioning, however, the CPU queues are statically allocated to a specific feature. If a feature is not used, the CPU queue statically allocated to the feature is not used either. This is a loss of resources.
- Written by Haris S M
- Posted on 6月 28, 2024
- Updated on 6月 28, 2024
- 283 Views
Configuring OSPF as PE-CE protocol enables us to distinguish between the “real external routes” and intra network routes between the sites that are stretched across VPN. But the problem arises when VPN sites are in the same area and have a backdoor connection. With OSPFv3 as PE-CE protocol redistribution, CE routers end up getting inter-area routes (assuming the VRFs on the PE devices that connect the CE sites, are configured with the same OSPFv3 domain id) that actually belong to the same area and just happen to be multihomed to the backbone.
- Written by Paulo Panhoto
- Posted on 4月 18, 2024
- Updated on 7月 17, 2024
- 1176 Views
This feature provides a continuous, live, stream of ingress counters for Policy-Based Routing (PBR) rules in terms of bytes and packets. It is implemented as a special call in EosSdkRpc and follows this definition:
- Written by Padmanabh Ratnakar
- Posted on 4月 20, 2021
- Updated on 7月 15, 2024
- 12003 Views
The postcard telemetry (GreenT - GRE Encapsulated Telemetry) feature is used to gather per flow telemetry information like path and per hop latency. For network monitoring and troubleshooting flow related issues, it is desirable to know the path, latency and congestion information for flows at different times.
- Written by David Cronin
- Posted on 3月 3, 2022
- Updated on 7月 9, 2024
- 15462 Views
Routing control functions (RCF) is a language that can be used to express route filtering and attribute modification logic in a powerful and programmatic fashion.
- Written by David Cronin
- Posted on 3月 3, 2022
- Updated on 7月 3, 2024
- 10486 Views
Routing Control Functions (RCF) is a language that can express route filtering and attribute modification logic in a powerful and programmatic fashion.The document covers: Configurations of a RCF function for BGP points of application
- Written by Gokul Unnikrishnan
- Posted on 6月 27, 2024
- Updated on 6月 27, 2024
- 296 Views
The sFlow VPLS extension adds support for providing VPLS-related information to sFlow packet samples, for VPLS forwarded traffic. Specifically, for customer traffic ingressing on a CE-facing PE interface in a VPLS deployment that uses statically configured LDP pseudowires, information such as the name of the VPLS instance and the ID of the pseudowire that the packet will egress over will be included in the sFlow datagram.
- Written by Jared Dulmage
- Posted on 7月 5, 2024
- Updated on 7月 5, 2024
- 194 Views
Priority-based flow control (PFC) buffer counters track ingress port buffer usage for each packet priority. This feature displays the high watermark buffer usage over two time intervals: a polling interval (by default 2 seconds) and the encompassing interval since the counters were cleared. The PFC buffer counter watermarks can be used to expose bursty and transient ingress buffer resource usage. High watermark values indicate congestion conditions that could explain packet loss.
- Written by Bo Hu
- Posted on 6月 28, 2024
- Updated on 6月 28, 2024
- 335 Views
Split horizon groups (SHG) may be used to divide all subinterfaces and VPLS pseudowires in a VLAN to different bridging groups so that bridging is prevented between members of the same SHG. Bridging is allowed between members of different SHGs and subinterfaces which don’t belong to any SHG.
- Written by Octavian
- Posted on 6月 28, 2024
- Updated on 7月 3, 2024
- 296 Views
This feature adds support for Static Route UCMP local forwarding in the multi-agent routing protocol model. Unequal Cost Multi Path (UCMP) for Static Route is a mechanism for forwarding traffic from a device for an ECMP route in the ratio of the weights with which the next hops of that route are programmed in the FIB.
- Written by Sameer Pakalapati
- Posted on 7月 3, 2024
- Updated on 7月 3, 2024
- 197 Views
The Command-tag feature adds support for grouping multiple configuration units/commands across features using a single command-tag, which is essentially a string. This tag can then be used to enable/disable/remove/disassociate all the associated commands with the tag, using a single CLI command, instead of performing the operation individually for each configuration command.
- Written by Abhishek Gupta
- Posted on 7月 2, 2024
- Updated on 7月 2, 2024
- 208 Views
Fail-To-Wire feature enables monitoring for software failures. Fail-To-Wire is a hardware supported feature. Since some agents are considered critical for the system, following events are tracked:
- Written by Kailin Zhang
- Posted on 7月 2, 2024
- Updated on 7月 3, 2024
- 209 Views
The new feature maintains STP restartability while a portfast-enabled port’s link status changes. In older releases, when portfast is enabled on an interface and the interface is flapping, i.e., going up and down, STP becomes non-restartable. After the new feature is introduced, STP remains restartable during port flapping. This may be applicable in several scenarios, but the most common usage is to keep STP restartable after endpoints are connected and disconnected. This feature is important for SSU because an SSU can only be performed while STP is restartable. After the portfast port's link status changes, SSU can still be conducted.
- Written by Alok Kumar
- Posted on 11月 29, 2023
- Updated on 7月 15, 2024
- 2343 Views
This feature provides a cli command showing the list of mac addresses which could not be learned due to hash collision in the hardware table. A hash collision occurs when two or more distinct pieces of data map to the same entry ( or slot ) in the hardware table. It can happen when the hash function used to calculate the index for a given mac address results in the already occupied index, resulting in failure of inserting the later mac address to the hardware table.
- Written by Eddie Xie
- Posted on 1月 31, 2024
- Updated on 7月 15, 2024
- 1349 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 7月 2, 2024
- Updated on 7月 2, 2024
- 234 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 6月 28, 2024
- Updated on 7月 3, 2024
- 307 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 12月 23, 2021
- Updated on 7月 12, 2024
- 11606 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 6月 20, 2022
- Updated on 7月 18, 2024
- 5041 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 7月 2, 2024
- Updated on 7月 10, 2024
- 222 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 7月 5, 2024
- Updated on 7月 5, 2024
- 193 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 Pierre
- Posted on 5月 30, 2024
- Updated on 7月 10, 2024
- 474 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 1月 31, 2024
- Updated on 7月 18, 2024
- 1957 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 5月 5, 2021
- Updated on 7月 18, 2024
- 15262 Views
This article describes how to customize TCAM ( Ternary Content Addressable Memory ) lookup for each feature which uses TCAM.