Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

What’s Changed


Learn about what’s different in behavior and syntax in Junos OS Evolved for 19.2R1.

Changes in CLI Statements and Commands

  • To see the list of CLI statements and commands changed in Junos OS Evolved, see How Junos OS Evolved Differs from Junos OS in the Introducing Junos Os Evolved Guide.

  • The [edit system extensions extension-service] configuration is deprecated (Junos OS Evolved)—This configuration was used to configure and run Junos extension service scripts (e.g., Python scripts) from the CLI. You can run the same scripts from the shell mode by preloading library with the etenv LD_PRELOAD command and then running the file with python

    [See extension-service (System Extensions).]

  • Change in output for the show system uptime command (QFX5220)—The show system uptime command is a little different in how it displays output in Junos OS Evolved. The show system uptime command by itself shows system-wide uptime information.

    [See show system uptime.]

General Routing

  • Support for full inheritance paths of configuration groups to be built into the database by default (PTX10003 and QFX5220)—Starting with Junos OS Evolved Release 19.2R1, the persist-group-inheritance option at the [edit system commit] hierarchy level is enabled by default. To disable this option, use no-persist-groups-inheritance.

    [See commit (System).]

System Management

  • Change in where core-dump files are stored—For Junos OS Evolved, a core-dump file during early bootup is stored in /var/core/re. But a core-dump file later in the bootup, for example, after the Routing Engine slot number can be determined, is stored in /var/core/re0 or /var/core/re1. The command show system core-dumps continues to show all cores generated.

    [See show system core-dumps.]