Understanding EOS Software Download Options

This post is to help explain the different Software Download options for a particular EOS release. For recommendations on which train or version of EOS you should use, please take a look at our Software Lifecycle, and Recommended Release pages. This advice only concerns images located in the Active and Support Only Releases folder. Images from the Other Releases and EFT folders are not for general use. Those releases are available only for specific deployments, and should only be used when specifically recommended by Arista. In this case, I’m taking a look at EOS-4.17.1F and you can see from the...
Continue reading →

Deploying Virtual SAN Over L2/L3 Networks with Arista Networking Devices

This is a great posting from on how to deploy Virtual SANs over an Arista underlay networks with the actual switch configurations. Here is the video on how to automate the deployment of a VSAN infrastructure from the same blog – VMware Virtual SAN Stretched Cluster Automated Deployments with PowerCLI Thought our user community would benefit from these blog postings. Happy 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 →

Upgrade Questions for EOS

We are about to upgrade our Arista switches to address the newest vulnerabilities that came out recently, and I have a few questions I’m hoping you can help with. Some of our switches are on older hardware. Is there a table somewhere that lists the highest code level a particular platform can run? Will all newer code releases run on all older hardware? Some of our switches are running very old code. Does SSU work on very old code (say, 4.5)? Assuming not, what is the upgrade path to get these switches up to 4.14…? Do I have to upgrade...
Continue reading →

Script to update EOS in sw’s in a bulk

Hi We want to upgrade EOS in sw’s. We want to automate this process. We can use solarwinds to execute a script or a phython script to do it. If someone can provide with template for it so we can test it in a lab sw and use it in production.   Thanks Raj  

Installing Puppet on EOS

Getting started with Puppet and EOS isn’t a difficult process. It involves taking advantage of the extensible nature of EOS. There are two primary extensions that need to be loaded in EOS in order for an Arista network element to be included in the Puppet ecosystem. Installation Installation of the agent on a switch includes adding the Ruby Client for eAPI (rbeapi) and the Puppet agent extensions, basic management configuration, including hostname, domain, and time synchronization (for SSL certificate management), and enabling eAPI access to the switch. Additionally, the Puppet master needs the appropriate modules installed (NetDev_stdlib and EOS) so you...
Continue reading →

Arista’s EOS Innovation Enabling Ecosystem Partner Software Development

Network software automation and intelligence is a passion we share as network engineering software developers at Intelligent Visibility, Inc. Creating innovative software solutions in the rising world of software-defined networking (SDN) can prove challenging. The source data that we require for our software is mostly located within the network device’s operating system. In the past accessing this source data has been a serious time investment mainly due to inconsistent API implementation types across different operating systems for many different hardware platforms.

How to keep last X startup configs

If you would like to keep track of last 10 (or more, or less) configuration changes, here’s the event-handler code to do that: event-handler config-versioning    trigger on-startup-config action bash FN=/mnt/flash/startup-config; LFN="`ls -1 $FN.*-* | tail -n 1`"; if [ -z "$LFN" -o -n "`diff -I 'last modified' $FN $LFN`" ]; then cp $FN $FN.`date +%Y%m%d-%H%M%S`; ls -1r $FN.*-* | tail -n +11 | xargs -I % rm %; fi    delay 0 Description: Every time the startup config gets changed, this event handler will be executed (“trigger on-startup-config”). You could increase the delay, if you wish, but now it’s engaged immediately...
Continue reading →

Fabric Visibility

A leaf and spine fabric is challenging to monitor. The fabric spreads traffic across all the switches and links in order to maximize bandwidth. Unlike traditional hierarchical network designs, where a small number of links can be monitored to provide visibility, a leaf and spine network has no special links or switches where running CLI commands or attaching a probe would provide visibility. Even if it were possible to attach probes, the effective bandwidth of a leaf and spine network can be as high as a Petabit/second, well beyond the capabilities of current generation monitoring tools. The 2 minute video...
Continue reading →

Fan Failure String Status Question

Hi, Sorry for this weird request, but I am looking to know the exact string that EOS will give me in an show environment all command results output? <Snippet from show environmental all – all fans good in this case.> Airflow: front-to-back Fan Tray         Status           Speed ---------------- --------------- ------ 1                Ok                 46% 2                Ok                 46% 3                Ok                 46% 4                Ok                 46% 5                Ok                 46% 6                Ok                 46% Thank you much in advance! Mike

Recommended Minimum EOS Release API?

Arista does a great job posting the Recommended Minimum EOS Release versions however it requires partner level access (the information I have found thus far). I would like to programmatically access this information and I was hoping that Arista might have this information in a RestFUL API or at a minimum a public web link? Any help is appreciated.   Thank you again, Mike Cotrone

Automating the collection of system logs using logGrab

Typically when a support case is opened the first item requested by the support engineer is more data.  If all necessary data can be provided when a support case is opened it allows the support engineer to immediately begin looking at a customer issue, however it is often difficult to know exactly which information will be required.  logGrab aims to simplify this complexity by automating the process reducing the typical time to resolution of service requests. logGrab is a simple bash script, when executed it collects all data typically required by TAC engineers and places it into a single timestamped ZIP...
Continue reading →

Virtual Machines in EOS

How-to implement virtual machines in Arista EOS Virtualization was first developed in the 1960s and used to partition mainframe hardware to improve utilization. Today, virtualization has many meanings and widely implemented on a variety of platforms. Arista EOS leveraging it’s unmodified Linux kernel and embracing open source standards based technology has brought the concept of operating system virtualization to Ethernet switching. The approach that Arista has taken is to utilize Kernel-based Vitual Machines (KVM). Turning the Linux kernel into a hypervisor by loading a kernel module which provides the core virtualization infrastructure, a processor specific module (Intel or AMD) which...
Continue reading →

Running Arista vEOS inside VMware Workstation

Arista EOS is released as a single image that supports all of our platforms. That same single image can even be run in a virtual machine! This video describes how to set up a virtual machine in order to test EOS functionality, or to develop and test your own extensions.  

Intelligent Bootstrap with Arista EOS and ZTPServer

Many customers inquire about how to get started with automation into their operational networks. These conversations tend to revolve around how to reduce the operational expense and risk associated with managing data center networks. In most cases, the general consensus leads to starting automation around the bootstrap process or, in other words, how to find a better way to introduce consistency and agility into the deployment process.  Arista’s early heritage grew from solving real world operational problems that enhance our customers ability to deliver massively scalable data center networks efficiently. Throughout the development process EOS has provided innovative solutions that...
Continue reading →

Where to download Across

Can you help point out the download location of software “Across” required to generate EOS kernel source code? Many thanks! I didn’t find its download location with Google or on Arista web site. Error when generating source code: Installing EosKernel-2.6.38.8.Ar-1945438.EOS41281.src.rpm error: Failed build dependencies: Across is needed by EosKernel-2.6.38.8.Ar-1945438.EOS41281.x86_64

Running a Guest VM on EOS

Introduction One of the key features of Arista EOS is its Extensibility. (that is what the E in EOS stands for.) Many people already love that EOS is based on unmodified Linux kernel and basically runs a subset of Fedora Linux (as of writing, Fedora Core 14). To anyone familiar with Unix or Linux an Arista switch basically looks like a Linux server with lots of ethernet interfaces: switch>enable switch#bash Arista Networks EOS shell [admin@switch ~]$ uname -a Linux switch 2.6.32.28.Ar-957380.EOS4104gaurav #1 SMP PREEMPT Sat Nov 3 13:07:31 PDT 2012 x86_64 x86_64 x86_64 GNU/Linux [admin@switch ~]$ ifconfig -a cpu Link encap:Ethernet HWaddr 00:1C:73:19:F6:46...
Continue reading →

Securing EOS CLI

Objective This Tech Tip is intended to provide Arista EOS users with the configuration guidelines and best practices to enable secure management plane protocols according to IT industry security standards. It is not the objective of this document to set the foundations or rules of a company security policy or a password policy. Note: This document is not intended to set company security or password policy. Ultimate responsible to define and apply an end-to-end IT security policy is the responsibility of the end user and must take into account any regulations directly related with company activities. Arista EOS includes a wide...
Continue reading →