Tag :: TOI

Arista Access Points (AP) support configuring the Maximum Transmission Unit (MTU) to send large packets without fragmentation. The default MTU is 1500 bytes.

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.

A new Connectivity Monitor panel allows users to easily view the health of device connections in Dashboards. The Connectivity Monitor panel displays EOS probes, categorizes connections as either Healthy or Unhealthy, and identifies the number of devices involved. By clicking on an Unhealthy connection, you can view the Connectivity Monitor events related to the connection.

This feature is an extension to the Explicit Congestion Notification (ECN) functionality for non ECN Capable

With the 12.0 release, CloudVision Cognitive Unified Edge (CV-CUE) introduces the capability to copy policies from one Wireless Manager server and reuse it in another server.

With the 16.0 release, network administrators do not have to define the VLANs received from the RADIUS server or CoA servers. The RADIUS server can dynamically generate VLANS for clients and send the VLAN to the access point (AP) when the client connects. This eliminates the need to manually configure all the dynamic VLANS in the SSID and Device settings. When Dynamic VLAN is enabled, network administrators do not have to configure the VLANs in SSID Settings; they are created dynamically on the AP.

This feature supports configuring more than one L3 delivery interface over the same subnet using the same gateway.

The feature adds cross-VRF support for dynamic prefix-list.

Dynamic prefix-list policy construct is similar to the traditional IP and IPv6 prefix-list, except that they have an additional state associated. This state associated with the dynamic prefix-lists, is determined on the basis of the route entries in FIB, and hence as and when the FIB changes, the state also changes dynamically. This state determines the dynamic prefix-list behavior, when used in route-map/RCF match clauses or route injection.

Until the DMF release 8.9, DMF users had no direct visibility into the current scale against the verified scale across the DMF fabric. This feature exposes the current scale against the verified scale via REST APIs, GUI, and CLI commands. The verified scale represents the capacity tested under reference conditions.

This feature allows the configuration of custom DSCP-to-DSCP maps on a per-Nexthop Group (NHG) basis. When applied it rewrites the DSCP of the outer IPv4 header of IPvX-in-IPv4 (X represents both v4 and v6) encapsulated packets using the inner IPvX header’s DSCP value while ensuring the DSCP of the inner IPvX overlay is preserved.

This feature allows the user to define a custom COS To Traffic-Class (TC) and Drop-Precedence (DP) map and apply it to an interface.

This feature allows the user to define a custom COS To Traffic-Class (TC) profile and apply it to an interface.

This feature allows the user to define a custom DSCP-To-TC map and apply it to an interface.

The feature allows to create a custom (i.e. named) TC, DP to DSCP mapping profile that can be applied on an interface.

This feature allows the user to define custom EXP To Traffic-Class (TC) maps that can be associated with individual interfaces to classify packets based on EXP bits (MPLS priority bits) of the outer MPLS header.

This feature allows defining custom TC-To-CoS mapping profiles that can be attached to the interfaces.

With the 15.0 release, access points can authenticate themselves to the network using respective certificates. With access point (AP) VPN, AP uses the EAP-TLS protocol for authentication. Since EAP-TLS requires the client and network to authenticate themselves using respective certificates, the protocol is considered robust compared to exchanging shared secret and Xauth password. 

With the 14.0 release, you can provide a custom name to your system backup file and also rename it. You can back up the entire system or only the configuration files, and restore them when needed.

This document describes how to prefix syslog messages with a custom string value. Previously, syslog messages were constrained to being prefixed with either the device’s hostname, IPv4 address or fully qualified domain name. This can be controlled with the command “logging format hostname ( fqdn | ipv4 )”. Support has now been added for prefixing the syslog messages with a custom comment. This provides users with greater freedom when deciding the format of their syslog messages including those which are sent to syslog servers.

Network Administrators can configure device settings at any location in CV-CUE, and the device configuration attributes get inherited from a parent to a child location. By default, inherited settings share the same attributes as the parent location. With this release, Administrators can override certain attributes of a device configuration at a child location without breaking inheritance, so that the entire device configuration remains unchanged except for the overridden attributes.

Network Administrators can create SSIDs at any location in CV-CUE, and the same SSID can be inherited from a parent to a child location. The inherited SSIDs, by default, share the same attributes as the parent location. With the 18.0 release, Administrators can override certain attributes of SSID at a child location without breaking the inheritance, so that the entire SSID configuration remains the same, except for the overridden attributes.

With the 20.0 release, you can create more custom attributes for SSID settings. This article lists all the enhancements made to this feature in the 20.0 release. To see the list of updates made in the previous release, see the 18.0 TOI.

This feature can be used to customize hardware reported transceiver DOM thresholds to uniformize part-to-part differences in various parameter thresholds.

CVX High Availability (HA) provides CVX Controller redundancy by having multiple CVX controllers running in a

This feature adds support for securing out of band connection between CVX server and CVX clients by SSL/TLS

This feature allows adding third party VTEPs to  a common L2 domain comprising of Arista and non Arista switches

S supports L3 EVPN gateway with Type 5 nexthop-self mechanism. While the nexthop-self mechanism is simple to operate, the L3 gateway lacks the support to rewrite the EVPN route distinguisher as well as the BGP route target. This feature supports an alternative L3 EVPN gateway mechanism using multi-domain L3 VRF instead. A multi-domain IP VRF allows configuring not only the local domain route distinguisher (RD) and route targets (RT), but also the remote domain route distinguisher and route targets on a DCI gateway.

This document describes the configuration and behavior of physical interfaces on the DCS-7060CX5 series switch including:

This document describes the configuration and behavior of physical interfaces on the DCS-7060X6-series switches including: Speed, Forward Error Correction (FEC), FEC histograms, Logical ports, Precoding, Transceiver Online Insertion and Removal (OIR).

Arista’s DCS-7130LBR series of switches are powerful network devices designed for ultra latency applications along with a wealth of networking features.

Arista’s DCS-7130LBR series of switches are powerful network devices designed for ultra low latency applications along with a wealth of networking features.

Arista’s DCS-7135LB series of switches are network devices designed for ultra low-latency applications along with a suite of networking features. It combines the following functionality on a single device

Arista’s DCS-7135V series of switches are network devices designed for ultra low-latency applications along with a suite of networking features.

ACL based QoS marking and policing is supported on DCS 7160 switches. Currently we support IPv4 ACL based QoS via

Stream Control Transmission Protocol (132) is a transport layer protocol, much like TCP. After the IP header, a

Delay based ECN on DCS 7280SE and DCS 7500E adds support for measuring the queueing delay that an IPv4 unicast routed

This feature introduces a configurable delay for flushing the MAC address when the network interface goes down, reducing unnecessary MAC address flushing during transient link failures. By default, when the link goes down MAC addresses associated with the link are flushed immediately. With this feature MAC address flushing is delayed by the configured time when the link goes down and if the link comes up before the configured timer elapses MAC addresses won’t be flushed from the forwarding table and the timer is cancelled. 

As Ethernet technologies made their way into the Metropolitan Area Networks ( MAN ) and the Wide Area Networks ( WAN ), from the conventional enterprise level usage, they are now widely being used by service providers to provide end-to-end connectivity to customers. Such service provider networks are typically spread across large geographical areas. Additionally, the service providers themselves may be relying on certain internet backbone providers, referred to as “operators”, to provide connectivity in case the geographical area to be covered is too huge.

CloudVision Portal release 2017.2.0 introduces support for the network wide Telemetry framework consisting of the

IPsec control packets are generally sent out of any of the egress interfaces based on the ECMP IP route that covers the remote IP address of the IPsec connection. This is not suited in some deployments. For example, when an IPsec end device is establishing connections with another device across more than one ISP (Internet Service Provider) and the control packets may get different NAT treatment based on which ISP they are going over.

This feature detects duplicate IP addresses configured on the switch already owned by hosts the switch has already learned. When the duplicate IP address is detected, a syslog message will be generated. It can help the network operator to identify IP address misconfiguration.

CV-CUE displays the missing VLANs in the network, allowing Network Administrators to diagnose and resolve the issue quickly. Sometimes out-of-the-box Access Points (APs) cannot send and receive traffic through the switchport they are connected to because the Switch doesn’t have the same VLAN as the AP. This issue could be time-consuming to diagnose and identify as Network Administrators follow a series of error elimination steps to determine the root cause. After the administrator identifies the root cause, the fix is trivial; they only need to create the missing VLANs in the Switch network.

CloudVision allows users to monitor a device’s environment by displaying graphs for temperature, power supply and fan speed. Power Supply shows the power used at each power socket on the device. Previously users could only view a visualization of output power. A visualization for input power is now available to view.

The above figure depicts a typical wireless network deployment. In the above deployment, the traffic from wireless networks are encapsulated into VXLAN tunnels by the AP (Access Point) VTEPs and terminated at the aggregation switches. When a host on the wireless network transmits a DHCP request broadcast packet, the AP encapsulates it in a VXLAN tunnel and sends it to the aggregation switch.

With the 12.0 release, you can configure DHCP fingerprinting to allow or deny clients getting connected to an SSID. Using DHCP fingerprinting, you can identify the operating system (OS) of the client based on the DHCP exchange packets between the client and the DHCP server. 

Dynamic Host Configuration Protocol (DHCP) is a feature which can be used to provide an IP address to the interfaces on

Arista Wi-Fi Access Points (AP) use DHCP Options 16 and 17 for IPv6 to discover and connect to a specific CV-CUE server on-premises or in the cloud. For a dual-stack DHCP server, IPv4 is preferred over IPv6.

The DHCP relay feature, forwards DHCP packets between a client and the DHCP server when the server is not in the same broadcast domain as the client. The DHCP relay should be configured on the gateway interface (SVI/ L3 interface) for the clients.

The EOS DHCP relay agent now supports forwarding of DHCP requests to DHCP servers located in a different VRF to the DHCP

Support for DHCPv4 (RFC 2131)  and DHCPv6 Server (RFC 8415) was added to EOS-4.22.1 and EOS-4.23.0 respectively. EOS DHCP server leverages ISC Kea as backend. The router with DHCP Server enabled acts as a server that allocates and delivers network addresses with desired configuration parameters to its hosts.