• Tag : troubleshooting


clear platform trident counters

Hi Forum we currently troubleshoot input discards. we found the rich command show platform trident counters for our platform.(DCS-7050SX3-48YC8-F) I’ve tried to reset counter to have a blank situation. I’ve used: clear platform trident counters this cause reset of all interfaces in LAG on this switch. January 23rd 2020, 10:22:02.000 MODULE_RESET 6 Informational Switch Linecard0/0 restarting. Cause: Strata-FixedSystem crashed January 23rd 2020, 10:22:02.000 UNEXPECTED_RESTART 3 Error Unexpected restart of Strata agent Strata-FixedSystem occurred after my mistake i’ve checked the documentation about this clear command, but i didn’t found any reference. does someone has knowledge what the clear platform trident counters...
Continue reading →

Configure Daemon Script to Collect Data

Summary The EOS daemon command is typically used to run TerminAttr (Streaming Telemetry Agent) on Arista switches. The daemon command can also be used to create custom daemon processes to do just about anything you wish. It can be useful in troubleshooting and collecting data over a period of time. In the example below, we create a bash script that runs 4 show commands and adds a timestamp to the log and repeats the process every 5 seconds. The output of the script commands are stored in an agents file located in /var/log/agents. Create Script File From the switch, drop...
Continue reading →

Arista 7280R Series 40G/100G systems Multi-Speed Port Configuration

Overview In high performance leaf and spine networks the Arista 7280R Series enables a high level of flexibility with a common consistent architecture, with a choice of 1RU and 2RU fixed systems, 10G to 100G interface speeds and port density up to 72 ports of 40G and 60 ports of 100G. The 7280R Series include the ability for enabling multiple speeds on QSFP ports, with a per interface configuration that is optimized for the maximum overall system flexibility. On some members of the 7280R Series to maximise the total system port count, and at the same time facilitate the most...
Continue reading →

Alias – Simple yet powerful

Alias – Simple yet powerful   About: Alias mySimpleAlias <a maybe complicated command you would never remember>     Alias commands can be composed of multiple lines and embed variables. Below is an example of alias used as configuration template for automating configuration with just few arguments. Sunch template can satisfy complex configurations and be highly reusable. This high-level scripting or command bundling is simple to implement yet powerful.     The below example is a multi-line alias with variables (%<x>)   alias set-baremetal !! Syntax : set-baremetal <INTF> <Po ID> <DESCR> <VLAN> !! Example: set-baremetal e1,2 po1 “To Server...
Continue reading →

Arista 7280QR-C36 Load Balancing Optimization for Dual Homed Systems and Networks

Arista 7280QR-C36  The Arista DCS-7280QR-C36 switch is a purpose built flexible fixed configuration 1RU system capable of supporting a wide range of interface choices. Its designed for the highest performance environments such as IP Storage, Content Delivery Networks, Data Center Interconnect and IP Peering. The 7280QR-C36 is optimized for environments with dual connected nodes such as storage and for spine applications with dual homed leaf switches. This technical application note describes the internal optimized load-balancing mechanism used within the switch and how network architects can best deploy this system to maximize overall system performance. The internal architecture of the DCS-7280QR-C36...
Continue reading →

Troubleshooting congestion – Investigating and taking corrective steps

  1) Introduction Congestion might not be obvious, it can be discovered reactively in disastrous situations, or proactively by collecting statistics off equipment and investigating symptoms demonstrated by the applications and systems.   Deep buffers on switches is a blanket and effortless solution to the problem, but it might not be materially possible or justifiable everywhere on a network. This document discusses design considerations in case of congestion.     2) Measuring The first step (which might seem obvious) for understanding some potential issues is to translate the symptoms such as slow, unresponsive, poor performance, into measurable and baselined metrics...
Continue reading →

Introduction to Managing EOS Devices – Memory Utilisation

A common question that users new to EOS have is concerning the high levels of memory utilisation seen on Arista switches (~70% utilised). Typically this is first flagged by the NMS and triggers a low memory warning or alarm. Unlike a traditional switching OS, EOS uses Linux page caching. Most free memory is used as a live cache and very low ‘free memory’  numbers are entirely normal, providing that enough memory is available from the buffers and cached memory for applications demanding more RAM. In this case, the OS is capable of freeing up memory from cache as processes demand it. Memory...
Continue reading →

Introduction to Managing EOS Devices

Summary   Several mechanisms exist to manage and instrument Arista Networks’ devices, ranging from industry standard SNMP counters to more Arista EOS/platform-centric functionality and deep debugging capabilities. The following articles introduce some fundamental management activities:   Setting up Management Monitoring Troubleshooting Platform Specific Monitoring and Troubleshooting Automation and Extensibility Annex A – Configuration Example Annex B – EOS Tips for Power Users   This document serves to highlight the basic parameters required to automate monitoring of an Arista EOS based device, while providing a high level overview of additional, more advanced functionality for low level troubleshooting and application specific monitoring. Many of the topics...
Continue reading →

Troubleshooting High CPU Utilization

Introduction   This article aims at helping you define what is CPU load on an Arista switch, how to know when it has a high load, and help troubleshoot high CPU utilization. We will cover different topics related to High CPU utilization: How do I identify if my switch has a high CPU? What is considered normal CPU % utilization? What is example of a High CPU utilization? How to identify average load on an Arista switch? What is the difference between CPU load average and CPU utilization How to interpret the load numbers? Can the load average be greater than...
Continue reading →

Using tcpdump for troubleshooting

tcpdump is a command line packet sniffer (built into Linux) that is used to assist in troubleshooting network problems. Any traffic coming to or from the control plane of the Arista is visible when running the tcpdump utility on the Arista.  This does not include data plane traffic transiting the Arista – for capturing this type of traffic, Arista Aristaes support Monitor / SPAN ports which can be used to copy traffic to a sniffer or to other suitable capture device for analysis. tcpdump allows users to instantly analyse important traffic such as Spanning Tree and routing protocols, as well...
Continue reading →

Debugging EOS agents

EOS’s architecture is built around the notion of agents. While the CLI show commands offer some great insights into the operational status of the switch, there is deeper level of detail that can be gathered from the agents by using a EOS debugging feature called agent tracing. Through this feature, which delivers live debug output to the CLI, EOS provides extensive troubleshooting information and enables users to debug complex control plane or protocol layer interactions. To configure agent tracing, first check the list of available agents. For example, in order to see the list of all agent starting with ‘A’, use: Arista#show trace...
Continue reading →

How to store and view previous contents of ‘show tech-support’

Introduction Starting with EOS 4.8.1, Arista introduced a unique feature called CLI Scheduler. Besides helping with troubleshooting and debugging Arista switches, this feature is used in order to automatically save the last 100 outputs of show tech-support (taken every hour). Please see an Arista EOS Manual for further details on the CLI Scheduler. Scheduling a show tech-support command The schedule command facilitates the periodic execution of a specified CLI command. Command parameters can be used in order to configure: the interval between consecutive executions of the command the maximum number of log files to be saved Starting with 4.8.1, by default, the...
Continue reading →


Get every new post on this blog delivered to your Inbox.

Join other followers: