Virtualbox-Based Lab on Windows, MacOS or Linux¶
Virtualbox-based Vagrant lab is extremely easy to set up on Windows, MacOS, or Linux:
Install Virtualbox (might require fiddling with BIOS setup on Ubuntu bare-metal installations)
Create lab topology file. Use
provider: virtualboxin lab topology to select the virtualbox virtualization provider.
Execute vagrant up
Testing the Installation¶
The easiest way to test your installation is to use netlab test command. If you prefer to do step-by-step tests, or if you don’t want to use WSL on Windows, you might find this recipe useful:
Create an empty directory and
topology.ymlfile with the following contents within that directory:
--- defaults: device: cumulus nodes: [ s1, s2, s3 ] links: [ s1-s2, s2-s3, s1-s2-s3 ]
Create Vagrantfile with
vagrant upto spin up three Cumulus VX virtual machines
Connect to the Cumulus VX devices with
Destroy the lab with
vagrant destroy -f
Creating Vagrant Boxes¶
Vagrant relies on boxes (prepackaged VM images). The only image currently available on Vagrant Cloud is the Cumulus VX image – Vagrant automatically downloads it whenever you use Cumulus VX in your lab topology.
You’ll have to download Arista vEOS and Nexus 9300v images from the vendor web site and install them with vagrant box add filename –name boxname command
The Vagrant boxes should have the following names:
|Virtual network device||Vagrant box name|
|Cisco Nexus 9300v||cisco/nexus9300v|
If you want to add other network devices, build your own Vagrant boxes and modify topology-defaults.yml file (search for eos: or nxos: keys to see how to set up devices that work with multiple virtualization providers).
The latest version of Arista vEOS available as Vagrant box for VirtualBox is 4.21.14M. You’ll have to build your own box if you want to have a more recent EOS version.
Vagrantfile created by netlab create sets up port forwarding for SSH (22), HTTP (80) and NETCONF (830), but the corresponding Ansible inventory contains only ansible_port (SSH). You could edit the final inventory by hand, add extra file to
host_vars, or fix netsim-tools code. Should you decide to do the latter, please contact us in advance to discuss the necessary data structures.
Running Ansible on Windows is not supported, but supposedly it runs just fine under WSL.