Juniper vQFX virtualized router is identified with
vr-juniper_vqfx kind in the topology file. It is built using vrnetlab project and essentially is a Qemu VM packaged in a docker container format.
vQFX images built with hellt/vrnetlab have experimental support for vQFX version v18 and newer.
Managing vr-vqfx nodes#
Containers with vQFX inside will take ~7min to fully boot.
You can monitor the progress with
docker logs -f <container-name>.
Juniper vQFX node launched with containerlab can be managed via the following interfaces:
to connect to a
bash shell of a running vr-vqfx container:
docker exec -it <container-name/id> bash
to connect to the vQFX CLI (password
Default user credentials:
eth0- management interface connected to the containerlab management network
eth1- first data interface, mapped to first data port of vQFX line card
eth2+- second and subsequent data interface
When containerlab launches vr-vqfx node, it will assign IPv4/6 address to the
eth0 interface. These addresses can be used to reach management plane of the router.
eth1+ needs to be configured with IP addressing manually using CLI/management protocols.
Features and options#
vr-vqfx nodes come up with a basic configuration where only the control plane and line cards are provisioned, as well as the
admin user with the provided password.
It is possible to make vQFX nodes boot up with a user-defined startup-config instead of a built-in one. With a
startup-config property of the node/kind user sets the path to the config file that will be mounted to a container and used as a startup-config:
topology: nodes: node: kind: vr-vqfx startup-config: myconfig.txt
With this knob containerlab is instructed to take a file
myconfig.txt from the directory that hosts the topology file, and copy it to the lab directory for that specific node under the
/config/startup-config.cfg name. Then the directory that hosts the startup-config dir is mounted to the container. This will result in this config being applied at startup by the node.
Configuration is applied after the node is started, thus it can contain partial configuration snippets that you desire to add on top of the default config that a node boots up with.