Tag :: TOI

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-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

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.

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.

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

DHCP Relay feature forwards DHCP packets between client and server when the DHCP Server is not in the same broadcast domain as the client. 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

DHCPv6 Prefix Delegation support enables a DHCP relay agent to program routes for addresses assigned by a DHCP server. The assigned prefixes could either be DHCPv6 IA_PD prefix delegation addresses, or DHCPv6 IA_NA global /128 addresses.

Directed broadcast is method of transfer to send a packet to recipients in a target subnet. This is done by sending a

DirectFlow runs alongside the existing layer 2/3 forwarding plane, enabling a network architecture that

The following new enhancements to DirectFlow and/or OpenFlow are added in EOS 4.15.0F:. DirectFlow

With the 19.0 release, network administrators can turn off 802.11b rates on SSIDs operating in the 2.4 GHz band. Turning off these legacy rates enhances overall network performance and prevents the association from outdated 802.11b clients.

IEEE802.1D 2004, Section 7.12.6 specifies destination MAC addresses that are normally trapped (not forwarded) by

The Switch detail page in the DMF GUI has a new Inventory tab displaying information about optics, cables, and transceivers.

This document describes the updates to the DANZ Monitoring Fabric (DMF) 8.7 release verified scale and performance numbers.

The hardware support update details newly supported hardware and other changes in the DANZ Monitoring Fabric (DMF) release 8.7.0.

Egress Filtering is an option to send different traffic to each tool attached to the policy's delivery setting. It provides additional filtering at the delivery ports based on the egress filtering rules specified at the interface.

As of DMF version 8.7.0, all DMF appliances will operate on the AlmaLinux 9.4 operating system, replacing the previous Ubuntu 20.04 LTS. This migration of the underlying operating system will not impact any currently supported features.

The DMF Recorder Node now supports deployment as a Virtual Machine (VM) for functional testing in Proof of Concept (POC) environments. Performance is limited and will vary based on allocated VM resources. DMF 8.7.0 and later Recorder Node images support being deployed as a VM.

This feature provides a method to rename a DMF object. DMF 8.7 Controllers support the Policy rename feature.

The DANZ Monitoring Fabric (DMF) allows the integration and monitoring of virtual machines in a VMware NSX fabric deployed in a vSphere environment. The DMF Controller communicates with NSX to retrieve its managed inventory and configures port mirroring sessions for selected virtual machines managed by the NSX fabric.

Currently data packets going over a DPS+IPsec tunnel have a fixed source IP, destination IP, protocol, source port and destination port after encapsulation for a given DPS path. Because of this, there is no good way to load-balance the tunneled traffic. However, to improve performance there is a need to load-balance the tunneled traffic. 

With this feature, user can fetch various internal hardware drops info from each switch and isolate the switch or

Precision Time Protocol (PTP) management messages are general PTP messages sent to PTP-enabled switches on the data plane. On Arista switches, its behavior depends on the configured PTP mode. In Boundary Clock mode, they are handled by the control plane. In Transparent Clock mode, they are forwarded in the data plane. PTP management messages can be sent through the PTP network either in a multicast or unicast fashion (by using ptp forward unicast, see Forwarding Unicast PTP Packets in Boundary Mode).

DCS 7280E. Arad QOS MAP:. This command assigns the DSCP rewrite value of 37 to traffic classes 2, 4, and 6.

Dual Tag VLAN mapping feature defines mapping between (outer VID and inner VID of double tagged packet) and bridging

Starting with EOS4.15.0F, dynamic and symmetric LAG hashing policies are supported on the 7500E platform. Dynamic

Dynamic Explicit Congestion Notification (D-ECN) configures an ECN marking threshold that changes dynamically based on a transmit queue’s available shared buffers. A D-ECN offset and D-ECN floor is configured per unicast transmit queue which defines how the ECN marking threshold will change as the queue’s shared buffer limit changes.

Until EOS release 4.32.0F, EOS allows users to statically configure link min-delay and max-delay used for IS-IS FlexAlgo. This feature adds support for dynamic measurement of link delay using the TWAMP Light protocol described in RFC 8186 and provides it to IS-IS FlexAlgo dynamically.

This document describes how to configure and monitor this feature.

Dynamic NAT connection limit is a feature that provides the functionality to limit the number of dynamic NAT connections.

Dynamic resizing of nexthop groups, as the name suggests, is a feature that enables a nexthop group to dynamically

This feature allows eAPI to run in multiple non default VRFs on the same physical router. In this way, users can

ECMP Hash visibility CLI determines the output interface for an ECMP set based on the flow parameters supplied by the user. Ingress interface, source IP address, destination IP address and IP protocol are the required parameters. L4 source and destination ports and VLAN identifier are optional, but should be specified if the packet has them.

This feature supports counting ECN-marked packets (ECN = Explicit Congestion Notification) on a per egress port per tx-queue basis. The feature can be used to gather these packet counts via CLI or SNMP. There are two cases when an ECN-marked (congestion) packet is counted on the egress port/queue:

This feature provides the capability to count the number of packets hitting rules associated to egress ACLs applied

This feature allows generating the syslog message for the packets matching rules in egress ACLs. This can be enabled using the log keyword when configuring an ACL rule. A copy of the packet matching such an ACL rule is sent to the control plane, where a syslog entry for the packet header is generated.

The feature allows to create a named TC to DSCP mapping that can be applied on an interface.DSCP of routed packets egressing out of the interface will be rewritten according to the map.

This feature enables users to configure MPLS EXP rewrite behavior on the egress interface based upon the global TC-to-EXP mapping. Starting from software version 4.33.2F, the CLI configuration to enable or disable EXP rewrite on the egress interface introduces a clear distinction in the behavior of MPLS EXP processing during POP and SWAP operations.

IPv4/IPv6 over MPLS packets are now eligible for ACLs at egress stage by default. The feature is applicable only to

Normally, an ingress router has no control over an autonomous system border router’s (ASBR) selection of inter-AS links. In the example below, Peer 2 and Peer 3 both advertise reachability to some remote network to ASBR 1 (e.g. service route 172.16.1.0/24). ASBR 1 would then use normal bestpath selection rules to select a preferred egress path (for traffic flowing to that service route). However, this means that the ingress router has no control over which egress path is chosen.