Tag :: Counters

ACL counters can be displayed on a per chip basis by passing an additional option in the ACL show command. The output of

Beginning with EOS version 4.36.0F, the CCS-710XP series offers the ability to increase ingress Access Control List (ACL) scale if counters are declared unnecessary. This will be the default behavior on CCS-710XP platforms running releases from 4.36.0F onwards. This document details steps to enable or disable counters as required, along with resources for related issues.

Tagging traffic with a drop precedence is a method that can be used to differentiate traffic flows over a given

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

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

Multiple dynamic counter features may be enabled simultaneously, primarily configured using the ‘[no] hardware counter feature [feature]’ CLI commands. Compatibility of these features has been enhanced to allow for greater flexibility in simultaneously enabled counter features. Changes in counter feature compatibility across EOS releases is detailed below.

The EOS Event Manager feature provides the ability to specify a condition and an action to be carried out when that

The EOS Event Manager feature provides the ability to specify a condition and an action to be carried out when that

Fast poll counters allow for rapid collection of a basic set of MAC counters on supported platforms at a very high frequency.

This feature adds support for the front panel Ethernet (Et) interface counters on the platforms listed below and enables the Et interfaces to dynamically adopt the counter values (packet and error) of interfaces (Switch, App interfaces etc.) related to the currently running FPGA application, based on user or default configuration. All Arista FPGA applications are supported. Both the receive and transmit packet counters can be independently configured for each interface, as desired. Counters are supported for interfaces of any speed including agile ports.

Prior to EOS 4.27.0F, MPLS tunnel egress counters could only be enabled for all MPLS tunnels present in the system

Hardware-based GRE tunnel interface counters are supported on the DCS-7050X4 platform family starting from EOS-4.36.1 release. When GRE tunnels are configured and traffic is hardware-forwarded, per-tunnel packet and byte counters are available for both ingress (decapsulation) and egress (encapsulation) directions. The hardware tunnel counters are disabled by default and must be explicitly enabled using the `hardware counter feature` CLI command. The ingress and egress counters can be enabled independently.

Hardware counter feature allows enabling counters for features using programmable hardware counter resources.

This feature adds support for separate unicast and multicast counters, per ingress interface and per traffic class. 

This feature provides support for per-interface ingress/egress packet/byte counters for both IPv4 and IPv6.

This feature provides support for packet and byte ingress counters for IPv6 multicast routes.

The nexthop group feature allows users to manually configure a set of tunnels. Nexthop group counters provide the ability to count packets and bytes associated with each tunnel nexthop, irrespective of the number of times it appears in one or more nexthop groups. In other words, if a nexthop group entry shares a tunnel resource with another entry, they will also share the same counter.

EOS now exposes ASIC integrated-circuit memory health metrics via gNMI, under the vendor-augmented OpenConfig component tree. Two categories of memory are reported per chip instance: DRAM Bulk Data Block (BDB) free counts and SRAM buffer free counts. Each category provides three views: current value, minimum observed since last reset, and minimum observed in the latest polling interval.

Priority-flow-control (PFC) buffer and history counters provide information on both present PFC pause conditions and past pause events. These buffer counters (since EOS-4.34.2F) and history counters (since EOS-4.35.0F) are available via OpenConfig in addition to the show commands that have existed in previous versions.

The per-CoS (Class of Service) discard counters allow the device to count discarded packets on the switch extender based on the packet COS. For ingress, there are three categories of traffic: regular traffic, control plane traffic, and flow-control traffic (used for end-to-end congestion control).

This document describes the PFC (priority-based flow control) history counters that are available to debug network oversubscription issues. These counters track statistics on the switch that is sending network traffic at a rate that is more than what its peer can handle.

This feature provides a continuous, live, stream of ingress counters for Policy-Based Routing (PBR) rules in terms of bytes and packets. It is implemented as a special call in EosSdkRpc and follows this definition:

The rate watermark counters feature allows for the capturing of microbursts within a configured interval based on the fast interface counters. The rate watermark counters feature is built on top of the high frequency fast poll counters which allows for increased visibility of microbursts that may happen within a short time window.

Priority-based flow control (PFC) buffer counters track ingress port buffer usage for each packet priority. This feature displays the high watermark buffer usage over two time intervals: a polling interval (by default 2 seconds) and the encompassing interval since the counters were cleared. The PFC buffer counter watermarks can be used to expose bursty and transient ingress buffer resource usage. High watermark values indicate congestion conditions that could explain packet loss.

This feature modifies the display format of “show interface Tunnel <num> counters” on hardware

This feature modifies the display format of “show interface Tunnel <num> counters”. 

When an interface is overloaded with packets and goes beyond its buffering capabilities, packet drops become

The IPv6 multicast route counters count packets and bytes per group, source and vrf . Every IPv6

The multicast route counters count packets and bytes per group, source and vrf. Every multicast route will be counted when the feature is turned on if there are sufficient hardware counter resources available. 

The feature allows the user to determine the rate of ingress packets on a class-map over a span of a specified interval. This specified interval is the global load-interval (default value is 5 minutes). 

The VLAN interface (SVI) counter feature allows the device to count packets received and sent by the device on a per SVI basis. By default, in a VXLAN routing scenario, packets are not counted on the "overlay" SVI. The platform CLI command described below allows for counting on the overlay SVI. When enabled, this feature still permits counting on underlay network SVIs

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

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

The MPLS LFIB counters feature was enhanced to add support for counting labels that correspond to VRF termination labels. The full details of the MPLS LFIB counters feature can be found in the original

WRED stands for Weighted Random Early Detection for congestion avoidance. A queue can differentiate certain

The VXLAN VNI counters feature allows the device to count VXLAN packets received and sent by the device on a per VNI basis. Specifically, it enables the device to count bytes and packets that are encapsulated and decapsulated as they are passing through.

The VXLAN VTEP and VNI counters feature allows the device to count VXLAN packets received and sent by the device on a per VTEP and per VNI basis. Specifically, it enables the device to count bytes and packets that are encapsulated and decapsulated as they are passing through.

The VxLAN VTEP counters feature allows the device to count VxLAN packets received and sent by the device on a per

The VxLAN VTEP counters feature allows the device to count VxLAN packets received and sent by the device on a per VTEP

The VxLAN VTEP counters feature allows the device to count VxLAN packets received and sent by the device on a per VTEP