• Tag : lab

 
 

Deploying Cloudvision Portal (CVP) on Proxmox VE

Introduction Proxmox is an open source server virtualization solution based on QEMU/KVM and LXC.  You can manage virtual machines, containers, high availability clusters, storage and networks with an integrated, easy-to-use web interface or via CLI. The purpose of this article is to assist in deployment of Arista’s Cloudvision Portal (CVP) within Proxmox VE.  The benefit of utilizing CVP within Proxmox VE is that it offers an open source, subscription free option for those who may not be able to afford proper VMware licensing for lab/demo deployments and/or would like to utilize the rich, open source feature set provided by Proxmox...
Continue reading →

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 →

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 →

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?

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 →

Follow

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

Join other followers: