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 MX Series routers.

Class of Service (CoS)

  • You cannot apply a classifier to a physical interface on MX Series routers. On MX Series routers, you must apply the classifier to a logical interface.

  • Changes to the XML output for CoS RPCs (MX204, MX240, MX304, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, MX2020)—We've updated the junos-rpc-class-of-service YANG module and the corresponding Junos XML RPCs to ensure that the RPC XML output conforms to the YANG schema. As a result, we changed the XML output for the following class of service (CoS) RPCs:

    • <get-cos-adjustment-control-profile-information>—The <adjustment-control-profile-name> tag is a child of the <adjustment-control-profile> element instead of a sibling.

    • <get-cos-red-information>—The <red> tag no longer emits the xmlns="m-t-mx-j-series-cosinfo-red-entry-format" namespace attribute.

    • <get-cos-slice-information>—The XML output only emits integers for parameters such as <shaping-rate>, <delay-buffer-rate>, and similar fields. The output does not include any units.

    • <get-scheduler-map-table-map-information>—The <cos-scheduler-map-table-information> tag does not emit a namespace attribute.

EVPN

  • EVPN-VXLAN tracing configuration—The set services trace evpn-vxlan configuration invokes a built-in commit script to generate tracing configurations for troubleshooting EVPN-VXLAN in multiple modules and hierarchies.

    [See trace (EVPN-VXLAN).]

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

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

  • Support for podman-based JDM deployment—Starting in Junos OS Release 23.2R1, the external server-based Junos node slicing supports deployment of Juniper Device Manager (JDM) using the Pod Manager tool (podman). This change is applicable to servers running Red Hat Enterprise Linux (RHEL) 9. In Junos releases prior to 23.2R1, Junos node slicing supported RHEL 7.3 that provided libvirt?s lxc driver (libvirt-lxc) to deploy JDMs.

  • In older Junos OS Releases, Data Definition Language (DDL) lists were ordered by the sequence in which the user configured the list items, for example a series of static routes. With 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.

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

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

  • Introduction of extensive option for IPsec security associations (MX Series, SRX Series and vSRX 3.0)—We've introduced the extensive option for the show security ipsec security-associations command. Use this option to display IPsec security associations with all the tunnel events. Use the existing detail option to display upto ten events in reverse chronological order.

    [See show security ipsec security-associations.]

  • Change in the XML tags displayed for the show virtual-network-functions command in JDM (Junos node slicing) — To align the XML tags displayed for the show virtual-network-functions "gnf-name"| display xml with the new XML validation logic, we have replaced the underscores (_) in the output with hyphens (-) as shown below:

    Old output:

    This change is applicable to any RPC that previously had underscores in the XML tag name.

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

  • XML output tags changed for request-commit-server-pause and request-commit-server-start (ACX Series, EX Series, MX Series, QFX Series, SRX Series, and vSRX)—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>.

Network Management and Monitoring

  • NETCONF <copy-config> operations support a file:// URI for copy to file operations (ACX Series, EX Series, MX Series, QFX Series, SRX Series, and vSRX)—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>.]

Platform and Infrastructure

  • Previously, shaping of Layer 2 pseudowires did not work on logical tunnel interfaces. This has been fixed for all platforms except QX chip-based MICs and MPCs.

Routing Protocols

  • After this change ISIS export policies support setting the down bit configuring the "set-down-bit" action in an export policy term.

User Interface and Configuration

  • XML output tags changed for request-commit-server-pause and request-commit-server-start (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, and vSRX)—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.

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

    [See Login Classes Overview.]