• Tag : vEOS


vEOS / CloudEOS and interface ordering

Hi, I am trying to wrap my head around what logic vEOS uses to map PCI network cards to EthernetX numbers. I am running a lab in ESXi with 1x E1000 interface which always gets mapped to Ma1 – so far so good. However when I add 10x VMXNET 3 interfaces with ordered PCI IDs EOS seems to jumble the order. Ethernet1 ends up being the 4th VMXNET, Ethernet2 is the 8th. It is seemingly random to me. It seems this would be a severe limitation if it is indeed random, so I must assume I am missing some crucial...
Continue reading →


Introduction vEOS-lab/cEOS-lab on GNS3 – What is it? Fast, Multi-user, Efficient nested virtual lab using Qemu/Kvm/docker images of vEOS-lab/cEOS-lab Dynamic persistent config/storage of each cEOS container across stop/starts and GNS3 project closure/re-opens Deployed in minutes on ESXi host. Cloning and creating another bubble is easy, fast and can be moved around Integrated data plane traffic generation tool (Ostinato) in this lab Packet capture on any links between vEOS/cEOS devices Required SW/HW  GNS3 Server VM (Ubuntu 18.04 LTS VM + GNS3 Server) VMware Host system running ESXi version 6 or above with Mgmt Network access ESXi host to deploy this GNS3...
Continue reading →

Problem with EVPN type-5 packet forwarding on vEOS

Hello, I am testing a solution based on VXLAN EVPN, with Type-5 routes, with vEOS, but I am having some issues in packet forwarding. The routes are correctly propagated, but when I try to ping from a device connected to one node, on a device connected to another node, the ping does not work. I also tried a ping, with a forced source IP, from the vEOS machine itself, but it has problems too. LEAF-2 LEAF-2#sh ip route vrf gold VRF: gold Codes: C – connected, S – static, K – kernel, O – OSPF, IA – OSPF inter...
Continue reading →

EVPN peering not being established

I’m building an EVPN test network using GNS3 (v2.2.0) and vEOS-lab images ( basing the configuration on the EVPN Deployment guide. I’ve built a network with 2 pairs of leaf switches & a pair of spine switches (see image). The Underlay BGP network is established fine, and I can reach the endpoints correctly. However when I try and establish the eVPN overlay peerings between the leaf switches and the spines some links never proceed beyond ‘OpenConfirm’ state. spine1(config-router-bgp)#show bgp evpn summary BGP summary information for VRF default Router identifier, local AS number 65000.0 Neighbor Status Codes: m - Under...
Continue reading →

Static tunnel interface counters on vEOS Router DPDK mode

Description This feature modifies the display format of “show interface Tunnel <num> counters”.  Platform compatibility This feature is for vEOS router DPDK mode (MODE=sfe in /mnt/flash/veos-config) Configuration There are no new configuration commands for this feature. Show  Commands The display format of “show interface tunnel <num> counters” command has changed. It uses a three column display format –  Number of Bytes, Number of Unicast, Number of Multicast packets. switch#show interface tunnel 1 counters Tunnel InOctets InUcastPkts InMcastPkts Tu1 0 0 0 Tunnel OutOctets OutUcastPkts OutMcastPkts Tu1 0 0 0 Old Format switch#show interface tunnel 1 counters Port InOctets InUcastPkts InMcastPkts...
Continue reading →

LACP/802.3ad on vEOS

Hey folks – I’m playing around on a KVM server with vEOS 4.22.0F, trying my hand at the EVPN/ESI multihoming. The basic network is 2 x Spines connected to 2 x Leafs with a single Linux (Debian) VM connected to both Leafs. VXLAN with EVPN is running between the 4 vEOS devices and the EVPN multihoming seems to be working well. The server thinks it has an 802.3ad bundle, and packets can flow through either link. All good. The challenge I’m running into is detecting and/or simulating link failure properly. If, for instance, I “shut” the Ethernet interface on the...
Continue reading →

vEOS with Vagrant

Hello, I am building demo lab using Vagrant, and I am having a hard time finding the Vagrant box file for virtual box at arista software downloads. The last version available seems to be the 4.20.1F are there any plans to provide builds for the newer releases like 4.22.1F?

vEOS missing Qemu flag

Hi, I am trying to make use of qemu’s -fw_cfg flag. Usage: -fw_cfg name=opt/GuestInfo,file=/guest_infos/guestinfo.txt This allows a config to be passed into qemu vms. For example, on fedora 30: cat /sys/firmware/qemu_fw_cfg/by_name/opt/GuestInfo/raw HOSTNAME=foobar.example.com IPADDR= However this does not work on vEOS. The firmware driver (https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/commit/?h=driver-core-testing&id=75f3e8e47f381074801d0034874d20c638d9e3d9) i believe is included in kernels 4.6 and above. I am using vEOS 4.22.0F which has a kernel above 4.6 Any help much appreciated?

Switchport VLAN on vEOS

I’m wanting to test out VLAN translation using the vEOS image, however it doesn’t appear switchport vlan translation is a valid command. localhost(config-if-Et1)# vlan not supported on this hardware platform localhost(config-if-Et1)#switchport vl Am I not able to test this feature in a lab environment?

How to add hosts to vEOS Switch via virtual machine

I am new to Arista EOS and networking. I have created a vSwitch using EOS as OS and integrated with ONOS controller. I want to add hosts to this switch. Can you guide me or is these any documentation available to do the same?

Virtual Box Crash On VEOS Reboot

Symptom – When the VM reboots after zerotouch cancel or after a reload command the VM crashes. Please let me know if I can provide any additional information. Hardware and Software: Mac Book Pro Mac OS 10.13.6 8 GB RAM VirtualBox 6.0.0 Arista VEOS – vEOS-lab- Guest Settings – 64bit Fedora, 2 GB RAM Following instructions http://www.gad.net/Blog/2012/10/27/building-a-virtual-lab-with-arista-veos-and-virtualbox/ Attached is my VBoxLog File Thank you for your assistance.

Deploy a Transit VPC with vEOS using IGW (Public IP)

Deploy a Transit VPC with vEOS using IGW (Public IP) fanyang@arista.com   This document focuses on the steps to build a Transit VPC solution using Internet Gateway (IGW) vs. VPC peering. There are certain advantages to use IGW as transport. This eliminate the limits on how many VPC peering can be created and gives customer a larger scale deployment. It also enables spoke VPCs to communicate with each other directly with one hop, which can potentially save data cost. Besides, even it’s public ip to public ip communication, if both IPs belong to AWS, AWS will route the traffic through...
Continue reading →

docker image failed to load on arista vEOS

Hi, I have a docker image built on my mac machine. I pushed docker image on arista VEOS. But, when I am trying to load the image on vEOS then giving error “Error processing tar file(exit status 1): unexpected EOF” bash-4.3# docker load < simple-flask-app.tar Error processing tar file(exit status 1): unexpected EOF Please help me to resolve this issue.

how to build RPM for arista vEOS

I have build RPM file with HelloWorld program. It is getting installed on vEOS, But when I am trying to run with exec /usr/bin/HelloWorld.py then it is giving error file is not executable. Can you please share SPEC file to create RPM file, steps to create RPM & execute on the vEOS?

Arista Any Cloud Platform – vEOS Router in Azure Deployment Guide

Introduction In this document, we will demonstrate the deployment of Arista’s vEOS Router in Microsoft Azure. A vEOS Router can be leveraged to implement various Azure architectures such as the transit-edge or hub-spoke architecture. This particular document provides a step-by-step guide to deploy vEOS Router in a transit-edge architecture in the Azure public cloud. Overview Arista’s private and public cloud infrastructure both offer significant efficiencies that make it a compelling option for workload placement.   We have proven this in the private cloud with a simple yet scalable Spine/Leaf topology utilizing industry standard protocols across all of Arista switches. With...
Continue reading →

Arista Any Cloud Platform – VM Migration

Introduction In many scenarios, resources are provisioned in the public cloud as a service, without a need to connect to a private on-prem environment. Situations will arise where connectivity is required between a public and private environment that conflict in IP space. This article will showcase how to leverage vEOS Router in AWS to establish connectivity between a VPC and a private on-prem datacenter that conflict in IP space. In this particular example, there are a hand-full of VMs that need to be migrated from AWS to a private environment. Objective Establish connectivity between the AWS VPC and the private environment. Once connectivity is established,...
Continue reading →

vEOS on ESXi – Jumbo MTU Problem

Hi, I run couples of latest vEOS switches on ESXi, trying to build a VXLAN lab to test. Between vEOS switches, I used standard virtual switch as a virtual cable for each individual connection.  In vSwitch settings, I’ve set the MTU to 9000. MTU1500 works OK. But ping test over 1500 bytes all failed. PING ( 1473(1501) bytes of data. ping: sendmsg: Network is unreachable ping: sendmsg: Network is unreachable ping: sendmsg: Network is unreachable Searching over Internet came up no result…. Any thought?  

vEOS-Lab on Hyper-V

Introduction There are multiple ways to setup a vEOS-Lab environment if you have a linux system or on hypervisors such as VMware ESXi, vCenter, VM Workstation, VM Fusion, Virtualbox, etc using the vmdk provided in the Software downloads page. But if you have a Windows machine or a Windows server, the vmdk will not be useful. So here are the steps on how you can convert the vmdk to a  vhdx and create a vEOS VM on Hyper-V. Pre-requisites 1. Hyper-V Manager and Hyper-V 2. vEOS-Lab vmdk 3. Aboot ISO  Instructions Steps 1. Download the vEOS vmdk for the EOS version...
Continue reading →

Arista Any Cloud Platform – Security Use Case

Introduction In this document we will demonstrate how to effectively leverage Arista’s vEOS Router in a Transit – Edge VPC model to satisfy a common security use case. As most companies look to move into the public cloud space, security vulnerabilities have gained more focus than ever before. Objective Provide a centralized security model within an AWS region, which will allow for ease of visibility and control. Deploying separate AWS Internet Gateways in every VPC, increases complexity and vulnerabilities in the public cloud space.  Prerequisites This document assumes that you have the following architecture deployed: A Transit – Edge VPC topology deployed...
Continue reading →


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

Join other followers: