Alert Type

SRN - Software Release Notification
Low/NotificationSoftware Release Notification
Low/NotificationSoftware Release Notification

Product Affected

ACX PTX QFX running Junos Evolved software

Alert Description

Junos Software Service Release version 23.2R2-S6-EVO is now available for download from the Junos software download site

Download Junos Software Service Release:

  1. Go to Junos Platforms - Download Software page
  2. Input your product in the "Find a Product" search box
  3. From the Type/OS drop-down menu, select Junos SR
  4. From the Version drop-down menu, select your version
  5. Click the Software tab
  6. Select the Install Package as need and follow the prompts

NOTE: Starting on August 30th, 2024, we include PR's severity with each entry. See KB86335 [juniper.net] for the definition of PR's Severity

Junos Selective Update (JSU) feasible

Not applicable

Call to Action

For your review

Solution

Junos Software service Release version 23.2R2-S6-EVO is now available.

23.2R2-S6-EVO - List of Fixed issues

PR NumberSynopsisCategory: Border Gateway Protocol
1898734
Major		The rpd process crashes in an Inter-AS Option-AB L3VPN with BGP multipath list-nexthop enabled
Product-Group=evo
Severity=Major		On all Junos and Junos OS Evolved platforms, in an Inter-AS (Autonomous System) Option-AB L3VPN (Layer3 Virtual Private Network) scenario, if 'bgp multipath list-nexthop' is configured and a VRF (Virtual Routing and Forwarding) generates a route with list-nexthop that is advertised to an Option-AB peer, the rpd process crashes and generates a core-dump.
1907391
Major		Routes are hidden when accept-own feature is enabled with rib-sharding
Product-Group=evo
Severity=Major		On MX480 and MX960 platforms, routes become hidden when the "accept-own" feature is enabled in environments configured with rib-sharding. This issue arises when the "vrf-table-label" is configured within a routing instance and route sharding is enabled, potentially leading to routing failures.
PR NumberSynopsisCategory: PFE COS features on BT based platforms
1856528
Major		Missing traffic statistics via telemetry on PTX EVO platforms with MPC10E, MPC11E, and LC9600 line cards
Product-Group=evo
Severity=Major		On PTX EVO platforms equipped with MPC10E, MPC11E, or LC9600 line cards, when telemetry monitoring is enabled and the sensor /junos/system/linecard/interface/traffic/ is subscribed to, some entries for interface traffic statistics might be missing. This occurs due to an issue where the volume of telemetry data per interface can lead to message fragmentation, resulting in incomplete data export.
PR NumberSynopsisCategory: MX304 Chassis specific platform
1905954
Critical		memory leak caused by using the "show ccl statistic summary ... " command
Product-Group=evo
Severity=Critical		On Junos OS and Junos OS Evolved platforms, running the command "show ccl statistic summary ... " cause memory leaks in the Packet Forwarding Engine (PFE).
PR NumberSynopsisCategory: EVO Netstack FIB Service Daemon
1814970
Minor		fibd crash is seen after excessive logging in scaled scenarios
Product-Group=evo
Severity=Minor		On all Junos Evolved platforms, in scaled scenarios, excessive logging by the Routing Protocol Process (rpd) or other applications that manage protocols can lead to a Forwarding Information Base Process (fibd) crash.
PR NumberSynopsisCategory: EVO L2 Control Plane PRs
1899530
Major		MAC learning failure when moving the AE interface from one VLAN to another VLAN in a single commit
Product-Group=evo
Severity=Major		On Junos OS Evolved platforms, when an Aggregated Ethernet (AE) logical interface (IFL) is moved from one Virtual LAN (VLAN) to another VLAN in a single commit, Layer 2 forwarding tables fail to update correctly. This causes Media Access Control (MAC) learning failure and traffic disruption.
PR NumberSynopsisCategory: Lacp related problems and issues.
1898531
Major		AE interfaces flap during GRES following an RE reboot on all Junos Evolved platforms
Product-Group=evo
Severity=Major		On all Junos Evolved platforms, Aggregate Ethernet (AE) interfaces with LACP configured will experience a flap due to a timing issue when Graceful Routing Engine Switchover (GRES) is performed after a Routing Engine (RE) reboot, resulting in traffic loss during the flap.
PR NumberSynopsisCategory: Configd, ffp issues
1900883
Major		Traffic loss occurs due to missing apply-path handling during reboot or configd restart
Product-Group=evo
Severity=Major		On platforms running Junos OS Evolved 20.2R1-EVO and later releases, apply-path configurations with wildcards after leaf nodes are not evaluated correctly during reboot or configd restart. This is due to missing special handling required for evaluating such configurations during reboot and configd restart, this causes failure of routing and forwarding functions that rely on apply-paths, leading to traffic loss post reboot or configd restart.
PR NumberSynopsisCategory: FIPS related issues
1871858
Minor		The device is in a reboot loop when fips mode is enabled
Product-Group=evo
Severity=Minor		On all Junos platforms, after loading the image where FIPS (Federal Information Processing Standards) mode is already enabled, the FIPS self-test may fail and the device may encounter a reboot loop.
PR NumberSynopsisCategory: ACX7509 Platform related issues
1907310
Major		After RE switchover on the device, the capacity of DC PSM is observed to be zero after toggling the input power
Product-Group=evo
Severity=Major		On all Junos OS Evolved platforms, whenever a Routing Engine (RE) switchover occurs and the DC input supply to one of the Power Supply Modules (PSMs) is toggled or flapped, the output capacity of that PSM becomes zero. If the remaining PSMs are unable to provide sufficient power to the chassis, all Flexible PIC Concentrators (FPCs) go offline, resulting in traffic impact.
PR NumberSynopsisCategory: ACX7509 timing related issues
1892751
Minor		On Junos OS Evolved ACX7509 system's clock break synchronization
Product-Group=evo
Severity=Minor		On Junos OS Evolved ACX7509 platforms, clockd uses an older API to communicate with the Zarlink DPLL (Digital Phase-Locked Loop) timing registers, and because this API lacks proper locking, it can impact Zarlink register synchronization and lead to time-synchronization issues for PTP (Precision Time Protocol) and SyncE (Synchronous Ethernet).
PR NumberSynopsisCategory: Port-based link layer security services and protocols that a
1911538
Major		Show command execution failure for show system macsec license on MX platforms
Product-Group=evo
Severity=Major		On all Junos MX10004, MX10008, MX304, MX301 platforms on executing the command "show system maces license" fails and doesn't fetch any information however it doesn't cause any service disruption. This is a Day-1 issue.
PR NumberSynopsisCategory: Category for tracking Olympus-MX issues
1906557
Major		While collecting RSI, takes long time to produce output on MX platform
Product-Group=evo
Severity=Major		On MX platforms, the cli output for 'show services nat source summary' can take a long time to execute on a highly scaled environment. The issue aggravates when collecting RSI (request support information) and it takes more than an hour for the process to complete. In few instances, this also led to other processes like SNMP monitoring getting stuck.
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1907558
Major		The rpd process crashes in a vrf having EVPN-VXLAN routes with specific configuration.
Product-Group=evo
Severity=Major		In all Junos and Junos OS Evolved platforms, when EVPN-VXLAN (Ethernet Virtual Private Network-Virtual Extensible LAN) routes are present in a VRF (Virtual Routing and Forwarding), configuring a generate route in same vrf can cause rpd (Routing Protocol Daemon) to crash and restart. Generate route configuration has to be removed to recover from this behaviour.
PR NumberSynopsisCategory: Resource Reservation Protocol
1896022
Major		More bandwidth admitted onto a TE link when Label Switched Paths (LSPs) undergoing make-before-break re-route over the same link carrying the bypass LSP during local repair
Product-Group=evo
Severity=Major		On all Junos and Junos evolved platforms with Point of Local Repair Router, in a Multiprotocol Label Switching(MPLS) Label Switched Paths (LSPs) set-up if the ingress router is configured with link-protection , if Label Switched Paths (LSPs) undergo local repair and subsequently undergo global repair in make-before-break fashion such that the LSPs are re-routed over the same TE link that carries the bypass LSP that protect the LSPs during local repair, then more re-routed LSPs may be admitted on the TE link carrying the bypass LSP than that should be admitted. This may result in some re-routed LSPs remaining on the TE link causing additional traffic sent on the TE link than the capacity of the TE link.
PR NumberSynopsisCategory: ACX724 platform issues
1895749
Critical		System crashes due to a CPU glitch
Product-Group=evo
Severity=Critical		On Junos Evolved ACX7024 and ACX7024X platforms, the system crashes, and a kernel crash is generated due to a random CPU error.
PR NumberSynopsisCategory: ACX7000 platform software related issues.
1889258
Minor		SSD firmware for both primary & secondary SSD is not displayed
Product-Group=evo
Severity=Minor		SSD firmware for both primary & secondary SSD is not displayed
PR NumberSynopsisCategory: Express ZX PFE L3 Features
1914060
Major		Ipv4/ipv6 ingress filters are not applied for mpls explicit null traffic on PTX10003
Product-Group=evo
Severity=Major		On Junos OS Evolved PTX10003 platforms, IPv4 or IPv6 ingress filters are not applied to Multiprotocol Label Switching (MPLS) packets carrying an explicit NULL label with IPv4 or IPv6 payloads. This occurs due to ingress packet classification, where MPLS explicit NULL packets are processed as MPLS traffic instead of native Internet Protocol (IP) traffic. As a result, configured IPv4/IPv6 ingress filter actions are not executed, leading to unexpected traffic handling and reduced effectiveness of configured policies

 

 

23.2R2-S6-EVO - List of Known issues

PR NumberSynopsisCategory: EVO interface software
1878198
Major		Link flapping occurs on stable subinterfaces when using QDD400GZR optics if any one subinterface in the channelized group is down
Product-Group=evo		On all Junos OS Evolved platforms that support the QDD-400G-ZR coherent optical transceiver modules (400G-ZR and 400G OpenZR+), when an interface is equipped with any of these optics and configured in breakout mode, if anyone of the sub-interfaces in the group is administratively up and operationally down, the remaining stable sub-interfaces in the same group experience the link flaps at a regular interval.

Resolved In: evo:23.2R2-S4-J2-EVO evo:23.4R2-S4-J2-EVO evo:23.4R2-S4-J31-EVO evo:23.4R2-S6-EVO evo:24.2R2-J7-EVO evo:24.2R2-S2-EVO evo:24.4R2-EVO evo:24.4R2-S3-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:25.4R1
PR NumberSynopsisCategory: Border Gateway Protocol
1875834
Major		On switchover on ACX7509, L3VPN some of the prefixes traffic hit is around 1-5secs
Product-Group=evo		On switchover on ACX7509, L3VPN some of the prefixes traffic hit is around 1-5secs. Some of the prefixes seen traffic drop in terms of seconds after NSR switchover and issue is not consistent. It is not a continuous traffic drop and it recovers.

Resolved In:
PR NumberSynopsisCategory: PFE L2 forwarding features on BT based platforms
1890878
Major		On PTX EVO platforms in EVPN-VXLAN scenario traffic will not egress out of the irb next-hop when the bridge-domain doesn't have VXLAN VNI configured
Product-Group=evo		On all PTX Evolved platforms that support EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN), when the PTX router acts as a MAC-VRF (Media Access Control - Virtual Routing and Forwarding) EVPN gateway, it will fail to forward traffic routed through the 'irb' interface due to packets being discarded at PFE (packet forwarding Engine), causing packet loss.

Resolved In: evo:22.4R3-S8-EVO evo:23.4R2-S6-EVO evo:24.2R2-S3-EVO evo:24.4R2-EVO evo:24.4R2-S1-EVO evo:25.2R1-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO
PR NumberSynopsisCategory: Express PFE FW Features
1876672
Major		SCU/DCU match is not working when configured along with the forwarding-class
Product-Group=evo		On PTX Junos OS Evolved platforms, the SCU/DCU (Source class usage/ Destination class usage) match is not working when it is configured along with the forwarding-class.

Resolved In: evo:22.3X80-D49-EVO evo:23.4R2-S6-EVO evo:24.2R2-S3-EVO evo:24.4R2-S1-EVO evo:24.4X200-D20-EVO evo:25.2R1-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO
PR NumberSynopsisCategory: N/A:sw-qfx5k-evo-macsec:
1903384
Major		QFX5700:MACsec traffic loss might occur on specific traffic streams inspite of successful SAK rekeying and MACsec session establishment
Product-Group=evo		QFX5700:MACsec traffic loss might occur on specific traffic streams inspite of successful SAK rekeying and MACsec session establishment

Resolved In:
PR NumberSynopsisCategory: Issues related to NETCONF
1879816
Major		GNMI get native configuration garbage reply when there is no configuration related to openconfig
Product-Group=evo		The native configuration is observed when there is no configuration related to openconfig but if there are configuration related to openconfig, the native config is not seen. This is just a corner case and no service impact is observed.

Resolved In: evo:24.4R2-EVO evo:25.2R1-S1-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:24.4R2 junos:25.2R1-S1 junos:25.2R2 junos:25.2X30 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: PRs related to PICd and associated lib WAN side PI code.
1748138
Major		Port speed delete is resulting in setting the it to the default speed
Product-Group=evo		On all Junos OS Evolved platforms, if any other speed apart from the default speed is configured on any interface, then on deleting the configured speed, it will not set to the default speed.

Resolved In: evo:23.4R2-EVO evo:24.2R1-EVO

 

Modification History

First publication 2026-01-16