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 ACX 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

  • 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 is shown in the show chassis alarm and show system alarm output instead of FPC x Major Errors alarm.

Interfaces and Chassis

  • ACX7509: In the CLI using the command request chassis feb slot slot-number offline if you make the primary FEB offline, a traffic loss warning message is displayed and the FEB offline request is rejected. If offline or restart is still intended for primary FEB, use force option in addition to the command.

    WARNING message displayed in the CLI: warning: RCB and FEB work in the paired slot mode. FEB %s offline/restart will result in traffic loss and does not cause a switchover. Please re-try after initiating a mastership switchover using request chassis routing-engine master switch CLI.

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.

Network Management and Monitoring

  • Support for NETCONF event notifications filtering and interleave capabilities (ACX7100-32C and ACX7100-48L)—NETCONF clients can specify top-level filters when they subscribe to NETCONF event notifications. Additionally NETCONF sessions support the interleave capability, which enables a NETCONF client to receive NETCONF event notifications and execute NETCONF requests in the same session.

    [See NETCONF Event Notifications.]

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

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

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

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