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.
virsh listThe
virsh listcommand displays the name and state of the VM. The state can be: running, idle, paused, shutdown, crashed, or dying.# virsh list Id Name State --------------------------- 72 vJunosEvo-RE1 running
-
You can stop and start the VMs with the following
virshcommands:-
virsh shutdown—Shut down the vJunosEvolved. -
virsh start—Start an inactive VM that you defined previously.
Note:Do not use the
virsh destroycommand because this commmand can corrupt the vJunosEvolved VM disk.If your VM stops and does not boot after using the
virsh destroycommand, 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.
root@vjunos-host:~# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 46 bits physical, 48 bits virtual CPU(s): 32 On-line CPU(s) list: 0-31 Thread(s) per core: 2 Core(s) per socket: 8 Socket(s): 2 NUMA node(s): 2 Vendor ID: GenuineIntel CPU family: 6 Model: 62 Model name: Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz Stepping: 4 CPU MHz: 2593.884 CPU max MHz: 3400.0000 CPU min MHz: 1200.0000 BogoMIPS: 5187.52 Virtualization: VT-x L1d cache: 512 KiB L1i cache: 512 KiB L2 cache: 4 MiB L3 cache: 40 MiB NUMA node0 CPU(s): 0-7,16-23 NUMA node1 CPU(s): 8-15,24-31 [snip]
View Log Files
View the system logs using the show log command on the
vJunosEvolved instance.
root > show log ?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-infocommand 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.