Alert Type

SRN - Software Release Notification
Low/NotificationSRN
Low/NotificationSRN

Product Affected

ACX EX MX NFX PTX QFX SRX vSRX

Alert Description

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

IMPORTANT: MX platforms - review TSB72576 [juniper.net] The Routing Engine requires 200G SSD before upgrading to Junos 23.4, 24.2, 24.4, or later software.

https://supportportal.juniper.net/s/article/RE-S-X6-64G-X-disk-space-limitation-for-MX960-480-240

Solution

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

24.2R2-S5 - List of Fixed issues

PR NumberSynopsisCategory: Software build tools (packaging, makefiles, et. al.)
1663426
Major		NETCONF: RPC get & get-configuration display invalid json format response for an OpenConfig when adds a routing-options configuration
Product-Group=junos
Severity=Major		After adding a "routing-options" configuration via OpenConfig operation, subsequent "get" and "get-configuration" may display an invalid JSON format.
PR NumberSynopsisCategory: MX10008/16 Platform
1896343
Major		A DC PEM (Part number: 740-073256) shows up "PEM 0 Not Powered" alarm even though the power feeds to this PEM has been recovered normally.
Product-Group=junosvae
Severity=Major		JunOS software has been updated to prevent unintended shutdown of JNP10K-PWR-DC2 VOUT when the 0xDA fault is falsely asserted due to external power feeds being disconnected or unpowered. The software now masks the 0xDA fault as a false positive in these scenarios, while preserving protection for genuine internal PEM faults.
PR NumberSynopsisCategory: NFX Series Platform Software
1890688
Major		Junos to VMHost SSH connectivity is lost after restarting NFX platforms with FIPS mode enabled
Product-Group=junosvae
Severity=Major		On all Junos OS NFX platform with FIPS(Federal Information Processing Standards) mode enabled , restarting the system results in loss of SSH(Secure Shell) connectivity between Junos OS and the host system (VMHost). This causes any CLI command that runs on host internally to fail.
PR NumberSynopsisCategory: SRX Fleming L2NG platform support
1911533
Minor		SRX1600 switching mode : table full error message displayed even the L2 table is not full
Product-Group=junos
Severity=Minor		On SRX1600 switching mode, table full error message displayed even the L2 table is not full
PR NumberSynopsisCategory: SRX Fleming Platforms related issues
1927758
Critical		HA failover not triggered after PFE process crash in HA deployments (Chassis Cluster / MNHA) on SRX1600/2300/4300/4700
Product-Group=junosvae
Severity=Critical		On SRX1600/2300/4300/4700 platforms configured in HA mode (Chassis Cluster or MNHA), when a PFE (Packet Forwarding Engine) process crash occurs on the active node, HA failover is not triggered because the failure condition is not detected by the HA subsystem. This can lead to traffic disruption and service outage.
PR NumberSynopsisCategory: L2NG bug tracking
1919768
Minor		"SCHED: Thread 19 (BCM AGING periodic) ran for 1016 ms without yielding" message is frequently displayed
Product-Group=junos
Severity=Minor		On SRX1500 platform in L2 mode, "SCHED: Thread 19 (BCM AGING periodic) ran for 1016 ms without yielding" message is frequently displayed
PR NumberSynopsisCategory: Accounting Profile
1914977
Minor		Whenever a client(eg lacp/ifinfo/snmp) requests statistics from PFE, the query is routed via the kernel and not through the use of the BULKGET protocol
Product-Group=junos
Severity=Minor		On specific VMHost platforms like MX204/MX304/MX10003/MX10008/MX10016/ PTX1000/PTX10008/PTX10016/ EX2300/EX3400/EX4650/ QFX5100/QFX5110/QFX5200/ QFX10002/QFX10008/QFX10016/ vSRX/SRX1500/SRX1600/SRX2300/SRX4100/SRX4200/SRX4300/SRX4600 platforms. Whenever a client (e.g., lacp/ifinfo/snmp) requests statistics from PFE, the query is routed via the kernel and not through the use of the BULKGET protocol.
PR NumberSynopsisCategory: "agentd" software daemon
1843184
Major		JSD core reported (backtrace truncated)
Product-Group=junos
Severity=Major		JSD utilizes the libaudit API to send accounting messages for gRPC RPCs to auditd. The libaudit library establishes a socket connection and writes accounting messages to auditd. This socket is intended to be shared across multiple threads within JSD. Upon a write failure, the existing socket is closed, and a new socket is created. However, in a multi-threaded environment, there is a race condition whereby multiple threads may simultaneously detect that the socket has been closed and attempt to create a new one. This can result in multiple sockets being opened concurrently, ultimately leading to a file descriptor (FD) leak. To address this issue, a mutex lock has been introduced around the function responsible for socket creation and message transmission via libaudit. With this fix in place, when a socket is closed due to a write failure, the same thread will recreate the socket while holding the lock, and the updated socket descriptor will then be safely shared across all threads within JSD.
1913260
Major		Discrepancy noticed in the interfaces when there is a reset in Linecard or PFE
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms, with an established telemetry session with multiple collectors, there will be interface statistics discrepancy when there is a linecard OIR event or PFE offline/online sequence.
1929823
Major		The sysd process crashes with error logs upon exceeding its memory limit
Product-Group=junos
Severity=Major		On Junos OS Evolved platforms with telemetry streaming configured, the sysd (System Daemon) process crashes on the backup RE (Routing Engine), and error logs are observed when sysd memory usage continues to grow over time, and the memory limit is exceeded. This issue is observed when the 64-bit sysd consumes more memory than the configured system limit when the device has been running for a long time (typically more than 100 days) in the dual RE scenario.
PR NumberSynopsisCategory: BBE routing
1922536
Major		Forwarding issues for an access DHCPv6-PD or access-internal DHCPv6-IA route or both may be seen on LNS due to an incorrect route programming of such route on PFE
Product-Group=junos
Severity=Major		Drop of traffic to subscriber DHCPv6 prefixes may be observed on LNS (L2TP network server) if CPE uses IPv6 address obtained via NDRA process as the source address for DHCPv6 negotiation instead of link-local address.
PR NumberSynopsisCategory: BBE Statistics daemon & libraries
1856217
Major		Memory corruption in bbe-statsd due to double free for IP demux lite subscribers
Product-Group=junos
Severity=Major		On Junos MX platforms with bbe-statsd running, there is a rare timing issue that could cause memory corruption in the bbe-statsd process due to a double-free scenario for IP demux lite subscribers. The issue could result in bbe-statsd process crashes. but had no service impact. The bbe-statsd process may crash, but there is no service or network impact.
PR NumberSynopsisCategory: Border Gateway Protocol
1889749
Critical		BGP Prefix-SID Label collision causing RPD crash
Product-Group=junos
Severity=Critical		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.
PR NumberSynopsisCategory: MX304 PSM issuues
1923135
Major		On MX304 platform repetitive logic fault alarm on both PEMs observed
Product-Group=junosvae
Severity=Major		On MX304 platforms, PEM Logic Fault alarms may intermittently appear due to I2C transaction timing limitations. PEMs require a delay between backtoback transactions; without this delay, alarms can be raised randomly on either PEM.
PR NumberSynopsisCategory: MX304 Routing Engine issues
1913540
Minor		[MX304] Certain 'cat' commands within the 'show vmhost support-info' command in RSI try to access files that are not present on the MX304, causing error messages to appear.
Product-Group=junos
Severity=Minor		As part of the RSI process, the command "show vmhost support-info" is executed, which comprehensively collects vmhost logs using various cat commands. Some of these commands attempt to access files that do not exist on the MX304, leading to the display of error messages.
PR NumberSynopsisCategory: MX Platform SW - Power Management
1924872
Major		SFB-Redundant mode not applied after reboot when "event-options event-script file" is configured
Product-Group=junos
Severity=Major		On Junos MX2020 platforms with SFB3, when event script is configured on the device, the platform does not correctly apply the SFB power-redundant-mode configs (set chassis power sfb-redundant-mode) during a full chassis reboot, affecting the chassis resiliency.
PR NumberSynopsisCategory: Class of Service
1928420
Minor		Incorrect COS scheduler-map gets attached to an AE IFL after GRES or 'cosd' process restart
Product-Group=junos
Severity=Minor		On all Junos MX platforms with line cards (MPC1-11, MS-MPC, LC2101, LC2103, LC480, LC4800, LC4802, LC9600, JNP304-LMIC), when a scheduler-map is attached to an AE (Aggregated Ethernet) IFL (Logical Interface) directly or by 'traffic-control-profile' and when this AE is in 'replicate' mode, upon GRES (Graceful Routing Engine Switchover) or on 'cosd' process restart operation, configured scheduler-map gets removed from this AE IFL and a default (Incorrect) scheduler-map gets attached to it. This causes change in the traffic flow pattern via the COS (Class of Service) queues of the AE IFL and can impact service.
PR NumberSynopsisCategory: QFX Access Control related
1934680
Major		The radius accounting interim updates is missing framed-ip-address when manually triggered
Product-Group=junos
Severity=Major		On platforms supporting dot1x authentication, when a Radius accounting Interim-Update is manually triggered from the switch (using a COA), the resulting accounting packet does not include the Framed-IP-Address attribute. However, when the same session generates an interim update via the periodic timer (10-minute interval), the Framed-IP-Address is included as expected.
PR NumberSynopsisCategory: QFX Control Plane VXLAN
1921796
Minor		Traffic dropped after priority change in VRRP with EVPN-VxLAN scenario
Product-Group=junos
Severity=Minor		On all Junos and Junos Evolved platforms, in Virtual Router Redundancy Protocol (VRRP) with Ethernet Virtual Private Network - Virtual Extensible Local Area Network (EVPN-VXLAN) scenario, when VRRP priority is changed, the VRRP virtual Media Access Control (MAC) address can remain pinned as a static entry on the remote device. As a result, MAC movement does not occur correctly, and VRRP packets are dropped on the leaf device. This impacts VRRP operation after priority changes.
PR NumberSynopsisCategory: OpenSSH and related subsystems
1922002
Major		Major alarms showing SPMB1 not online on MX2008 will be seen on 24.2R1 and later releases
Product-Group=junos
Severity=Major		On the Junos MX2008 VMhost platform with dual Routing Engines (REs), the backup SPMB {Switch Processor Mezzanine Board} (spmb1) fails to come online following a graceful switchover on releases starting when upgrading to releases starting from Junos 24.1. As a result, if the backup SPMB cannot boot, the traffic will be impacted during switchovers.
PR NumberSynopsisCategory: Firewall Filter
1903874
Major		[MX10008] cmd='ls -i /var/etc/filters/filter-define.conf' is logged every 1 second instead of every 30 seconds
Product-Group=junos
Severity=Major		An issue where client sessions were not cleared on a router/switch, leaving stale session data that triggered immediate timeout handling instead of the expected 30?second delay. This caused once?per?second master?data lookups and repeated log entries such as "ls -i /var/etc/filters/filter-define.conf", but had no functional impact.
PR NumberSynopsisCategory: Dynamic rendering infrastructure
1915225
Major		cli-pfe does not terminate immediately when user issues Ctrl-C
Product-Group=junos
Severity=Major		A cli-pfe show command may continue to gather data in the background after the user issues a Ctrl-C. Eventually the background command will complete. However, the CPU usage for the cli-pfe process will continue to be high while it is still running.
PR NumberSynopsisCategory: Control Plane for Node Virtualization
1926166
Minor		Temperature Sensor Failure Alarms on ULC Platforms after enabling SLC
Product-Group=junos
Severity=Minor		On Universal Line Card (ULC) platforms running Junos releases after 24.1DCB, temperature sensor failure alarms can persist after a transient sensor read failure or a nonrecoverable Peripheral Input/Output (PIO) hardware read error. The issue is most easily reproducible on systems using MPC11E with Sliceable Line Card (SLC) configuration due to increased software concurrency. Once triggered, the sensor state remains in a failed condition even though temperature values subsequently report normally, and alarms can reoccur after applying or rolling back chassis slicing configuration.
PR NumberSynopsisCategory: JUNOS Dynamic Profile Configuration Infrastructure
1930036
Major		High memory usage is showing, when we configure unsupported licensing feature
Product-Group=junos
Severity=Major		On all Junos EX and QFX platforms operating in an EVPN (Ethernet Virtual Private Network) environment, this issue occurs when the CLI command 'licensing hourly update' is executed on a device that does not support the licensing feature.
PR NumberSynopsisCategory: EVO L2 Control Plane PRs
1914423
Major		On-change telemetry events dropped when l2ald telemetry queue memory limit is not configured
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms, when l2-learning telemetry is enabled without explicitly configuring a memory limit for the l2ald (Layer 2 Address Learning Daemon) telemetry queue, the default memory limit is not applied. As a result, all on-change telemetry events are dropped.
PR NumberSynopsisCategory: mgd, ddl, odl infra issues
1867821
Major		The "ui-gnmi-pubd.log" file growth may cause disk space issues on all Junos OS Evolved platforms
Product-Group=junos
Severity=Major		On all Junos OS Evolved platforms, when telemetry is enabled and an active gNMI subscription includes a configuration path, the "ui-gnmi-pubd.log" file will grow continuously without log rotation or archival. This behaviour will lead to potential disk space exhaustion over time, however, there is no traffic impact due to this issue.
PR NumberSynopsisCategory: EVPN control plane issues
1925825
Major		Inter-vlan traffic failure due to missing IRB symmetric routing
Product-Group=junos
Severity=Major		On QFX5210, QFX5220, QFX5210 - 64C platforms, inter-VLAN routed traffic fails, not because route targets aren't autoupdating, but due to missing or incorrect EVPNVxLAN (Ethernet Virtual Private Network - Virtual Extensible LAN) IRB(Integrated Routing and Bridging) symmetric routing configuration within the T5 VRF(Virtual routing and forwarding).
PR NumberSynopsisCategory: EX interfaces issues
1904884
Critical		VCP link flap due to SYSPLD read failures
Product-Group=junos
Severity=Critical		On EX4100 platform VCP link flap due to SYSPLD read failures and mark SFP as unplugged
PR NumberSynopsisCategory: EX4400 platform
1942085
Major		Kernel panic and unexpected reboot on certain EX4400 platforms due to CPU erratum
Product-Group=junos
Severity=Major		On EX4400/EX4400-24Xand EX4400-48X platforms, device experienced an unexpected reboot and recovers automatically. The system logs indicate a kernel panic, and a VMcore file is generated. Traffic impact will be seen until the recovery.
PR NumberSynopsisCategory: EX POE
1930080
Major		PoE outage observed on EX4400 in a rare scenario
Product-Group=junos
Severity=Major		On EX4400 platforms, loss of PoE (Power over Ethernet) power is seen on ports after port bounce or even during normal operation without specific external trigger . This causes outage on all PoE ports and devices connected to PoE port will not receive power causing service impact.
PR NumberSynopsisCategory: EX Entry Level Access VC platform
1919727
Minor		The dcpfe process crashes repeatedly with continuous error logs 'smb_transfer: SMBus ioctl failed'
Product-Group=junos
Severity=Minor		On EX4400 platforms, due to an internal communication issue within the CPU controller, the system triggers repeated fxpc panics which in turn lead to the dcpfe process (Dataplane Packet Forwarding Engine) to crash and restart continuously, resulting in service disruption.
PR NumberSynopsisCategory: Express PFE L2 fwding Features
1865354
Major		Traffic to anycast IPv6 destination addresses dropped when using ECMP routes
Product-Group=junos
Severity=Major		On QFX10002-60C platforms when ECMP (Equal Cost Multi-path) is required to get multiple-path to multiple hosts connected, and with ipv6 address configured as a destination address, the destination MAC rewrite process fails, due to the unilist nexthop for ipv6 destination is getting overwritten. This leads the IPv6 anycast packets from/to the host, to get dropped over the ECMP routes.
PR NumberSynopsisCategory: FIPS related issues
1905490
Major		On MX10003 with FIPS enabled, KATs failure in SMIC_QSFP28_MACSEC_TIC causes system halt
Product-Group=junos
Severity=Major		In Junos, MX10003 platforms with Federal Information Processing Standards (FIPS) enabled experience repeated halts due to Known Answer Test (KATs) failures in the SMIC_QSFP28_MACSEC_TIC crypto path.
PR NumberSynopsisCategory: Enhanced Broadband Edge support for firewall
1928462
Major		FPC crash occurs after configuration changes are made to a service-filter on specific MX platforms
Product-Group=junos
Severity=Major		FPC crash and aftd-trio core-dump will be observed on MX platforms supporting MPC10E, MPC11E, LC9600 line cards, and MX304 after configuration changes were made to a service-filter which was in use by BBE subscribers.
PR NumberSynopsisCategory: SRX1500 platform software
1905001
Minor		FPC stuck in network loop scenario
Product-Group=junos
Severity=Minor		On SRX1500 in network loop scenarios, FPC gets stuck and traffic drop happens. System can be recovered by rebooting the device.
PR NumberSynopsisCategory: LC4800 specific Fabric software issues
1881595
Minor		When an FPC is ungracefully offlined it remains online for 12 minutes causing a service impact
Product-Group=junos
Severity=Minor		On all MX platforms with 2 or more FPCs (Flexible PIC Concentrators), a temporary service impact will be observed if a FPC is ungracefully offlined (for example, due to an ungraceful switchover, command to simulate ungraceful offline, or physical removal). The FPC that is being ungracefully offlined appears online for ~12 minutes before going offline. During this 12-minute period, the Fabric Manager remains in a stuck state and recovers automatically after the FPC goes offline.
PR NumberSynopsisCategory: Kernel software for AE/AS/Container
1938565
Major		LACP remains in collecting and distributing state after GRES on PE and interface flap with lacp-oos-on-ndf enabled
Product-Group=junos
Severity=Major		On Junos platforms supporting Ethernet Segment Identifier (ESI) based Aggregated Ethernet (AE) Link Aggregation Group (LAG) deployments, Link Aggregation Control Protocol (LACP) does not return to the expected Attached state when a Graceful Routing Engine Switchover (GRES) occurs on the Provider Edge (PE) device and is followed by an AE member interface flap on the connected device, with lacp-oos-on-ndf (LACP out-of-sync on non-designated forwarder) enabled on the PE.
PR NumberSynopsisCategory: Integrated Routing & Bridging (IRB) module
1933452
Major		ICMP ping with higher MTU size fails in VPLS when IRB MTU exceeds MPLS core MTU
Product-Group=junos
Severity=Major		On all Junos OS platforms, configured with VPLS (Virtual Private LAN Service) and IRB (Integrated Routing and Bridging ) interfaces, when the MTU (Maximum Transmission Unit) configured on the IRB or CE interface is larger than the MPLS ( Multiprotocol Label Switching ) core interface MTU (including MPLS label overhead), ICMP Echo Request (ping) packets with higher packet sizes fail.
PR NumberSynopsisCategory: jdhcpd daemon
1939685
Minor		Insert command not working for "dhcp-local-server group" hierarchy
Product-Group=junos
Severity=Minor		Insert command not working for "dhcp-local-server group" hierarchy, below error is seen: user@host# insert system services dhcp-local-server group servers-1 after syntax error, expecting `after' or `before'. user@host# insert system services dhcp-local-server group servers-1 bef syntax error, expecting `after' or `before'.
PR NumberSynopsisCategory: Flow Module
1832547
Minor		The flowd process crash is observed on certain SRX platforms
Product-Group=junos
Severity=Minor		On certain Junos SRX devices upon initiation of session scan, flowd process might crash due to session getting deleted/re-routed. This could result switchover of redundancy group in case of high availability.
PR NumberSynopsisCategory: High Availability/NSRP/VRRP
1842874
Major		Traffic through ipsec vpn tunnel halts/stops after back to back failover until rekey occurs
Product-Group=junos
Severity=Major		On Junos SRX5600 platforms, when the primary node reboots, the VPN(Virtual Private Network) sequence number sync RTO(Retransmission Timeout) packets between the primary node and secondary node stops for few mins. Once the nodes have fully transitioned, such as from primary to secondary and vice versa, any failover during this period can lead to traffic loss. This occurs until the IPsec (Internet Protocol Security) sequence number on the new primary node catches up with the sequence number last sent by the previous primary node.
PR NumberSynopsisCategory: IPSEC/IKE Key Management
1841364
Major		The kmd process crash is seen on random number generation by the third-party library API
Product-Group=junos
Severity=Major		On Junos and Junos evolved platforms on rare circumstances when device is busy kmd process crash is seen on random number generation used for VPN negotiation by the third-party library API.
PR NumberSynopsisCategory: Firewall Network Address Translation
1933239
Critical		The FPC restarts on SRX series platforms when session-persistence-scan is configured
Product-Group=junos
Severity=Critical		On Junos OS SRX Series platforms with 'session-persistence-scan' and NAT46 or NAT64 configured, modification to source Network Address Translation (NAT) rule will cause Flexible PIC Concentrators (FPCs) to restart when there is live IPv6 traffic. This will cause all traffic to be dropped and cause service disruption.
PR NumberSynopsisCategory: Layer 2 Control Module
1930380
Major		The hash collision for storm control profile indices will result in an l2ald process crash
Product-Group=junos
Severity=Major		On all Junos OS platforms and Junos OS Evolved platforms which supports storm control, when a different storm-control profile is applied for interface where these profile have same profile index allocated then the storm control profile configuration and system state will not be in sync and a different profile will be applied for interface binding due to profile index collision which results into l2ald process crash.
PR NumberSynopsisCategory: Layer2 forwarding on EX/NFX/PTX/QFX
1928530
Critical		A buffer overflow during IPv6 NDP operations in an EVPN environment caused segmentation faults leading to FPC crash files and repeated reboots
Product-Group=junos
Severity=Critical		On JunOS MX240/MX480/MX960/MX2008/MX2010/MX2020 platforms with MPC10E/MPC11E line cards as well as the MX304 platform, an issue in IPv6 EVPN (Ethernet Virtual Private Network) during NDP (Neighbor Discovery Protocol) resolicitation of a link local target address causes the system to use the IRB link local address in outgoing packets. Stack corruption happens when handling the IRB link local address and resulting in continuous FPC (Flexible PIC Concentrator) reboots (around 3 or 4 times) and crash files generation.
1936648
Major		EVPN-VXLAN remote MAC IP programming is removed after a MAC move, resulting in missing ARP on a remote VTEP
Product-Group=junos
Severity=Major		In an Ethernet VPN (EVPN) Virtual Extensible LAN (VXLAN) deployment, a remote MAC move event can cause the remote MAC IP entry to be removed after it is initially installed, resulting in missing Address Resolution Protocol (ARP) state and incomplete hardware programming on the remote Virtual Tunnel Endpoint (VTEP), which can lead to traffic loss for the affected endpoint.
PR NumberSynopsisCategory: Issues related to Junos licensing infrastructure
1925706
Major		Snmp license polling cause license-check service crash
Product-Group=junos
Severity=Major		On Junos platforms, a race condition occurs when the Simple Network Management Protocol (SNMP) poller attempts to retrieve device license information while subscriber management and SNMP policing features are in use. This condition causes the license-check process to encounter a null pointer and generate a core dump. There is no traffic or service impact. However, license information retrieval through SNMP polling fail until the license-check service recovers.
PR NumberSynopsisCategory: SW PRs for MPC10E Interfaces
1945343
Major		Disabling one port in the breakout port channel makes another port down
Product-Group=junos
Severity=Major		On all Junos MX platform, when MPC10E interfaces use breakout cabling, administratively disabling one breakout port may unexpectedly impact another port within the same MAC quad due to nondeterministic breakout initialization.
PR NumberSynopsisCategory: Multiprotocol Label Switching
1889546
Major		MPLS ping/trace not working for direct peers via routing-instance over MPLS protocols
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms, when a routing instance is configured at the destination device, an echo request packet is received over this routing instance interface. This routing instance should have a valid route to reach the source device. But the default routing instance should not have a valid route to reach the source device. This issue is not specific to MPLS ping over SR alone. This issue is applicable for all the protocols MPLS ping.
PR NumberSynopsisCategory: ACX Timing software
1900889
Major		High CPU utilization of the acx-arm-feb process on ACX710 platforms after upgrade or reboot when Precision Time Protocol (PTP) or Synchronous Ethernet (SyncE) is configured
Product-Group=junos
Severity=Major		On ACX710 platforms running Junos OS, the acx-arm-feb process reaches 100 percent CPU utilization after a system upgrade or reboot when Precision Time Protocol (PTP) or Synchronous Ethernet (SyncE) is configured and the associated interfaces are enabled. This condition results in control plane degradation and traffic impact.
PR NumberSynopsisCategory: FreeBSD Kernel Infrastructure
1932893
Major		vmhost upgrade may fail due to 'Validation failed' when upgrading to freebsd15 based Junos from older releases.
Product-Group=junos
Severity=Major		vmhost upgrade may fail due to 'Validation failed' when upgrading to freebsd15 based Junos from older releases. This does not apply to Junos-EVO.
PR NumberSynopsisCategory: TCP/UDP transport layer
1893210
Minor		Master RE crashed and triggered unexpected switchover due to memory corruption
Product-Group=junos
Severity=Minor		On all Junos OS platforms, In Nonstop active routing (NSR) enabled system Routing Engine (RE) crash can occur due to a double free of a memory buffer (mbuf) was not handled properly leading to memory corruption causing synchronization issue and triggers unexpected switchover.
PR NumberSynopsisCategory: Protocol Independant Multicast
PR NumberSynopsisCategory: Issues related to PKI daemon
1919729
Major		SRX4300 and SRX1600 Enter System Halt or Amnesiac State After Reboot When TPM/MEK is Enabled
Product-Group=junos
Severity=Major		On SRX4300 and SRX 1600 platforms When Master password and Master Encryption Key is set on the device and rebooted , the system was getting into amnesiac state.
PR NumberSynopsisCategory: Periodic Packet Management Daemon
1931633
Major		PFE crash due to memory corruption when STP is enabled
Product-Group=junos
Severity=Major		On all Junos Platforms, a rare memory corruption condition may occur in the Packet Forwarding Engine (PFE) when Spanning Tree Protocol (STP) is enabled and operating in default (distributed) mode. When the issue is triggered, the PFE crashes and a dc-pfe core file is generated. The exact trigger for the memory corruption is currently unknown.
PR NumberSynopsisCategory: L2NG PVLAN feature
1916610
Minor		Primary VLAN mapping causes MAC learning failure on PVLAN inner port
Product-Group=junos
Severity=Minor		On EX2300 platform, A Private VLAN (PVLAN) issue occurs where Media Access Control (MAC) learning works correctly for Isolated and Community Virtual Local Area Network (VLAN) access ports, but when the Primary VLAN is assigned to an inner VLAN port, the switch stops forwarding traffic and no Media Access Control addresses are learned after committing the configuration. This issue impacts services on interfaces configured with PVLAN.
PR NumberSynopsisCategory: QFX PFE Class of Services
1894833
Minor		PFE crash observed during VXLAN classifier unbind or EZ-LAG commit operations
Product-Group=junos
Severity=Minor		On Junos QFX5k platforms, a PFE (Packet Forwarding Engine) crash is observed when unbinding VXLAN (Virtual Extensible LAN) access ports or classifiers with large number of SVP (Source Virtual Port) associations, or after committing EZ-LAG (Easy EVPN LAG) configurations with large VLAN-ID list leading to excessive CPU utilization, watchdog timeout, and eventually a crash.
PR NumberSynopsisCategory: QFX5K hostpath
1932314
Minor		Errors "fpc0 ifd null, port X and TD3:ifd null, port X" are seen on QFX5k platforms
Product-Group=junos
Severity=Minor		On QFX5k platforms, if sflow is configured without multicast and BUM traffic is sampled, then the errors "fpc0 ifd null, port X and TD3:ifd null, port X" are observed.
PR NumberSynopsisCategory: QFX L2 PFE
1938291
Major		Deactivating sub-interfaces on flexible ethernet ports leads to VLAN traffic loss
Product-Group=junos
Severity=Major		On Junos platforms having QFX and EX, VLAN(Virtual Local Area Network) traffic loss occur on interfaces configured with flexible-vlan-tagging when an L3 (SP style) sub-interface is deactivated on a port that also carries L2 (enterprise style) VLAN units.
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1905607
Major		Hardware MTU stuck at default value, causing packet drops on VXLAN Interfaces
Product-Group=junos
Severity=Major		On QFX5K and EX4K platforms which are running Junos release, when new VxLAN (Virtual Extensible LAN) vlans with IRBs (Integrated Routing & Bridging) are added, the L3 (Layer 3) interface values overwrite the MTU (Maximum Transmission Unit) entries previously programmed for non-VxLAN vlans that use the same hardware token internally. The VxLAN L3 interface is created with default MTU (1514) because L3 interface MTU value is still 1514 as it is not update by RE (Routing Engine).
PR NumberSynopsisCategory: QFX analyzer, sflow
1884080
Major		JTI telemetry data missing for nonmaster VC ports
Product-Group=junosvae
Severity=Major		On EX465048Y, EX430048MP, and all QFX5K platforms running Junos in Virtual Chassis (VC) mode, telemetry data from nonmaster VC members is not streamed to the collector. Telemetry packets from nonmaster members are dropped before reaching the master VC member. This affects all Packet Forwarding Engine (PFE) sensors on nonmaster VC members.
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1924654
Minor		DC-PFE Core due to Concurrent Filter Reprogramming and VTY Command Execution
Product-Group=junos
Severity=Minor		While a filter with a routing-instance action was being reprogrammed as part of a CLI commit, a firewall VTY command to dump this filter was executed concurrently. This concurrent access resulted in a DC-PFE core, as filter-related data structures were modified during reprogramming.
1933698
Major		PFE crash due to memory corruption in EVPN-VxLAN type5 overlay ECMP at high tunnel next hop scale
Product-Group=junosvae
Severity=Major		On Junos QFX5110, QFX5120, EX4650, EX4400, EX4100, and EX5200 platforms, when operating with EVPN-VxLAN type5 overlay ECMP at high tunnel next hop scale, the Packet Forwarding Engine (PFE) crash when a memory corruption issue is observed due to a buffer overflow that leads to corruption of heap management structures. This corrupted metadata is detected by the memory manager when later heap allocation or free operations are invoked, resulting in a reported heap corruption condition.
1936048
Major		QFX5K RE is consuming EAPOL packets on interfaces even though layer2-control l2pt is configured
Product-Group=junos
Severity=Major		On QFX5K platforms, it is observed that due to a software issue, RE (Routing Engine) is consuming EAPOL (Extensible Authentication Protocol over LAN) packets on VXLAN (Virtual Extensible LAN) enabled interfaces even though layer2-control l2pt (Layer 2 Protocol Tunneling) is configured.
1939298
Major		Traffic drop is seen due to tagged IRB L3 interface with native-vlan and vlan members
Product-Group=junos
Severity=Major		On all Junos OS QFX5K and EX4k platforms, configuring a native VLAN along with VLAN members on an underlay Integrated Routing and Bridging (IRB) Network-to-Network Interface (NNI) that carries VxLAN (Virtual Extensible LAN) traffic results in the VLAN tag not being stripped as expected. Instead of treating the native VLAN traffic as untagged, the interface adds the VLAN tag, leading to packet drops at the remote end.
PR NumberSynopsisCategory: QFX5K JUNOS Interface, MACSec, Optics, SDK, PHY
1938876
Major		Incorrect interface mode leading to 100G Link Flaps on QFX5210-64C
Product-Group=junos
Severity=Major		On Junos OS QFX5210-64C platform, 100G optics inherently operate in CAUI-4 (Chip-to-Module 100 Gb/s Four-Lane Attachment Unit Interface) mode, which is automatically selected by the system and not user-configurable; mismatches due to software versions leading to link instability or flapping.
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platfom issues
1938921
Major		Software rollback may cause device to become unresponsive on Junos platforms with qfx-5e image
Product-Group=junosvae
Severity=Major		On Junos platforms running qfx-5e image, the device fails to boot after issuing the command "request system software rollback". Once the issue occurred, the system gets hung and the CLI becomes unresponsive, as a result both control plane and forwarding plane traffic will be impacted.
PR NumberSynopsisCategory: KRT Queue issues within RPD
1931875
Major		The L2Circuit traffic which are resolving over BGP-LU get drop when 'chained-composite-next-hop' for BGP-LU and 'preserve-nexthop-hierarchy' is configured
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms supporting 'chained-composite-next-hop' for BGP-LU (Border Gateway Protocol - Labeled Unicast), when having L2Circuit (Layer 2 Circuit) links configured, with indirect next-hop resolving on BGP-LU prefix, if 'chained-composite-next-hop' enabled for BGP-LU and with 'preserve-nexthop-hierarchy' configured, L2Circuit traffic will get dropped due to failure in installing the forwarding next-hop with labels for L2Circuit service.
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1863248
Major		On all Junos OS Evolved platforms, traffic loss will be seen after switching the LSP from SRTE to L-ISIS
Product-Group=junos
Severity=Major		On all Junos OS Evolved platforms with Segment Routing Traffic-Engineering (SRTE) and Labeled- Intermediate System- Intermediate System (L-ISIS) configuration, when a service route is resolved over SRTE route in inet6color.0 and if the SRTE path in inet6color.0 is deactivated/goes down, the SRTE route is deleted and service route starts resolving over L-ISIS. However traffic loss for 20 minutes or more is seen after switching the Label Switched path (LSP) from SRTE to L-ISIS path.
PR NumberSynopsisCategory: Issues related route resolution routing infrastructure
1858032
Major		The rpd process crashes when generate routes are configured in a rib-sharding scenario
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms, rpd process crash is seen when Border Gateway Protocol (BGP) rib-sharding is enabled and generate routes are configured. This occurs due to issue in route resolution, the rpd crash impacts routing and rpd will restart when this issue occurs.
PR NumberSynopsisCategory: SRX branch platforms
1927646
Minor		Ethernet interfaces with fiber SFPs and configured with 'family ethernet-switching' and 'no auto negotiation' don't come up after reboot
Product-Group=junos
Severity=Minor		After reboot on branch SRX300 Series platforms, interfaces using Small Formfactor Pluggable (SFP) SX/LX fiber transceivers and configured with 'family ethernet-switching' and 'no auto negotiation' might remain in a down state due to incorrect physical medium detection by the Ethernet physical layer (PHY). The issue is timing-dependent, it might happen with single or after several reboots.
1934517
Major		SRX380 XE interface flap on every configuration commit with 1G SFP transceivers
Product-Group=junos
Severity=Major		On the SRX380 platforms, in both cluster and standalone modes, the XE interfaces with 1G SFP fiber transceivers flap once after every configuration commit, causing the device to temporarily lose upstream reachability.
PR NumberSynopsisCategory: MPC7E, MPC8E and MPC9E timing and synchronization
1803105
Major		PTP attribute changes on upstream device causes best clock master slot switchover
Product-Group=junos
Severity=Major		On all MX platforms(except MX80) with multi line card chassis, when PTP slave or stateful streams are configured across multiple linecards with clock from same PTP time provider and the announce msg parameters changes from the upstream device, the best master clock (BMC) slot switchover is observed and is restored back within few seconds. Although the slot time interval is very less, it can still lead to major impact as the active PTP slot and clock path is switched over and results in re-routing of the clocks.
PR NumberSynopsisCategory: Trio pfe l3 forwarding issues
1921361
Major		Slow memory leak triggered by subscribing to the pipeline sensor for a long duration
Product-Group=junos
Severity=Major		On Junos platforms with MPC 1-9, LC2101, LC480, LC2103 line-cards and MX204, a slow memory is observed when subscribing to the pipeline sensor ( path is /components/component/integrated-circuit/pipeline-counters/). Over time, this causes a gradual increase in heap memory usage. Increase in heap memory usage beyond a certain threshold will lead to FPC crash resulting in loss of services and traffic over that FPC.
1927194
Major		When a resolution for an IPv4/IPv6 address fails, NH IFL is throttled causing service impact
Product-Group=junos
Severity=Major		In MX uKern and AFT based cards, NH IFL throttling will be seen when resolution for an destination IPv4/IPv6 address fails.
PR NumberSynopsisCategory: Authentication, Authorization, Accounting, PAM (RADIUS/tacplus)
1850776
Critical		Multiple Products: RADIUS protocol susceptible to forgery attacks (Blast-RADIUS) (CVE-2024-3596)
Product-Group=junos
Severity=Critical		An Authentication Bypass by Spoofing vulnerability in the RADIUS protocol of Juniper Networks Junos OS and Junos OS Evolved platforms allows an on-path attacker between a RADIUS server and a RADIUS client to bypass authentication when RADIUS authentication is in use. Please refer to https://supportportal.juniper.net/JSA88210 [juniper.net] for more information.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1902358
Minor		RPC crash when non-ASCII character is included in XML data result
Product-Group=junos
Severity=Minor		RPC calls fail when non-ASCII characters (i.e. UTF-8 encoded characters) are included in XML data results.
1947196
Minor		Commitd core dumps observed during specific config commits with "patch generation error - not syncing patch"
Product-Group=junos
Severity=Minor		Resolved an issue where configuration commits could intermittently fail when applying certain routing policy changes. The problem occurred only under specific conditions during commit processing and could result in the commit operation aborting unexpectedly. This fix improves commit stability when updating routing policies.
PR NumberSynopsisCategory: Issues related to NETCONF
1879816
Major		GNMI get native configuration garbage reply when there is no configuration related to openconfig
Product-Group=junos
Severity=Major		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.
1906621
Major		RPC reply delayed for commit during NETCONF over SSH session on Junos TVP-based VMhost platforms
Product-Group=junos
Severity=Major		On JUNOS VM Host-based platforms, when performing NetConf "", an internal script caused its PID to be displayed in the NETCONF session during commit.
PR NumberSynopsisCategory: content filtering bugs
1927484
Critical		Traffic loss occurs due to high memory utilisation in UTM pools
Product-Group=junos
Severity=Critical		On Junos OS SRX platforms, configuring cache preload in web filtering causes high memory utilization in the UTM (Unified Threat Management) pool, which results in traffic loss.
PR NumberSynopsisCategory: VMHOST platforms software
1924890
Major		During vmhost upgrade or downgrade livirtd.conf file was not updated correctly
Product-Group=junosvae
Severity=Major		During update and downgrade of vmhost images the livirtd.conf cleanup entries had not been performed properly. See TSB103739 [juniper.net]. https://supportportal.juniper.net/s/article/VM-Host-system-will-fail-to-start-after-a-system-reboot-due-to-expired-Vcertificate
1927342
Minor		Junos VMhost platforms restart unexpectedly due to deadlock
Product-Group=junos
Severity=Minor		On all Junos VMhost platforms, when Junos performs disk access, a rare deadlock involving FreeBSD kernel processes will occur. This condition causes FreeBSD kernel panic, resulting in crash of vmcore and an unexpected device restart, leading to temporary system unavailability.
PR NumberSynopsisCategory: Virtual Private LAN Services
1806424
Major		The snmp mib walk on jnxVplsPwBindTable fails with vpls routing-instances having multiple mesh-groups
Product-Group=junos
Severity=Major		If VPLS mesh-groups are configured with different neighbours having different vpls-id the SNMP mib walk over jnxVplsPwBindTable might fail with the error Request failed: OID not increasing. No functional impact is seen due to this issue.
PR NumberSynopsisCategory: usf ams related issues
1913560
Major		Routing Engine restart on MX platforms with SPC3 line card could cause loss of traffic processing
Product-Group=junos
Severity=Major		On Junos MX960, MX240, and MX480 platforms using SPC3 service line cards, restarting the Routing Engine may result in the network security daemon (nsd) not starting or failing to program internal subsystems like service sets . When this occurs, the control plane becomes unavailable and traffic stops forwarding permanently. This is a timing related behavior observed during the boot sequence and does not appear on every restart.
PR NumberSynopsisCategory: usf flow and datapath issue on SPC3
1925039
Major		Memory leak in ipv4-to-ipv6 session reuse trigger flowd crash
Product-Group=junos
Severity=Major		On Junos OS MX240/MX480/MX960 platforms with MX-SPC3 cards, the flowd process crash and reboots the service PIC when a stale IPv4 session is mistakenly reused for IPv6 due to a memory issue. During process restart the services remain down, session information is briefly lost and active traffic will drop, however the system recovers automatically.
PR NumberSynopsisCategory: usf nat related issues
1881192
Major		NAT Pool Installation failure due to Service-Set name length mismatch
Product-Group=junos
Severity=Major		On MX240, MX480, and MX960 platforms with SPC3 ( Services Processing Card 3 ) , new NAT ( Network Address Translation ) pools may fail to install, this is due to a mismatch in service-set name length handling. The system stores only 32 characters for service-set information, causing failures when names exceed this limit.

 

 

24.2R2-S5 - List of Known issues

PR NumberSynopsisCategory: Software build tools (packaging, makefiles, et. al.)
1663426
Major		NETCONF: RPC get & get-configuration display invalid json format response for an OpenConfig when adds a routing-options configuration
Product-Group=junos		After adding a "routing-options" configuration via OpenConfig operation, subsequent "get" and "get-configuration" may display an invalid JSON format.

Resolved In: evo:24.2R2-S5-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:25.2R2 junos:25.3R1
PR NumberSynopsisCategory: EX4300 Platform implementation
1631640
Major		The rollback might bring down the devices and the cores also might be observed
Product-Group=junosvae		On EX4300-MP platforms, when the command 'request system software rollback' is performed device is going down and dcpfe cores are dumping.

Resolved In: junos:21.2R3-S1 junos:21.4R3 junos:22.3R1
PR NumberSynopsisCategory: SRX Fleming Platforms related issues
1897025
Minor		Health monitor process in SRX cluster causing shared resource lock errors in chassisd
Product-Group=junos		On all SRX platforms in cluster, The "failed to lock chassis" error is seen in chassisd(Chassis Daemon) logs when health monitor process is enabled and subscribed to telemetry sensors, this is due to an internal process access issue.

Resolved In: junos:24.4R2-S2 junos:25.2R2 junos:25.4R1 junos:26.1R1
PR NumberSynopsisCategory: ACX L2 related features
1933501
Major		Device remains down after reboot, when "input-vlan-map tag-protocol-id" is configured but "ethernet-switch-profile tag-protocol-id" is deleted
Product-Group=junos		On all Junos platforms, if an interface is configured with "input-vlan-map tag-protocol-id" and the associated "ethernet-switch-profile tag-protocol-id" is deleted while the VLAN mapping is still active, the system may incorrectly allow the configuration commit. If the device is subsequently rebooted or the chassis is restarted, the device may fail to recover and remain down, resulting in traffic impact.

Resolved In: evo:25.4R2-EVO junos:23.2R2-S7 junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: "agentd" software daemon
1923848
Major		Junos Evolved platfrom, when gNMI collecting data from "optics/lanediags/lane/lane_laser_receiver_power_dbm" and "optics/lanediags/lane/lane_laser_output_power_dbm" are unreadable
Product-Group=junos		The JavaScript Object Notation (JSON) encoding of leafs of type "ieeefloat32"(https://github.com/openconfig/public/blob/master/release/models/types/openconfig-types.yang#L127) is not correct, causing gRPC Network Management Interface (gNMI) data outputs unreadable.

Resolved In: evo:24.4R2-S4-EVO evo:25.4R2-EVO evo:26.2R1-EVO junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: BBE Layer-2 Bitstream Access
1941118
Major		Modifying "inner-vlan-id-swap-ranges" with active L2BSA subscribers causes new login failures
Product-Group=junos		On Junos MX Broadband Edge (BBE) platforms where Subscriber access management service Layer-2 Bitstream Access (L2BSA) solution is deployed, when "inner-vlan-id-swap-ranges" is modified in the presence of active L2BSA subscribers, free inner-vlan-id count is not calculated correctly, hence subsequent L2BSA login attempts fail and subscribers move to pending state.

Resolved In: evo:26.2R1-EVO evo:26.3R1-EVO junos:23.2R2-S4-J12 junos:23.2R2-S7 junos:26.2R1
PR NumberSynopsisCategory: Border Gateway Protocol
1854194
Major		Handling cores when always-compare-med is configured in BGP path selection
Product-Group=junos		When using rib-groups, which copy inet.3 routes to inet.0 and inet6.3, configuring path-selection always-compare-med triggers a local RIB evaluation that will miss inet6.3 because inet6.3 tables are not initialized as a BGP RIB. As a result, Inet6.3 routes will not get updated.

Resolved In: evo:23.4R2-S8-EVO evo:24.4R2-EVO evo:25.1R1-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:22.4R3-S7-J1 junos:23.4R2-S8 junos:24.4R2 junos:25.1R1 junos:25.2R1 junos:25.3R1
1864676
Major		The rpd process will crash due to memory leak
Product-Group=junos		The rpd process will crash due to a memory leak when configuration using apply-groups or ephemeral database for "routing-options autonomous-system independent-domain".

Resolved In: evo:22.2R3-S7-EVO evo:24.4R2-EVO evo:25.2R1-S2-EVO evo:25.2R2-EVO junos:20.3X75-D442 junos:22.2R3-S7 junos:23.4R2-S5 junos:24.4R2 junos:25.2R1-S2 junos:25.2R2 junos:25.3R1
1875144
Minor		Longer convergence is seen for a BGP neighbor having validation configured in its import policy
Product-Group=junos		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
PR NumberSynopsisCategory: Track PRs in BGP Flow Spec area & is part of BGP inside RPD.
1945627
Minor		BGP IPv6 Flow Specification Session Flapping When inet6-flow Is Enabled
Product-Group=junos		In certain Junos OS releases, BGP sessions may repeatedly reset when IPv6 Flow Specification (inet6-flow) is enabled. This behavior occurs when the router receives specific IPv6 Flow Specification updates that include a default (wildcard) match. Earlier releases do not exhibit this behavior, leading to a difference in observed stability when upgrading.

Resolved In: evo:23.4R2-S8-EVO evo:24.4R2-S4-EVO evo:25.2R2-S1-EVO evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:21.2R3-S11 junos:23.4R2-S8 junos:24.4R2-S4 junos:25.2R2-S1 junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: MX Platform SW - UI management
1898722
Major		The craft-control process is unable to start on MX10004/MX10008 platforms
Product-Group=junos		On all Junos MX10004 and MX10008 platforms with FPM/craft interface, the craftd (craft control daemon) is unable to run, it causes the craft-control process does not start properly, leading the jnxAlarmRelayMode unable to retrieve data when an alarm condition is triggered. The issue does not cause traffic impact and only may affects monitoring traffic.

Resolved In: junos:24.4R2-S1 junos:25.2R2 junos:25.4R1
1906927
Major		SNMP jnxDomCurrentLaneWarnings OID values are wrong due to other lane values are copied from lane 0
Product-Group=junos		When a interface supports multiple lanes, the SNMP OID jnxDomCurrentLaneWarnings is incorrectly handled as a single lane, resulting in the value from lane 0 being replicated across all other lanes.

Resolved In: junos:23.2R2-S7 junos:23.4R2-S8
PR NumberSynopsisCategory: L2NG Access Security feature
1911142
Major		Client IP assignment failure observed on EX4300 due to DHCPv6 snooping validation issue
Product-Group=junos		On EX4300, DHCPv6 ( Dynamic Host Configuration Protocol for IPv6 ) clients will fail to receive IP addresses due to improper client entry handling when DHCPv6 snooping is enabled.

Resolved In: junos:21.4R3-S12
PR NumberSynopsisCategory: OpenSSL and related subsystems
1939872
Major		xnm-ssl: TLS connection fails with RSA cert and key size of 1024
Product-Group=junos		Starting with stunnel version 5.75, the application operates with OpenSSL Security Level 2 by default when linked with OpenSSL versions that enforce modern security policies. At Security Level 2, OpenSSL requires a minimum RSA key size of 2048 bits. As a result, certificates using RSA 1024-bit keys are no longer accepted. If a service is configured with a certificate using a 1024-bit RSA key, stunnel will fail to load the certificate and the service may fail to start, typically producing an error similar to: SSL_CTX_use_certificate: ee key too small. Impact Systems using 1024-bit RSA certificates for TLS authentication with stunnel may experience service startup failures or TLS handshake failures after upgrading to stunnel 5.75. Recommended Action It is recommended to replace existing 1024-bit RSA certificates with certificates using RSA 2048-bit or stronger keys to comply with modern cryptographic security standards.

Resolved In:
PR NumberSynopsisCategory: JDM issues in CSDS solution
1914935
Critical		Junos OS: MX Series: Missing Authorization for specific 'request' CLI commands in a JDM/CSDS scenario (CVE-2026-33785)
Product-Group=junos		A Missing Authorization vulnerability in the CLI of Juniper Networks Junos OS on MX Series allows a local, authenticated user with low privileges to execute specific commands which will lead to a complete compromise of managed devices. Please refer to https://supportportal.juniper.net/JSA107872 [juniper.net] for more information.

Resolved In: evo:25.4R1-EVO evo:26.1R1-EVO junos:24.4R2-S3 junos:25.2R2 junos:25.4R1 junos:25.4R2 junos:26.1R1
PR NumberSynopsisCategory: EVPN ELAN/E-TREE
1882561
Major		EVPN-MPLS BUM Traffic Disruption Due to Incorrect QinQ STag Insertion
Product-Group=junos		On Junos OS ACX5448/ACX710 platforms, the traffic towards the MPLS (Multiprotocol Label Switching) core Provider Edge (PE), specifically BUM (Broadcast, Unknown Unicast, and Multicast) traffic, has a QinQ (802.1ad) Service Tag (STag) added to the Customer (CTag). This insertion can disrupt traffic forwarding, leading to malformed packets or corruption of the destination MAC address in the inner Ethernet header.

Resolved In: junos:24.4R2 junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: Host path software for ACX platform
1889637
Major		DHCP clients do not come up when VRF leak and "dhcp-relay" with "no-snoop" are configured under a routing-instance
Product-Group=junos		On all Junos OS Evolved ACX7K Series platforms, when DHCP (Dynamic Host Configuration Protocol) relay mode is used within a routing-instance scenario, DHCP clients fail to come up because DHCP offer packets are being dropped.

Resolved In: evo:23.4R2-S7-EVO evo:24.2R2-S4-EVO evo:24.2R2-S5-EVO evo:24.4R2-S4-EVO evo:25.2R1-S2-EVO evo:25.2R2-EVO evo:25.4R1-EVO evo:26.1R1-EVO junos:25.2R1-S2 junos:25.2R2 junos:25.4R1 junos:26.1R1
PR NumberSynopsisCategory: Dynamic rendering infrastructure
1745615
Minor		Telemetry data is not exported in an IS-IS scaled Segment Routing scenario
Product-Group=junos		On all Junos and Junos OS Evolved platforms configured with SR-ISIS(Segment Routing-Intermediate System to Intermediate System) and with gRPC/gNMI telemetry, subscription to the path: "/junos/services/segment-routing/sid/usage/" will not work and the output could not be proper. The issue could happen only in scaled configuration (Approximately, 4000 or more per-sid ingress sensors and 4000 or more IPv4/IPv6 per-sid egress sensors are configured).

Resolved In: evo:22.3X80-D47-EVO evo:23.2R2-S3-EVO evo:23.4R1-S2-EVO evo:23.4R2-EVO evo:23.4R2-S1-EVO evo:23.4R2-S2-EVO evo:23.4X31-EVO evo:24.2R1-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:23.2R2-S3 junos:23.4R1-S1 junos:23.4R1-S2 junos:23.4R2 junos:23.4R2-S1 junos:23.4X30-D30 junos:24.2R1 junos:24.2R2 junos:24.3B1 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: EVO L2 Control Plane PRs
1914423
Major		On-change telemetry events dropped when l2ald telemetry queue memory limit is not configured
Product-Group=junos		On all Junos and Junos OS Evolved platforms, when l2-learning telemetry is enabled without explicitly configuring a memory limit for the l2ald (Layer 2 Address Learning Daemon) telemetry queue, the default memory limit is not applied. As a result, all on-change telemetry events are dropped.

Resolved In: evo:24.2R2-S5-EVO evo:24.4R2-S3-EVO evo:25.2R1-S2-EVO evo:25.2R2-EVO evo:25.4R1-EVO evo:25.4R2-EVO evo:26.1R1-EVO junos:24.4R2-S3 junos:25.2R1-S2 junos:25.2R2 junos:25.4R1 junos:25.4R2 junos:26.1R1
PR NumberSynopsisCategory: mgd, ddl, odl infra issues
1867821
Major		The "ui-gnmi-pubd.log" file growth may cause disk space issues on all Junos OS Evolved platforms
Product-Group=junos		On all Junos OS Evolved platforms, when telemetry is enabled and an active gNMI subscription includes a configuration path, the "ui-gnmi-pubd.log" file will grow continuously without log rotation or archival. This behaviour will lead to potential disk space exhaustion over time, however, there is no traffic impact due to this issue.

Resolved In: evo:23.4R2-S7-EVO evo:24.2R2-S5-EVO evo:24.4R2-S1-EVO evo:24.4R2-S1-J1-EVO evo:25.2R2-EVO evo:25.2X100-EVO evo:25.4R1-EVO evo:26.1R1-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:25.4R1
PR NumberSynopsisCategory: EVPN control plane issues
1862755
Critical		The associated EVPN RI peers are not learning routes when there is change in EVPN RI name or EVPN RI is deleted and added back
Product-Group=junos		On all Junos and Junos OS Evolved platforms with Dual RE with NSR enabled, if automatic RD (Route-Distinguisher) is used for EVPN (Ethernet VPN) RI (Routing Instances) in a scaled configuration setup, and when there is a change in the EVPN RI or the EVPN RI is deleted and added back, the associated EVPN RI remote peers are not learning routes, which results in traffic loss.

Resolved In: evo:24.2R2-S4-EVO evo:24.4R2-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:24.4R2 junos:24.4R2-S2 junos:25.2R1-S2 junos:25.2R2 junos:25.3R1
PR NumberSynopsisCategory: ACX7332 & ACX7348 Platform Software
1896521
Minor		Intermittent "broadsync_lock_failure" alarms are seen on Junos OS Evolved ACX platforms
Product-Group=junos		On Junos OS Evolved ACX platforms, "broadsync_lock_failure" alarms are seen intermittently without any external trigger. These alarms are seen as a result of internal firmware misconfiguration and affects PTP (Precision Time Protocol) functionality. The alarms are cleared after few seconds (~10 secs) once the broadsync lock is restored.

Resolved In: evo:25.4R1-EVO evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: Kernel software for AE/AS/Container
1898780
Major		MPC10E PPPoE keepalive not working after FPC slot restart, multiple subscriber entries with same MAC address get created.
Product-Group=junos		MPC10E PPPoE keepalive not working after FPC slot restart, multiple subscriber entries with same MAC address get created. In this scenario PPPoE subscribers are stuck on MX in Active state after client connection is aborted. Duplicate client connections will be created and potentially local address pools exceed limits and report out of addresses.

Resolved In:
PR NumberSynopsisCategory: jdhcpd daemon
1934742
Major		DHCPv6 Relay Active Leasequery not able to establish TCP session to peer
Product-Group=junos		On all MX platforms, when configuring Dual Stack DHCPv6 ALQ without configuring DHCPv4 ALQ (active-leasequery), the ALQ will not be able to establish the TCP (Transmission Control Protocol) session for the ALQ peer due to XID (Exchange Identification) mismatch. This can lead to DHCPv6 subscriber bindings sync issue and server ALQ, resulting in compromising the redundancy functionality.

Resolved In: junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: SRX power-mode (PMI/PME)
1858490
Major		flowd crashes due to a timing issue during IPsec SA re-keying on certain SRX platforms
Product-Group=junos		On certain SRX platforms, the flowd process crash is observed during Internet Protocol Security (IPsec) Security Association (SA) re-keying. This occurs due to an internal timing issue, leading to IPsec tunnel establishment failure, traffic loss during re-key events, and traffic switchover.

Resolved In: junos:23.2R2-S7 junos:23.4R2-S8 junos:24.2R2-S4 junos:24.4R2-S4 junos:25.2R2-S1 junos:25.4R1-S2 junos:25.4R2 junos:26.1R1 junos:26.2R1
PR NumberSynopsisCategory: IPSEC/IKE VPN
1937239
Major		Process crash during IPSEC tunnel operations due to error.
Product-Group=junos		On all SRX platforms with IPSEC VPN tunnel configuration, the srxpfe process leaks during IPSEC tunnel operations when internal error occurs. With a period of time, memory can continue to grow causing the process to crash with error.

Resolved In: junos:25.2R2-S1 junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: Security platform jweb support
1931780
Major		The Captive Web Authentication might not be completed on specific Junos versions for EX Series switch
Product-Group=junos		When a MAC-RADIUS authentication succeeds and the RADIUS server returns CWA redirect attributes (URL-Redirect), the EX switch should intercept client HTTP traffic and return an HTTP 302 redirect to the Captive Portal. The switch instead responded with HTTP 405 (Method Not Allowed), causing the client to bypass the CWA redirect workflow.

Resolved In: evo:25.4R2-EVO evo:26.2R1-EVO junos:23.2R2-S7 junos:23.4R2-S8 junos:24.4R2-S4 junos:25.2R2 junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: Layer 2 Control Module
1938991
Minor		VSTP bridge-priority configuration not taking effect for VLAN group
Product-Group=junos		The VSTP (VLAN Spanning Tree Protocol) bridge-priority configuration does not apply to VLAN (Virtual LAN) groups as expected. This issue results in VLAN groups not reflecting the intended bridge priority. This configuration issue can affect the network's root bridge election process, causing potential inconsistencies in network behavior and performance.

Resolved In: evo:26.1R1-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:26.1R1 junos:26.2R1
PR NumberSynopsisCategory: Label Distribution Protocol
1852934
Major		The rpd process crash is seen during RE switchover
Product-Group=junos		On Junos and Junos OS Evolved dual RE (Routing-Engine) platforms with LDP (Label Distribution Protocol) configuration, an rpd process crash in the new master RE is observed during a RE switchover.

Resolved In: evo:25.3R1-EVO junos:25.3R1
1906611
Major		Crash in the rpd process after LDP P2MP LSP Identifier reaches its maximum value and rolls over, due to duplicate identifier allocation
Product-Group=junos		On all Junos OS and Junos OS Evolved versions that support Label Distribution Protocol Point-to-Multipoint Label Switched Paths (LDP P2MP LSPs), the rpd process (routing protocol daemon) crashes when an LSP Identifier reaches its 24-bit maximum value (224 1 = 16, 777, 215) and rolls over to the starting value because a duplicate identifier is incorrectly allocated. This condition occurs only after prolonged tunnel flapping (typically more than 16 million flaps). When the rpd process crashes, routing convergence is briefly disrupted, and services relying on label-switched traffic are impacted until the process automatically restarts.

Resolved In: evo:26.1R1-EVO junos:26.1R1
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1865432
Critical		The dcpfe crash is seen in the EVPN-VXLAN scenario
Product-Group=junos		On QFX5120-48Y and QFX5120-32C platforms, dcpfe crash is seen due to inline BFD (Bidirectional Forwarding Detection) configured in EVPN-VXLAN (Ethernet VPN - Virtual Extensible Local Area Network) scenario.

Resolved In: junos:23.4R2-S4 junos:24.4R2 junos:25.1R1 junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: Issues related to krt-async routing infrastructure
1866522
Major		VPLS session stays down after interface flaps
Product-Group=junos		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.

Resolved In: evo:23.2R2-S5-EVO evo:23.2X2-EVO evo:23.4R2-S8-EVO evo:24.2R2-S4-EVO evo:24.4R2-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:26.2R1-EVO junos:23.4R2-S8 junos:25.2R2 junos:25.3R1
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 evo:25.4R1-EVO junos:23.2R2-S2-J9 junos:23.4R2-S5 junos:24.4R2-S2-J8 junos:24.4R2-S3 junos:25.2R2 junos:25.2R2-S1 junos:25.3R1 junos:25.4R1 junos:25.4R2 junos:26.1DCB
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1849202
Major		BGP route still seen in routing table when route not available
Product-Group=junos		On all Junos and Junos Evolved platforms , the router learns routes through the BGP (Border Gateway Protocol) and has the feature: "BGP RIB Sharding" enabled for IPv4. These routes are stored in the Inet.0 routing table. Later, if the neighbor that announced this route or the protocols associated with the routing table of the used VRF (Virtual Routing and Forwarding) are removed, the route remains in the routing table, and hence traffic is forwarded to the stale routes.

Resolved In: evo:22.3X50-EVO evo:22.3X50-J3-EVO evo:22.4R3-S7-EVO evo:23.2R2-S4-EVO evo:23.4R2-S4-EVO evo:24.2R2-S4-EVO evo:24.4R2-EVO evo:25.1R1-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:22.4R3-S7 junos:23.2R2-S4 junos:23.4R2-S5 junos:24.2R2-S4 junos:24.4R2 junos:25.1R1 junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: SRX-1RU platfom related protocol, QoS, filtering features et
1886757
Minor		Alarms for high usage in /var partition are not generated
Product-Group=junos		On Junos SRX4600/SRX4700/SRX1600/SRX2300/SRX4300 platforms, alarms for high usage at /var partition storage is not reported.

Resolved In: evo:25.4R1-EVO junos:22.4R3-S9 junos:23.2R2-S6 junos:23.4R2-S7 junos:25.2R1-S1 junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: ZT/YT pfe firewall software
1848740
Critical		Support FW_Continue with HW Segmented Filters on AFT TRIO platform
Product-Group=junos		This PR is a performance optimization PR for AFT Trio-based systems. Software Segmented Firewall enables FLT support for a maximum of 3584 terms, this PR adds support for HW segmented filter with support to up to a maximum of 8192 terms and better performance than the software segmented filters.

Resolved In: evo:24.4R2-EVO evo:25.1R1-EVO evo:25.2R1-EVO junos:24.4R2 junos:25.1R1 junos:25.2R1
PR NumberSynopsisCategory: Issues related to broadband edge apps (PPP, DHCP) on Trio ch
1924812
Minor		Dual stack PPPoE/DHCPv6 syslog reports PFE_ERROR_INVALID_STATE fd01:3333:b205:44f1:: /64 => source lookup is not enabled for flow 18558885
Product-Group=junos		Dual stack PPPoE/DHCPv6 syslog reports PFE_ERROR_INVALID_STATE fd01:3333:b205:44f1:: /64 => source lookup is not enabled for flow 18558885

Resolved In: evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:25.4R2 junos:26.2R1

 

Modification History

First publication 2026-05-07