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 changed in Junos OS Evolved Release 19.2R1 for the PTX10003.

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 libsi.so.0 library with the etenv LD_PRELOAD libsi.so.0 command and then running the file with python filename.py.

    [See extension-service (System Extensions).]

  • Change in output for the show system uptime command (PTX10003)—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.]

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

    [See commit (System).]

General Routing

  • Output MPLS filters not supported (PTX10003)—The PTX10003-80C router does not support MPLS firewall filters that are applied on the output interface.

    [See filter (Applying to an Interface).]

  • Junos OS Evolved does not support use of an interactive password (PTX10003)—You must set up the password-less login between two devices to use jcs:open to open a connection to the remote device using junoscript, netconf, junos-netconf. if you do not, junoscript, netconf, and junos-netconf fail with following error:

  • Change in empty regex results (PTX10003)—When the regular expression is to return empty matches, no error is thrown.

  • 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).]

Interfaces and Chassis

  • DSCP action is not supported when a filter is bound to the input of the lo0 interface (PTX10003)—In Junos OS Evolved Release 19.2R1, on the PTX10003 device, when a filter with DSCP is bound to the input of the lo0 interface, a commit error occurs.

  • Management interface name changed (PTX10003)—In Junos OS Evolved, the management interface name is mgmtre0.

    [See Understanding Management Ethernet Interfaces.]

  • Change in what happens when a new interface is added as a member to an AE bundle (PTX10003)—In Junos OS Evolved when a new interface is added to an AE bundle, the physical interface is deleted as a regular interface and then added back in as an AE member. This differs from how this is handled in Junos OS: When a new interface is added as a member to an AE bundle, the child interface is not deleted and added but every thing below it is.

    [See open() Function (SLAX and XSLT).]

Routing Policies and Firewall Filters

  • Change in behavior for matching fragmented packets (PTX10003)—In Junos OS Evolved, all fragmented packets, including the first fragment of a fragmented packet, will match on a firewall filter term containing an "is-fragment" match. This is slightly different behavior compared to other Junos platforms in which the first fragment of fragmented packets do no match on a firewall filter term containing an "is-fragment" match.

    [SeeFirewall Filter Match Conditions for IPv4 Traffic.]

System Management

  • Messages logged when using the restart command—Starting in Junos OS Evolved Release 19.2R1, The following message will be logged when restart command is used:

    App restarting <app name>. Related apps that may be impacted - <related-app name> .

    For example: Jan 14 11:42:08 RE0 sysman[5100]: SYSTEM_APP_RESTARTING_WITH_RELAPPS_EVENT: App restarting re0-ifmand. Related apps that may be impacted - aggd

  • 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.]

User Interface

  • View core-dump files (PTX10003)—Use the request system core-dump command instead of the request system live-core command.

    [See show system core-dumps.]

  • Change in error message (PTX10003)—For op scripts run with the max-datasize statement configured for the minimum, an error occurs. In Junos OS Evolved, the error is "Out of memory." In Junos OS, the error is "Memory allocation failed."

    [See max-datasize.]