• Tag : docker

 
 

vEOS/cEOS GNS3 Labs

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 →

Management port on cEOS missing

I foloowed the setup at https://eos.arista.com/ceos-lab-in-gns3/ and successfully installed CEOS 4.21.7M on docker on my GNS3 VM. I can start, log in and configure. However, no Management port is available, and cannot be created. the ENV parameter “MGMT_INTF=eth0” has been added and can be seen in the running container. Any help would be appreciated. localhost(config)#sh run ! Command: show running-config ! device: localhost (cEOSLab, EOS-4.21.7M) ! transceiver qsfp default-mode 4x10G ! spanning-tree mode mstp ! no aaa root ! interface Ethernet1 ! interface Ethernet2 ! interface Ethernet3 ! interface Ethernet4 ! interface Ethernet5 ! interface Ethernet6 ! interface Ethernet7 !...
Continue reading →

cEOS-lab in GNS3

GNS3 is a great tool to visualize your (home-)lab environment and simulate all kinds of network topologies using different virtualization and isolation technologies. It has been widely used to create environments using vEOS-lab, but because vEOS-lab requires quite some resources (e.g. 2GB of RAM is required) the scale of these labs was often quite limited, especially on low-memory devices. Arista’s cEOS-lab is a new way of packaging the EOS-lab suite. Using the Docker container daemon, it is possible to use the kernel of the host machine and to only run the EOS processes that are required on the machine, making...
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.

cEOS instability

Hi, I played a bit with cEOS, I have 4 containers running, 2 spines and 2 leaf, each spine is connected to the 2 leafs. I first built a lab with eBPG between the spines and leaf, and then wanted to try eVPN. The connectivity between the cEOS is quite unreliable, I often have to “shut / noshut” the interfaces when they lose connectivity (ie: spine can no longer ping leaf). Anyone aware of issues with cEOS ? This is the process I followed to create the lab: # create docker instances with needed environment variables docker create –name=spine1 –privileged...
Continue reading →

Network CI/CD Part 1 – Building network topologies with Docker and cEOS-lab

Introduction As the networking industry continues riding the DevOps wave and network engineers become more comfortable using automation tools like Ansible and Salt, network still remains the most brittle piece of IT infrastructure. Partially this can be justified by the fact that network underpins all other areas of IT infrastructure stack – compute, storage and virtualisation. However we, as network engineers, have done very little to improve our confidence in networks and until now some of the biggest outages were caused by trivial network configuration mistakes. When software industry was facing similar challenges, the response was to create Continuous Integration (CI) pipelines –...
Continue reading →

Follow

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

Join other followers: