Tag :: TOI

This feature adds support for user-configured BGP Nexthop Resolution RIB profiles for various BGP-based services e.g. IP unicast, L3 VPN, EVPN, etc. The feature allows an administrator to customize the next hop resolution semantics of BGP routes with an ordered list, or profile, of resolution RIB domains (i.e., either tunnel or IP domain). This allows EOS to direct specific services over the specified RIB domains, overriding the default behavior.

BGP Non Stop Forwarding (NSF) aims to minimize the traffic loss when the the following scenarios occur:

Creating Traffic Policies that regulate control plane traffic from BGP peers by writing the list of BGP peer addresses statically in a field-set is error prone and difficult to update. Selecting only internal or external peers requires additional care. This feature automatically populates a field-set with IPv4 or IPv6 prefixes corresponding to iBGP or eBGP peers. This can be used instead of “protocol neighbors bgp” (see "Support for CPU traffic policy" ) where only a particular peer type is needed, or to replace complicated manual field-set updates.

Peer Tagging Route Filtering feature discards BGP route advertisements by the peers which the routes are received from. The feature lets users assign a peer-tag to a peer or a group of peers in inbound direction and discard routes advertisements by the peer-tag in outbound direction. One use case of the feature is to discard AS loop routes in outbound direction in data center deployments.

The sub route map configuration simplifies routing policies by sharing common policy across route maps. Common

BGP Prefix Independent Convergence (PIC Edge) refers to fast re-convergence of traffic destined for BGP prefixes on a network event affecting the best path(s) such that the time taken to switch traffic from the active best path(s) to the next best path (i.e. backup path) is independent of the number of prefixes. The above behavior is achieved by pre-programming the best path and alternate backup path in the forwarding agent in steady state. 

The BGP Prefix Independent Convergence (PIC) Edge feature refers to fast re-convergence of traffic destined for BGP prefixes on a network event affecting the best path(s) such that the time taken to switch traffic from the active best path(s) to the next best path (i.e. backup path) is independent of the number of prefixes. The above behavior is achieved by pre-programming the best path and alternate backup path in the forwarding agent in steady state.

The BGP Prefix Independent Convergence (PIC Edge) is an existing feature that was first introduced in EOS 4.15.0F.

RPKI provides a mechanism to validate the originating AS of an advertised prefix. Using the result of the validation to apply inbound policy in a route map.

Nexthop Groups is a feature that allows users to manually configure a set of nexthops by specifying their nexthop

Nexthop Groups allow users to manually configure a set of nexthops by specifying their nexthop addresses and

This feature adds support for a 'match route type' route map match clause in release 4.20.1F. This clause allows

The BGP selective route download feature allows learning and advertising BGP prefixes without installing them in

When a Provider Edge (PE) device loses BGP connectivity to the core (uplink) devices, it may be unable to forward any traffic from its downlink devices, typically CE (Customer Edge) devices. It is beneficial to indicate this connectivity loss to these CE devices so that they may find alternative paths to forward traffic.

BGP sFlow export is to add BGP route information including source and destination AS path information, local

BGP sFlow export is to add BGP route information in sFlow sample packet is the destination IP matches a BGP route. Prior

BGP triggered IP-in-GUE Encapsulation provides a mechanism for dynamically creating tunnels in a core network using an IP underlay.  IP-in-GUE (Generic UDP Encapsulation) encapsulates IP traffic in an IPv4/UDP header.  IP unicast routes to destinations reachable across the core network are learned via BGP at the ingress edge.

Unequal Cost Multi Path (UCMP) for BGP is a mechanism for forwarding traffic from a device for an ECMP route in the ratio

This feature adds support for BGP UCMP in the multi agent routing protocol model. The TOI for BGP UCMP in the ribd

This feature introduces support for BGP wildcard-AS route targets specifically for route import into VRFs.

Bidirectional Protocol Independent Multicast (PIM) allows routers to build trees to deliver multicast traffic from sources to receivers. It is a variant of sparse-mode PIM that efficiently addresses the use case where receivers for a multicast group are also sources for that group. While sparse-mode PIM builds shared trees and source-specific trees, bidirectional PIM only builds shared trees. A shared tree for a multicast group is rooted at the Rendezvous Point (RP) for that group. The RP for a bidirectional group is an IP address, which may or may not be real, but is reachable via all routers in the multicast domain. There may be multiple RPs in a multicast domain.

"Block Untagged Frames on Dot1Q Tunnel port" is a new feature that has been added in this release. When this feature is

With the 12.0 release, CV-CUE supports Bluetooth scanning to detect nearby Bluetooth devices.  

A device's classification as a phone or non-phone is determined by the switch through three mechanisms: advertisement via LLDP packets, explicit MAC address classification via CLI commands, or classification as a phone through the DeviceType VSA from a AAA server during authentication. This feature enables the port to be flapped (portflap) when the device's classification transitions from phone to non-phone or vice versa. This functionality applies to classification changes for both MBA and EAPOL supplicants. 

Bug Alerts is a service that runs on Arista CloudVisionTM eXchange (CVX) that provides customers with information on

The Campus Dashboard provides an overview of your network state. Devices stream telemetry data to CloudVision in real time, giving you immediate and up-to-date insights into your network’s health. The timepicker can be used to view historic data of the network state.

The Campus Fabric studio allows you to set up and configure a complete campus network using Arista’s validated designs. By leveraging zero touch provisioning (ZTP), you can seamlessly onboard EOS devices, define their roles and connections within the fabric, and configure L2 and L3 services across the fabric. 

Deployments utilizing VXLAN, a routing underlay (OSPF or eBGP), and a routing overlay (eBGP) are supported, and you can also define connections to non-EOS devices in the fabric. Additionally, PTP, 802.1X, IP locking, and other network features are supported by the studio.

The Campus Health Dashboard provides an overview of your network state. Devices stream telemetry data to CloudVision in real-time, giving you immediate and up-to-date insights into your network’s health. The timepicker can be used to view historic data of the network state.

Class Based Forwarding (CBF) is a means for steering IP traffic into specific tunnels based on either the ingress DSCP values or based on “classes”, which are derived from fields in the ingress packet headers and policies provisioned on the router. CBF may be used with SR-TE Policy or RSVP-TE colored tunnels. 4.35.1F adds support for CBF with flex-algo colored tunnels.

Arista’s CCS-710XP series of ethernet switches consist of CCS-710XP-12TH-2S SKU. CCS-710XP-12TH-2S is a 12 port 1000BASE-T PoE & 2-port SFP+ fanless switch device rich with networking features suited for campus deployments.

This document describes the configuration and behavior of physical interfaces on the CCS-710XP series switch

This is an addition to the SSL certificate and key management feature added in EOS 4.15.0F.

Connectivity Fault Management (CFM) is used in Virtual Bridged Local Area Networks for detecting, isolating, and

 With the 12.0 release, CloudVision Cognitive Unified Edge (CV-CUE) introduces Channel Maps. This chart displays the number of clients and access points (APs) visible to the managed device at a time on a given channel.

With the 12.0 release, you can view the criteria and parameters that influenced a channel change event. The data provides you insights on why the access point (AP) selected a particular channel over another.

With the DANZ Monitoring Fabric (DMF) 8.7 release, DMF Controller support for modular chassis switches has been improved by adding platform compatibility for DCS-7289-CH switches. DMF Controller and switch sync-up have also been improved to maintain state consistency.

With the 14.0 release, CV-CUE brings the ability to create checkpoints to save your current configurations, profiles, and settings. Creating and restoring a checkpoint is possible for all configuration settings available in CV-CUE. You can create a checkpoint for location based configurations, group configurations, or global configurations. For all the configurable settings that are available for a network, you can create a checkpoint to save it. 

With the 20.0 release, the checkpoint feature in CV-CUE also captures custom attributes created on the child or parent location. When you create a checkpoint for a location that has custom attributes, the custom value is also captured in the saved checkpoint.

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

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.