Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Verify and Troubleshoot cJunosEvolved on Docker

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

Verify that cJunosEvolved Container is Running and Ready

  1. The docker container ls command lists the containers running on your server. The status column should show cJunosEvolved as being UP.
  2. You can use the command mentioned in this step to enter the CLI of cJunosEvolved. If the container is not yet completely up, a "not ready" message will print periodically on the host server console. You can also SSH to the management port IP.
    # docker exec -ti R1 cliroot@re0>
  3. Run standard commands such as show chassis fpc and show interfaces terse in the CLI mode to verify if the FPC is online, and if interfaces are up.

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 information is for an Ubuntu 22.04 LTS host server supporting a total of 56 CPUs (with hyperthreading enabled).

Collect Log Files

Docker Logs

The docker logs -f <container-name> command provides cJunosEvolved logs starting with its bootup logs.

EVOVM System Logs

To view the system logs, login to the EVOVM as previously described. Then run the root@re0 > show log ? command to see the list of log files available.

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 cJunosEvolved Routing Engine. These logs are the standard JunosEvolved log files that are also found on other Juniper Networks® products.

  1. Use the request system debug-info command.

    This command places all the system traces in a file named /var/tmp/ debug_collector_<date_time>.tgz

  2. Run scp command on the host server to transfer the debug_collector files to the host server.

    Example: scp admin@<management IP> :/var/tmp/debug_collector__<date_time>.tgz

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

    The /var/crash directory of the cJunosEvolved stores all the core files. You can follow the standard procedures of the Junos OS to transfer the core files cJunosEvolved-BX to an external host.