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 this release for PTX Series routers.

General Routing

  • The active-user-count is defined as a numeric integer value in ODL request output —The output for the get-system-uptime-information ODL request contains information for the active-user-count. The active-user-count is now defined as a numeric integer value and avoids an invalid value type error.

    [See show system uptime.]

  • Two new alarms are added and can be seen with MPC11E when 400G-ZR optics are used. High Power Optics Too Warm: warning of the increase in chassis ambient temperature with no functional action taken on the optics Temperature too high for optics power on: New inserted optics when the chassis ambient temperature is elevated beyond the threshold will not be powered on and would need to be reinserted when the ambient temperature is within the acceptable range

  • The packet rate and byte rate fields for LSP sensors on AFT (with the legacy path) have been renamed as jnx-packet-rate and jnx-byte-rate and is in parity with the UKERN behavior. Previously, these rate fields were named as packetRate and byteRate.

  • Single source of data for operational state sensor leaves (PTX10008)— You can use the suppress-interface-leaf CLI statement to suppress telemetry streaming of the following sensors from the packet forwarding engine (PFE): /interfaces/interface/state/high-speed /interfaces/interface/state/oper-status This might be required for collectors that require a single source of data for each sensor.

    [See suppress-interface-leaf.]

  • LSPs scale license-Starting in 22.4R3 and 23.4R1 Junos OS Evolved releases, the license counts only the Resource Reservation Protocol-Traffic Engineering (RSVP-TE) and Segment Routing Traffic Engineering (SR-TE) LSPs. Prior to the 22.4R3 and 23.4R1 Junos OS Evolved releases, license counts all Traffic Engineering (TE) such as RSVP-TE and SR-TE and non-TE such as LDP, BGP-LU, L-ISIS, L-OSPF LSPs.

  • The backup routing instance then starts index (hrStorageIndex) at 1, incrementing each time after assigning index to an entry in this list. If a mount is unmounted, the other mounts indices will not shift. hrstoragetable indices persist during the lifetime of mib2d. When a new mount is detected, it is assigned the next free index in the system. If there is no free index, it is assigned the last index +1.

  • Enhanced DDoS status operational command (PTX Series)—We've enhanced the aggregate DDoS status output field to display the aggregate count of all sub packet types.

    Earlier to this release, the aggregate DDoS status output displayed only the packet type level output information.

    [See show ddos-protection protocols.]

  • In TVP Platforms, When the FPC is configured to bring offline due to major errors, the alarm string FPC x Offlined due to Major Errors will be shown in the show chassis alarm and show system alarm output instead of FPC x Major Errors alarm.

  • Before this change most list were ordered by the sequence in which the user configured the list items, for example a series of static routes. After this change the list order is determined by the system with items displayed in numerical sequence rather than by the order in which the items were configured. There is no functional impact to this change.

  • Deprecated license revoke information—Starting in Junos OS Release 23.4R1, we've deprecated the show system license revoked-info command. You can use the show system license and show system license usage commands to know the license information.

  • While running request system snapshot recovery command on all VMHost based Routing Engines, disable or stop reporting any warning message.

Interfaces and Chassis

  • Starting in Junos OS release 23.2R1 and Junos OS Evolved release 23.2R1-EVO, the output of show chassis power command displays the state of the power supply in PTX10003 platform.

    [See show chassis power.]

Junos XML API and Scripting

  • Ability to commit extension-service file configuration when application file is unavailable—When you set the optional option at the edit system extension extension-service application file file-name hierarchy level, the operating system can commit the configuration even if the file is not available at the /var/db/scripts/jet file path.

    [See file (JET).]

  • Ability to restart daemonized applications—Use the request extension-service restart-daemonize-app application-name command to restart a daemonized application running on a Junos device. Restarting the application can assist you with debugging and troubleshooting.

    [See request extension-service restart-daemonize-app.]

  • XML output tags changed for request-commit-server-pause and request-commit-server-start (ACX Series and PTX Series)—We've changed the XML output for the request system commit server pause command (request-commit-server-pause RPC) and the request system commit server start command (request-commit-server-start RPC). The root element is <commit-server-operation> instead of <commit-server-information>, and the <output> tag is renamed to <message>.

Licensing

  • Deprecated license revoke information—Starting in Junos OS Evolved Release 23.4R1, we've deprecated the show system license revoked-info command. You can use the show system license and show system license usage commands to know the license information.

  • LSPs scale license—Starting in 22.4R3 and 23.4R1 Junos OS Evolved releases, the license counts only the Resource Reservation Protocol-Traffic Engineering (RSVP-TE) and Segment Routing Traffic Engineering (SR-TE) LSPs. Prior to the 22.4R3 and 23.4R1 Junos OS Evolved releases, license counts all Traffic Engineering (TE) such as RSVP-TE and SR-TE and non-TE such as LDP, BGP-LU, L-ISIS, L-OSPF LSPs.

    [See Software Licenses for PTX Series Routers.]

Network Management and Monitoring

  • Changes to the RPC response for <validate> operations in RFC-compliant NETCONF sessions (ACX Series and PTX Series)—When you configure the rfc-compliant statement at the [edit system services netconf] hierarchy level, the NETCONF server emits only an <ok/> or <rpc-error> element in response to <validate> operations. In earlier releases, the RPC reply also includes the <commit-results> element.

  • NETCONF <copy-config> operations support a file:// URI for copy to file operations (ACX Series and PTX Series)—The NETCONF <copy-config> operation supports using a file:// URI when <url> is the target and specifies the absolute path of a local file.

    [See <copy-config>.]

  • gNOI OS RPCs use the software version string instead of the package filename (PTX Series)—The version field in the gnoi.os.OS Activate(), Install(), and Verify() RPCs uses the software version string (as displayed in /system/state/software-version) instead of the package name.

  • Simplified gRIBI configuration—Starting in Junos OS Evolved Release 23.4R1, we have simplified the configuration to run gRPC Routing Information Base Interface (gRIBI) service remote procedure calls (RPCs). You no longer need to configure statements at the [edit routing-options resolution] hierarchy level.

    [See gRIBI.]

Routing Protocols

  • In Junos OS Evolved platforms, show route snooping and show route forwarding-table does not show /56 routes in the VPLS address family table.

  • Before this change most list were ordered by the sequence in which the user configured the list items, for example a series of static routes. After this change the list order is determined by the system with items displayed in numerical sequence rather than by the order in which the items were configured. There is no functional impact to this change.

  • Starting in Junos OS Evolved 23.4R1, we have enabled the process-non-null-as-null-register configuration statement under edit protocols pim rp local by default. For earlier releases, you must configure this statement explicitly.

Software Installation and Upgrade

  • configuration and no-configuration options for the request system snapshot command (ACX Series and PTX Series)—When you omit or include the configuration option, the request system snapshot command copies the /config directory and the configuration stored for each installed software version to the alternate solid-state drive (SSD) as part of the snapshot. You can use the no-configuration option to exclude the /config directory and the configuration stored for each installed software version from the snapshot.

User Interface and Configuration

  • Information about users editing system configuration— The show system configuration database status command displays information from the Junos OS configuration database that describes the users currently editing the system configuration.

    [See Display Users Currently Editing the Configuration.]

  • Output for request system software status | display xml validate has a tag mismatch error (all platforms)—The output contains the error message CRITICAL ERROR: Root tag 'package-status' is either not defined in ODL or does not have 'flag root' set. Please check. Rendering may not work properly. We have removed the improperly defined package-status tag and replaced it with a new child tag package-status-message.

  • Starting in Junos OS Evolved 23.4R1, you need not set up passwordless communication explicitly by issuing request security ssh password-less-authentication command for transfer-on-commit and syslog archival operation over scp.

  • Viewing files with the file compare files command requires users to have maintenance permission— The file compare files command in Junos OS and Junos OS Evolved requires a user to have a login class with maintenance permission.

    [SeeLogin Classes Overview.]