Skip to content

Juniper vJunosEvolved#

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

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

How to obtain the image#

The qcow2 image can be freely downloaded from the Juniper support portal without a Juniper account and built with vrnetlab.

Managing Juniper vJunosEvolved nodes#

Note

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

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

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

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

to connect to the vJunosEvolved CLI

ssh admin@<container-name/id>

NETCONF server is running over port 830

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

Info

Default user credentials: admin:admin@123

Interfaces mapping#

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 vJunosEvolved node, it will assign IPv4/6 address to the eth0 interface. These addresses can be used to reach the management plane of the router.

Data interfaces eth1+ need to be configured with IP addressing manually using CLI/management protocols or via a startup-config text file.

Features and options#

Node configuration#

Juniper vJunosEvolved nodes come up with a basic configuration supplied by a mountable configuration disk to the main VM image. Users, management interfaces, and protocols such as SSH and NETCONF are configured.

Startup configuration#

It is possible to make vJunosEvolved 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_vjunosevolved
      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 the Juniper vJunosEvolved node:

Known issues and limitations#

  • To check the boot log, use docker logs -f <node-name>.