vEOS Router Architecture

One of the benefits of the vEOS router is that it runs the same code as normal EOS, but in a virtual machine instead of on a hardware switch. Thanks to the EOS’s modular architecture, supporting a virtual machine instance is as simple as adding different agents to the system to accommodate the virtual network drivers. In this post, I describe how the different virtual networking options work with vEOS both on a server and in the cloud. Then I will explore some of the differences between vEOS router, vEOS-lab, and EOS on a hardware switch. For more information on...
Continue reading →

Agent unable to connect to Sysdb

I’m relatively new to EOS, so I feel like I’m probably missing a basic step. I’ve setup a vEOS testlab, running under KVM.  Most things have been going well, the virtual switches can see each other, i’ve been able to test some ZTP scripts. I’m getting stuck however when it comes to running an agent using the python sdk.  I’m attempting to start the from this example ( However, all I get when looking at the agent logs is “waiting for connection to Sysdb …..” and it never connects. veos-vdf-core1#configure veos-vdf-core1(config)#daemon HelloWorldAgent veos-vdf-core1(config-daemon-HelloWorldAgent)#show active daemon HelloWorldAgent exec /mnt/flash/ no...
Continue reading →

Arista eapi multiple commands not working

Hi, When I’m trying to use Arista veos eapi to configure vlan on an interface using multiple commands, it is failing (single command is working fine like “show vlan”, “show version”). It is not showing any response and in the background also configuration is not happening on the virtual switch. Please help me if I’m missing anything. I’m using VEOS (virtual switch) for my testing. Following are commands I’ve used and attached the screenshot of eapi. Thanks in advance   enableconfigureinterface Ethernet1switchport access vlan 745show vlan 745

vEOS on GENI Experimental Portal

Hi, I am trying to use vEOS on GENI experimental portal as it seems ideal for my requirements. To do this I need to create a GENI image as given by So I tried to use vEOS 4.16.9M with Aboot 2.1.  But according to the GENI guide mentioned above, I need to create and save the OS image locally (in the guest VM). I am unable to mount an extra disk drive to my virtualbox (or use the pendrive). If you could help me with this, I would appreciate it greatly. Also, I tried to use the .swi file...
Continue reading →

Running vEOS in Openstack

I’m trying to setup a vEOS lab environment in our internal Openstack infrastructure.  This is what I’ve done so far:- Uploaded the ABOOT image (Aboot-veos-8.0.0.iso) & the VMDK (EOS-4.18.0.vmdk) to Glance. Create a volume based on the VMDK Launch an instance from the ABOOT image with the Volume mapped to the instance:- nova boot –flavor m1.small \                 –image <aboot image ID> \                 –nic net-id=<Neutron Net ID> \                –block-device id=<Volume ID>,source=volume,device=hdb,dest=volume,shutdown=preserve \                veos-test-01 However, the instance hangs after loading the initrd & doesn’t run aboot. Has anyone tried this / had this working?

Management interface down

I am running arista veos in vmware workstation. All the interfaces are working fine except the management interface. Status: down, Protocol: not present. I have configured the IP for the management interface, and I am able to ping it from the host. But ping fails 50% of the time

Configuration Session on vEOS

Hello everyone, I got the vEOS running on Virtualbox integrated with GNS3, so far everything running fine. Im trying to find out if the configuration session feature is not available on the vEOS or maybe im missing somthing. I’ve tried to issue the command : configure session from enable mode but it looks like there is no such command. Did anyone else encountered the issue?   Best Regards, Chen.

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 →

vEOS BGP fails to establish with Cumulus VX

I’m running vEOS (4.17.0F) in a KVM hypervisor along with an instance of Cumulus VX 3.0.1. I’m attempting to bring up a simple BGP session between the devices through a virbr virtual network, but AFACT the vEOS instance is failing to ack any SYN packets to TCP/179 coming from the Cumulus instance; every 30 seconds the vEOS instance sends a SYN to TCP/179 to the Cumulus instance, which then sends a SYNACK back…which vEOS doesn’t acknowledge either. I’m not seeing any oddities WRT the BGP configs or basic reachability (the fact that I do see SYNs going in both directions...
Continue reading →

Saving configuration

Hello, i am quite new to Arista. So i am using Arista vEOS to do some projects. And after finishing one project, i use the “wr” command to save my running configuration. And when i start another new project, the configuration of the previous project is now in my new project. For example, in project 1, i simply changed my hostname to “New”, and saved the configuration. Then if i start a new project using the same device, the hostname is already the name i changed which is “New”. This is not what i want, what i want is whenever...
Continue reading →

Difference between Aboot-veos-serial-8.0.0.iso vs Aboot-veos-8.0.0.iso

Hi Team, i have asked many questions over here on this forum but hardly people answer to my query.this time i hope i will get my answer.My confusion start when i see this 2 supportive file for arista vEOS (Aboot-veos-serial-8.0.0.iso vs Aboot-veos-8.0.0.iso).which one should i use and why . what one have advantage over other.recently i checked download section  and found new vEOS 4.16.6M released by Arista is it just bug fix or any new feature added in this .please answer to my query  

Valid Python Scripts may fail in OS X ‘El Capitan’

Python scripts can be run on OS X using eAPI to access Arista Switches or vEOS instances. Python Scripts can also be run on OS X to automate the installation of vEOS: ( After installing or upgrading to OSX ‘El Capitan’ (OS X version 10.11.5) Python Scripts that previously worked fine under earlier versions of OS X or work on other operating systems may fail. This is evident when making a Python Script executable after issuing the chmod +x command.  This is due to operating system changes Apple has introduced in ‘El Capitan’. Although, this problem may affect eAPI and...
Continue reading →

VRF import export

Is there a way to perform a VRF import and export target? Similar to: ip vrf wanconnection:1 rd 65000:1 route-target export 65000:2 route-target import 65000:99 ip vrf wanconnection:2 rd 65000:2 route-target export 65000:1 route-target import 65000:99 ip vrf shared:1 rd 65000:99 route-target export 65000:99 route-target import 65000:1 route-target import 65000:2

Puppet Agent installation

Hi there, I’m experiencing some issue with the Puppet agent installation on a vEOS switch running on VirtualBox. I’m following this ( When it comes to the Agent installation, I’ve downloaded the two All-in-One packeges from the above link (puppet-agent-1.2.7-1.eos4.i386.swix and rbeapi-puppet-aio-0.4.0.swix). Then, the guide suggests to do some tests to verify that everything is fine. Anyway, any test return the same error: “/bin/bash: puppet: command not found” I tried to switch to the root user. Here, after I configured proper path (PATH=/opt/puppetlabs/bin:$PATH;export PATH), the puppet command start to work and I can now verify Puppet version: -bash-4.1# puppet –version 4.2.3 -bash-4.1# facter...
Continue reading →

Getting EOS-lan image online via Qemu

Sorry about the previous post. I tried editing it, but but it wiped out the question, which deleted the entire post. Long story short, I can get the vEOS image online via a setup in GNS3, but the download speeds are abysmal. I can get other non-vEOS images online outside GNS3 via the CLI, and the speeds are lightning fast. Here’s what I tried in gnome-term: qemu-system-x86_64 -hda vEOS-lab-4.15.2F.vmdk -boot order=d -cdrom Aboot-veos-serial-2.0.8.iso -m 2048 -enable-kvm -netdev user,id=network0 -device e1000,netdev=network0 -serial telnet::3355,server,nowait   The image loads fine (provided I use a second term to telnet into the vEOS term window)....
Continue reading →

unable to load EOS image in OpenStack/KVM

Hello all, Recently I tried to install the vEOS on KVM/OpenStack. In OpenStack, I created two images for Aboot and vEOS vmdk files. An instance is created with the Aboot image to get it loaded properly and the vEOS vmdk image is attached as a storage (Attached To vEOS 4.15.0F on /dev/vda). Unfortunately, the instance loads and stopped with error in the attached screenshot. It seems the Aboot image is unable to find the attached storage in order to load the EOS image. Wondering if you experienced this and have a solution / workaround. Thanks, Steven

Using vEOS with Vagrant and VirtualBox

Beginning with EOS 4.15.2F, vEOS is available as a Vagrant box for VirtualBox.  This single-file VM package makes it one of the fastest ways to get started with vEOS and is ideal for testing in automated environments.  Multiple VMs may be defined within a single Vagrantfile, including non-vEOS VMs, allowing an entire topology to be defined in a single file.  A customized Vagrantfile, checked in to revision control, is an effective way for multiple users to consistently recreate a complete environment. Prior to EOS 4.15.2F, the vEOS vmdk and Aboot.iso files can be converted to a Vagrant box by following the directions...
Continue reading →

vrf configuration in vEOS instances

Hi All, I have a vEOS instance as well as a Arista hardware box. I was trying to configure vrf in both. In hardware box it was easy to configure and was able to ping my gateway using ping vrf <newvrf> <IP> command. The same configuration i tried in vEOS but it is not pinging. Is there any special config to enable vrf in vEOS? Both are in same LAN and has common gateway. The gateway is lying in a Cisco device which is out of my access. From vEOS i can do self ping, but none other IPs in...
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.

Tip for Arista vEOS on VMware ESX 6

Note: This tip was discovered and shared by Sandy Breeze at Claranet   Arista provide the EOS network operating system for test/lab virtual environment under the form of vEOS, either as a VMDK or a SWI (software image to install on an existing vEOS). With the vEOS VMDK as currently provided, in thin provisioning for saving on the file size, ESX4 and 5 would work fine, but upon booting the vEOS VM under ESX6, it will report “LZMA data is corrupt”,  and “system halted”, despite the image not being corrupted (you could verify the checksum). This issue may also manifest itself with an...
Continue reading →

issue using event-handler with bash command

Hi, I run vEOS 4.13.7M in VirtualBox. Inspired by the logGrab bash script provided here on EOS Central I wrote this tiny little script #!/bin/bash FILENAME=startup-config_$HOSTNAME_$(date +%Y-%m-%d.%H%M%S) cd /mnt/flash cp startup-config $FILENAME Invoked from CLI it works like a charm, producing lots of config files to fill my flash: Leaf1#bash /mnt/flash/ Leaf1#dir Directory of flash:/ -rwx         154           Feb 19 16:52 -rwx          20           Jun 16  2014  boot-config drwx        4096           Aug 22  2014  debug drwx        4096           Feb 19 07:44  persist drwx        4096           Aug 22  2014  schedule -rwx        1062           Feb 19 16:53  startup-config -rwx        1062           Feb 19 16:26  startup-config_2015-02-19.162615 -rwx        1062           Feb...
Continue reading →

unable to send traffic over VXLAN

I am trying to setup a basic VXLAN configuration using vEOS on KVM VMs. Topology is as follows : [Linux VM1][edge1][Eth2][core1][Eth1][Eth1][core2][Eth2][edge2][Linux VM2] Each switch has two ports apart from the mgmt port. Both edge switches are configured to allow VLAN 42. I am trying to setup VTEPs on core1 and core2, hoping to see VXLAN traffic between them. Basic connectivity is there. Without any VLANs I am able to ping between Linux VM1 and VM2. Even with trunk ports on core switches allowing VLAN 42, I am able to connect. Now onto the VXLAN config -------------------------------------- core1 : ------- Interface...
Continue reading →

Quick and Easy vEOS Lab Setup (VMware or VirtualBox)

Introduction A local vEOS lab is always helpful when trying out new features or validating configuration. So how would you like to be able to setup a 4-node spine/leaf virtual lab pictured below with one simple command? user:packer-veos user$ ./ -H virtualbox And what if you wanted to try out the ZTPServer with this new set of nodes? user:packer-ztpserver user$ ./ -H virtualbox -o fedora This is possible with the help of the EOS+ Consulting Services Github projects: packer-veos packer-ztpserver Follow the READMEs at those individual repos to setup your virtual machines, but here’s a quick overview of the process....
Continue reading →

vEOS v4.13.8M Cant issue IP ROUTING command

I have been using vEOS v4.13.7M perfectly and I upgraded one of my VM’s to 4.13.8M to fix the eAPI documentation link bug. Everytime I try to enable “ip routing” it kicks back the command with “% Unavailable command (not supported on this hardware platform). I compared all of my VM settings and everything matches my working .7M versions. Did something change? Thank you in advance!

vEOS Documentation URL Link broken

I am running vEOS version 4.13.7M-1877079.4137M.1 and when I click on the “Command Documentation Link” in the eAPI Explorer it says that the link is broken. URL: Message Received: page /documentation.html not found   Is this expected? thank you in advance, Mike Cotrone


Hello, I am using VirtualBox with the Am79C973 driver to run vEOS, and I’ve run into some issues when combining LLDP and LACP.  Individually, either works great.  But if I create a LAG with LACP enabled, LLDP stops working on the members of the LAG.  If I change the LAG to static, non-LACP configuration, LLDP works again. Is this a vEOS bug or a known limitation?  On a number of physical 7050s, the combination works as expected. Ross

VXLAN VEOS support

Hi, Previously saw that VXLAN was supported on VEOS. However, I tried to configure a vxlan interface using VEOS version 4.13.7M and got message stating that it’s not supported on VEOS. Can someone please confirm? Thank you  

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.  

Running vEOS on ESXi 5.5

What is vEOS? Arista Networks vEOS is a software only version of the EOS network operating system. vEOS is meant to be run in a virtual machine environment. vEOS is useful for feature testing and especially for development of scripts and extensions. vEOS can be run on many different virtualization platforms like Virtual Box, VMware Fusion or Workstation as well as ESXi. Arista Networks has previously published how to documentation for running vEOS on other virtualization platforms and this document will extend that documentation to ESXi. What is ESXi? VMware ESXi is a server virtualization platform that supports hypervisor clustering,...
Continue reading →

VMWare Fusion Virtual Networks

Introduction This Tech Tip explains how to setup VMWare Fusion to enable isolated network segments between guests. This is particularly useful when used in conjunction with vEOS (vEOS – Running EOS in a VM). When vEOS instances are run in VMWare Fusion and share the same virtual network interface on the host, for example the hostonly interface, all VMs will appear to be connected to the same segment. This is fine for testing routing and usual EOS feature but poses a problem when testing a feature that depends on the VM or vEOS instance only being able to see one...
Continue reading →

vEOS – Running EOS in a VM

Overview 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 article describes how to set up a virtual machine in order to test EOS functionality, or to develop and test your own extensions. EOS in a VM EOS run in a VM can be used to test almost all aspects of EOS, including: Management Tools – CLI, Snmp, Aaa, ZTP L1 Connectivity – Link up/down (when connected to another EOS VM port), LLDP L2 – VLANs, Port-channels, MLAG L3 – Routed ports, Static routing, BGP, OSPF, VARP,...
Continue reading →

Building a Virtual Lab with Arista vEOS and VirtualBox

It’s no secret that I love Arista switches. When I wrote Arista Warrior, I was lucky enough to have a loaner switch from Arista in my home lab, but sadly they made me give it back. Since Arista is a relative newcomer to the world of Networking, there isn’t a pile of used Arista gear on eBay, so I can’t build a killer lab at home without spending thousands of dollars. As much as I love Arista switches, I’d rather spend my spare cash on guitars my wife and kids. Understanding the plight of cash-strapped networking guys the world over, Arista has...
Continue reading →

Which vEOS release for OF support?

Back in Interop, you demonstrated OpenFlow integration with Big Switch Controller.  2 questions related to this. 1. Probably can’t answer this if it isn’t released, but what release did it start in? 2. Will there be support in vEOS for OpenFlow?  My main question.   As a person that likes to try out new tech, it would be nice to find a way to try OpenFlow from a vendor without having to purchase (personal financing) a new switch.  I’m trying to find some way I can see what OpenFlow looks like from a vendor.  I’ve used OpenVSwitch, but I want...
Continue reading →

Configure vEOS VM

I have the vEOS configured under ESX5.1i and have two question 1) I created an OVF template in VMplayer (where all Ethernet1-4 interfaces were ok) and imported this in to my ESX5.1i host – On E3 / E4 I now get the message “Interfaces does not exist. The configuration will not take effect until the module is inserted”  How can the E3 / E4 interfaces be made available?  (I have all 5 x interfaces – 1xmgmt 4xethernet configured in the VM) 2) I can’t bring up a trunk port to support MLAG.  This worked in VMplayer but despite configuring the...
Continue reading →

vEOS and VirtualBox

Tech Tip originally posted by Edmund Roche-Kelly 09 Nov 2012 This tech tip describes how to set up and network EOS VMs in VirtualBox. The examples are based on a vanilla installation of VirtualBox 4.2.4 on Mac OS X Version 10.7.4. By the end of the post, we will have 4 EOS VMs connected together with remote ssh access.   Install VirtualBox and download vEOS images VirtualBox is “a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Not only is VirtualBox an extremely feature rich, high performance product for enterprise customers, it is also the only...
Continue reading →