Alert Type

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

Product Affected

ACX PTX QFX platforms running Junos Evolved software

Alert Description

Junos Software Service Release version 23.2R2-S5-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

Please review

Solution

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

23.2R2-S5-EVO - List of Fixed issues

PR NumberSynopsisCategory: EVO Debug collector
1868326
Major
FPC commands repeatedly prompt for a password and fail when debug-collector is run by non-root users
Product-Group=evo
Severity=Major
On all Junos EVO platforms, when debug-collectors are run by non-root users the flexible physical interface card concentrators (FPC) commands repeated prompt for passwords. The commands will fail to run though the password is provided.
PR NumberSynopsisCategory: Issues with pluggable optics
1883912
Major
2x100G-LR4 optical modules based on CMIS 4.0 and above won't intialize properly
Product-Group=evo
Severity=Major
All 2x100G-LR4 modules based on CMIS 4.0 and above require new SFF 8024 codes for the CAUI-4 host interface for initialization. This change does not apply to CMIS 3.X modules. All Junos Evolved platforms, including PTX, ACX, QFX, and Junos-based platforms such as MX304 and MX with MPC11/LC9600/LC4800 line cards, are impacted by this issue.
1888506
Major
Support for new CMIS 4.0-compliant 2x100G-LR4 optics on Junos Evolved/ULC Platforms
Product-Group=evo
Severity=Major
Junos Evolved and ULC platforms now support CMIS 4.0+ compliant 2x100G-LR4 optics using updated host electrical interface codes (e.g., 100GAUI-4) as defined in SFF-8024. This enhancement enables proper optic detection and initialization for newer modules.
1890558
Major
Mismatch between configured and reported wavelength for some optics
Product-Group=evo
Severity=Major
On all Junos OS Evolved platforms and MX paltforms with MPC11E / LC9600 line cards , the issue is seen with optics that doesn't support 6.25GHz spacing. There is a mismatch seen between the configured and the reported wavelength. The wavelength mismatch will lead to the loss of signal and thus result in impact on the traffic.
PR NumberSynopsisCategory: Border Gateway Protocol
1842955
Critical
Route validation sync status remains incomplete when sharding is enabled
Product-Group=evo
Severity=Critical
On all Junos and EVO platforms, When we have No-stop routing configured on the router, and route-validation is turned on, we see route-validation sync to be in Not-started state in show task replication output.
1851205
Major
Junos OS and Junos OS Evolved: When route validation is enabled, route validation cache connection establishment leads to an rpd crash (CVE-2025-52958)
Product-Group=evo
Severity=Major
A Reachable Assertion vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent, unauthenticated attacker to cause a Denial of Service (DoS). Please refer to https://supportportal.juniper.net/JSA100066 [juniper.net] for more information.
1853025
Major
Updating a source-file to load ROAs should be done by changing the name of the source file
Product-Group=evo
Severity=Major
Loading ROAs from a source-file was a feature introduced as a convenience feature and as such this only affects that feature. This feature is not in widespread use and was created to have a fallback ROA when all sessions go down. This problem scenario requires multiple reloads with the being modified back and forth to add and then delete and re-add the database configured in the import policy.
1857801
Major
Memory leak is observed when "graceful-shutdown" is configured
Product-Group=evo
Severity=Major
On all Junos and Junos Evolved platforms with Border Gateway Protocol (BGP) "graceful-shutdown" configured, memory leak is observed. This issue does not cause traffic impact.
1877261
Major
BGP updates missing graceful-shutdown community after quick sender knob flaps
Product-Group=evo
Severity=Major
On all Junos and Junos Evolved platforms, when the graceful-shutdown sender knob is repeatedly deleted and subsequently re-added in quick intervals under a BGP-LU (Border Gateway Protocol-Labeled Unicast) session, the router CLI (command line interface) incorrectly indicates that the graceful-shutdown community is being advertised. However, the actual BGP update messages sent over the session do not include the graceful-shutdown community. This results in the graceful-shutdown community not being propagated to BGP peers during graceful shutdown events, which will potentially cause traffic forwarding issues.
1877288
Major
rpd crash when changes are applied to as-path with dynamic-db in use
Product-Group=evo
Severity=Major
On Junos OS platforms using as-path-groups (Autonomous System Path Group) with dynamic-db (dynamic Data base) feature enabled, rpd (Routing Protocol Daemon) may crash after as-path configuration changes.
1881717
Major
Incorrect MPLS label derivation with inactive EBGP route advertisement
Product-Group=evo
Severity=Major
On Junos and Junos Evolved platforms, MPLS (Multiprotocol Label Switching) forwarding issues may occur when labels are assigned from a locally preferred IBGP (Interior Border Gateway Protocol) route, while an inactive EBGP (Exterior Border Gateway Protocol) route is advertised via Add-Path or advertise-external. When per-prefix-label allocation is either explicit or via SRGB(Segment Routing Label Block), this mismatch can result in incorrect label forwarding.
1887911
Major
The rpd process crashes after BGP configuration commits involving group-split-size and RIB-sharding
Product-Group=evo
Severity=Major
On Junos and Junos OS Evolved platforms, configuring "group-split-size" with BGP RIB-sharding(Border Gateway Protocol Routing Information Base Sharding) can lead to a crash in the routing protocol daemon (rpd) when a route update for a non-negotiated NLRI(Network Layer Reachability Information) is received in the update thread. This occurs if the NLRI is targeted at other BGP peers within the group that have negotiated it.
PR NumberSynopsisCategory: Express BT PFE L3 Features
1784498
Minor
Higher AE traffic convergence observed in ALB configured AE interface
Product-Group=evo
Severity=Minor
On PTX10001-36MR/PTX10004/PTX10008 and PTX10016 platforms, if Adaptive load balancing (ALB) is configured on AE (Aggregated Ethernet) interface and link up/down, the AE interfaces will take higher traffic convergence during FRR (Fast Reroute) compared to regular AE.
PR NumberSynopsisCategory: DNX L2 related features
1742136
Minor
Traffic impact is seen on Junos OS Evolved ACX7K platforms due to an evo-pfemand process crash after the FPC restart or system reboot
Product-Group=evo
Severity=Minor
The FPC (Flexible PIC Concentrator) restart or system reboot causes evo-pfemand process crash on Junos OS Evolved ACX7K platforms. Forwarding traffic will be affected here.
1886421
Minor
VSTP convergence failure on Junos OS Evolved ACX7K when IRB shares bridge domain with VSTP enabled IFL
Product-Group=evo
Severity=Minor
On all Junos Evolved ACX7K platforms, when a VLAN Spanning Tree Protocol (VSTP) enabled Layer 2 logical interface (IFL) shares a bridge domain with an Integrated Routing and Bridging (IRB) interface, VSTP fails to converge due to Spanning Tree Protocol (STP) packets are misrouted to the IRB interface, preventing them from reaching the VSTP process. This causes potential traffic loops due to lack of VSTP convergence.
PR NumberSynopsisCategory: ACX IFL, IFF creation
1891275
Major
Framing error observed on AE interface after performing RE switchover on Junos OS Evolved ACX7509 platform
Product-Group=evo
Severity=Major
Continuous increase in framing errors observed on AE interface after doing RE switchover on Junos OS Evolved ACX7509 platform.
PR NumberSynopsisCategory: DNX VPLS
1896785
Major
Traffic loss observed after routing engine reboot or core interface flap on ACX7K platforms
Product-Group=evo
Severity=Major
On all Junos OS Evolved ACX7K Platforms, Layer 3 traffic loss can occur after an RE (Routing Engine) reboot or core interface flap due to a race condition between ARP (Address Resolution Protocol) and VPLS (Virtual Private LAN Service) programming.
PR NumberSynopsisCategory: Firewall related development
1875725
Minor
The firewalld process crashes post specific set of filter related modifications performed in single commit
Product-Group=evo
Severity=Minor
On Junos EVO platforms, When Firewall Filter change involved both delete and change to new filter on an interface in a single commit resulted in Firewalld coredump
PR NumberSynopsisCategory: Binding Queue
1859621
Minor
SNMP walk failure due to missing OID after FCO/TPA delete compression
Product-Group=evo
Severity=Minor
On all PTX Junos and Junos evolved platforms, an issue occurs when performing SNMP walks, resulting in the error No Such Instance currently exists at this OID. This is caused by a lifecycle management problem involving FCO (Factory Configuration Object) and TPA (Third-Party Attachment) objects. Specifically, when both FCO (IFDO) and TPA (IfSnmpInfo) are deleted in quick succession, only the FCO delete notification is sent, skipping the FCO modification callback that the TPA would typically trigger a delete event. As a result, the SNMP index mapping associated with the TPA is not properly updated, leading to missing entries during SNMP walks.
PR NumberSynopsisCategory: software upgrade infra issues
1867902
Major
Software upgrade aborts or FPC does not come online on specific Junos Evolved PTX platforms while upgrading with an option validate-restart or add restart
Product-Group=evo
Severity=Major
1. Software upgrade failure is observed on specific to Junos OS Evolved PTX platforms (PTX10004/PTX10008/PTX10016/PTX12K) when 'request system software validate-restart' or 'request system software add restart' is used to perform software upgrade and the base and target image have different IMA (Integrity Measurement Architecture) keys or successful 'request system software add restart', followed by a second 'request system software add restart' will fail and there is a low disk space issues on FPC. 2. FPC is not coming online on specific to Junos OS Evolved PTX platforms (PTX10004/PTX10008/PTX10016/PTX12K) when reboot is performed post installing an image with 'request system software add restart' and the base and target image have different IMA keys.
PR NumberSynopsisCategory: Interface PRs defect & enhancement requests
1875917
Major
Disabling a single AE IFL in a MAC-VRF can bring the entire AE interface down
Product-Group=evo
Severity=Major
On all Junos Evolved platforms, under MAC-VRF routing configurations, when any Layer 3 IFL is deactivated, it causes the associated AE interface to go administratively down, leading to complete traffic disruption across the AE bundle.
1882754
Major
AE interface speed mismatch causes link down and missing command outputs on Junos OS Evolved platforms
Product-Group=evo
Severity=Major
On all Junos OS Evolved platforms, when the AE (Aggregated Ethernet) interface is configured with a link-speed different from its member interfaces, it results in a misconfiguration. Due to this, the link between devices goes down, causing disruption in traffic forwarding.
PR NumberSynopsisCategory: jdhcpd daemon refactored for evo
1816246
Major
[ACX7000 Series] DHCPv4/v6 packets may be dropped because DHCP packets are not routed to kernel after initial jdhcpd starts
Product-Group=evo
Severity=Major
Under certain conditions, the DHCP session database becomes unstable or JDHCPD not getting IFL/IFD events which cause DHCP packets to fail to route to the kernel and then leads to DHCP packet drop.
PR NumberSynopsisCategory: EVO Netstack Juniper Tunnel Driver Module
1865403
Major
Memory leak is observed when Telemetry is configured
Product-Group=evo
Severity=Major
On all Junos and Junos Evolved platforms having Telemetry configured, the memory allocations in 512 bytes slab that are seen to be growing in problem state, are related to write on a unix domain socket (internal to application). Since the data is not read, the send buffer keeps growing and the associated memory does not gets released. Every telemetry response from the producer does a 1 byte write on this socket and over a period of time the send buffer gets full. The default size of the unix socket send buffer is set to 512MB. But there is no functional impact.
PR NumberSynopsisCategory: EVO L2 Control Plane PRs
1853879
Major
The IRB VGA is not shown after deleting one of the IRB interfaces with the same VGA address configured
Product-Group=evo
Severity=Major
On Junos OS Evolved platforms, when two different IP addresses under an IRB interface are configured with the same virtual-gateway-address (VGA), and one of the IP addresses is deleted, the VGA IP address gets cleaned up in the router/switch resulting in traffic loss in the remaining address entry.
1874476
Major
Transient traffic loss for CE in an EVPN MPLS setup with Multi-Homing
Product-Group=evo
Severity=Major
On Junos and Junos Evolved platforms with EVPN MPLS, Multi-Homing scenarios, when there is a Multi-Homing peer node reboot, the destination route entries that were learned locally on IRB(Integrated Routing and Bridging) interface of rebooted node get deleted on other multi-homing peers without RE-ARP (Routing Engine-Address Resolution Protocol) causing transient traffic loss for CE (Customer Edge) traffic.
1889335
Minor
Traffic drop is observed in an EVPN multihoming as the MAC route points to the ESI interface when the CE (ESI) IFD flaps
Product-Group=evo
Severity=Minor
On all Junos and Junos Evolved platforms, in an Ethernet Virtual Private Network (EVPN) MultiHoming setup with Ethernet Segment Identifier (ESI) configured under logical Interface (IFL) (CE-facing), when the corresponding IFD (Physical Interface) flaps, the MAC route will point to the ESI interface, while it should point to the Multihoming CE (Customer Edge) interface. This results in traffic loss.
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1848993
Major
The data plane will be out of sync when migrating to EVPN A/A stitching with Vanila VXLAN (PIM Multicast)
Product-Group=evo
Severity=Major
On MX platforms, to improve the convergence of node failures in EVPN MH interconnects with Data Plane VXLAN, migrating to an Active-Active setup may cause the data plane to become out of sync for ARP entries. The gateway learns the MAC address and advertises it to the peer gateway. However, on the peer gateway, some MAC-IP entries may remain stuck in the 'Unresolved' (Ur) state.
PR NumberSynopsisCategory: Common PR category for all EVO AFT based L2 features related issues on Express platforms
1890125
Major
In scale EVPN scenario with IRB, host traffic via IRB will be impacted ICMP, OSPF, BGP and L3 protocols on Junos Evolved OS PTX series platform
Product-Group=evo
Severity=Major
On Junos OS Evolved PTX series platforms, in a scale EVPN (Ethernet Virtual Private Network) scenario with IRB (Integrated Routing and Bridging), the traffic via IRB will be impacted ICMP, OSPF, BGP and L3 protocols.
PR NumberSynopsisCategory: Express pfe ddos protection feature
1734892
Major
Junos OS Evolved: PTX Series: When a firewall filter rejects traffic these packets are erroneously sent to the RE (CVE-2025-59958)
Product-Group=evo
Severity=Major
An Improper Check for Unusual or Exceptional Conditions vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS Evolved on PTX Series allows an unauthenticated, network-based attacker to cause impact to confidentiality and availability. Please refer to https://supportportal.juniper.net/JSA103147 [juniper.net] for more information.
PR NumberSynopsisCategory: Enhanced Broadband Edge support for firewall
1883530
Critical
FPC crash is seen on certain Junos platforms when firewall filter is configured for subscribers
Product-Group=evo
Severity=Critical
On MX platforms with MPC10E, MPC11E, LC9600 line-cards and MX304 with subscriber-management enabled, Flexible PIC Concentrator (FPC) crashes in a rare scenario and crash files are generated when filters are configured for subscribers . This will lead to traffic impact since the line-card reboots and subscribers are re-logged.
PR NumberSynopsisCategory: ACX7509 platform, FEB, RCB and linecaard resi
1891967
Major
The fetched firmware version results an incorrect value on ACX7509
Product-Group=evo
Severity=Major
On Junos OS Evolved ACX7509 platforms, firmware version mismatch alarm is observed. This occurs in rare scenarios and results in incorrect display issue.
PR NumberSynopsisCategory: ACX7509 Linecard (FPC) related issues
1885937
Major
Interface on mismatch speed configuration flaps
Product-Group=evo
Severity=Major
After system boot, continuous link flaps are observed if the optics are configured with an incorrect speed, typically 1G or 10G. However, when the correct speed is set on both ends (DUT and peer end), the link comes up normally without further flapping. This issue has been seen specifically with SFP+ optics (10G/1G) when mismatched speeds are configured. For example, configuring 1G speed for an SFP-10G-SR module results in link flaps instead of the link remaining down.
1893886
Major
Auto-negotiation mismatches leading to connectivity issues on Junos OS Evolved ACX7509, ACX7332, and ACX7348 platforms
Product-Group=evo
Severity=Major
On Junos OS Evolved ACX7509, ACX7332, and ACX7348 platforms having auto-negotiation is configured on a 1G interface, connectivity issues will occur under certain conditions: system reboots or FPC (Flexible PIC Concentrator) restarts or changes in auto-negotiation settings on the peer side. In these scenarios, ARP (Address Resolution Protocol) resolution will fail due to a mismatch in the auto-negotiation state between the local and peer interfaces. The local interface will incorrectly appear as UP, while the peer interface shows as DOWN, leading to link-level inconsistencies and loss of connectivity.
1898908
Major
The other port in a port group goes down after an RE switchover if one of the port in the port group is already down on an ACX7509
Product-Group=evo
Severity=Major
On Junos OS Evolved ACX7509 platforms, when one port in a channelized group (like ports 0 in a port group consisting of port 0 and port 1) is already in 'down' state in a ACX7509-FPC-16C with 16x100G-QSFP, performing a Routing Engine (RE) switchover or restarting the picd process can cause the other port in the port group to go down. This will lead to disruption of services running on the port.
PR NumberSynopsisCategory: ACX7509 Platform related issues
1848468
Minor
ACX7509 and QFX5700 may report SSD DMA error on secondary disk.
Product-Group=evo
Severity=Minor
ACX7509 and QFX5700 may report below SSD DMA error on secondary disk. In most cases there is no operational impact observed. Aug 26 04:16:02 test-re0 kernel: ata2.00: exception Emask 0x0 SAct 0x8000000 SErr 0x0 action 0x6 frozen Aug 26 04:16:02 test-re0 kernel: ata2.00: failed command: READ FPDMA QUEUED Aug 26 04:16:02 test-re0 kernel: ata2.00: cmd 60/f8:d8:08:5a:06/01:00:03:00:00/40 tag 27 ncq dma 258048 in res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Aug 26 04:16:02 test-re0 kernel: ata2.00: status: { DRDY } Aug 26 04:16:03 test-re0 kernel: print_req_error: I/O error, dev sdb, sector 50747912 flags 80700 New firmware being packaged into software via this PR fix will resolve this issue.
PR NumberSynopsisCategory: ACX7509 platform, FEB, RCB and linecaard resi
1846199
Major
Device will not boot from secondary disk
Product-Group=evo
Severity=Major
On Junos OS Evolved platforms, the system may access the backup SSD (/dev/sdb) frequently which will reduce the useful life of the SSD.
PR NumberSynopsisCategory: ISIS routing protocol
PR NumberSynopsisCategory: Multiprotocol Label Switching
1859219
Major
RSVP-TE LSP path is not re-optimised to the path with best IGP metric
Product-Group=evo
Severity=Major
On all Junos and Junos Evolved platforms, when RSVP-TE (Resource Reservation Protocol - Traffic Engineering) is configured with MBB (make-before-break) setup, if the protected link of the primary LSP (Label Switched Path) goes down and if "clear mpls lsp" or "clear rsvp session" commands are executed, then LSP switches to new instance from the old which will be on higher IGP (Interior Gateway Protocol) metric. However, after re-optimization, LSP will not get switched to better IGP metric path and remain in old instance. Traffic drop can be seen due to this double fault events.
PR NumberSynopsisCategory: KRT Queue issues within RPD
1868085
Major
The rpd process crashes and asserts are seen due to memory leak
Product-Group=evo
Severity=Major
On all Junos and Junos Evolved platforms, rpd process crashes and asserts are seen due to a memory leak when BGP sharding is enabled and 'show route' is performed continuously.
PR NumberSynopsisCategory: Issues related to krt-async routing infrastructure
1866522
Major
VPLS session stays down after interface flaps
Product-Group=evo
Severity=Major
An LSI IFL remains in RPD even after being deleted by the interface manager daemon. It is visible in show interface routing but not in show interfaces, indicating that RPD still holds the IFL despite its removal elsewhere. rpd-agent does not send a delete message to RPD due to a reference count issue. Another daemon?likely l2ald?still holds a reference to the IFL. rpd-agent only sends the delete once all references are cleared, which doesn't happen in this case. The fix is to send a "delete pending" message from rpd-agent to RPD. RPD will treat this as a delete and remove the IFL, ensuring consistency across the system.
PR NumberSynopsisCategory: Shard routing infrastructure within RPD
1854481
Minor
The rpd gets struck with 100% CPU usage after enabling BGP RIB-Sharding
Product-Group=evo
Severity=Minor
On all Junos OS and Junos OS Evolved platforms , enabling the BGP RIB-Sharding causes the routing protocol daemon (rpd) leading to spike and remain at 100% CPU usage due to a background task ( such as the Route Target/User Interface (RT/UI) delete job ) entering into the continuous processing cycle and looping behaviour.
PR NumberSynopsisCategory: Resource Reservation Protocol
1866944
Major
Traffic blackholing in LSPs due to link failure before protection signalling is processed
Product-Group=evo
Severity=Major
On all Junos and Junos OS Evolved platforms, traffic blackholing occurs on MPLS (Multi-Protocol Label Switching) Label Switched Paths (LSPs) when link protection is enabled, under specific conditions during link failure events that occur just after the LSP is established.
PR NumberSynopsisCategory: PTX10K platform specific fabric PRs
1900242
Critical
Fabric link OAM fault detected after upgrade to 23.2R2-S4-EVO
Product-Group=evo
Severity=Critical
On a PTX10016, and possibly PTX10008, the router will show fabric link OAM fault causing the system to not function properly.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1842868
Major
XML namespace string in rpc-reply tag for system-uptime-information was changed to represent the full version name.
Product-Group=evo
Severity=Major
XML namespace string in rpc-reply tag for system-uptime-information was changed to represent the full version name.
PR NumberSynopsisCategory: Issues related to Logging/Tracing, errmsg, eventd infrastruc
1848106
Major
The eventd process crash occurs due to flooding of out of memory logs
Product-Group=evo
Severity=Major
On all Junos and Junos OS Evolved platforms, eventd process crashes is observed. This happens when eventd process is processing the flooding of out of memory logs generated by any of the processes running on FPC (Flexible PIC Concentrator). This is traffic impacting depending on the process with memory issues.
PR NumberSynopsisCategory: Virtual Private LAN Services
PR NumberSynopsisCategory: Express ZX PFE L3 Features
1842666
Minor
IPv6 Neighbor Discovery Packets Punted to RE Instead of Transiting via Core Interface
Product-Group=evo
Severity=Minor
In a cross-connect (L2Circuit) scenario, IPv6 Neighbor Advertisement (NA) and Neighbor Solicitation (NS) packets originating from the CE side are being punted to the Routing Engine (RE) instead of passing through the L2Circuit over the core interface.

 


 

23.2R2-S5-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.4R2-S4-J31-EVO evo:23.4R2-S6-EVO evo:24.2R2-J7-EVO evo:24.2R2-S2-EVO evo:24.4R2-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:25.4R1
PR NumberSynopsisCategory: Border Gateway Protocol
1875144
Minor
Longer convergence is seen for a BGP neighbor having validation configured in its import policy
Product-Group=evo
On all Junos and Junos Evolved platform, when any BGP peer has validation policy configured for import, it is observed that there is an extra walk to re-evaluate the routes in the loc-rib for validation even though the policy/unrelated configuration is changed for an unrelated peer.

Resolved In: evo:23.2R2-S4-J2-EVO evo:23.4R2-S4-J2-EVO evo:23.4R2-S5-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:22.4R3-S6-J11 junos:22.4R3-S7 junos:23.4R2-S5 junos:24.2R2-S2-J6 junos:24.2R2-S3 junos:24.4R2 junos:25.2R1 junos:25.3R1
1889749
Major
BGP Prefix-SID Label collision causing RPD crash
Product-Group=evo
On all Junos and Junos OS Evolved platforms, In Segment Routing the RPD ( Routing Protocol Daemon ) crash was observed due to different prefixes were trying to use same label, when Bgp prefix SID ( Segment Identifier ) feature was configured and labels were derived using the SID index.

Resolved In: evo:24.2R2-S3-EVO evo:25.2R1-S1-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:21.2R3-S8-J22 junos:23.2R2-S6 junos:25.2R1-S1 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: Issues related to EVO dependency layer including object graphs, incompletes, anomalies and nkdb
1874151
Critical
Rare assert with an Junos Evolved process
Product-Group=evo
This is a rare chance of a process panic. This can be seen in Evo apps. If seen in forwarding apps it can result in system reboot and resulting traffic loss.

Resolved In: evo:22.3X80-D49-EVO evo:23.4R2-S6-EVO evo:23.4X100-D31-EVO evo:24.2R2-S1-EVO evo:24.2R2-S2-EVO evo:24.4R1-S3-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: Interface PRs defect & enhancement requests
1898055
Minor
Unexpected commit failure will be observed when deactivating of unit or changing any configuration and performing a commit operation
Product-Group=evo
On Junos OS Evolved platforms, if input-vlan-map and output-vlan-map are configured, an unexpected commit failure may occur when deactivating a unit (e.g., unit ) or making any configuration changes followed by a commit operation. This issue results in commit failure errors and prevents further configuration changes.

Resolved In: evo:23.4R2-S6-EVO evo:24.2R2-S3-EVO evo:24.4R2-S1-EVO evo:25.4R1-EVO
PR NumberSynopsisCategory: EVO Socket replication
1895827
Major
Adding a new key to authentication-key-chain causes kernel crash
Product-Group=evo
On all Junos Evolved platforms, when setting/changing the tolerance value of key-chain to max value of 4294967295 and committing and then adding a new key to a key-chain and performing a commit action will result in kernel crash. Device self-recovers after the crash. "show system core-dumps" can be used to check the core. Core name starts with vmcore*

Resolved In: evo:23.4R2-S6-EVO evo:24.2R2-S3-EVO evo:24.4R2-S1-EVO evo:25.2R2-EVO evo:25.4R1-EVO junos:22.4R3-S8 junos:23.2R2-S5 junos:23.4R2-S6 junos:24.2R2-S3 junos:24.4R2-S1 junos:25.2R1-S1 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1858750
Critical
Route change is not synced after rpd restart due to rib-fib inconsistency
Product-Group=evo
On all Junos OS Evolved platforms, after rpd (Routing Protocol Daemon) restart, the route change is not sent from routing daemon RIB(Routing Information Base) to forwarding plane FIB (Forwarding Information Base). This results in traffic drop.

Resolved In: evo:22.3X50-EVO evo:22.3X80-D49-EVO evo:23.4R2-S4-EVO evo:23.4X100-D40-EVO evo:24.2R2-S1-EVO evo:24.2R2-S2-EVO evo:24.4R1-S2-EVO evo:24.4R2-EVO evo:24.4X200-D10-EVO evo:25.2R1-EVO junos:23.4R2-S4 junos:24.2R2-S2 junos:24.4R1-S2 junos:24.4R2 junos:25.1R1 junos:25.2R1
PR NumberSynopsisCategory: Resource Reservation Protocol
1893822
Major
Record Route Object displayed in show mpls lsp output is trucated if number of hops is sixteen or more
Product-Group=evo
If the number of RSVP LSP hops is sixteen or higher, the RRO displayed in show mpls lsp extensive output may get truncated

Resolved In: evo:23.4R2-S4-J2-EVO evo:24.2R2-S3-EVO evo:24.4R2-EVO evo:25.2R1-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:22.4R3-S7-J1 junos:22.4R3-S8 junos:23.2R2-S5 junos:24.2R2-S3 junos:24.4R2 junos:25.2R1-S2 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: PTX10K Line Card specific interface PRs
1835757
Minor
snmp mib walk on jnxDomCurrentLaneRxLaserPower any OID under XcvrDiagLaneData does not show object instance values for all lanes except lane 0
Product-Group=evo
On all Junos Evolved platforms having SNMP configured, snmpwalk output is suppose to print for all lanes and snmp index. However, last interface's snmp index printed out only lane 0 value and skipped all other lanes when applicable.

Resolved In: evo:23.4R2-S3-EVO evo:24.2R2-EVO evo:24.4R1-EVO evo:24.4R2-EVO evo:25.1R1-EVO junos:24.2R2 junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: ZT/YT pfe infra issues
1796344
Minor
PacketIO PFE process will drop small fragments of TCP and UDP packets destined to the routing engine
Product-Group=evo
On platforms running PacketIO PFE process (MPC10E, MPC11E, MX10K-LC9600, MX304 and all Junos OS Evolved platforms), small fragments of TCP and UDP packets destined to the routing engine will be dropped.

Resolved In: evo:23.4R2-S4-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:25.4R1-EVO junos:20.3X75-D46 junos:21.2R3-S9 junos:21.2X35 junos:21.4R3-S5-J4 junos:23.2R2-S5 junos:23.4R2 junos:24.2R1 junos:24.2R2 junos:24.3R1 junos:24.4R2
PR NumberSynopsisCategory: Configuration mgmt, ffp, load-action, commit processing
1751574
Major
Netconf RPC commit fails due to commit warning received for unprotect operation, CLI commit completes with warning
Product-Group=evo
In Netconf private edit configuration session, commit RPC fails when unprotect operation is performed.

Resolved In:
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1704406
Major
XML validation failure may be seen with the "show host | display xml validate" command
Product-Group=evo
The XML output of "show host| display xml validate" command results in the "WARNING: Received the tag , the output may not have been properly xmlized." error.

Resolved In:
PR NumberSynopsisCategory: Virtual Private LAN Services
1885690
Major
RPD core seen sometimes on switchover @ l2vpn_vpls_auto_site_primary_new_site
Product-Group=evo
On switchover, sometimes we have seen RPD core with BT l2vpn_vpls_auto_site_primary_new_site

Resolved In:

 

Modification History

First publication 2025-10-30