Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Verify vJunosEvolved on KVM

SUMMARY Use this topic to verify your vJunosEvolved configurations and for any troubleshooting information.

Verify That the VM is Running

  • Verify whether vJunosEvolved is running after you install it.

    The virsh list command displays the name and state of the VM. The state can be: running, idle, paused, shutdown, crashed, or dying.

  • You can stop and start the VMs with the following virsh commands:

    • virsh shutdown—Shut down the vJunosEvolved.

    • virsh start—Start an inactive VM that you defined previously.


    Do not use the virsh destroy command because this commmand can corrupt the vJunosEvolved VM disk.

    If your VM stops and does not boot after using the virsh destroy command, then create a live QCOW2 disk copy of the original QCOW2 image provided.

Verify CPU Information

On the host server, use the lscpu command to display CPU information.

The output displays information such as the total number of CPUs, the number of cores per socket, and the number of CPU sockets.

For example, the following codeblock information is for an Ubuntu 20.04 LTS host server supporting a total of 32 CPUs.

View Log Files

View the system logs using the show log command on the vJunosEvolved instance.

The root > show log ? command displays the list of log files available for viewing.

For example, to view the EVO init logs, run the root> show log evoinit.log command.

The log files can be viewed from the /var/log directory of the vJunosEvolved RE. These logs are the standard vJunosEvolved log files that are also found on other Juniper Networks® products. The serial console can be used to log in to the Routing Engine VM. Alternatively, you can SSH to the Routing Engine VM and view the same information.

Some of the key log files collected are the following:

  • Use the request system debug-info command to transfer all the system traces in a file named /var/tmp/debug_collector_<date_time>.tar.gz

  • /var/log/cosim.log and /var/log/cosim_ppd.log: COSIM traces during initialization.

Collect Core Files

Use the show system core-dumps command to view the collected core files. You can transfer these core files to an external server for analysis through the management interface on the Routing Engine.

The /var/crash of the directory of the JunosEvolved Routing Engine stores all the core files. You can follow the standard procdures of the Junos OS to transfer the core files vJunosEvolved Routing Engine to an external host.