What's Changed

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

For firewall filter action and match on slice ID, family-name can be inet, inet6, mpls, or any.PR1742998

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.

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.

Disable the integrity check value (ICV) indicator type, length, and value (TLV) on the MKA protocol to enable MACsec sessions—By default, the ICV indicator is enabled. In most networks, when MACsec is configured, devices ignore the ICV TLV and establish a MACsec session instead. In networks that do not establish a MACsec session when the ICV TLV is enabled, use the disable-icv-indicator option at the [edit security macsec connectivity-association ca-name mka] hierarchy level to disable the ICV TLV and allow the network to establish the MACsec session. To confirm the ICV TLV is disabled, use the show security mka sessions detail command. [See mka and show security mka sessions.]PR1743300

Changes to XML output for MACsec operational commands—We have changed the XML output for the following MACsec operational commands (and the corresponding RPCs) so that they emit valid XML.

• show security mka sessions brief ? — A new session-common element encloses each set of information for each session.

• show security mka sessions detail ? — A new session-live element encloses the state of the interface.

• show security mka sessions summary ? — A new mka-session-terse tag encloses the set of tags for each session.

• show security macsec connections ? — A new macsec-interface-common-information element encloses the set of tags for each connection.

• show security mka statistics ? — A new mka-interface-statistics element encloses each interface's protocol statistics.

[See show security mka sessions, show security macsec connections, and show security mka statistics.]PR1744564

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.

New commit check for MAC-VRF routing instances with the encapsulate-inner-vlan statement configured—We introduced a new commit check that prevents you from configuring an IRB interface and the encapsulate-inner-vlan statement together in a MAC-VRF routing instance. Please correct or remove these configurations prior to upgrading to 23.2R2 or newer to avoid a configuration validation failure during the upgrade.

[See encapsulate-inner-vlan.]PR1768407

ephemeral-db-support statement required to configure MSTP, RSTP, and VSTP in the ephemeral configuration database (ACX Series, EX Series, and QFX Series)—To configure Multiple Spanning Tree Protocol (MSTP), Rapid Spanning Tree Protocol (RSTP), or VLAN Spanning Tree Protocol (VSTP) in the ephemeral configuration database, you must first configure the ephemeral-db-support statement at the [edit protocols layer2-control] hierarchy level in the static configuration database.

[See Enable and Configure Instances of the Ephemeral Configuration Database.]PR1769383

Change in options and generated configuration for the EZ-LAG configuration IRB subnet-address statement—With the EZ-LAG subnet-address inet or subnet-address inet6 options at the [edit services evpn evpn-vxlan irb irb-instance] hierarchy, you can now specify multiple IRB subnet addresses in a single statement using the list syntax [ addr1 addr2 ... ]. Also, in the generated configuration for IRB interfaces, the commit script now includes default router-advertisement statements at the [edit protocols] hierarchy level for that IRB interface.

[See subnet-address (Easy EVPN LAG Configuration).]PR1773375

When all the members of the AE have the same speed (x) and no mixed speed configured. If you change the speed value of any member of the AE to a value other than x, the commit succeeded in earlier releases. From this release, the commit fails. When there are et interfaces with different speeds and you want them to be part of an AE interface. If you change the speed of all the members of the interfaces to be the same speed (x), configure the AE interface, and commit, the commit failed in earlier releases. From this release, such commits succeed.PR1745893

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

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

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

DDoS syslog messages enhancement (MX Series devices with MPC10, MPC11, LC4800, or LC9600 line cards)—We've enhanced the severity of the DDoS module syslog messages ddos_get_vbf_ifl_from_flow_id and ddos_get_vbf_ifl_name in a subscriber management environment. In earlier releases, these syslog messages displayed incorrect messages in a subscriber management environment when you enable suspicious control flow detection (SCFD).

[See Control Plane DDoS Protection Flow Detection Overview.]PR1737034

Two-Way Active Measurement Protocol (TWAMP) server/reflector test traffic classified by the ingress filter was re-classified with the values configured on the host-outbound-traffic configuration statement (All Junos OS Evolved platforms; MX Series platforms with MPC10E, MPC11E, or JNP10K-LC9600 cards)—We no longer re-classify the egress TWAMP traffic. We now maintain the same queue for the packets in the egress direction that the packets had in the ingress direction.PR1739935

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.

TI-LFA and Legacy LFA Configuration Commit Validation Update (Junos OS and Junos OS Evolved)—You can now enable TI-LFA and legacy FRR (node-link-protection) in separate OSPF instances. The system generates a commit error only if you enable both TI-LFA and legacy FRR under the same OSPF instance. In that case, the commit fails and triggers the following message: "error: commit failed: (statements constraint check failed)".

[See Topology-Independent Loop-Free Alternate with Segment Routing for IS-IS and OSPF.]PR1718886

BGP Multipath route calculation—When configuring multipath in the routing-instance, BGP routes that are inactive due to cluster-list length are also considered as eligible for multipath calculations. This enhances route selection by including more potential paths in your multipath configuration.

[See Understanding BGP Path Selection.]PR1719797

Prior to this change the output of the show isis spring flex-algorithm | display xml command was invalidly formatted when multiple flex algorithm instances were configured. With the change, the XML output is properly structured showing flex algorithm information for each instance. A new XML tag "isis-spring-flex-algorithm" is added to bundle information for each instance.PR1722352

BGP Multipath State Information in show route extensive Command (Junos OS and Junos OS Evolved)—The show route extensive command now includes per-prefix BGP multipath state information. This update provides detailed insight into BGP multipath state for the prefix and enhances network troubleshooting for more effective diagnostics and issue resolution.

[See show route extensive.]PR1729787

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

Separate prefix value for micro-SID and classic SSID locator—If micro SIDs and static SIDs are configured with the same prefix value, the commit fails. Do not use the same prefix value for micro SIDs and static SIDs.PR1738160

Correction in show bgp neighbor Output (Junos OS and Junos OS Evolved)—We corrected a typo in the show bgp neighbor command output where configrued was displayed instead of configured. We've also added the existing option AcceptedPrefixLimit to the output so it displays when configured. This improvement ensures accurate display of the configuration settings and provides additional information for monitoring and managing BGP neighbor configurations.

[See show bgp neighbor.]PR1740982

[BGP BFD Strict Mode and Holddown Configuration Issue (Junos OS)]?We?ve identified an issue with the BGP BFD strict mode where, if a router is configured with BFD strict mode and a holddown interval, and the peer router does not have these configurations, the BGP session remains in the idle state indefinitely. This occurs because the router with the strict configuration waits for the BFD session to establish, while the peer router waits for the BGP session to establish. To avoid this issue, ensure that both routers are consistently configured with BFD strict mode and holddown intervals. [See {https://www.juniper.net/documentation/us/en/software/junos/bgp/topics/topic-map/bfd-for-bgp-session.html#id-understanding-bfd-for-bgp__d58e80}BFD strict mode for BGP peer sessions.]PR1749221

Changed Advertisement of Argument-Length Values (Junos OS and Junos OS Evolved)—Argument-Length (AL) values calculation formula has been updated to 128 - (Block-Length + Node-Length + Function-Length). This change aligns the system with updated standards, promoting smoother interoperability across network devices. No configuration changes are required from the users' side.PR1750434

Commands for Viewing Transport-Class and Resolution Scheme Information (Junos OS and Junos OS Evolved)—We've introduced the show route transport-class command to view transport-class information and show route resolution scheme command to view custom resolution schemes for route next-hop resolution.

[See show route transport-class and show route resolution scheme.]PR1757468

BGP Neighbor Telemetry Statistics (Junos OS and Junos OS Evolved)—BGP neighbor statistics reported through telemetry are now always aggregated, regardless of whether rib-sharding is enabled. Previously, when sharding was active, statistics were streamed per shard. With the current behavior, sensors are installed appropriately, and statistics are aggregated in the main thread before being streamed. The controllers and collectors now receive a single, unified view of BGP neighbor statistics.PR1765189

Port Mirroring Configuration Update—Interface ranges are no longer supported as part of configuration groups for creating analysers. If you attempt to use an interface-range in a config group, you will encounter an error indicating an invalid interface type. Additionally, interface ranges or interface lists cannot be configured under this setting. This change ensures precise and error-free configuration by requiring the specification of individual interfaces rather than ranges, thus improving the accuracy and reliability of port mirroring setups.PR1728883

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

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

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