Juniper / Vqfx10k Vagrant
Labels
This repository is a library of examples/demo using Vagrant and vqfx10K. Each example has its own directory and will contain at least a Vagrantfile
Launch vqfx10k
Once you have followed the installation procedure, you can start a topology with few lines
To try an example, you just have to go inside a specific directory and run "vagrant up":
git clone https://github.com/Juniper/vqfx10k-vagrant.git
cd vqfx10k-vagrant/light-2qfx
vagrant up
Some topologies are using Ansible, If you don't have ansible you can start them using
vagrant up --no-provision
Once both VMs are up and running, you can connect to them with:
vagrant ssh vqfx1
vagrant ssh vqfx2
Available examples:
Installation Guide
Installation Guide is available here
How to contribute
Contributions to this repository are welcome and encouraged, especially to:
- Enhance the documentation of existing examples
- Enhance existing examples
- Create new examples
To contribute
- Fork this repository
- Send a merge request
Guidelines to create a new example
TODO
How to provide feedback or report an issue
The best solution to provide feedback is to open a new issue on the git tracker associated with this repo.
Before opening a new issue, please check the troubleshooting guide - work in progress
vQFX10K
vqfx10k is a tool provided for lab and training; this is not a intended to be used in production. Capacities are similar to a real QFX10K but performance are very limited in this version, few 100s PPS.
Mode, Architecture and Limitations
vqfx10k for Vagrant can work in 2 modes: Full and Light
Full Mode
In Full mode, it require 2 VMs for each instance:
- 1 Routing Engine VM, running Junos (vqfx10k-re-virtualbox-##.box)
- 1 Packet Forwarding Engine, running Linux (vqfx10k-pfe-virtualbox-##.box)
In Full mode, the dataplane is fully functional and is very close to the real QFX10K
These 2 VMs need to be interconnected with a dedicated private network on their interface number 1, (interface 0 is always reserved for Vagrant for management). All data plane interfaces need to be connected to the Routing Engine (RE) VM. Up to 12 data plane interfaces are supported. Port names will be xe-0/0/0 to xe-0/0/11.
Full Mode Limitations
Only few features are not supported due to some architecture differences between vQFX10K and a real QFX10K
Unsupported features:
- Analytics
- Guest VM/ Guest container
Light Mode
In Light mode, only 1 Routing Engine VM, running Junos is required for each instance.
Up to 5 interfaces are supported to connect to external devices. Interface names will be em3 to em7
Light Mode Limitations
In Light mode, most data plane features are not supported and all packets are processed in kernel
Family ethernet-switching is not supported in light mode
VM Characteristics
vqfx10k-re
Requires:
- 1GB of memory
- Interfaces type must be type: 82540EM
A maximum of 12 interfaces are supported:
- first interface is used by vagrant (em0)
- second interface is used to connect to the PFE VM (em1)
- third interface is a management port not used (em2)
- All remaining interfaces can be used to connected to other devices
This VM has 2 account by default:
- login: vagrant, with ssh_key authentication using vagrant insecure_key
- login: root, password: Juniper
Virtualbox only support 8 interfaces by default
vqfx10k-pfe
Requires:
- 1.5/2GB of memory
- 1 dedicated core
A maximum of 2 interfaces are supported:
- first interface is used by vagrant (eth0)
- second interface is used to connect to the RE VM (eth1)
This VM has 2 account by default:
- login: vagrant, with ssh_key authentication using vagrant insecure_key
- login: root, password: no
Vagrant
What is Vagrant
Vagrant is an open-source (MIT) tool for building and managing virtualized development environments developed by Mitchell Hashimoto and John Bender.
Vagrant is able to create VMs, connect them together and is specify configure them automatically.
Here is a good introduction to Vagrant for Network Engineer
Providers
For now, only VirtualBox is supported as a provider.
VMware will be added later.