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 →

VM Tracer configuration on a layer 2 switch

Introduction There are many network architectures, which include a separate network for out-of-band management. All Arista switches come with at least one designated management interface that is VRF-aware. When VM Tracer is configured on an Arista switch, by default, vCenter communication will be sourced from the management interface. There are situations where a layer 2 switch has the management interface configured in a separate VRF, not reachable from the vCenter network segment.  Objective Create reachability to vCenter from layer 2 switches that have the management interface configured in a separate VRF, not reachable from the vCenter network segment.  Prerequisites Proper VM Tracer configuration...
Continue reading →

Fusion VM Missing IP

Hello. I am trying to set up a single instance of the Arista EOS VM on VMWare Fusion (v8.1.1).   I am able to get it to boot and I can run things like ‘show interfaces’.  I am unable to ping 8.8.8.8, or more important for me, get the IP so I can set up a second VM to test the eAPI. I currently have a host-only interface, set private to my Mac. If I run `show management api http-commands` (copy paste not working): Enabled: No HTTPS server: enabled … HTTP server enabled … .. I suspect its because I...
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!    

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$ ./create-veos.py -H virtualbox And what if you wanted to try out the ZTPServer with this new set of nodes? user:packer-ztpserver user$ ./create-ztpserver.py -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 →

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.  

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 →

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 →

VMware ESX 5 – Arista LACP guide

LACP Overview Link aggregation is a method for combining multiple Ethernet links into a single logical link with the goal of increasing both bandwidth and availability. By aggregating multiple links within a link aggregation group (LAG) customers improve performance by increasing bandwidth & ensure path redundancy in the event of a single link failure.  These benefits have made link aggregation a popular deployment standard in today’s Data Centers. Link Aggregation can be implemented in two ways: static and dynamic. With static LAG, each port-channel is created manually, with no automated mechanism to validate the port-channel configuration on the other switch....
Continue reading →