Versions this guide is based on:

EVE Image Foldername	Downloaded Filename	Version	vCPUs	vRAM	Console	Qemu	NIC Type	Max interfaces
vjunosevo-23.1R1	vJunosEvolved-23.1R1.8.qcow2	23.1R1.8	4	8192	telnet	5.2.0	virtio	17

Instructions
Before you start: Make sure your EVE is upgraded to the latest version. EVE Community version 5.0.1-19 or later, and EVE Pro is 5.0.1-93 or later. IMPORTANT: You may need to obtain the template for this image. Please follow the lint to update your EVE templates. How to update my EVE Templates Juniper NOTE: It is strongly recommended to deploy vEVO KVM image directly on the server/hypervisor. (Bare Metal EVE). Note: vJunos-switch is not supported on EVE-NG deployments that launch vJunos from within a VM due to the constraints of deeply nested virtualization. Juniper vEVO image setup Step 1 Use your Juniper access for login and download image from: https://support.juniper.net/support/downloads/?p=vjunos Downloaded image file: vJunosEvolved-23.1R1.8.qcow2 Step 2 SSH CLI to your EVE as root and create the new image directory in: /opt/unetlab/addos/qemu/ root@eve-ng:~# mkdir /opt/unetlab/addons/qemu/vjunosevo-23.1R1 Step 3 Upload the downloaded image to the EVE newly created directoriy using FileZilla or WinSCP. vJunosEvolved-23.1R1.8.qcow2 to /opt/unetlab/addons/qemu/vjunosevo-23.1R1 Step 4 Rename original filename to EVE format, commands from EVE CLI root@eve-ng:~# cd /opt/unetlab/addons/qemu/vjunosevo-23.1R1 root@eve-ng:~# mv vJunosEvolved-23.1R1.8.qcow2 virtioa.qcow2 root@eve-ng:~# cd /opt/unetlab/addons/qemu/vjunosevo-23.1R1 root@eve-ng:/opt/unetlab/addons/qemu/vjunosevo-23.1R1# ls virtioa.qcow2 Step 5 Fix permissions root@eve-ng:~# /opt/unetlab/wrappers/unl_wrapper -a fixpermissions default login: root / no password, just enter Juniper vEVO Lab setup The device is requiring back to back cabling of PFE and RPIO. For EVE Professional you need to add single bridge network and connect ‘RPIO’ and ‘PFE’ interfacesit to the bridge via 4 links. These PFE and RPIO bridges are required for vJunosEvolved to map virtual eth interfaces correctly. Use manage EVE Pro smart-bridge feature and edit your bridge network accorgingly the settings shown below. Enable Smart Bridge and 802.1ad feature. Set the different vlan for RPIO and PFE accordingly. For EVE Community you need to add two new bridge networks per node named ‘RPIO’ and ‘PFE’, as seen below, and connect it to the node via dual links. These PFE and RPIO bridges are required for vJunosEvolved to map virtual eth interfaces correctly.

Instructions

Before you start: Make sure your EVE is upgraded to the latest version. EVE Community version 5.0.1-19 or later, and EVE Pro is 5.0.1-93 or later.

IMPORTANT: You may need to obtain the template for this image. Please follow the lint to update your EVE templates. How to update my EVE Templates

Juniper NOTE: It is strongly recommended to deploy vEVO KVM image directly on the server/hypervisor. (Bare Metal EVE). Note: vJunos-switch is not supported on EVE-NG deployments that launch vJunos from within a VM due to the constraints of deeply nested virtualization.

Juniper vEVO image setup

Step 1

Use your Juniper access for login and download image from:

https://support.juniper.net/support/downloads/?p=vjunos

Downloaded image file: vJunosEvolved-23.1R1.8.qcow2

Step 2

SSH CLI to your EVE as root and create the new image directory in: /opt/unetlab/addos/qemu/

root@eve-ng:~# mkdir /opt/unetlab/addons/qemu/vjunosevo-23.1R1

Step 3

Upload the downloaded image to the EVE newly created directoriy using FileZilla or WinSCP.

vJunosEvolved-23.1R1.8.qcow2 to /opt/unetlab/addons/qemu/vjunosevo-23.1R1

Step 4

Rename original filename to EVE format, commands from EVE CLI

root@eve-ng:~# cd /opt/unetlab/addons/qemu/vjunosevo-23.1R1
root@eve-ng:~# mv vJunosEvolved-23.1R1.8.qcow2 virtioa.qcow2

root@eve-ng:~# cd /opt/unetlab/addons/qemu/vjunosevo-23.1R1
root@eve-ng:/opt/unetlab/addons/qemu/vjunosevo-23.1R1# ls
virtioa.qcow2

Step 5

Fix permissions

root@eve-ng:~# /opt/unetlab/wrappers/unl_wrapper -a fixpermissions

default login: root / no password, just enter

Juniper vEVO Lab setup

The device is requiring back to back cabling of PFE and RPIO.

For EVE Professional you need to add single bridge network and connect ‘RPIO’ and ‘PFE’ interfacesit to the bridge via 4 links. These PFE and RPIO bridges are required for vJunosEvolved to map virtual eth interfaces correctly. Use manage EVE Pro smart-bridge feature and edit your bridge network accorgingly the settings shown below. Enable Smart Bridge and 802.1ad feature. Set the different vlan for RPIO and PFE accordingly.

For EVE Community you need to add two new bridge networks per node named ‘RPIO’ and ‘PFE’, as seen below, and connect it to the node via dual links. These PFE and RPIO bridges are required for vJunosEvolved to map virtual eth interfaces correctly.