• Tag : vEOS

 
 

vEOS on ESXi – Jumbo MTU Problem

Posted on March 30, 2018 by

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 172.16.11.0 (172.16.11.0) 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

Posted on January 19, 2018 by

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

Posted on January 9, 2018 by

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 →

Using vEOS for ZTP tests, cannot find any serial number

Posted on October 19, 2017 by

Hi! Using the vEOS to setup a docker container handling ZTP.No about ztpserver but I need to manage multiple vendors so I’m placing something in front handling all of them. Noticed that the serial number is empty in the image. Wondering about the possibilty of tweeking on in?Will try to get the image into single user mode and look myself but I guess this will be a timeconsuming task.   Any ideas??   Thanks! Fredrik

How to config vmtracer on vEOS

Posted on June 15, 2017 by

I want to test vmtracer on vEOS  can see my network topology in (.pdf)  and log in (.txt) My vmtracer session can connect to vCenter but command ” Show vmtracer vm ” didn’t see anything. vEOS can ping all guest vEOS_eth1 , vCenter , ESX  have network adapter in vlan 2 what did I do wrong?

Python agent terminates: “Exiting because NboAttrLog connection has closed”

Posted on June 5, 2017 by

Hi, I’m trying to run HelloWorld.py agent straight from the tutorial on Github. I have created the mount profile as described in the tutorial: gentName:HelloWorld.py-%sliceId Include: EosSdk_acl.include Include: EosSdk_agent.include Include: EosSdk_class_map.include Include: EosSdk_decap_group.include Include: EosSdk_directflow.include Include: EosSdk_eth_intf.include Include: EosSdk_eth_lag_intf.include Include: EosSdk_eth_phy_intf.include Include: EosSdk_fib.include Include: EosSdk_hardware_table.include Include: EosSdk_intf.include Include: EosSdk_IntfMgrHelper.include Include: EosSdk_ip_intf.include Include: EosSdk_ip_route.include Include: EosSdk_lldp.include Include: EosSdk_mac_table.include Include: EosSdk_mlag.include Include: EosSdk_mpls_route.include Include: EosSdk_neighbor_table.include Include: EosSdk_nexthop_group.include Include: EosSdk_policy_map.include Include: EosSdk_subintf.include Include: EosSdk_system.include Include: EosSdk_vrf.include Include: EosSdk_GOpenFlow.include Include: EosSdk_bfd_session.include When I try to run it (whether from configuration: daemon HelloWorld.., or from the shell, it terminates with the following output Connection from...
Continue reading →

Agent unable to connect to Sysdb

Posted on May 22, 2017 by

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 HelloWorld.py from this example (https://github.com/aristanetworks/EosSdk/wiki/Quickstart:-Hello-World) 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/HelloWorld.py no...
Continue reading →

Arista eapi multiple commands not working

Posted on May 1, 2017 by

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

Posted on April 4, 2017 by

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 http://www.exogeni.net/2014/07/creating-a-custom-exogeni-image-using-virtual-box/ 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

Posted on March 9, 2017 by

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

Posted on October 20, 2016 by

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

Posted on September 26, 2016 by

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

Posted on September 13, 2016 by

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

Posted on August 8, 2016 by

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

Posted on July 19, 2016 by

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

Posted on July 12, 2016 by

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’

Posted on May 25, 2016 by

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: (https://github.com/arista-eosplus/packer-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

Posted on April 28, 2016 by

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

Posted on February 21, 2016 by

Hi there, I’m experiencing some issue with the Puppet agent installation on a vEOS switch running on VirtualBox. I’m following this (http://puppet-eos.readthedocs.org/en/master/installation.html). 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 →

« Older posts
Follow

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

Join other followers: