Tag :: TOI

This feature allows failover to the backup path to occur in constant time per interface going down for features such as RSVP link protection, RSVP node protection, TI-LFA link protection, and BGP PIC. Without this feature enabled, it would take time proportional to the number of paths going over the interface experiencing the link down event to failover to the backup path. With this feature enabled, the failover time would be constant regardless of the number of paths.

Class based forwarding (CBF) is a means for steering network traffic into colored tunnels based on one or more fields of the ingress traffic. Rephrased, CBF is forwarding of traffic based on “classes” which are derived from fields in the ingress packet headers and policies provisioned on the router.

Class Based Forwarding (CBF) provides a means for forwarding traffic through selected tunnels based on the traffic class of the incoming packet. Starting 4.32.2F CBF supports forwarding MPLS labeled traffic based on the EXP value in the incoming packet or the internal traffic class (TC) resolved from the parameters of the packet (e.g TC derived from EXP bits combined with port trust mode). Here, EXP bits refer to the Experimental bits in the MPLS header.

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”. Class Based Forwarding (CBF) for SR-TE is a means for steering IP traffic into an SR Policy based on the ingress DSCP values. This mechanism is described in the section on Per-Flow Steering in the Segment Routing Policy Architecture Internet draft.

Class Based Forwarding (CBF) is a means for steering IP traffic into colored tunnels based on the ingress DSCP values. CBF may be used with SR-TE Policy, RSVP-TE or Flex-Algo colored tunnels.

Class Based Forwarding (CBF) is a way of steering IP traffic into specific tunnels based on the ingress DSCP values. Arista already supports class based forwarding today, and the details about the existing support can be found in this CBF TOI. CBF is implemented in the hardware using an override model. As always, forwarding for an ingress IP packet begins with a lookup in the L3 FIB, which returns a default Forwarding Equivalence Class (FEC) to use. If CBF is enabled, an additional lookup is made in order to determine whether traffic associated with that default FEC and with the ingress packet’s DSCP should be steered into an SR Policy tunnel/RSVP-TE/Flex-Algo tunnel. In network deployments where unique (gateway) endpoints are large, the default FEC combinations generated by controller based on these endpoints can be a lot, and the existing approach with the override model using hardware’s TCAM resource doesn’t scale well, given that this resource is limited in nature. To overcome these scale issues, we have developed an alternative approach for CBF that is based on VRF Selection Policy.

Support of DSCP + ECN filter in ACL rules for QoS policy ma. Packet classification is supported on basis

The Clear Recorder Node (RN) Query History feature introduces CLI and GUI support on the DMF Controller for managing query records. Previously, deleting query history required direct interaction with the Floodlight (FL) API. This update allows for the removal of all query history entries through standard management interfaces. Note: The CLI and GUI support the deletion of the entire query history only; selective filtering of entries for deletion is not supported.

This feature provides the ability to track the reason why a BGP path is excluded from the BGP best path selection

In order to use the BST(Binary Search Tree) resources more efficiently for multicast, we are introducing a new CLI

This feature implements the ability to configure any tx serdes parameters via the CLI. This is useful to work around any L1 issues that customers may encounter due to suboptimal networks/links/transceivers.

With the 18.0 release, you can perform Client Connectivity Tests (CCT) in a network that has deployed proxy servers.  CCT lets you use the Access Point’s third radio as a client that can connect to another AP you want to test. This gives you the ability to proactively validate network connectivity, the reachability of network services, and the quality of experience for critical applications such as VoIP.  For more information on CCT,

With the 17.0 release, CloudVision Cognitive Unified Edge (CV-CUE) introduces a redesigned dashboard for viewing client details. The following image shows the new client details dashboard:  Along with client and network details, the client details dashboard also contains multiple data points regarding client connectivity, performance, and application experience. From a single dashboard, you can conduct live troubleshooting, and review past data to identify and troubleshoot past issues, thus resulting in a faster resolution.

With the 19.0 release, the Client Listing UI provides more insights into the Wi-Fi capabilities, security settings, and encryption methods each connected client uses. It now includes precise security reporting, distinguishing between configured and actual encryption methods used by devices in mixed-mode SSIDs.

With the 13.0 release, CloudVision Cognitive Unified Edge (CV-CUE) introduces the Client Explorer view. It helps you view the distribution of clients that are connected to Arista devices. 

The Related AP Events chart is a diagnostic chart that correlates a client's connectivity experience with the health of the Access Points (AP) they are connected to. Using this chart, network administrators can instantly see whether a client’s connection issue was caused by an infrastructure event, such as an Access Point reboot or a configuration change, or whether the problem was isolated to the client's device. By syncing these two perspectives, network administrators no longer need to manually cross-reference timestamps across multiple logs, making troubleshooting significantly faster and more efficient.

Cloud HA feature provides active active redundancy between two vEOS router instances running in Cloud such as AWS and

This document describes the supported IPFIX functionality on platforms that make use of the SFE forwarding agent.

Arista CloudEOS provides optimized routing and security functionality by connecting different enterprise branches, DCs and head office across different geographical regions, zones and sites. It uses traffic engineering to leverage the best paths across a bunch of Dynamic Path Selection( DPS ) tunnels which are used to carry the overlay data traffic. It uses the concept of AVT( Adaptive Virtual Topology) to map any given VRF traffic into a specific subsets of traffic each of which is treated uniformly for the routing/security perspective.

Network Address Translation (NAT) is a feature used to obfuscate private internal addresses to the external world. The feature makes sure that private internal addresses are translated into a publicly visible address which is used by all external hosts and it also does the reverse translation of the public address to the private internal address.

Network Hierarchy transforms the way you monitor and manage your campus network by providing an aggregated view of metrics and telemetry across distinct network layers. With just a few clicks, you can drill down through the aggregated state of the network to individual interfaces, providing you with both high-level and granular perspectives of the network, device, and interface states.

We’re excited to introduce end-to-end provisioning with Studios, a major step forward in simplifying and accelerating how you manage your network. With these enhancements, Studios now supports the full provisioning lifecycle—from initial onboarding to software management and ongoing configuration—through a single, streamlined workflow. This means less manual effort, faster deployment times, and easier collaboration when using CloudVision as your network’s management plane. The new capabilities also open the door to more advanced automation, helping teams reduce errors and scale operations more effectively. Whether you're replacing devices or enforcing software compliance, Studios now offers a more powerful and intuitive way to get it done.

We’ve moved feature toggles from the General Settings page and introduced a Features section with new functionality. You can now quickly filter features by name or status to easily customize your CloudVision environment and see which settings have been modified from their default state. 

Explore new and enhanced features shipping with CloudVision 2026.1.

CVA 7 is a full rebuild of the CloudVision Appliance (CVA)software on a new architecture. The new architecture provides a much richer set of management and security primitives. It is fully controllable by REST API, Web based GUI or CLI.

CVA 7 is a full rebuild of the CloudVision Appliance (CVA) software on a new architecture. The new architecture provides a much richer set of management and security primitives. It is fully controllable by REST API, Web based GUI or CLI, all of which expose all features.

Profiles are assigned to user accounts to customize their landing page on CloudVision and present information relevant to them. You can use built-in profiles or create custom ones. Profiles are assigned in Users to user accounts.

In a typical CloudVision-DMF integration deployment, CloudVision Portal (CVP) deploys alongside the DANZ Monitoring Fabric (DMF). The DMF Controller communicates with CVP to retrieve its managed device inventory and configures port mirroring sessions on any CVP-managed production devices that are Arista Extensible Operating System (EOS) switches.

Cluster Load Balancing is a feature designed to ensure optimal load balancing of flows used as part of GPU based cluster communication. When this feature is enabled, a TOR router monitors RoCE traffic flowing between the GPU servers and spine uplinks and ensures optimal load balancing in the network.

Cluster Load Balancing for Spine is a feature designed to ensure optimal load balancing of flows used as part of GPU based cluster communication in a network that uses multiple links to connect a TOR router to a Spine router.. When this feature is enabled on a Spine, it monitors RoCE traffic coming from a TOR and applies optimal load balancing when forwarding the traffic to the next TOR router hosting the destination GPU server.

Common Management Interface Specification (CMIS) defines, starting with revision 4.0, a standard mechanism for managing the firmware of compliant transceivers. This mechanism allows for transceivers’ firmware to be updated without having to remove the transceiver from the switch. Firmware updates may be necessary in a testing or production environment to resolve potential firmware bugs. Some transceivers may also support firmware management operations in a hitless manner (without impacting traffic).

Coherent signaling technology is used for data transmission over long distances. These transmitted signals are

The 7500R 8CFPX LC linecard with ACO CFP2 optics provides connectivity over DWDM systems and links. 7500R 8CFPX LC

Traditional policers treat all packets equally without considering the color of the incoming packet, potentially leading to transmission of excess packets that have already been marked with lower priority. Color aware flag in a policer configuration addresses this by providing the ability to consider the incoming packets’s drop precedence (DP) value while taking the policing decision on a given interface.

Command API's authentication can now be accomplished via X.509 public key certificates. Public key

Command API requests for "show" commands return structured outputs which are based on some internal models in EOS. In

CloudVision allows users to maintain multiple login sessions simultaneously. However, to prevent account sharing, administrators can now limit the number of active login sessions a user can have and terminate a user’s open sessions if that have reached their limit and are unable to log in.

Config checkpoint mechanism provides a shortcut to copy the current running config into a file stored in checkpoint

The Commit Timer mechanism provides a way to automatically rollback changes done by a config session, unless

In EOS 4.15.0F release, we have introduced the configuration sessions feature. Configuration sessions allow the

Under config router bgp mode, the following is the format for configuring remote port for a peer or peer grou

Currently when programming ECMP routes only one path is programmed in the kernel. There exists an environment variable (KERNELFIB_PROGRAM_ALL_ECMP) that allows users to program all paths from an ECMP route in the kernel. However, setting the variable requires restarting the KernelFib agent. This restart then reprograms all the routes.

An IPv6 link local address for an interface is generated automatically using the modified EUI 64 scheme. All IPv6

A DMF interface used by a DMF policy as both a filter and a delivery interface is known as a filter-and-delivery interface. Filter-and-delivery interfaces now support configuring sFlow in the DMF Controller.

On 7280R/R2, "Configurable TPID" enables a TPID to be configured per switchport (default TPID on switchport is 0x8100). A packet is considered tagged (both from ingress and egress point of view) on an interface if and only if TPID of the outermost VLAN tag on the packet matches the TPID configured on the interface.  Up to 3 distinct (non-default) TPID values may be recognized per chip.

Configurable TPID enables TPID to be configured per switchport (default TPID on switchport is 0x8100) on

Transmit queues are logical partitions of an Ethernet port’s egress bandwidth. Data streams are assigned to queues based on their traffic class, then sent as scheduled by port and transmit settings. Sand platform switches have eight queues, 0 through 7, and all queues are exposed through the CLI. However, queue 7 is not user-configurable. Queue 7 is always mapped to traffic class 7, which is reserved for control plane traffic. This feature allows tx-queue 7 to be configurable. As of 4.33.0F, a limited set of features are configurable on tx-queue 7.

Antenna gain measures an antenna's effectiveness in sending and receiving signals. It doesn’t amplify the total radio signal strength but redistributes the signal in the desired direction to maximize signal coverage, reduce interference, and enhance network performance.

CV-CUE utilizes several external cloud-hosted services to enable key features, including AFC, Ekahau integration, Webhooks, and Arista Firmware Repositories. In a standard on-premises deployment, CV-CUE often resides within a restricted network with no direct access to the Internet. To use and leverage the cloud-dependent features while maintaining security policies, CV-CUE supports the proxy server configuration. This service allows CV-CUE to communicate with specific external services via a customer-managed proxy server

MACsec operates as a global fabric configuration, encrypting traffic between core switches while excluding ancillary traffic, such as tap-to-filter or tool delivery. This feature introduces configurable MACsec path requirements, enabling the formation of multi-DC fabrics where inter-DC communication utilizes encrypted MACsec links while intra-DC traffic remains unencrypted.