Alert Type

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

Product Affected

QFX platforms running Junos Software

Alert Description

Junos Software Service Release version 24.4R2-S1 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 24.4R2-S1 is now available.

24.4R2-S1 - List of Fixed issues

PR NumberSynopsisCategory: ISSU
1900759
Major		EX4650/QFX5120-48Y: ISSU fails with reason "error Host OS is not compatible; in-service-upgrade cannot continue"
Product-Group=junosvae
Severity=Major		EX4650/QFX5120-48Y: ISSU fails with reason "error Host OS is not compatible; in-service-upgrade cannot continue"
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=junos
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.
PR NumberSynopsisCategory: EVPN control plane issues
1846266
Major		The inet filters attached to the IRB interface will not function as expected
Product-Group=junos
Severity=Major		On Junos QFX5k and EX4k platforms, in an Ethernet VPN-Virtual Extensible LAN (EVPN-VXLAN) scenario, inet filters applied to Integrated Routing and Bridging (IRB) interfaces will not function as expected, and the associated actions of the filter are not enforced.
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=junos
Severity=Major		On Junos 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: Express PFE L2 fwding Features
1884163
Major		IFL Memory Leak on QFX10K8/16 device
Product-Group=junos
Severity=Major		On QFX10K8/16 , IFL memory is not freed on non-local interface of FPC during configuration changes (eg: IFL delete/deactivate) for L3IFL/L2IFL on AE/Scalar interfaces. Fix is present in common code and risky. It is a day one issue and the per IFL leak is minimal (0.00016% of total Kernel heap size) .
PR NumberSynopsisCategory: Integrated Routing & Bridging (IRB) module
1871420
Major		Fragmented packets dropped in EVPN-MPLS scenario due to the IRB interface MTU limitation
Product-Group=junos
Severity=Major		On all Junos platforms running in EVPN-MPLS (Ethernet Virtual Private Network over Multiprotocol Label Switching) scenarios, host-generated packets exceeding the IRB interface MTU (Maximum Transmission Unit) are fragmented. Only the first fragment is forwarded, while remaining fragments are dropped, leading to loss of control-plane traffic.
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1895433
Minor		The enable-pxe-boot is not working as expected on specific EX or QFX platforms with Easy EVPN LAG single home server topology
Product-Group=junos
Severity=Minor		The enable-pxe-boot option does not work as expected for Easy EVPN LAG (Ethernet Virtual Private Network Link Aggregation Group) single home server topology configuration on specific EX or QFX platforms. The enable-pxe-boot configuration knob does not generate the "force-up" configuration. Consequently, the physical link remains down until "force-up" is manually added on physical child interface. It causes LACP (Link Aggregation Control Protocol) to go down when singled homed server is added with LACP.
PR NumberSynopsisCategory: Multicast for L3VPNs
1902405
Major		The rpd process crash is observed with MVPN and RIB sharding enabled
Product-Group=junos
Severity=Major		On Junos platforms, with RIB sharding enabled, and if either IPv4 or IPv6 address family is disabled in MVPN (multicast virtual private network), the unicast route flow from the shard tries to access MVPN data structures without validation, leading to rpd (Routing Protocol Daemon) process crash.
PR NumberSynopsisCategory: OS IPv4/ARP/ICMPv4
1881956
Major		IPv6 default route gets deleted from FIB by slaac daemon after an upgrade with an unsupported configuration
Product-Group=junos
Severity=Major		On all Junos OS platforms , deletion of IPv6 default route from FIB (Forward Information Base) by slaacd (Stateless Address AutoConfiguration Daemon ) is observed while recovering the device from amnesiac state after the OS upgrade with any unsupported or incompatible configuration.
PR NumberSynopsisCategory: Kernel Tunnel Interface Infrastructure
1897240
Major		Chassis-Control restart triggers when configuring GRE interface across multiple routing-instances leading to kernel crash
Product-Group=junos
Severity=Major		On Junos series devices, the kernel crash occurs when creating and configuring a identical GRE(Generic Routing Encapsulation) interface across different routing-instances.
PR NumberSynopsisCategory: Paradise pfe ddos protection feature
1828196
Major		Error messages are seen due to high CPU utilization
Product-Group=junos
Severity=Major		On Junos platforms (non-AFT based), error messages are seen with the operations that involve high CPU utilization on the RE and/or FPC. This issue has no impact on traffic.
PR NumberSynopsisCategory: QFX analyzer, sflow
1850213
Minor		L3 multicast traffic not forwarded when multi-homing node is acting as source in VXLAN
Product-Group=junos
Severity=Minor		When Group Based Policy (GBP) is enabled on Junos OS and Junos OS Evolved, Layer 3 multicast traffic originating from a Multi-homing (MH) source node is not forwarded.
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1895903
Major		Traffic loss will be observed when VPLAG is configured on Junos QFX5k and EX4k platforms
Product-Group=junos
Severity=Major		On Junos QFX5k and EX4k platforms, if VPLAG(Virtual Private Link Aggregation group) is configured and if there is event change which could make ECMP(Equal Cost Monitoring Protocol) programming to change like ECMP link flap, dcpfe restart, system reboot etc which causes traffic loss.
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platfom issues
1902869
Critical		Significant system slowness is observed post software upgrade on QFX5120-48YM
Product-Group=junosvae
Severity=Critical		On QFX5120-48YM devices, after performing a software upgrade to versions containing the fix for PR1882472, users may observe significant system slowness immediately following the first boot. This slowness manifests as degraded performance across multiple system parameters, including increased reboot time, slower interface initialization, and longer service restoration periods.
PR NumberSynopsisCategory: KRT Queue issues within RPD
1830588
Critical		The rpd process crashes on all Junos and Junos OS Evolved platforms when recursively resolved routes are changed or deleted
Product-Group=junos
Severity=Critical		On all Junos and Junos OS Evolved platforms when recursively resolved routes are changed or deleted, route churn will potentially lead to the rpd process crash.
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1815837
Minor		Configure low file size in traceoptions while logging volume is high will lead to high CPU and RPD scheduler slips causing operational impact
Product-Group=junos
Severity=Minor		If the file size is too small and the amount of traceoptions volume is too high it can cause scheduler slips and operational impact.
PR NumberSynopsisCategory: Resource Reservation Protocol
1896022
Major		More bandwidth may be 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=junos
Severity=Major		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: UI Infrastructure - mgd, DAX API, DDL/ODL
1873253
Major		The "show system storage" command output should show only true and distinct storages
Product-Group=junos
Severity=Major		On all Junos platforms, the "show system storage" command output is modified to list only all real UFS filesystem ie { 'ffs', 'tmpfs', 'ufs' } instead of virtual filesystem like '/var/jails/rest-api'.

 

 

24.4R2-S1 - List of Known issues

PR NumberSynopsisCategory: Software build tools (packaging, makefiles, et. al.)
1900881
Major		EX2300 While installing junos net image, device got stucked in loader prompt
Product-Group=junos		On the EX2300 platforms, using the net image to upgrade a switch may results in the switch unable to complete the software upgrade.

Resolved In:
PR NumberSynopsisCategory: ISSU
1898501
Major		EX4650/QFX5120-48Y: ISSU incompatibility with previous releases
Product-Group=junos		EX4650/QFX5120-48Y: Older releases (that do not contain the 1882472 fix) are ISSU incompatible with current releases that have 1882472 fix.

Resolved In:
PR NumberSynopsisCategory: "agentd" software daemon
1820119
Major		Sensor data is not streamed via gNMI
Product-Group=junos		On all Junos Evolved Platforms, sensor data is not streamed via gNMI.

Resolved In: evo:22.3R3-S4-EVO evo:22.3X50-EVO evo:22.3X80-D45-EVO evo:22.3X80-D46-EVO evo:22.4R0-J0-EVO evo:22.4R3-S5-EVO evo:23.2R2-S3-EVO evo:24.2R1-S2-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO evo:25.1R1-EVO junos:22.3R3-S4 junos:22.3X60 junos:22.4R3-S4 junos:22.4R3-S5 junos:22.4X4 junos:22.4X50 junos:23.2R2-S3 junos:23.4R2-S3 junos:23.4X30-D30 junos:24.2R1-S1 junos:24.2R2 junos:24.2X1 junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: BBE multicast related issues
1882756
Major		The bbe-smgd process crash triggered by a multicast event failure
Product-Group=junos		On all MX platforms with Broadband Edge Subscriber Management configured, the bbe-smgd process crashes when the multicast sync service add publish fails. This crash is automatically recovered by the system without requiring manual intervention.

Resolved In: evo:25.3R1-EVO junos:25.3R1
PR NumberSynopsisCategory: BBE subscriber PFCP
1891388
Major		BNG User Plane: Changing the BNG Controller name is allowed with subscribers on the user-plane
Product-Group=junos		BNG user plane: Changing the BNG Controller name is allowed after the user-plane is already associated with the BNG Controller and subscribers are logged in. This leaves the system in a bad state.

Resolved In:
1892276
Major		Updating BNG-UP IP Address leaves user-plane in READY state.
Product-Group=junos		Updating BNG-UP IP Address leaves user-plane in READY state.

Resolved In:
PR NumberSynopsisCategory: BBE UP Session Manager related issues
1890895
Major		BNG Controller: Issue with changing the IP address of an active BNG user-plane
Product-Group=junos		BNG Controller: Issue with changing the IP address of an active BNG user-plane

Resolved In:
PR NumberSynopsisCategory: BBE CUPS Subscriber Group Related issues
1886696
Major		BNG Controller: When running with local static pools, a subscriber group is allowed to be deleted with active sessions
Product-Group=junos		When using static address pools BNG Controller allows for the SGRP using the pool to be deleted while subscribers are still logged in.

Resolved In:
PR NumberSynopsisCategory: Bi Directional Forwarding Detection (BFD)
1888400
Major		EX4100/EX4400 8 member VC: Observing high convergence on GRES
Product-Group=junos		Traffic convergence issue was resolved with the work around provided. BFD issue was known limitation.

Resolved In:
PR NumberSynopsisCategory: Border Gateway Protocol
1861799
Major		The "advertise-inactive" configuration does not work as expected when "add-path multipath" is configured and negotiated with the neighbor
Product-Group=junos		On all Junos and Junos Evolved platforms with "advertise-inactive" configured under Border Gateway Protocol (BGP), inactive routes are not advertised to peers when "add-path multipath" is configured and negotiated with the neighbor.

Resolved In: evo:22.3X50-EVO evo:22.3X50-J3-EVO evo:22.3X80-D49-EVO evo:25.2R1-EVO junos:20.3X75-D442 junos:20.3X75-D52 junos:22.3X60 junos:25.2R1
1889749
Major		BGP Prefix-SID Label collision causing RPD crash
Product-Group=junos		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:25.2R1-S1 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: QFX Access Control related
1901304
Major		[ex4000]:: Dot1x client remains in server-fail vlan post radius-reachability timer expiry
Product-Group=junos		As a best practice dot1x server-timeout should be configured higher than radius-timeout * (retries + 1). Radius reachability feature is supposed to trigger periodic check if server is reachable and if it is then trigger reauth for all the clients in server-fail. There is a corner case which breaks this feature where no action is taken when reachability timer fires. In such scenario client will remain in server-fail unless its reauth timer fires.

Resolved In: junos:23.4R2-S6 junos:24.2R2-S3 junos:24.4R2-S2 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: CoS support on DNX
1897336
Major		ARP resolution and device discovery failure is observed due to unexpected VLAN tags on ARP replies
Product-Group=junos		On ACX710 and ACX5448 platforms, due to VLAN edit profile remapping and VLAN translation, all the packets are getting VLAN-tagged. The RE ( Routing Engine ) drops ARP ( Address Resolution Protocol ) reply packets that contain VLAN ( Virtual Local Area Network ) tags, if the interface encapsulation was set to ethernet-ccc and VLAN configuration was removed. As a result, ARP resolution fails, leading to ping and device discovery failure.

Resolved In: junos:24.2R2-S3 junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: EVO MACSEC Platform Independent Implementation
1908196
Major		All Marvell(MX, ACX): LLDP protocol goes down when 'exclude protocol LLDP' is deleted from MACsec policy attached to IFD
Product-Group=junos		With IFD MACsec configured with exclude-protocol LLDP and LLDP protocol enabled, LLDP protocol goes down when 'exclude-protocol LLDP' is deleted from MACsec connectivity association.

Resolved In: evo:25.4R1-EVO evo:26.1R1-EVO junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: EVPN control plane issues
1839959
Critical		The MAC+IP table and mac-table are not in sync in the EVPN-MPLS active-active multihomed scenario leading to traffic loss
Product-Group=junos		On all Junos and Junos OS Evolved platforms that supports ESI lag interface and in an EVPN-MPLS (Ethernet Virtual Private Network - Multi Protocol Label Switching) active-active multihomed scenario, when the multihomed access interfaces are flapped in quick succession, it results in an unresolved destination route for the specific IP host. This is occurred due to race condition within l2ald (Layer 2 Address learning daemon) followed by an interface flap which causes the locally learned MAC to go missing from the mac-table on the other PE router.

Resolved In: evo:21.4R3-S10-EVO evo:22.2R3-S6-EVO evo:22.4R3-S7-EVO evo:23.2R2-S4-EVO junos:21.4R3-S10 junos:21.4R3-S4-J26 junos:22.2R3-S6 junos:22.4R3-S7 junos:23.2R2-S4 junos:23.4R2-S4 junos:23.4R2-S5 junos:24.4R1
PR NumberSynopsisCategory: ISIS routing protocol
1886347
Major		partial traffic drops seen on NSR switchover for Indirect route Going over L-ISIS transport route having "sensor-based-stats" configured under protocols isis
Product-Group=junos		On Junos and EVO platforms, After a Graceful Routing Engine Switchover (GRES), in New master, Indirect routes gets updated to the PFE and result in traffic loss when the transport is L-ISIS with telemetry traffic sensors enabled. In this scenario, Indirect routes going over L-ISIS route. Reason for Indirect route change is due to Underlying L-ISIS route next-hop getting changed. L-ISIS route next-hop getting changed due to ?Sensor-based-stats? configuration which does not support NSR functionality. Hence After Switchover, New Master Create sensors and Installed in the L-ISIS next-hop result in L-ISIS next-hop changed. Once L-ISIS routes nex-thop gets changed, Indirect routes under going for re-resolution which cause traffic impact.

Resolved In:
PR NumberSynopsisCategory: Flow Module
1876536
Major		Configuring tunnel over tunnel can leads to traffic disruption on SRX/VSRX platforms
Product-Group=junos		On all Junos SRX/VSRX platforms when tunnel over tunnel scenario is configured, the tunnel MTU (Maximum Transfer Unit) gradually decreases below the minimum MTU. As a result, this condition can lead to a srxpfe crash and traffic drop. In scenarios where a FPC (Flexible PIC Concentrator) is present, the traffic drop will be seen over the specific FPC, and after the crash happens, the FPC is restarted. In cluster scenarios, traffic on RG (Redundancy Group) will fail over to the backup node.

Resolved In: junos:22.4R3-S8 junos:23.2R2-S3-J13 junos:23.2R2-S3-J15 junos:23.2R2-S5 junos:23.4R2-S5 junos:23.4R2-S6 junos:24.2R2-S2 junos:25.3R1
1895420
Major		First path SM interest check fail on SRX4100
Product-Group=junos		When traffic is processed application services which uses tcp proxy in flowd, the usage of object cache increases and possible to drop traffic.

Resolved In: junos:24.2R2-S3 junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: IPSEC/IKE VPN
1877966
Minor		Some new VPN tunnels are not coming up on SRX5K platforms with SPC3
Product-Group=junos		On SRX5K platforms with SPC3 installed, IPSec (Internet Protocol Security ) tunnels with iked which reuses the same IKE (Internet Key Exchange) gateway peer IP, could be observed not re-establishing.

Resolved In: junos:22.4R3-S8 junos:24.2R2-S2 junos:24.4R2-S2 junos:25.3R1
PR NumberSynopsisCategory: Key Management Daemon
1869769
Major		The kmd process crashes when device with MS-MPC has DPD enabled and a SA is deleted
Product-Group=junos		On all MX platforms with MS-MPC (Multiservices Modular PIC Concentrator), when DPD (Dead Peer Detection) is enabled under IPsec/IKE (Internet Key Exchange) VPN settings and for any reason an IPsec SA (Security Association) is deleted, the kmd process crashes. Due to the kmd process restart some disruption in tunnel establishment is seen.

Resolved In: junos:22.4R3-S7
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1892944
Minor		EX4300 VC L2ALD core after upgrade from 21.4R3-S3.4 to latest 21.4R3-S6 and above versions
Product-Group=junos		On EX4300 switch running Junos version 21.4R3-S6 and above, when SNMP polling is done for oid 1.3.6.1.2.1.17.7.1.4.5.1 with redundant-trunk-group interfaces configured there will be L2ALD memory leak seen on the switch. It can be verified using command: show ethernet-switching debug-statistics memory | match l2ald_mib_dot1dTp_lookup ---(refreshed at 2025-09-03 20:28:30 IST)--- Allocated Allocated Allocated Memory (current) (total) (freed) (owner) 6532 450708 444176 [l2ald_mib_dot1dTp_lookup (0x1bd9f60)] ---(refreshed at 2025-09-03 20:28:35 IST)--- Allocated Allocated Allocated Memory (current) (total) (freed) (owner) 6856 473064 466208 [l2ald_mib_dot1dTp_lookup (0x1bd9f60)] ---(refreshed at 2025-09-03 20:28:40 IST)--- Allocated Allocated Allocated Memory (current) (total) (freed) (owner) 7280 502320 495040 [l2ald_mib_dot1dTp_lookup (0x1bd9f60)]

Resolved In: evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: Port-based link layer security services and protocols that a
1909013
Major		EAPOL: Interface should be deleted only after deleting MACsec on the interface in question. Applies to MPC3E only
Product-Group=junos		On MPC3, delete MACsec provisioning before deleting interface

Resolved In: evo:26.1R1-EVO
PR NumberSynopsisCategory: Protocol Independant Multicast
1880262
Major		PIM neighbors timeout on backup RE due to inconsistent state with master
Product-Group=junos		On all Junos and Junos Evolved platforms with dual Routing Engines (REs), Protocol Independent Multicast (PIM) neighborship is not be maintained on the backup Routing Engine after a ppmd-agent restart. This can lead to loss of PIM neighbor state on the backup RE.

Resolved In: evo:23.4R2-S6-EVO evo:24.2R2-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:22.4R3-S8 junos:23.2R2-S5 junos:23.4R2-S6 junos:24.2R2-S2 junos:25.2R2 junos:25.3R1
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platfom issues
1758400
Major		JUNOS_REG: QFX51200-48YM: Fan status output was not same after/before device vc-switch over.
Product-Group=junos		In a QFX51200-48YM-8C VC setup, after a a mastership switch over fan tray of linecard may not be displayed in show chassis hardware and show chassis environment. There is no functional impact

Resolved In: junos:23.2R2-S5 junos:23.2R2-S6 junos:25.2R1-S2 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: Shard routing infrastructure within RPD
1757915
Major		The rpd process crashes when processing multipath routes with mixed indirect and composite next-hops under rib-sharding
Product-Group=junos		On all Junos and Junos OS Evolved platforms, when rib-sharding is enabled and RT (Route Target) multipath routes containing both indirect and composite next-hop types are processed, the rpd (Routing Protocol Daemon) process will crash due to incorrect handling during the next-hop copy operation from RIB (Routing Information Base) shards to the main RIB thread. An rpd crash results in all routing protocols going down and causes a brief traffic disruption until the rpd process restarts.

Resolved In: evo:25.2R2-EVO evo:25.3R1-EVO junos:23.2R2-S2-J9 junos:23.4R2-S5 junos:25.2R2 junos:25.3R1
PR NumberSynopsisCategory: RPM and TWAMP
1908499
Minor		RFC2544/Y.1564 Reflection Mismatch
Product-Group=junos		There are limitations associated with the implementation features of the generator in the Broadcom chip. Multiple Y.1564/RFC2544 generators should not be used on the same interface. Juniper engineering recommend running tests one by one or distributing tests across different VLANs. This PR will commit code to ensure an error is presented when trying to run multiple tests

Resolved In: evo:26.1R1-EVO
PR NumberSynopsisCategory: Generic platform and infra issues for MS-MIC and MS-MPC(XLP)
1899178
Critical		Service session drops are observed when CPU throttling is configured on platforms with service cards installed
Product-Group=junos		On all Junos MX platforms that have MS-MPC or MS-MIC service cards installed, the use of the CPU throttling can cause the production service sessions to be dropped.

Resolved In: junos:21.2R3-S10 junos:21.2R3-S6-J16 junos:22.4R3-S7-J5
1901021
Major		Service-Set Configuration Bug Leading to Kernel Panic on Junos MX
Product-Group=junos		On Junos MX platforms with MS-MPC, when new rules are added to a service-set, the configuration size increases incrementally. This growth will cause failures during the commit process, potentially leading to a kernel panic. As a result, new configurations may not be successfully applied.

Resolved In: evo:25.2R2-EVO evo:25.4R1-EVO junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: SRX branch platforms
1897579
Minor		Packet drops are observed on SRX380 platforms in packet mode
Product-Group=junos		On Junos OS SRX380 (cluster/standalone) platforms in packet mode, when L2 (Layer 2) encapsulation is configured on an ingress interface of the PE (Provider-Edge) device, the incoming packets are dropped because these packets are identified as L2 unknown unicast packets. This issue happens due to the default drop ACL (Access Control List) applied for L2 unknown unicast packets.

Resolved In: junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: Junos Automation, Commit/Op/Event and SLAX
1872284
Major		master-eventd will fail after multiple RE switchover
Product-Group=junos		On Junos and Junos OS Evolved platforms with dual RE(Routing Engine) , master-eventd will fail to start after multiple RE switchovers when event-options policies are configured. This happens only if a process is still waiting for an action (like file transfer or SSH) to complete.

Resolved In: evo:23.4R2-S6-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:23.2R2-S5 junos:23.4R2-S6 junos:24.2R2-S3 junos:24.4R2-S2 junos:25.2R1-S2 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: Issues related to YANG Data Models
1781023
Minor		Few yang package are occuring multiple place On Box
Product-Group=junos		Few yang package are occuring multiple place On Box

Resolved In:
PR NumberSynopsisCategory: QFX10002 Platform
1869232
Major		CRC errors increase continuously after interface flap on some 100G transceivers with Rx CDR LOL support
Product-Group=junos		On Junos PTX10002-60C, and QFX10002-60C platforms, when using 100G QSFP modules with CDR LOL support, CRC errors have been observed on odd-numbered ports, leading to traffic disruptions.

Resolved In: junos:22.4R3-S7-J1