Tag :: TOI

This feature adds support for configuring an interface as a TX mirror source and a source for egress sFlow at the same time. For more information about mirroring and egress sFlow see the Resources section below.

This feature adds support for a selected set of configured interfaces to collect egress flow samples. Egress sFlow can be configured on Ethernet and Port-Channel interfaces, and on subinterfaces on select platforms. Hardware acceleration is not currently supported for egress sFlow and all sample processing is performed in software.

In Segment Routing, Adjacency Segment (Adj-SID) directs a node to forward the packet over a specific link or a set of links to the remote node. This feature adds support for statically configured SRv6 Adj-SIDs using micro-SIDs, also referred to as uA. This feature builds on the base SRv6 support described in SRv6 uN Support TOI.

This feature adds the support for tracking the number of syslog messages sent to the server and the number of syslog messages received on the server, along with other log forwarding action statistics, continuously within the existing syslog logging mechanism.

This feature terminates GTP packets arriving on a tap port of a TapAgg switch by stripping the GTP header. The decapsulated (inner) packets then proceed through the normal TapAgg path. This functionality allows a GTPv1 tunnel to transmit tapped traffic to the TapAgg switch over an L3 network, significantly extending the available use cases for TapAgg.

The S-BFD hold down timer feature enables delaying the steering of traffic to a previously preferred SR-TE Down path that came back Up. This delay period is configurable. Using this functionality allows time for the path to stabilize (by avoiding potential further path flaps) and allows the user to debug and diagnose the failure state.

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.

The Traffic Generator is an EOS feature that allows network traffic generation on Arista switches. It provides a simple and effective way to create high-speed traffic for testing and validation purposes. It can send a continuous stream of custom-defined packets at full speed to one or more destination interfaces

Access Control Lists (ACL) use packet classification to mark certain packets going through the packet processor pipeline and then take configured action against them. Rules are defined based on various fields of packets and usually TCAM is used to match packets to rules. For example, there can be a rule to match the packet source IP address against a list of IP addresses, and drop the packet if there is a match. This will be expressed in TCAM with multiple entries matching the list of IP addresses. The number of entries is reduced by masking off bits, if possible. TCAM is a limited resource, so with classifiers having a large number of rules and a big field list, TCAM runs out of resources.

This TOI supplements the Ingress Traffic Policy applied on ingress 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 egress direction on interfaces.

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. For Traffic Policies on the egress direction of VLAN interfaces, see the Egress Traffic Policy TOI.

This feature introduces the support for Traffic Policy on VLANs. Traffic Policy allows the user to configure rules to match on certain packets through the packet processing pipeline. The user can also place actions to match packets.

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.

 The "forwarding action trap" feature allows you to divert all incoming network traffic for an interface directly to the switch’s CPU for inspection and analysis. This feature is useful for advanced network testing, gaining deeper visibility into specific traffic flows, and potentially emulating existing network behaviors. Be aware that directing a high volume of network traffic to the CPU via this feature can overwhelm it.

This document describes the support for user-defined fields (UDF) ACL rules in egress mac/IPv4/IPv6 access lists. This feature is an extension of egress ACL to allow increased flexibility of the match criteria by using user-defined fields which will help customers control traffic based on other parts of the packet header and payload that is not supported by the other key-fields.

This supports checking that the value of a given x509 certificate OID matches a user-provided value during the TLS handshake in OpenConfig. If the value does not match, no connection will be established.

This document describes the availability of VLAN ingress and egress counters on R Series platforms. VLAN counters provide the ability to count packets and bytes ingressing or egressing a bridge domain (VLAN).

Overlay IPv6 routing over VXLAN tunnel using an anycast gateway (direct routing) has been previously supported using the “ipv6 virtual-router” configuration for both the data-plane and EVPN (or CVX) control-plane learning environments. 

Often, there is a need to accept IPFIX/NFv9 and NFv5 traffic arriving at ports other than the standard 4739 and 2055 ports, respectively. To address this need, DMF allows the following non-standard ports to forward traffic to their standard ports on the physical IP of the Analytics Node (AN) and the cluster's Virtual IP (VIP).

Often, there is a need to accept IPFIX/NFv9 and NFv5 traffic arriving at ports other than the standard 4739 and 2055 ports, respectively. To address this need, DMF allows the following non-standard ports to forward traffic to their standard ports on the physical IP of the Analytics Node (AN) and the cluster's Virtual IP (VIP).

This feature enables the support of applying a policy-map in egress direction on an SVI interface. A policy-map is a QoS feature in which we have multiple class-maps each with a match criteria and an action. These class-maps match on the given criteria and the configured action is applied on the traffic which matches. We can apply these policy-maps on interfaces in both input and output directions which match on ingress and egress traffic respectively. This feature adds the support of applying such output policy-map on an SVI( Switch Virtual Interface ).

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.

This feature allows the export of IP FIB (Forwarding Information Base) through the OpenConfig AFT YANG models.

This feature allows configuring a static IS-IS neighbor to have a full adjacency on an interface, without needing an IS-IS peer at the other end.. The adjacency state will depend on the BGP session with a single hop eBGP peer presen t on the same interface: when the BGP session is established, the IS-IS adjacency will be up; in any other state, it will be down. This allows advertising an interface's traffic engineering information—like bandwidth and admin groups—within IS-IS without needing an IS-IS neighbor adjacency on the remote end.

This feature enables the user to configure PBR policy on an interface in the default VRF to match and forward

This feature adds support for standard BGP GSHUT (0xFFFF0000) community. GSHUT community is the community used in

When configuring or modifying a RACL applied to a VLAN interface, the VLAN will be blocked while applying the updated

SWitch Aggregation Group (SWAG) is a feature in EOS that supports combining multiple physical switches into a single, powerful virtual switch, simplifying network management and increasing scalability. This document describes how to configure and troubleshoot a SWAG.

The Switch-less Service Node (SN) feature enables the direct installation of managed services on a service node, eliminating the requirement for an associated policy or connected switch. This capability supports deployments that are independent of the full Network Packet Broker (NPB) switching infrastructure. Existing workflows support the direct installation of managed services, such as filtering and deduplication, on the SN.

VXLAN tunneling requires that the switch where the tunnel terminates is configured with a VTEP that matches the configuration on the AP. CV-CUE now provides an easier way to match configurations on both AP and the switch. By having the same VXLAN configuration for access points (APs) and switches, you can aggregate all wireless traffic from the same VXLAN to a single wired destination for better traffic management and visibility.

SwitchApp is an FPGA-based feature available on compatible Arista 7130 devices. 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 user guide on the Arista Support site.

As a result of upgrading the Debian distribution to Bookworm, the original Python CLI (based on python2) was removed, as the interaction with the DANZ Monitoring Fabric (DMF) and CCF is performed mainly from the Controller. However, several customer operations involve some of the commands used on the switch. These commands are implemented in the new CLI (based on python3) in Switchlight in the Bookworm Debian distribution.

For modular systems operating under the SSO redundancy policy, if  the system database agent (Sysdb) on the

On platforms with multiple FAPs (e.g., chassis), hashing parameters (hash seed, polynomial, etc.) must be synced across all the FAPs when symmetric hashing is enabled to ensure hashing behavior is consistent for any given ingress port. The fix applies to all DMF Sand platforms running EOS.

With the 13.0 release, CloudVision Cognitive Unified Edge (CV-CUE) introduces system backup and restore capability. You can back up the entire system or only the configuration files, and restore them when needed.

Role based access control (RBAC) is an approach to regulating access to network resources based on the roles of

The tag matcher is a new simple input in Studios that allows you to specify a list of devices to be passed as the value for another input field. It is similar to the resolver input in that it allows users to specify a set of devices or interfaces using tag queries, but unlike the resolver, the tag matcher doesn’t require a member input to be configured.

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.

In TAP Aggregation mode, when receiving a packet whose Frame Check Sequence (FCS) is corrupted, the default behavior

This article describes the Tap Aggregation MPLS Pop feature. The purpose of this feature is to support tools that do not parse MPLS labels and therefore need the switch to remove (pop) the MPLS header.

The traffic steering policies used in tap aggregation mode allow steering traffic from tap to tool ports using ‘set

This article describes a new TAP Aggregation TCAM profile and a corresponding enhancement to the TAP Aggregation

This article describes the Tap Aggregation Traffic Steering on MPLS Labels feature. The purpose of this feature is to

This TOI briefs the commands related to the traffic steering policies used in Tap Aggregation. These commands

As of EOS 4.15.0F, there are two general enhancements to Tap Aggregation on the 7500E platform in 4.15.0F:

Extra MPLS Pop is an extension to TAP Aggregation that allows 4 to 6 MPLS labels to be removed from a packet, compared to the previous limit of 1 to 3 labels. Popping 4 to 6 MPLS labels works for all packet types where popping 1 to 3 MPLS labels is supported and,

As of 4.15.0F, tap aggregation can be configured in conjunction with other switching and routing features.  This

The Tap Aggregation Manager (TAM) is a GUI front end for configuring and monitoring Tap Aggregation features of

In TAP Aggregation mode, configuration options are provided to handle special packet types. When receiving a packet whose Frame Check Sequence (FCS) is corrupted, the default behavior is to replace the bad FCS with the correct value and forward it. Configuration options are available to control the FCS behavior, such as to discard errors, pass through the bad FCS, or append a new FCS.

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.