Skip to content

Juniper vMX#

Juniper vMX virtualized router is identified with juniper_vmx kind in the topology file. It is built using vrnetlab project and essentially is a Qemu VM packaged in a docker container format.

Juniper vMX nodes launched with containerlab come up pre-provisioned with SSH, SNMP, NETCONF and gNMI services enabled.

Managing Juniper vMX nodes#

Note

Containers with vMX inside will take ~7min to fully boot.
You can monitor the progress with docker logs -f <container-name>.

Juniper vMX node launched with containerlab can be managed via the following interfaces:

to connect to a bash shell of a running Juniper vMX container: 

docker exec -it <container-name/id> bash

to connect to the vMX CLI 

ssh admin@<container-name/id>

NETCONF server is running over port 830 

ssh admin@<container-name> -p 830 -s netconf

using the best in class gnmic gNMI client as an example: 

gnmic -a <container-name/node-mgmt-address> --insecure \
-u admin -p admin@123 \
capabilities

Info

Default user credentials: admin:admin@123

Interface naming#

vMX nodes use the interface naming convention ge-0/0/X (or et-0/0/X, xe-0/0/X, all are accepted), where X denotes the port number.

Info

Data port numbering starts at 0, like one would normally expect in the NOS.

Interfaces mapping#

You can use interfaces names in the topology file like they appear in Juniper vMX.

The interface naming convention is: et-0/0/X (or ge-0/0/X, xe-0/0/X, all are accepted), where X denotes the port number.

With that naming convention in mind:

  • et-0/0/0 - first data port available
  • et-0/0/1 - second data port, and so on...

Note

Data port numbering starts at 0.

The example ports above would be mapped to the following Linux interfaces inside the container running the Juniper vMX VM:

Juniper vJunosEvolved container can have up to 17 interfaces and uses the following mapping rules:

  • eth0 - management interface connected to the containerlab management network
  • eth1 - first data interface, mapped to a first data port of vJunosEvolved VM, which is et-0/0/0 and not et-0/0/1.
  • eth2+ - second and subsequent data interface

When containerlab launches Juniper vMX node the management interface of the VM gets assigned 10.0.0.15/24 address from the QEMU DHCP server. This interface is transparently stitched with container's eth0 interface such that users can reach the management plane of the Juniper vMX using containerlab's assigned IP.

Data interfaces et-0/0/0+ need to be configured with IP addressing manually using CLI or other available management interfaces.

Features and options#

Node configuration#

Juniper vMX nodes come up with a basic configuration where only the control plane and line cards are provisioned, as well as the admin users and management interfaces such as NETCONF, SNMP, gNMI.

Starting with hellt/vrnetlab v0.8.2 VMX will make use of the management VRF1.

Startup configuration#

It is possible to make vMX 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: juniper_vmx
      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.

Lab examples#

The following labs feature Juniper vMX node:

Known issues and limitations#

  • when listing docker containers, Juniper vMX containers will always report unhealthy status. Do not rely on this status.
  • vMX requires Linux kernel 4.17+
  • To check the boot log, use docker logs -f <node-name>.

  1. https://github.com/hellt/vrnetlab/pull/98 ↩