Alert Type

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

Product Affected

All platforms running Junos version 24.4 software

Alert Description

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

For your review

Solution

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

24.4R2-S5 - List of Fixed issues

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
1916697
Minor		srx1600 doesn't learn the max entries for l2 table
Product-Group=junosvae
Severity=Minor		MAC limit Count show 65k in srx1600, but it stops learning at 28k.
PR NumberSynopsisCategory: SRX Fleming Broadcom TD3/SDK, datapath related issue
1943275
Critical		On some SRX platforms configuring global-mode switching where 1G SFP is used on 10G port causes port to go down
Product-Group=junos
Severity=Critical		On SRX1600, SRX2300 and SRX4300 platforms, upon configuring "set protocols l2-learning global-mode switching" where 1G SFP is used on 10G port the port goes down after sometime causing traffic drop. This traffic drop is only subjected to the port where the configuration is applied, thus the other ports remains unaffected.
PR NumberSynopsisCategory: Fabric for LC1300 and SIB3
1964102
Major		Major alarms for fabric link faults that result in reduced fabric capacity are introduced on PTX10004 and PTX10008 platforms
Product-Group=junos
Severity=Major		On Junos OS Evolved PTX10004 and PTX10008 platforms with LC1301 line cards and SF5 fabric, fabric link faults need to be reported as major alarms. Link faults can occur during system operation and result in reduced fabric capacity with partial impact. This enhancement introduces the new alarm "One or more PFE pairs operating with less than acceptable fabric capacity" to indicate reduced fabric capacity conditions.
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
Severity=Major		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.
PR NumberSynopsisCategory: QFX Control Plane VXLAN
1926468
Major		EVPN-VXLAN: Duplicate Proxied Neighbor Advertisements Missing Router/Override Flags Disrupt IPv6 Connectivity
Product-Group=junos
Severity=Major		When Junos and Junos Evolved platform sends two proxied Neighbor Advertisement for default gateway, second one without Router flag and target Link-Layer address. The second Neighbor Advertisement can disrupt connectivity for end hosts. A proxied Neighbor Advertisement (NA) is an IPv6 mechanism where a network device responds to Neighbor Discovery requests on behalf of another device, instead of the actual endpoint replying itself.
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1951682
Major		Intermittent traffic loss due to re-arp failure of ARP entries learnt over VTEP
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms with EVPN-MPLS (Ethernet VPN- Multiprotocol label switching) and VXLAN (Virtual Extensible LAN) stitching , ARP (Address Resolution Protocol) entries learned over a VTEP (Virtual Tunnel Endpoint) interface are not refreshed by re-ARP (unicast ARP refresh) mechanism. As a result, ARP entries can age out and are temporarily removed causing intermittent traffic disruption. This issue will be restored automatically when ARP entries are re-learnt after some delay(several hundreds milli seconds).
PR NumberSynopsisCategory: EX optics issues
1879743
Major		Intermittent port flaps are seen with SFP-T connected
Product-Group=junos
Severity=Major		On EX4400-48F and EX4400-24X platforms with SFP-T (740-013111) connected, the ports can flap intermittently. This is related to ports 36-47 on these platforms only, which results in the traffic loss of ~5 seconds.
PR NumberSynopsisCategory: Enhanced Broadband Edge support for firewall
1902909
Major		Junos OS: MX Series: For subscribers configured on static interfaces, input filters are not in effect (CVE-2026-57031)
Product-Group=junos
Severity=Major		An Improper Check for Unusual or Exceptional Conditions vulnerability in the packet forwarding engine (PFE) of Juniper Networks Junos OS on MX Series allows adjacent subscribers to bypass configured firewall filters.Please refer to https://supportportal.juniper.net/JSA110091 [juniper.net] for more information.
PR NumberSynopsisCategory: ACX7332 ACX7348 Interfaces software
1965887
Critical		ACX7020/ACX7024/ACX7024X/ ACX71xx/ACX73xx/ACX7509/ Ufispace is not able to configure "no-temperature-monitoring" for ports higher than 23
Product-Group=junos
Severity=Critical		ACX7020/ACX7024/ACX7024X/ ACX73xx/ACX7509/Ufispace is not able to configure "no-temperature-monitoring" for ports higher than 23
PR NumberSynopsisCategory: ACX7509 Linecard (FPC) related issues
1931707
Minor		Framing errors will be seen on some ACX Evolved platforms when traffic is carried over 40G ports
Product-Group=junos
Severity=Minor		On Junos Evolved ACX7509, ACX7348, and ACX7332 platforms, framing errors will be seen on some ACX Evolved platforms when traffic is carried over 40G ports
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: Category for JET(JUNOS Extension Toolkit) related issues
1933395
Major		System connections are not established while Subscribing for OC path using ssl local-certificates after upgrading to 24.4R2-S3-EVO
Product-Group=junos
Severity=Major		System connections are not established while Subscribing for OC path using ssl local-certificates after upgrading to 24.4R2-S3-EVO. This issue is only applicable on 24.4R2-S3-EVO and 24.4R2-S4-EVO
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: Periodic Packet Management Daemon
1935823
Major		Protocols dependent on ppmd like LACP fails to recover after a GRES
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms when GRES (Graceful Routing Engine Switchover) is enabled and any other protocol dependent on Periodic Packet Management (PPM) in non-centralised mode(distributed to FPC's) is configured, after an RE (Routing Engine) switchover, the protocol fails to recover, resulting in services dependent on the protocol to go down.
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1947250
Major		Next-hop updates may fail for host routes installed in the LPM table when lpm-profile is configured without the unicast-in-lpm option
Product-Group=junos
Severity=Major		On QFX5K and EX4K platforms, next-hop updates for host routes in the LPM table may fail when the lpm-profile is configured without the unicast-in-lpm option. This can result in stale next-hop entries in hardware, causing traffic to continue forwarding over invalid or costed-out paths.
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1877194
Major		Traffic drop is seen in a scaled scenario on certain EX platforms
Product-Group=junos
Severity=Major		On Junos EX4400, EX4400-24T, EX4400-24X, EX4400-48T, EX4400-48F, EX4400-24MP, EX4400-48MP, EX4300-MP platforms, it is observed that in a scaled scenario with more than three thousand next hops configured, further next hop installation fails which in turn causes routes to fail leading to traffic drop.
PR NumberSynopsisCategory: SRX branch platforms
1913911
Major		ARP reply packets may be sent out from the STP blocked port
Product-Group=junos
Severity=Major		On SRX300-series devices, when ethernet-switching is used with spanning-tree protocol enabled, in some cases ARP reply packets may be sent out from a spanning-tree blocked port.
1943202
Minor		File copy CLI command fails to resolve remote hostnames when no username is specified
Product-Group=junos
Severity=Minor		On all Junos OS and Junos OS Evolved platforms, when copying a file to a remote host using a hostname, the device is unable to resolve the hostname, causing the file transfer to fail. Secure Copy (SCP) operations are not affected and continue to work as expected. This issue does not impact network services or device functionality.
1960745
Major		ICU upgrade fails on SRX300/320/340/345 platforms
Product-Group=junos
Severity=Major		On all SRX300/320/340/345 platforms, when ICU (In-cluster upgrade) is performed, the first node gets upgraded but the secondary node fails to come up within the timeout window of 20 mins. Service impact will be observed as the ICU upgrade fails.

 

 

24.4R2-S5 - List of Known issues

PR NumberSynopsisCategory: EX2300/3400 PFE
1970694
Major		Unicast routes not getting installed in the hardware causing traffic issue
Product-Group=junos		On Junos based EX2300 and EX3400 platforms with Equal Cost Multi-path (ECMP) and any Interior Gateway Protocol or Exterior Gateway Protocol (IGP/EGP) enabled, when due to a topology or configuration change the Kernel must change a route from ECMP to a single unicast next-hop: the hardware continues to hold the stale ECMP entry instead of installing the new unicast route. The hardware forwarding state did not match the control-plane forwarding state, causing traffic blockage and looping. This is a rare issue.

Resolved In: junos:23.4R2-S6-J9 junos:25.4R2 junos:26.2R2 junos:26.4R1
PR NumberSynopsisCategory: NSD process
1965832
Major		DNS cache failure occurs when the number of routes to the DNS server is a multiple of 256, causing FQDN object resolution to fail on SRX platforms
Product-Group=junos		On Junos SRX platforms of Mid-range (SRX1500, SRX1600, SRX2300) and High-end SRX platforms (SRX4K and SRX5K) platforms, Domain Name System (DNS) cache will not work for Fully Qualified Domain Name (FQDN) referenced objects which are a match criteria in a security policy or NAT rules, when the total number of routes that can reach to the DNS server is a multiple of 256. When this happens the DNS query will not be sent out from the SRX, and the TTL value in the DNS cache table will stay 0 or no IP address will not be populated in the dns-cache table. The related NAT or security-policy lookup may fail, which can lead to traffic drops.

Resolved In: junos:23.2R2-S8 junos:25.4R2 junos:26.2R2 junos:26.4R1
PR NumberSynopsisCategory: MX Services URL filter
1926259
Major		Junos OS: MX Series: Web filtering doesn't block specifically formatted URLs (CVE-2026-57054)
Product-Group=junos		A Use of Incorrectly-Resolved Name or Reference vulnerability in the URL filtering plugin of Juniper Networks Junos OS on MX Series allows a unauthenticated, network-based attacker to bypass web filtering and access downstream resources that should be unreachable. Please refer to https://supportportal.juniper.net/JSA110093 [juniper.net] for more information.

Resolved In: evo:25.4R2-EVO evo:26.1R1-EVO evo:26.2R1-EVO junos:21.2R3-S11 junos:22.2R3-S8 junos:22.3R3-S5 junos:23.2R2-S7 junos:23.4R2-S8 junos:24.2R2-S5 junos:24.4R2-S4 junos:25.2R2-S1 junos:25.4R1-S2 junos:25.4R2 junos:26.1R1 junos:26.2R1
PR NumberSynopsisCategory: JWEB for QFX family
1947005
Minor		RE 0 /var partition is full || httpd deleted-unclosed files
Product-Group=junos		Non service impacting issue

Resolved In: junos:25.4R2 junos:26.2R2 junos:26.3R1 junos:26.4R1
PR NumberSynopsisCategory: Fabric for LC1300 and SIB3
1964102
Major		Major alarms for fabric link faults that result in reduced fabric capacity are introduced on PTX10004 and PTX10008 platforms
Product-Group=junos		On Junos OS Evolved PTX10004 and PTX10008 platforms with LC1301 line cards and SF5 fabric, fabric link faults need to be reported as major alarms. Link faults can occur during system operation and result in reduced fabric capacity with partial impact. This enhancement introduces the new alarm "One or more PFE pairs operating with less than acceptable fabric capacity" to indicate reduced fabric capacity conditions.

Resolved In: evo:24.4R2-S3-C1-EVO evo:24.4R2-S3-J1-EVO evo:24.4R2-S4-EVO evo:24.4R2-S5-EVO evo:25.4R2-EVO evo:26.2R1-S2-EVO evo:26.2R2-EVO evo:26.4R1-EVO evo:27.1R1-EVO junos:25.4R2 junos:26.2R2 junos:26.4R1
PR NumberSynopsisCategory: BBE database related issues
1894192
Minor		EX/QFX : Message 'shmlog: argcnt 166 not enough memory for argtype' appears
Product-Group=junos		The memory allocation issue persists on EX and QFX devices. As a result, you may observe the message 'shmlog: argcnt 166 not enough memory for argtype' when executing command, show version detail.

Resolved In: junos:23.4R2-S6
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		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.

Resolved In: evo:25.2R1-EVO junos:23.2R2-S7 junos:23.4R2-S8 junos:24.2R2-S5 junos:24.4R2-J14 junos:25.2R1 junos:25.2R2-S2
PR NumberSynopsisCategory: Border Gateway Protocol
1712527
Minor		The PE advertises incorrect next-hop towards CE although BGP export policy configured with next-hop under policy-statement
Product-Group=junos		The show route advertising-protocol bgp reporting nexthop self rather than IP in the configured policy-statement for next-hop.

Resolved In: evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:21.2R3-S6 junos:21.3R3-S5 junos:21.4R3-S7 junos:22.2R3-S2-J2 junos:22.2R3-S3 junos:22.4R2-S1 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1 junos:23.4R1 junos:24.2R2
1818545
Major		BGP-LU Label is incorrect after convergence
Product-Group=junos		On all Junos and Junos OS Evolved platforms, traffic coming in with the BGP-LU label can drop post link-failure when BGP-LU (Border Gateway Protocol-Labeled-Unicast) with 'per-prefix-label' and IGP TI-LFA (Topology-Independent Loop-Free Alternate) is enabled.

Resolved In: evo:22.2R3-S7-EVO evo:22.3X80-D49-EVO evo:23.2R2-S3-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO evo:25.2R2-EVO junos:21.2R3-S9 junos:21.2X35 junos:22.2R3-S6 junos:22.2R3-S7 junos:22.3R3-S5 junos:22.4R3-J1 junos:22.4R3-S10 junos:22.4R3-S4 junos:23.2R2-S3 junos:23.4R2-S1 junos:23.4R2-S8 junos:24.2R1-S2 junos:24.2R2 junos:24.3R1 junos:24.4R1 junos:24.4R2-S3 junos:24.4R2-S4 junos:24.4R2-S6 junos:25.2R1-S2 junos:25.2R2
1889749
Critical		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:23.4R2-S8-EVO evo:24.2R2-S3-EVO evo:24.2X2-EVO evo:24.4R2-S4-EVO evo:25.2R1-S1-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO evo:25.4R2-EVO evo:26.2R1-EVO junos:21.2R3-S11 junos:21.2R3-S8-J22 junos:21.2R3-S9-J9 junos:23.2R2-S6 junos:23.4R2-S8 junos:24.2R2-S5 junos:24.4R2-S4 junos:25.2R1-S1 junos:25.2R2 junos:25.3R1 junos:25.4R1 junos:25.4R2
PR NumberSynopsisCategory: MX304 fabric issues (ULC side)
1969878
Minor		PFE remains disabled after MIC1 offline/online operation or hot swap
Product-Group=junos		On Junos OS MX304 platform, performing an LMIC (Line Module Interface Card) offline/online operation or LMIC hot swap on MIC1 (Modular Interface Card 1) causes the associated PFE (Packet Forwarding Engine) to remain disabled after recovery. This results in reduced fabric bandwidth and traffic impact due to fewer available PFEs.

Resolved In: junos:25.4R2 junos:26.2R2 junos:26.3R1 junos:26.4R1
PR NumberSynopsisCategory: MX304 interface specific
1967387
Minor		Active laser output detected from newly inserted optic on a disabled port
Product-Group=junos		On the MX304 platforms, When a transceiver is inserted into an empty port whose IFD (Interface Device) is administratively disabled, active laser output is detected even when the port is down. The laser-on logic ignored admin-disable state during OIR (Online Insertion and Removal), so the admin-down intent was never enforced. Therefore, when a transceiver is hot-inserted into a disabled port, the freshly powered-up optic comes up with its Tx laser enabled by default. There is no service impact.

Resolved In: evo:25.4R2-EVO evo:25.4R2-S1-EVO evo:26.4R1-EVO evo:27.1R1-EVO junos:25.4R2 junos:26.4R1
PR NumberSynopsisCategory: MX304 line card platform software
1843577
Major		Brief transient Temp Sensor Hot alarm observed on MX304 during reboot
Product-Group=junosvae		On MX304 platforms, a transient FPC xcvr Temp Sensor Hot alarm may briefly appear and then clear automatically during MIC power cycling or line card reboot operations. This condition occurs when temperature data has not yet been fully updated by the line card management daemon (lcmd). The alarm clears on its own and has no functional impact on the system or the hardware.

Resolved In: junos:24.2R2-S4 junos:25.1R1 junos:25.2R1 junos:25.2R2-S1 junos:25.4R2
PR NumberSynopsisCategory: MX304 Routing Engine issues
1886633
Major		Logs from internal ethernet links monitoring script keep repetitively logged to /var/log/messages file if "set system syslog file messages user any" config is used.
Product-Group=junos		Logs from internal ethernet links monitoring script keep repetitively logged to /var/log/messages file if "set system syslog file messages user any" config is used.

Resolved In: junos:26.2R1
1945622
Minor		On MX304 platforms, error logs are seen after reboot, due to a missing file presence check
Product-Group=junos		On MX304 platforms, repeated error messages are observed in Linux (jncl) logs after a reboot. The issue occurs when a shell script attempts to read the non-existent sysfs file: cat: /sys/devices/virtual/net/macvtap0/statistics/rx_errors There is no traffic or service impact.

Resolved In: junos:23.4X18 junos:25.2X31 junos:25.4R2 junos:26.3DCB junos:26.3R1
PR NumberSynopsisCategory: Device Configuration Daemon
1970933
Major		Tunnel interface flaps observed on every DNS TTL refresh when FQDN is used as the destination of IP-IP tunnel and the ip-0/0/0 interface is in a routing-instance
Product-Group=junos		On Junos OS SRX platforms, when FQDN (Fully Qualified Domain Name) is used for the destination of IP-IP (Internet Protocol-in-Internet Protocol) tunnel and the ip-0/0/0 interface is in a routing-instance, the ip-0/0/0 interface flaps every time the SRX sends DNS (Domain Name System) query. The issue is caused by a timing condition between rpd (Routing Protocol Daemon) and dcd (Device Control Daemon) during DNS (Domain Name System) re-resolution, resulting in tunnel interface flaps, leading to packet loss.

Resolved In: junos:25.4R2 junos:26.2R2 junos:26.4R1
PR NumberSynopsisCategory: EVPN control plane issues
1888931
Critical		EVPN: rpd crashes after GRES when EVPN-VXLAN is configured under a logical system with NSR enabled
Product-Group=junos		On MX Series platforms with EVPN-VXLAN configured under a logical system and nonstop active routing (NSR) enabled, the routing protocol daemon (rpd) crashes on the new primary Routing Engine after a graceful Routing Engine switchover (GRES). The crash causes BGP sessions to flap, triggers EVPN core isolation, and flaps the VXLAN tunnel endpoint (VTEP) interface, resulting in transit traffic loss until rpd restarts and the sessions reconverge.

Resolved In: evo:25.4R1-EVO evo:25.4R2-EVO junos:25.4R1
1935768
Minor		router-mac community is not removed when exporting the routes into evpn
Product-Group=junos

Resolved In: evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:25.4R2 junos:26.2R1 junos:26.3R1
1963894
Major		Local MAC addresses are not learned on newly added EVPN all-active interfaces
Product-Group=junos		On Junos OS and Junos OS Evolved systems configured with Ethernet VPN (EVPN) Media Access Control Virtual Private Network (MAC-VRF) over Multiprotocol Label Switching (MPLS), when a new all-active interface is added to a service that uses a VLAN-aware instance with interfaces from multiple Ethernet Segments (ESIs) and Egress Link Protection (ELP) enabled, local Media Access Control (MAC) addresses are not learned on the newly added interface. As a result, Layer 2 forwarding for the affected service is impacted and complete loss of Layer 2 forwarding can occur for the affected service. Service can be restored by restarting the affected routing application

Resolved In: evo:24.4R2-S1-J11-EVO evo:24.4R2-S2-J30-EVO evo:24.4R2-S2-J31-EVO evo:24.4R2-S3-J24-EVO evo:26.2R2-EVO evo:26.3R1-EVO evo:26.4R1-EVO junos:26.2R2 junos:26.3R1 junos:26.4R1
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1943641
Major		ARP and MAC/IP table for virtual IP mac is not installed in bridge domain which is part if EVPN instance
Product-Group=junos		In all Junos and Junos OS Evolved platforms supporting EVPN-MPLS, EVPN-VXLAN when VRRP device is connected to EVPN PE with Aggregate Ethernet interface the VRRP virtual IP may fail to install ARP and destination route entries when the VRRP virtual MAC is learned on one FPC while the ARP response is received on another FPC with a source MAC mismatch.

Resolved In: evo:23.4R2-S8-EVO evo:24.2R2-S6-EVO evo:25.2R2-S2-EVO evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:22.2R3-S8 junos:23.4R2-S8 junos:23.4R2-S9 junos:24.2R2-S6 junos:25.2R2-S2 junos:25.4R2 junos:26.2R1 junos:26.3R1
PR NumberSynopsisCategory: EX interfaces issues
1870962
Major		The CPU high utilization is observed after PIC offline/online
Product-Group=junos		On EX4400 platforms with 4x25G or 1x100G ULM (Universal Link Module), the CPU hogs by CMQFX thread for as much as 3.7 secs when Firmware download occurs during PIC offline/online and PFE restart time / Device reboot. To speed up the firmware download operation, the MDIO clock (MDC) frequency is increased from 2.6 MHz to 9 MHz which reduced firmware download time from ~3.8 s to ~2.2 s. This is an enhancement PR.

Resolved In: junos:26.2R1
PR NumberSynopsisCategory: EX4400 PFE software
1930323
Major		[ECU CUC-3574] Multicast traffic sent upstream by MC receiver-side access switch (ACCESS.1), in addition to being sent upstream by MC source-side access switch, when PEG is configured on BLs, in EVPN VXLAN IP Clos with Enhanced OISM, SMET and GBP
Product-Group=junos		If there is only a single receiver for a TTL-1 stream in an EVPN fabric with source bd forward policy(https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/statement/forward-on-source-bridge-domain-edit-protocols-evpn-oism-enhanced.html) applied for such a stream throughout the EVPN fabric, that stream could be sent upstream again to the BLs from the receiver leaf , in addition to being sent sent by src leaf(EVPN PE directly attached to the source) as well.

Resolved In: junos:26.3R1
1943278
Minor		FXPC crash triggered by firewall filter modification leading to PFE restart on Junos EX/QFX platforms
Product-Group=junos		A rare issue has been observed on Junos EX and QFX platforms where the Forwarding eXtension Packet Controller (fxpc) process crashes after modifying firewall filter configurations, leading to a Packet Forwarding Engine (PFE) restart. This results in a short traffic disruption.

Resolved In: junos:25.4R2 junos:26.3R1
PR NumberSynopsisCategory: EX optics issues
1864715
Major		EX4100: 10g-BASE-T didn't come up after dc-pfe restart
Product-Group=junos		After multiple iterations of dc-pfe process restart, we may see interface with 10g-base-t transceiver (part# 740-123734) will not come up.

Resolved In:
PR NumberSynopsisCategory: Express PFE including evpn, vxlan
1927521
Major		Unexpected FPC reboot in QFX device after inserting and removing a transceiver
Product-Group=junos		On Junos QFX10002-60C/QFX10008/QFX10016 an unexpected FPC reboot with dcpfe core dump is experienced due to a transceiver plug-in plug-out in an Aggregated Ethernet (AE) interface member affecting all traffic on that line card. No manual intervention is required, fpc will automatically reboot and recover

Resolved In: junos:22.2R3-S8 junos:23.2R2-S8 junos:24.2R2-S6
PR NumberSynopsisCategory: SRX1500 platform software
1876867
Major		FPC goes offline and srxpfe core dump is generated during the system normal operation or boot-up
Product-Group=junosvae		FPC (Flexible PIC Concentrators) on SRX1500 device goes offline and generates srxpfe core dump on system boot-up or normal operation in a rare timing scenario. This issue cause a traffic impact.

Resolved In: junos:19.3R3-S12 junos:20.2R3-S11 junos:21.4R3-S12 junos:22.4R3-S8 junos:23.2R2-S5 junos:23.4R2-S4-J26 junos:23.4R2-S5 junos:24.2R2-S2 junos:24.4R2 junos:25.2R1 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:24.2R2-S6-EVO evo:24.2X2-EVO evo:25.2R2-S2-EVO evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:24.2R2-S6 junos:25.2R2-S2 junos:25.4R2 junos:26.2R1 junos:26.3R1
PR NumberSynopsisCategory: SRX4100/SRX4200 platform software
1956183
Minor		Delayed failover on SRX platforms after Primary Node Power Off
Product-Group=junos		This issue is seen on Junos SRX platforms (vSRX, SRX1500, SRX4100, SRX4200, SRX4600), when powering off the primary node, redundancy group 1 (RG1) fails over several seconds late, causing traffic drop during that window.

Resolved In: evo:25.4R2-EVO evo:26.2R2-EVO junos:24.4R2-S3-J26 junos:25.2R2-J1 junos:25.4R2 junos:26.2R2 junos:26.3R1
PR NumberSynopsisCategory: Signature Database
1919218
Minor		Adding new CLI option to jist conversion command.
Product-Group=junos		Adding new CLI option to jist conversion command. > request security idp jist-conversion ? Possible completions: input-file Snort rules file output-file Redirect converted attacks-set commands to this file best-effort-conversion Best effort conversion, skip unsupported Snort modifiers

Resolved In: evo:25.4R2-EVO evo:26.2R1-EVO junos:24.4R2-S4 junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: Libjtask for RPD tasks, scheduler, timers, memory, and slip
1966878
Major		The rpd process might restart during normal routing events due to a rare timing condition
Product-Group=junos		During normal routing events, the rpd process might restart due to a rare timing condition, temporarily impacting new route learning and route changes while transit traffic using already programmed routes may continue forwarding.

Resolved In: evo:25.4R2-EVO evo:26.2R2-EVO evo:26.3R1-EVO evo:26.4R1-EVO junos:25.4R2 junos:26.2R2 junos:26.3R1 junos:26.4R1
PR NumberSynopsisCategory: MX Inline Jflow
1444849
Minor		Sampling applications like port-mirror and inline-jflow are not supported on VPLS tunnel interfaces in ingress direction where ingress packets are sent to the IRB interface for routing. Configuration of sampling application on VPLS tunnel interfaces in such scenario causes packet to drop in ingress direction.
Product-Group=junos		Sampling applications like port-mirror and inline-jflow are not supported on VPLS tunnel interfaces in ingress direction where ingress packets are sent to the IRB interface for routing. Configuration of sampling application on VPLS tunnel interfaces in such scenario causes packet to drop in ingress direction.

Resolved In:
1981380
Major		Heap exhaustion generates a crash file and triggers a linecard reboot on mx platforms using affected line cards
Product-Group=junos		On MX Series platforms using MPC7, MPC8, MPC9, or LC2101/LC2103 line cards, when heap exhaustion prevents memory allocation during a memory write, the memory-write routine makes no forward progress and enters a loop, generating a crash file and triggering a linecard reboot.

Resolved In: evo:25.4R2-EVO evo:26.2R2-EVO evo:26.4R1-EVO evo:27.1R1-EVO junos:25.4R2 junos:26.2R2 junos:26.4R1
PR NumberSynopsisCategory: ISIS routing protocol
1955832
Minor		Inconsistent ISIS IPV6 topology information seen in "show isis adjacency detail" command
Product-Group=junos		On all Junos and Junos OS Evolved platforms with IS-IS and IPv6 enabled, after interface flap, command "show isis adjacency detail" shows additional IPv6 topologies along with Unicast topology in the output. This is a display issue and non service impacting.

Resolved In: evo:26.3R1-EVO
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: evo:24.2R2-S6-EVO evo:25.2R2-S2-EVO junos:23.4R2-S7-J21 junos:24.2R2-S6 junos:25.2R2-S2 junos:25.4R2 junos:26.2R1 junos:26.3R1
1967994
Major		Subscribers cannot obtain IP addresses nor renew DHCP leases when configuring persistent-storage for DHCP
Product-Group=junos		On Junos OS platforms, with Dynamic Host Configuration Protocol (DHCP) configured and including persistent storage, option-82, interface id and remote id enabled, there is a buffer overwrite triggered by a large size on session attributes when they are written in the persistent file which can cause multiple jdhcpd core dumps and jdhcp process crashes resulting in existing and new subscribers unable to obtain IP addresses . When the issue is observed it can lead to service disruption.

Resolved In: junos:23.2R2-S8 junos:26.2R2 junos:26.4R1
PR NumberSynopsisCategory: High Availability/NSRP/VRRP
1952478
Critical		SRG with IPsec enabled can get stuck on backup-backup state on an MNHA pair
Product-Group=junos		On SRX Series platforms configured in Multinode High Availability (MNHA), under a rare timing condition, on a Service Redundancy Group (SRG) with IPsec enabled, when the control plane on the lower priority backup node is not ready and the monitored IP/Interface/BFD flaps on the higher priority active node, the SRG can get stuck in a backup-backup state. As a result, all IPsec related traffic will be dropped.

Resolved In: junos:25.4R2 junos:26.2R1 junos:26.2R2 junos:26.3R1
PR NumberSynopsisCategory: Firewall Policy
1939433
Major		Flow sessions not synchronizing from primary to backup in SRX High Availability clusters
Product-Group=junos		On SRX devices operating in a High Availability cluster with logical-systems enabled, the backup node may display fewer flow sessions than the primary node due to incomplete flow session synchronization. Sessions that do not synchronize to the backup node are lost during a failover, resulting in service interruption for the affected flows.

Resolved In: junos:23.4R2-S7-J20 junos:23.4R2-S7-J9 junos:25.2R2-S1 junos:25.4R1-S3 junos:25.4R2 junos:26.2R1 junos:26.3R1
PR NumberSynopsisCategory: IPSEC/IKE VPN
1848225
Minor		The PFE process crashes when handling IPsec tunnel operations on SRX Series platforms
Product-Group=junos		On all SRX Series platforms, the srxpfe/flowd process crashes and generates core files due to memory allocation failure when IPsec is configured. Because of the process crash, TCP, UDP, and IPsec-related flow session along with BFD (if configured) goes down.

Resolved In: junos:25.1R1 junos:25.2R1
1937239
Major		Srxpfe process crash due to memory allocation errors triggered by IPsec processing
Product-Group=junos		On all SRX platforms with Internet Protocol Security (IPsec) Virtual Private Network (VPN) tunnel configuration, the srxpfe (SRX Packet Forwarding Engine) process leaks memory during internal IPsec operation failures, where allocated memory is not freed in the error handling path. Over time, this results in excessive growth of virtual memory usage, eventually leading to memory allocation failures and a crash of the srxpfe process. This condition causes a temporary IPsec VPN service disruption and impacts traffic.

Resolved In: junos:23.2R2-S8 junos:24.2R2-S6 junos:25.2R2-S1 junos:25.4R2 junos:26.2R1 junos:26.3R1
1968614
Minor		The flowd process restarts and IPsec tunnel installation fails on SRX Series platforms
Product-Group=junos		On all SRX platforms, when IPsec (Internet Protocol Security) VPN (Virtual Private Network) tunnels are being turned up, simultaneous flapping of IPsec VPN tunnels leaves stale tunnel information in the system, causing a memory leak in the flowd process, potentially preventing new tunnel installation and triggering an unexpected flowd process crash and restart. Because of the process crash, TCP, UDP, and IPsec-related flow session along with BFD (if configured) goes down. Memory leak may also result in failure of further tunnels from getting established.

Resolved In: junos:26.4R1
PR NumberSynopsisCategory: Platform infra to support jvision
1964847
Major		The sensord generates a crash file and triggers an MPC10 line card restart on MX platforms
Product-Group=junos		On MX platforms with MPC10 line cards, the sensord daemon generates a crash file due to a race condition associated with telemetry subscriptions to sensors such as cmerror, fabric, transceiver, and optics. The issue can occur with explicit telemetry sensor subscriptions or with subscriptions that are active by default and results in an MPC10 line card restart and service impact on the affected line card.

Resolved In: evo:23.2R2-S8-EVO evo:25.4R2-EVO evo:26.2R2-EVO evo:26.4R1-EVO junos:23.2R2-S3-J25 junos:23.4R2-S8-J14 junos:25.4R2 junos:26.2R2 junos:26.4R1
PR NumberSynopsisCategory: Issues related to Junos licensing infrastructure
1914981
Minor		After multiple reboots, "usage-used-licensed" value for subscriber services will not be shown as expected on all Junos platforms
Product-Group=junos		Verification of system license on Junos platform failed, where used-licensed value for Subscriber Services Advanced is not as expected.

Resolved In: junos:23.2R2-S6 junos:23.4R2-S5-J46 junos:23.4R2-S7 junos:24.2R2-S2-J19 junos:25.4R2 junos:26.1R1
PR NumberSynopsisCategory: SW PRs for MPC10E Interfaces
1881511
Minor		MX platforms with MPC10 and PPPoE subscribers can experience egress traffic black holing after WAN link flap events
Product-Group=junos		On MX Series routers equipped with MPC10 cards and high scale PPPoE (Point to Point Protocol over Ethernet) subscriber deployments, a WAN (Wide Area Networks) interface link flap under active traffic conditions can cause corruption of internal scheduler credits. When this occurs, Packet Forwarding Engine queue flush operations can fail and subscriber egress traffic can become permanently black holed. Symptoms include "cannot Free L1/L2/L3/L4 node" messages, and queue flush failures. The issue is more likely to occur on interfaces carrying significant subscriber traffic and repeated link flap events.

Resolved In: evo:26.4R1-EVO junos:23.4R2-S1-J12 junos:23.4R2-S3-J35 junos:23.4R2-S7-J27 junos:24.4R2-J22 junos:26.4R1
PR NumberSynopsisCategory: MPC11 ULC platform software related issues.
1809351
Major		JDI-RCT:M/Mx: ISIS session over MPC11 cards flapped due to "3-Way handshake failed" during ISSU (FRU upgrade stage - reboot phase)
Product-Group=junos		JDI-RCT:M/Mx: ISIS session over MPC11 cards flapped due to "3-Way handshake failed" during ISSU (FRU upgrade stage - reboot phase)

Resolved In:
PR NumberSynopsisCategory: Multicast for L3VPNs
1908581
Major		Significant multicast traffic loss observed during ISSU in Next-Generation Multicast VPN (NGMVPN) deployments
Product-Group=junos		On all Junos platforms that support both InService Software Upgrade (ISSU) and NextGeneration Multicast VPN (NGMVPN), multicast traffic loss can occur during an ISSU operation when NGMVPN deployments use both the Inclusive Provider Multicast Service Interface (IPMSI) and the Selective Provider Multicast Service Interface (SPMSI) with a nonzero threshold. During the ISSU process, Flexible PIC Concentrators (FPCs) upgrade and synchronize, and multicast statistics may briefly report zero. This event causes withdrawal of the SPMSI and a fallback to the IPMSI. If the IPMSI next hops are not fully programmed at that moment, a temporary interruption of SPMSI flows occurs, while IPMSI flows continue forwarding normally. The traffic loss duration is short and typically limited to a few seconds to a few minutes during FPC upgrade cycles, not exceeding the expected ISSU convergence window. Both IPv4 and IPv6 multicast traffic are affected.

Resolved In: evo:26.2R1-EVO junos:26.2R1
PR NumberSynopsisCategory: build tools
1972129
Minor		FTP passive mode fails on Junos platforms
Product-Group=junos		On all Junos platforms, FTP ( File transfer protocol ) sessions using PASV mode fail. As a result, customers relying on PASV for fetching operational scripts experienced transfer failures. Impact included blocked transfers.

Resolved In: junos:24.2R2-S6 junos:25.4R2 junos:26.2R2 junos:26.4R1
PR NumberSynopsisCategory: "ifstate" infrastructure
1882329
Minor		The management interface is unreachable post switchover/RPD restart events
Product-Group=junos		On all Junos platforms with management interface em0/fxp0 disabled, the management port remains unreachable after performing RE switchover or rpd restart events and re-enabling the management port.

Resolved In: junos:25.4R1
PR NumberSynopsisCategory: IPv6/ND/ICMPv6 issues
1903132
Minor		IPSec tunnels configured with Traffic Selector are not coming up post 2nd GRES on MX platforms
Product-Group=junos		On all MX platforms, when the IPSec tunnels configured with Traffic Selector (TS) a replication problem with unicast nexthop post-GRES (Graceful Routing Engine Switchover) in the new backup is observed. IKE daemon sends route additions before the unicast nexthop is ready in the backup. This results in nexthop lookup failures on the backup, causing route replication failure and that the IPSE tunnels not coming up.

Resolved In: junos:25.4R1 junos:26.1R1
PR NumberSynopsisCategory: TCP/UDP transport layer
1893210
Minor		Master RE crashed and triggered unexpected switchover due to memory corruption
Product-Group=junos		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.

Resolved In: junos:22.4R3-S10 junos:23.4R2-S8 junos:24.2R2-S5 junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: Path computation client daemon
1929225
Critical		The pccd process crashes when muliple LSP updates are received from PCE
Product-Group=junos		On all Junos and Junos Evolved platforms with PCEP (Path Computation Element Protocol) configured, the pccd process crash is seen when multiple LSP (Label Switched Path) updates are received in a single PCE (Path Computation Element) message. The LSP update sent by the PCE will not get programmed into the forwarding plane and LSP states will not be updated till the pccd process restarts.

Resolved In: evo:23.2R2-S8-EVO evo:23.4R2-S8-EVO evo:25.2R2-EVO evo:25.4R2-EVO evo:26.2R1-EVO junos:22.2R3-S8 junos:22.3R3-S5 junos:22.4R3-S10 junos:23.2R2-S8 junos:23.4R2-S8 junos:24.2R2-S5 junos:24.4R2-S4 junos:25.2R2 junos:25.2R2-S2 junos:25.4R1-S2 junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: Protocol Independant Multicast
PR NumberSynopsisCategory: PPPoE functional plugin for bbe-smgd
1937254
Minor		PPPoE clients are ignoring the service-name-table configuration and attempting to connect subscribers into default routing-instance.
Product-Group=junos		PPPoE clients are ignoring the service-name-table configuration and attempting to connect subscribers into default routing-instance.In this scenario customer has static VLAN configured on DEMUX0 and uses service-name-table to ensure PPPoE client is terminated within desired routing-instance. demux0 { unit 200 { vlan-id 200; demux-options { underlying-interface ae4; } family pppoe { dynamic-profile PPPoE_DUALSTACK; service-name-table PPPOE-TO-VRF200; } } } pppoe { service-name-tables PPPOE-TO-VRF200 { service any { routing-instance VRF200; } service empty { routing-instance VRF200; } } } }

Resolved In: evo:26.2R2-EVO evo:26.4R1-EVO evo:27.1R1-EVO junos:26.2R2 junos:26.4R1
1939233
Major		Repeated bbe-smgd crashes caused when the system issues a dynamic profile add request during PPPoE session creation, but receives a delete event before the add completes on MX and certain Junos OS Evolved ACX Series platforms
Product-Group=junos		On MX and certain Junos OS Evolved ACX Series platforms with Enhanced Subscriber Management enabled, a rare race condition can lead to repeated bbe-smgd process crashes and core file generation when an access-side port flap occurs during L2TP session establishment in environments running PPPoE and L2TP services. This issue requires a very specific sequence of events and is therefore considered unlikely to occur.

Resolved In: evo:25.2R2-S1-EVO evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:23.2R2-S8 junos:24.2R2-S5 junos:25.2R2-S1 junos:25.4R2 junos:26.2R1 junos:26.3R1
PR NumberSynopsisCategory: QFX access control list
1977357
Minor		Filter HW programming fails when forwarding-class is used with UDF flexible-match-mask
Product-Group=junos		On QFX5120, EX4650, EX4400, and EX4100 series switches, firewall filters configured with forwarding-class fail to be programmed into the PFE when flexible-match-mask is used.

Resolved In: junos:25.4R2 junos:26.2R2 junos:26.4R1
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		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.

Resolved In: junos:23.4R2-S8 junos:23.4R2-S9 junos:24.2R2-S5 junos:25.2R2-S1 junos:25.4R2 junos:25.4R2-S1 junos:26.2R1 junos:26.2R2 junos:26.3R1 junos:26.4DCB
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1960236
Minor		QFX5K fails to generate ICMPv6 Packet Too Big messages when the return path uses indirect next-hop routes
Product-Group=junos		On QFX5K platforms, ICMPv6 Packet Too Big (PTB) messages may not be transmitted when oversized IPv6 packets are forwarded through an interface with a lower MTU. This can prevent IPv6 Path MTU Discovery (PMTUD) from operating correctly. Normal IPv6 forwarding and other ICMPv6 messages are unaffected.

Resolved In: junos:25.4R2 junos:26.2R2 junos:26.4R1
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1948146
Minor		BFD distributed mode not coming up on IRB with CRB in EVPN-VXLAN
Product-Group=junos		On Junos OS platforms, when the device is operating as a spine, with EVPN-VXLAN (Ethernet VPN Virtual Extensible LAN) in CRB (centrally routed bridging), enabling BFD (Bidirectional Forwarding Detection) as distributed mode on IRB (Integrated Routing and Bridging) interfaces, causes the BFD destination process to not to set the output interface correctly, preventing the BFD session from coming up.

Resolved In: junos:21.4R3-S13 junos:23.4R2-S8 junos:25.4R2 junos:26.2R1 junos:26.2R2 junos:26.3R1
1969241
Major		Duplicate egress VLAN-translation entry additions in VXLAN configurations cause a forwarding-plane memory leak on QFX5K and EX4K switches
Product-Group=junos		On QFX5k and EX4k switches running Junos OS with VXLAN and egress VLAN translation, repeated VLAN-translation updates or configuration churn over an extended uptime can gradually exhaust forwarding-plane memory. When memory is exhausted, the FPC restarts while the Routing Engine remains operational, causing all interfaces on the FPC to flap and traffic to be lost during the restart.

Resolved In: junos:23.2R2-S8 junos:25.4R2 junos:25.4R2-S1 junos:26.2R2 junos:26.4R1
PR NumberSynopsisCategory: QFX5K JUNOS Interface, MACSec, Optics, SDK, PHY
1934076
Minor		The dcpfe process crash observed during a system reboot or PFE restart when software-based linkscan is configured
Product-Group=junos		On QFX5120-48Y, QFX5120-48T, QFX5120-32C and EX4650 platforms, a system reboot or PFE restart after configuring software-based linkscan causes the dcpfe process to crash. As a result, traffic forwarding on interfaces associated with the affected FPC will be temporarily impacted during the recovery period.

Resolved In: junos:25.2R2-S2 junos:25.4R2 junos:26.2R2 junos:26.3R1 junos:26.4R1
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platfom issues
1800862
Major		On all dual disk QFX5K platforms having QFX-5e image with secondary (sdb) disk failure, WRITE DMA errors are observed and the device goes unresponsive
Product-Group=junos		Due to a the disk failure reboot support was not added for dual disk scenario, hence system was not booting in case of disk failure on sdb (the other disk) on QFX platform.

Resolved In: junos:22.2R3-S5 junos:24.2R2-S3
1920896
Major		EPDM version upgrade on QFX5120-48YM
Product-Group=junosvae		On QFX5120-48YM platforms, proposal for upgrading EPDM version from 4.0.4 to latest 4.4.2

Resolved In: junos:23.4R2-S7 junos:25.4R2 junos:26.2R1 junos:26.2R2
1938921
Major		Software rollback may cause device to become unresponsive on Junos platforms with qfx-5e image
Product-Group=junosvae		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.

Resolved In: junos:21.4R3-S13 junos:23.2R2-S8 junos:24.2R2-S5 junos:25.2R2-S1 junos:25.4R2 junos:26.2R1 junos:26.3R1
1968477
Major		Make the default linkscan as Software and modify the CLI command to set the linkscan as Hardware
Product-Group=junosvae		Keeping SW linkscan as default, so modified the existing CLI command for setting SW linkscan to HW linkscan.

Resolved In:
PR NumberSynopsisCategory: RPD infrastructure issues related to NSR, GRES, switchover,
1951132
Major		rpd crash caused by stale deleted tunnel entry
Product-Group=junos		On all Junos and Junos Evolved platforms, deleting a tunnel leaves its entry on the systems processing list instead of removing it. When the system later references this stale entry, it results in a crash. This issue is specific to APP-based dynamic tunnels.

Resolved In: evo:24.2R2-S6-EVO evo:25.4R2-EVO evo:26.2R2-EVO evo:26.3R1-EVO junos:21.2R3-S8-J18 junos:23.2R2-S8 junos:24.2R2-S6 junos:25.2R2-S2 junos:25.4R2 junos:26.2R1 junos:26.2R2 junos:26.3R1
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1922237
Major		In Class-Based Forwarding with ECMP scenario traffic gets dropped due to incorrect next-hop handling process in PFE programming
Product-Group=junos		On all Junos and Junos Evolved platforms where CBF (Class-Based Forwarding) and ECMP (Equal-Cost Multi Path) is configured and in non - MPLS (Multi-Protocol Label Switching) based IP traffic forwarding scenario, packet loss can be observed due to next-hop process handling in PFE (Packet Forwarding Engine) programming for indexed next-hop installation by CBF.

Resolved In: evo:26.2R1-EVO evo:26.2R2-EVO evo:26.3R1-EVO evo:26.4R1-EVO junos:26.2R2 junos:26.4R1
PR NumberSynopsisCategory: Issues related route resolution routing infrastructure
1853895
Major		Service route is hidden over BGP LU multipath upon neighbor route withdrawn
Product-Group=junos		On all Junos and Junos Evolved platforms, the following condition is a prerequisite - Service route resolving over BGP LU (Border Gateway Protocol Labeled Unicast) multipath route with multipath resolve policy enabled. The issue occurs when one BGP LU neighbour withdraws its route. This withdrawal causes the top-level service route to temporarily become hidden, and then it reappears after re-resolving over the remaining BGP LU multipath routes. However, after this recovery, the BGP LU resolution changes from multipath to single path.This behavior results in a brief traffic loss during the interval when the service route is hidden and then restored.

Resolved In: evo:24.4R2-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:22.2R3-S6-J3 junos:22.4X4 junos:24.4R2 junos:25.2R1 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 evo:26.3R1-EVO evo:26.4R1-EVO evo:27.1R1-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: Resource Reservation Protocol
1967461
Major		RSVP detour LSP does not follow configured FRR admin-group exclusion constraints
Product-Group=junos		On Junos OS and Junos OS Evolved platforms, when MPLS (Multiprotocol Label Switching), RSVP (Resource Reservation Protocol), dynamic tunnels, and an LSP (Label-Switched Path) template with FRR (Fast Reroute) admin-group exclusion constraints are configured, the detour LSP does not follow the configured exclusions after the primary LSP becomes unavailable. The detour LSP uses an unintended path, while traffic and services remain unaffected.

Resolved In: evo:25.4R2-EVO evo:26.2R2-EVO evo:26.3R1-EVO evo:26.4R1-EVO junos:25.4R2 junos:26.2R2 junos:26.3R1 junos:26.4R1
PR NumberSynopsisCategory: RPM and TWAMP
1965854
Minor		Incorrect ISIS delay metrics calculated when TWAMP is used
Product-Group=junos		On Junos OS and Junos OS Evolved platforms with ISIS (Intermediate System to Intermediate System) delay measurement using TWAMP (Two-Way Active Measurement Protocol), incorrect delay metrics being advertised. When this issue occurs, the affected ISIS delay metrics do not update correctly, which can result in stale routing information and suboptimal path selection.

Resolved In: evo:26.2R2-EVO evo:26.4R1-EVO evo:27.1R1-EVO junos:26.2R2 junos:26.4R1
PR NumberSynopsisCategory: PTX10K Line Card specific interface PRs
1954724
Major		Ingress packet drops not reflected in SNMP ifInDiscards
Product-Group=junos		On Junos OS and Junos OS Evolved platforms, the interface ingress packet drops caused by congestion are not reflected in the Simple Network Management Protocol Management Information Base version II (SNMP MIB-II) ifInDiscards counter. While show interfaces extensive correctly reports input drops, ifInDiscards remains at zero.

Resolved In: evo:25.4R2-EVO evo:26.2R2-EVO evo:26.3R1-EVO junos:25.4R1-S2-J10 junos:25.4R2 junos:26.2R2 junos:26.3R1
PR NumberSynopsisCategory: Issues related to control plane security
1865633
Major		Junos OS: A low-privileged user can escalate their privileges so that they can log in as root (CVE-2026-21916)
Product-Group=junos		A UNIX Symbolic Link (Symlink) Following vulnerability in the CLI of Juniper Networks Junos OS allows a local, authenticated attacker with low privileges to escalate their privileges to root, which will lead to a complete compromise of the system. Please refer to https://supportportal.juniper.net/JSA107807 [juniper.net] for more information.

Resolved In: evo:25.2R2-EVO junos:20.2R3-S12 junos:20.2X42 junos:20.3X75-D443 junos:21.2R3-S11 junos:21.2X33 junos:21.4R3-S10-J4 junos:21.4R3-S10-J4-X1 junos:21.4R3-S10-J6 junos:21.4R3-S12 junos:21.4R3-S13 junos:21.4X15 junos:22.4R3-S10 junos:22.4R3-S7-J1 junos:22.4R3-S9 junos:23.2R2-S6 junos:23.4R2-S6 junos:23.4R2-S7 junos:23.4X12 junos:23.4X13 junos:23.4X15 junos:23.4X30 junos:23.4X30-D30 junos:24.2R2-S3 junos:24.2R2-S4 junos:24.2X1 junos:24.2X4 junos:24.2X50 junos:24.4R2-S1 junos:24.4R2-S1-C1 junos:24.4R2-S2 junos:25.2R1-S1 junos:25.2R1-S2 junos:25.2R2
PR NumberSynopsisCategory: SNMP Infrastructure (snmpd, mib2d)
1957635
Major		SNMP trap is sent with incorrect source IP address
Product-Group=junos		SNMP traps are sent with fxp0 or uplink port IP even though trap source is configured with lo0.0 IP. The issue occurs after deactivate+activate of the trap-source/trap-target addresses.

Resolved In: evo:25.4R2-EVO evo:26.2R2-EVO evo:26.4R1-EVO evo:27.1R1-EVO junos:25.2R2-S1-J10 junos:25.4R2 junos:26.2R2 junos:26.4R1
PR NumberSynopsisCategory: SRX branch platforms
1934517
Major		SRX380 XE interface flap on every configuration commit with 1G SFP transceivers
Product-Group=junos		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.

Resolved In: junos:23.2R2-S8 junos:23.4R2-S8 junos:24.2R2-S5 junos:24.2R2-S6 junos:25.2R2-S1 junos:25.4R2 junos:26.2R1 junos:26.3R1
PR NumberSynopsisCategory: MX10002 Platform SW - Platform s/w defects
1972055
Major		MX Series node-slicing report a persistent craft-control chassis alarm after boot
Product-Group=junos		On node-slicing capable MX Series platforms running Junos OS 24.4R2, a guest network function (GNF) can report a minor craft-control chassis alarm after the device boots, the alarm does not affect system operation or traffic forwarding

Resolved In: junos:26.2R2
PR NumberSynopsisCategory: ZT/YT pfe firewall software
1931740
Major		Traffic drop is observed on specific MX platforms with EVPN-VXLAN during deletion and addition of IRB interface
Product-Group=junos		Traffic loss is seen on MX platforms with MPC10, MPC11, LC9600 or MX304 configured with EVPN-VXLAN (Ethernet Virtual Private Network - Virtual Extensible Local Area Network) when IRB (Integrated Routing and Bridging) interface ( which has filters ) is deleted/added.

Resolved In: evo:25.4R2-EVO evo:26.3R1-EVO junos:23.4R2-S3-J31 junos:25.4R2 junos:26.3R1
1960242
Major		Packet drops and PPE traps are observed after LC9600/LC4800/LC4802/LMIC offline/online with AE interface-specific filters
Product-Group=junos		On platforms with LC9600/LC4800/LC4802/LMIC line cards, performing LC9600/LC4800/LC4802/LMIC offline/online operation while AE (Aggregated Ethernet) interface-specific filters are configured, results in incorrect filter next-hop programming. As a result, packet drops and PPE (Packet Processing Engine) traps are observed, leading to traffic disruption.

Resolved In: evo:25.4R2-EVO evo:26.3R1-EVO evo:26.4R1-EVO junos:25.4R2 junos:26.3R1 junos:26.4R1
1975229
Major		FPC crash is seen when one AE member interface flap and filter delete occur concurrently
Product-Group=junos		On all Junos MX platforms, FPC (Flexible PIC Concentrator) crash is seen when filter is on AE (Aggregated Ethernet) interfaces, one AE member link flap and filter delete occurs concurrently. With filter on AE interfaces, when one AE member link flapped, it causes filter reprogramming, then FPC crash is seen and crash files are generated. Service impact will occur on the affected FPCs.

Resolved In: evo:25.4R2-EVO evo:26.2R2-EVO evo:26.4R1-EVO evo:27.1R1-EVO junos:24.4R2-J21 junos:25.4R2 junos:26.2R2 junos:26.4R1
PR NumberSynopsisCategory: ZT/YT pfe l3 forwarding issues
1958594
Minor		Micro BFD session flap is observed when there is aggressive interval timer with high host generated traffic
Product-Group=junos		On MX304, MX301, MPC10, MPC11, JNP10K-LC9600 platforms and line cards when micro BFD (Bidirectional Forwarding Detection) is configured on AE (Aggregated Ethernet) interface with aggressive interval (approx 15ms (millisecond) X 3) and there is presence of high-rate host generated traffic (approx 7K PPS (Packets Per Second)) it is observed that the micro BFD session flaps. As a result the AE interface flaps and causes traffic drop.

Resolved In: evo:25.4R2-EVO evo:26.2R2-EVO evo:26.3R1-EVO evo:26.4R1-EVO junos:25.4R2 junos:26.2R2 junos:26.3R1 junos:26.4R1
PR NumberSynopsisCategory: Trio pfe qos software
1958296
Major		FPC major alarm triggered by AE member link flaps resulting in PFE being disabled
Product-Group=junos		On MX platforms with MPC7E/MPC8E/MPC9E/MPC10E/MPC11E/LC9600 line cards or an MX304 platform, The PFE (Packet Forwarding Engine) is disabled following a Major alarm on the FPC (Flexible PIC Concentrator), when the error message "XQSS_CMERROR_DSTAT_INT_REG_DROP0_VOTE_OVRN" is triggered after a member link of an AE (Aggregated Ethernet) interface flaps, resulting in traffic impact on the affected PFE.

Resolved In: evo:25.4R2-EVO evo:26.2R2-EVO evo:26.3R1-EVO junos:21.2X34 junos:23.2R2-S8 junos:24.2R2-S6 junos:24.4R2-S4-J27 junos:24.4R2-S4-J6 junos:25.2R2-J3 junos:25.2R2-S2 junos:25.4R1-S2-J10 junos:25.4R2 junos:26.2R1 junos:26.2R2 junos:26.3R1
PR NumberSynopsisCategory: Trio pfe bridging, learning, stp, oam, irb software
1950853
Major		Multicast traffic disruption on VLAN after CoS configuration changes
Product-Group=junos		On MX platforms , multicast traffic over VLAN interfaces (IRB) will be impacted after certain CoS (Class Of Service) configuration changes. This can result in multicast traffic not reaching downstream receivers.

Resolved In: evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:22.2R3-S8 junos:22.3R3-S5 junos:22.4R3-S10 junos:23.2R2-S8 junos:23.4R2-S7-J17 junos:24.2R2-S6 junos:25.2R2-S2 junos:25.4R2 junos:25.4R2-S1 junos:26.2R1 junos:26.3R1
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1960382
Minor		After Junos upgraded to 24.2R2-S1, RSI command is not working when user permissions of view, view-configuration are set on tacacs server
Product-Group=junos		After Junos upgraded to 24.2R2-S1, when a cli user with permissions from remote auth server like tacacs/radius attempts to run RSI, error may be seen.

Resolved In: evo:25.4R2-EVO evo:26.2R2-EVO evo:26.3R1-EVO junos:24.4R2-S4-C1 junos:25.4R2 junos:26.2R2 junos:26.3R1
PR NumberSynopsisCategory: Issues related to NETCONF
1858635
Critical		ACX Series vmcore crash when netconf notifications are enabled
Product-Group=junos		On ACX7024, ACX710032C, and ACX7348 platforms running Junos OS Evolved, enabling netconf notifications with the command "set system services netconf notification" may cause a memory leak. This results in a control plane crash (vmcore). Forwarding plane remains unaffected.

Resolved In: evo:23.4R2-S8-EVO evo:24.2R2-S4-EVO evo:24.2X2-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO evo:25.4R2-EVO evo:26.1R1-EVO evo:26.2R1-EVO evo:26.3R1-EVO evo:26.4R1-EVO junos:23.4R2-S8 junos:24.2R2-S4 junos:24.4R2 junos:25.2R1 junos:25.3R1 junos:25.4R2
PR NumberSynopsisCategory: web filterig issues
1953486
Major		Traffic drops observed when using url-category without web filtering profile on Junos SRX Platforms
Product-Group=junos		On Junos SRX platforms, when only url-category is configured in policy (without web-filter policy), the packet handler continues to receive packets while the session is in HELD state, causing subsequent packets to be dropped.

Resolved In: junos:25.4R2 junos:26.2R1 junos:26.2R2 junos:26.3R1
PR NumberSynopsisCategory: MX10K linecard
1954671
Major		PTP remains in initializing state and fails to establish synchronization on MX10004/MX10008
Product-Group=junos		On MX10004 and MX10008 platforms, a rare timingd internal event-processing issue prevent PTP (Precision Time Protocol) synchronization from initializing successfully. When this condition occurs, PTP remains in the initializing state, PTP packet processing does not occur, and PTP Rx/Tx statistics remain at zero despite valid configuration and operational SyncE/ESMC (Ethernet Synchronization Messaging Channel) synchronization. The timingd process continues running, but internal timing events are no longer processed correctly, resulting in loss of PTP functionality until service recovery actions are performed. This issue does not impact normal data forwarding traffic and is limited to PTP operation.

Resolved In: evo:25.4R2-EVO evo:25.4R2-S1-EVO evo:25.4X300-EVO evo:26.2R2-EVO evo:26.3R1-EVO junos:25.2R2-S2 junos:25.2X31 junos:25.4R1-S3 junos:25.4R2 junos:25.4R2-S1 junos:26.2R2 junos:26.3R1
PR NumberSynopsisCategory: VMHOST platforms software
1827549
Minor		Large number of memory errors which slows down the system
Product-Group=junos		On all Junos that runs on VMHOST based Routing Engine, when the primary Routing Engine faces a continuous stream of correctable ECC errors, although these errors are individually handled by the hardware, their high frequency over time causes the control plane (Junos VM) on the Routing Engine to slow down and become partially unresponsive. Because of this degraded state, the backup Routing Engine can not take over control in time, delaying the GRES switchover. As a result, the system loses synchronization, all line cards reboot, and traffic disruption occurs.

Resolved In: evo:25.3R1-EVO junos:25.3R1
PR NumberSynopsisCategory: VSRX platform software
1922165
Major		ED25519 ssh key now supported from AWS and GCP upon vSRX 3.0 instance creation
Product-Group=junos		Starting in 25.4R2, customers can use ed25519 ssh keys from either the web console or CLI of AWS and GCP as well as rsa ssh keys when selecting an SSH key to be able to log into the system with at launch. Configuring the keys through cloud-init config was already supported.

Resolved In: junos:25.4R2 junos:26.1R1 junos:26.2R1
1945668
Major		Upgrading vSRX to Junos 24.4R2-S3 and above causes AE bundling issues and traffic loss
Product-Group=junos		Upon booting up a Junos vSRX platform following an upgrade to Junos 24.4R2-S3 and above, one or more interfaces may not be seen within the interfaces list from running a "show interfaces terse". Due to this, it causes AE / Reth bundling issue and interfaces don't come up leading to traffic loss.

Resolved In: junos:24.2R2-S6 junos:25.2R2-S2 junos:25.4R2 junos:26.2R1 junos:26.3R1
1953712
Major		vSRX3.0 connectivity loss and service disruption due to traffic interruption during processing delays
Product-Group=junos		On Junos OS vSRX3.0 platforms, two issues have been addressed. The first issue is related to flow control configured; connectivity loss and service disruption will be observed when the device experiences processing delays that can interrupt incoming network traffic. The issue affects critical control protocols such as BFD and BGP. The second issue is a CPU (Central Processing Unit) utilization display issue, where the show chassis routing-engine command reports CPU utilization for CPU0 only instead of showing the average utilization across all Routing Engine CPUs; this is a display-only issue.

Resolved In: evo:25.4R2-EVO junos:24.2R2-S6 junos:24.4R2-S3-J21 junos:25.2R2-S2 junos:25.4R2 junos:26.2R2 junos:26.3R1
PR NumberSynopsisCategory: usf ipsec related issues
1920710
Major		The ikemd daemon crashes after repeated interface flapping with multiple IKE gateways configured
Product-Group=junos		On MXXX/SRXX/NFXX platforms, the ikemd daemon will crash after repeated interface flapping when multiple IKE (Internet Key Exchange) gateways are configured. This issue does not impact existing or new tunnel formation. This is a very rare corner case.

Resolved In: evo:25.4R2-EVO evo:26.1R1-EVO junos:25.4R1 junos:25.4R2 junos:26.1R1

 

Modification History

First publication 2026-10-14