Article Detail

Alert Type

SRN - Software Release Notification

RiskRisk Description

Low/Notification

Software Release Notification

ImpactImpact Description

Low/Notification

Software Release Notification

Product Affected

ACX EX MX NFX PTX QFX SRX - Excluded QFX5110 QFX5120 EX4100 EX4400

Alert Description

Junos Software Service Release version 23.4R2-S7 is now available for download from the Junos software download site

Download Junos Software Service Release:

Go to Junos Platforms - Download Software page
Input your product in the "Find a Product" search box
From the Type/OS drop-down menu, select Junos SR
From the Version drop-down menu, select your version
Click the Software tab
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. Please note that this SRN does not include QFX5110 QFX5120, EX4100, and EX4400 series

Solution

Junos Software service Release version 23.4R2-S7 is now available.

23.4R2-S7 - List of Fixed issues

PR Number	Synopsis	Category: EX2300/3400 PFE
1899441 Major	Traffic loss is observed on the CVLAN interfaces during the transition between SP and EP configuration style Product-Group=junos Severity=Major	On Junos OS EX2300, EX3400, EX4100, EX4400, EX4650, EX4000 and QFX5K platforms with software-based MAC (Media Access Control) address learning enabled through interface-level MAC-limit or MAC-move-limit, the traffic fails to traverse CVLAN interfaces when changing the configuration mode from Service Provider (SP) style to Enterprise (EP) style and vice versa.
PR Number	Synopsis	Category: "agentd" software daemon
1805445 Major	Return Error for unsupported options with GNMI RPCs Product-Group=junos Severity=Major	On Junos and Junos OS Evolved platforms, the error message returned with unsupported encoding is changed for gnmi RPCs. It has no traffic impact.
PR Number	Synopsis	Category: SRX2000/50000 issue
1904267 Major	In SRX high availability cluster, RG0 failover to secondary node fails as srxpfe daemons failed to reconnect to routing-engine on secondary Product-Group=junos Severity=Major	On all Junos OS SRX except branch SRX platforms, in high availability scenario, during redundancy group (RG0) failover, all the FPC PICs need to reconnect to the new primary routing-engine on secondary node within 16 seconds timer. However, this is not happening which is causing a connection reset and impacting traffic.
PR Number	Synopsis	Category: chassisd related issues for high-end SRX platforms
1887000 Minor	SRX4600 node 1 enters hardware failure during upgrade Product-Group=junos Severity=Minor	On SRX4600 platforms running Junos OS and configured in High Availability (HA), a hardware alarm is triggered during Low Impact Cluster Upgrade (LICU) procedures due to incorrect alarm logic tied to control link status. This condition affects Node 1 and causes Redundancy Group 1 (RG1) to failover to Node 0, even if Node 0 interfaces are not yet active, resulting in a traffic outage.
PR Number	Synopsis	Category: BBE database related issues
1818781 Major	Multiple BBE daemons getting killed automatically on MX platforms Product-Group=junos Severity=Major	In a scaled subscriber management router, customers observe authd and Jdhcpd daemons being killed automatically due to block tasks.
PR Number	Synopsis	Category: BBE interface related issues
1848887 Major	Routing-services enabled on PPPoE dynamic profile causes subscriber login failure for new subscribers Product-Group=junos Severity=Major	On MX platforms, with routing-services enabled on PPPoE (Point-to-Point over Ethernet) Dynamic Profile, subscriber login fails for new subscribers with specific stacking model.
PR Number	Synopsis	Category: Border Gateway Protocol
1898734 Major	The rpd process crashes in an Inter-AS Option-AB L3VPN with BGP multipath list-nexthop enabled Product-Group=junos Severity=Major	On all Junos and Junos OS Evolved platforms, in an Inter-AS (Autonomous System) Option-AB L3VPN (Layer3 Virtual Private Network) scenario, if 'bgp multipath list-nexthop' is configured and a VRF (Virtual Routing and Forwarding) generates a route with list-nexthop that is advertised to an Option-AB peer, the rpd process crashes and generates a core-dump.
1914814 Major	BGP task replication will be stuck in 'InProgress' state following an RE switchover when two single hop EBGP sessions are configured on two different interfaces using the IP addresses from the same subnet Product-Group=junos Severity=Major	On all Junos OS and Junos OS Evolved platforms with NSR (Nonstop Active Routing), when two single hop EBGP (External Border Gateway Protocol) sessions are configured to run on two different interfaces using IP addresses from the same subnet (overlapping subnet), the BGP task replication process does not complete after an RE (Routing Engine) switchover for the EBGP session with a specified local-address. This results in one BGP peer being in the 'Idle' state on the Backup RE while remaining in the 'Established' state on the new Master RE, causing the BGP task replication process to remain stuck in the 'InProgress' state.
PR Number	Synopsis	Category: MX304 Chassis specific platform
1841098 Minor	The kernel trace messages will be seen on the logs in Junos OS Evolved based platforms and Linecards Product-Group=junos Severity=Minor	On MX platforms with MPC11, LC4800, LC9600 , MX304 and all Junos OS Evolved platforms, kernel trace will be seen in the log messages in a rare scenario due to a floating point unit register corruption. There is no known functional impact due to these traces.
1905954 Critical	memory leak caused by using the "show ccl statistic summary ... " command Product-Group=junos Severity=Critical	On Junos OS and Junos OS Evolved platforms, running the command "show ccl statistic summary ... " cause memory leaks in the Packet Forwarding Engine (PFE).
PR Number	Synopsis	Category: QFX Access Control related
1923266 Major	Upgrade from release 23.4R2-S4 with persistent-cache enabled on VC can cause dot1xd to crash continuously Product-Group=junos Severity=Major	On all Junos devices with dual RE configured with dot1x, if the device is upgraded from release 23.4R2-S4 or there is a RE switchover and persistent-cache feature enabled it will cause dot1xd to crash. It is due to presence of some stale files on backup node.
PR Number	Synopsis	Category: Device Configuration Daemon
1916208 Major	Traffic drops due to VLAN configuration not updated for Ethernet-Switching Interfaces Product-Group=junos Severity=Major	On Junos OS platforms in which VLAN information can be given as a VLAN member name, if both VLAN (Virtual Local Area Network) IDs and VLAN member names are configured together on an interface within a routing instance, the VLAN membership does not update correctly on that interface, resulting in traffic impact associated with that VLAN.
PR Number	Synopsis	Category: Firewall Filter
1859894 Major	MIB2D stucked at 100% on MX10003 Product-Group=junos Severity=Major	On all MX platforms, during interface flaps with interface-specific / list filters we may see an error "get_counter_list_async: failed in reading counter names (No such file or directory)" due to internal clean-up missing. Please, note that this error is also seen during the churn. This could result in MIB2D hitting at 100% CPU if error remains consistent. The best way to escape this 100% CPU is to restart MIB2d process as soon as the said error is noticed and keep repeating with same counter name.
1903874 Minor	[MX10008] cmd='ls -i /var/etc/filters/filter-define.conf' is logged every 1 second instead of every 30 seconds Product-Group=junos Severity=Minor	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 Number	Synopsis	Category: Alias for DHCP issue on DNX based 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 Severity=Major	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.
PR Number	Synopsis	Category: ACX platform interface issues
1914526 Minor	ACX710 copper SFP-T interface with forced 100 Mbps flaps on commit Product-Group=junos Severity=Minor	On Junos OS ACX710 platform, when a tri-rate Small Form-Factor Pluggable Twisted-Pair (SFP-T) copper interface (1 Gb capable) is explicitly configured to run at 100 Mbps speed, performing a commit causes that particular interface to flap (go down and then come back up). This results in a temporary service disruption on just that port during the commit.
PR Number	Synopsis	Category: Control Plane for Node Virtualization
1908719 Major	On all mx platforms chassid gets stuck and becomes unresponsive it resumes only after restarting both control units Product-Group=junos Severity=Major	On MX devices, the sub-linecard feature with MPC11 cards. When this feature is used, the main system process can sometimes freeze, which may lead to system crashes and error logs.
PR Number	Synopsis	Category: EVO Netstack FIB Service Daemon
1785913 Critical	Junos OS Evolved: TCP session state is not always cleared on the Routing Engine leading to DoS (CVE-2024-47502) Product-Group=junos Severity=Critical	An Allocation of Resources Without Limits or Throttling vulnerability in the kernel of Juniper Networks Junos OS Evolved allows an unauthenticated, network based attacker to cause a Denial of Service (DoS). Please refer to https://supportportal.juniper.net/JSA88132 [juniper.net] for more information.
PR Number	Synopsis	Category: EVO L2 Control Plane PRs
1899530 Major	MAC learning failure when moving the AE interface from one VLAN to another VLAN in a single commit Product-Group=junos Severity=Major	On Junos OS Evolved platforms, when an Aggregated Ethernet (AE) logical interface (IFL) is moved from one Virtual LAN (VLAN) to another VLAN in a single commit, Layer 2 forwarding tables fail to update correctly. This causes Media Access Control (MAC) learning failure and traffic disruption.
PR Number	Synopsis	Category: Lacp related problems and issues.
1898531 Major	AE interfaces flap during GRES following an RE reboot on all Junos Evolved platforms Product-Group=junos Severity=Major	On all Junos Evolved platforms, Aggregate Ethernet (AE) interfaces with LACP configured will experience a flap due to a timing issue when Graceful Routing Engine Switchover (GRES) is performed after a Routing Engine (RE) reboot, resulting in traffic loss during the flap.
PR Number	Synopsis	Category: EVO linux defects & enhancement requests
1892248 Minor	Junos OS Evolved: A Linux kernel vulnerability in the HID driver allows an attacker to read information from the HID Report buffer (CVE-2024-50302) Product-Group=junos Severity=Minor	A Use of Uninitialized Resource in the Linux kernel driver for Human Interface Devices (HID) in Junos OS Evolved allows a local low-privileged attacker to use a malicious input device to read information from the report buffer. This could be used to leak kernel memory, enabling the exploitation of additional vulnerabilities. Please refer to https://supportportal.juniper.net/JSA106000 [juniper.net] for more information.
PR Number	Synopsis	Category: 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.
1884781 Major	Slow configuration commit observed on devices with a single Routing Engine (RE) Product-Group=junos Severity=Major	On all Junos OS Evolved platforms with single RE and the system type is cluster, a commit delay is observed when operating with a single RE. This occurs because the system attempts to synchronize with the second RE by default, but since it's not present, the process waits and causes the delay in commit.
PR Number	Synopsis	Category: EX4000 PFE issues
1847159 Major	Reachability issues are seen on interfaces that are aggregated without address-family Product-Group=junos Severity=Major	On Junos platforms, specifically on EX and QFX series aggregated interfaces configured without address-family results in reachability issues.
PR Number	Synopsis	Category: EX4100 PFE
1905783 Major	FXPC core dumps and crashes on EX switches during RA packet processing when SLAAC snooping is enabled Product-Group=junos Severity=Major	On EX switches, when SLAAC Snooping is enabled in certain IPv6 Router Advertisement (RA) packet, both PFE (Packet Forwarding Engine) and Routing Engine (RE) are used to free the same packet leading to double free scenario. This double packet free eventually might lead to FXPC cores and switch crashes caused by an invalid access or while freeing the packet. This impacts overall switch stability.
PR Number	Synopsis	Category: EX interfaces issues
1827595 Minor	Broadcom phy/EPDM SDK upgrade to version 2.3 Product-Group=junos Severity=Minor	Broadcom PHY EPDM SDK has been upgraded to version 2.3 to address the port not coming up issue.
1833177 Major	Incorrect Green LED Indication on 4x10G SFP/SFP+ Uplink Module When Link Is Down Product-Group=junos Severity=Major	On EX2300 and EX3400 platforms, When running the 'show chassis led' command, the uplink port LED on the 4x10G SFP/SFP+ module consistently shows green even when the link is down. This behavior is cosmetic only and does not impact service.
PR Number	Synopsis	Category: EX4400 PFE software
1870016 Minor	Traffic will be dropped due to IPv4 header checksum mismatch on EX4400 platform Product-Group=junos Severity=Minor	On EX4400 platform, if the switch is acting as a routing transit device, and if the value of the IPv4 header checksum is 0xFFFF in the ingress traffic, the checksum of the IPv4 header will not be recalculated even though the TTL (time to live) value has been reduced. This will lead to traffic being dropped by the next transit-device due to the bad checksum.
PR Number	Synopsis	Category: EX optics issues
1858986 Major	EX4400: Error message 'Failed to read eeprom' intermittently on SFP-T Product-Group=junos Severity=Major	On EX4400, error message 'Failed to read eeprom' is seen intermittently on SFP-T.
PR Number	Synopsis	Category: EX POE
1906507 Minor	False "Device Manager Failure" Alarms Observed on PoE Subsystem Product-Group=junos Severity=Minor	On EX2300/EX3400 platforms, The system reports false Power over Ethernet (PoE) "Device Manager failure" alarms, typically triggered by older PoE controller chips. These are not port-level or hardware issues, and connected PoE devices operate normally with correct power levels. The PoE subsystem auto-recovers, and the alarms are safe to ignore.
PR Number	Synopsis	Category: 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 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 packets to the host, to get dropped over the ECMP routes.
PR Number	Synopsis	Category: Dynamic flow capture
1880090 Major	On-Box IPv6 packet capture support Product-Group=junos Severity=Major	On all Junos and Junos OS Evolved platforms, IPv6 support was added for on-box packet capture. This is an enhancement request and has no service impact.
PR Number	Synopsis	Category: SRX1500 platform software
1910445 Major	Link status of disabled SFP-T port becomes up after rebooting on SRX1500 Product-Group=junos Severity=Major	When an SFP-T port is disabled, it shows admin down but can be in a physical up state after a reboot.
PR Number	Synopsis	Category: ACX7332 & ACX7348 Platform Software
1809091 Minor	ACX7024 sees a vmcore and restarts or potentially hangs on reboot Product-Group=junos Severity=Minor	ACX7024 sees a vmcore and restarts or potentially hangs on reboot
PR Number	Synopsis	Category: jdhcpd daemon
1911001 Major	On Junos devices supporting subscriber services acting as DHCPv6 relay randomly deletes IA_NA or IA_PD binding/route Product-Group=junos Severity=Major	On all Junos devices supporting subscriber services, in case of dual stack DHCP (Dynamic Host Configuration Protocol) subscribers with IA_NA (Identity Association for Non-temporary Address) and IA_PD (Identity Association for Prefix Delegation) bindings with lease times (For the assignment of IPv6 address to a client device), when a client initiates separate renew exchanges for the IA_NA and IA_PD, and once client and DHCP server are in sync with these timers, there can be a race condition at Junos device which is DHCPv6 relay, has not refreshed lease timer and can go out of sync. This can result in deleting IA_NA/IA_PD binding and route to get deleted for that subscriber only. This causes one of the leg for IA_PD or IA_NA to go down for that subscriber, which can result in traffic impact for that leg.
PR Number	Synopsis	Category: Flow Module
1785993 Major	The flowd process crash is observed in cluster HA mode when there is a route change Product-Group=junos Severity=Major	On all SRX and vSRX platforms with cluster high availability configured and route change egress interface then flowd process crashed observed.
1903515 Major	On the SRX platform the FPC reboots when traffic reaches the FAT IPSec tunnel Product-Group=junos Severity=Major	All Junos SRX platforms that support PMI (Power Mode IPsec) experiences FPC reboot due to traffic hitting the FAT (flow aware transport) IPSec tunnel configuration.
PR Number	Synopsis	Category: flow ha module
1895134 Minor	ISSU failure and process crash on primary node during HA upgrade Product-Group=junos Severity=Minor	On all Junos SRX platforms, performing ISSU (In-Service Software Upgrade) with the no-validate option in HA ( (High availability ) setups can cause ISSU failure and a process crash on the primary node.
PR Number	Synopsis	Category: SRX Firewall Authentication
1829894 Minor	Captive portal authentication fails when firewall-authentication is used in conjunction with identity management services (JIMS) Product-Group=junos Severity=Minor	On all SRX platforms, when a user tries to authenticate to a captive portal to get access to resources, the authentication is successful, but the user is rerouted back to the captive portal with no resources access.
PR Number	Synopsis	Category: High Availability/NSRP/VRRP
PR Number	Synopsis	Category: Firewall Policy
1882193 Critical	On SRX platform flowd process is generating crash files. Product-Group=junos Severity=Critical	On Junos OS SRX platforms, a crash in the flowd process occurs when the system attempts to retrieve interface information. During this process, an invalid memory address is accessed while copying the interface memory address from the database. This issue typically arises when accessing interface details to check session status on the backup device.
PR Number	Synopsis	Category: IPSEC/IKE VPN
1901732 Major	VPN traffic stops flowing intermittently on the st0 interface on SRX platforms Product-Group=junos Severity=Major	On Junos SRX platforms, Virtual Private Network (VPN) traffic stops even though the IPsec tunnel remains UP. This issue occurs when Class of Service (CoS) is configured on the secure tunnel (st0) interface. IPsec packet processing fails, and memory buffer (mbuff) resources are not freed, leading to resource exhaustion. As a result, encrypted traffic cannot be transmitted through the tunnel. The problem does not impact tunnel status or Internet Key Exchange (IKE) negotiation, but impacts the interface traffic.
PR Number	Synopsis	Category: Security platform jweb support
1725808 Critical	Junos OS: J-Web: Multiple vulnerabilities resolved in PHP software (CVE-2023-0567, CVE-2023-0662, CVE-2023-3823, CVE-2023-3824, CVE-2023-0568) Product-Group=junos Severity=Critical	PHP software included with Juniper Networks Junos OS J-Web has been updated to resolve multiple vulnerabilities. Please refer to https://supportportal.juniper.net/JSA88120 [juniper.net] for more information.
1916722 Minor	Software upgrade via J-Web does not work on specific SRX platforms while using Upload Package option Product-Group=junos Severity=Minor	The Upload Package option does not work on all non-vmhost SRX platforms ( all SRX platforms except SRX5K with SRX5K-RE3, SRX1600, SRX2300, SRX4120, SRX4300) or vSRX when J-Web is used to upgrade the software release.
PR Number	Synopsis	Category: Layer2 forwarding on EX/NFX/PTX/QFX
1905196 Minor	Stale entry in MAC-IP table affects ARP resolution Product-Group=junos Severity=Minor	On all Junos OS platforms, when an IP address already exists in the MAC-IP table as a remote entry and then an IRB (Integrated Routing and Bridging) interface is configured with the same IP address but a different MAC address, then the L2ALD (Layer 2 Address Learning Daemon) does not handle the update correctly, leading to incorrect ARP (Address Resolution Protocol) resolution.
PR Number	Synopsis	Category: Port-based link layer security services and protocols that a
1911538 Major	Show command execution failure for show system macsec license on MX platforms Product-Group=junos Severity=Major	On all Junos MX10004, MX10008, MX304, MX301 platforms on executing the command "show system maces license" fails and doesn't fetch any information however it doesn't cause any service disruption. This is a Day-1 issue.
PR Number	Synopsis	Category: JNP10K-RE3 CB Centralized MX timing
1849943 Minor	"show snmp mib get <>" output is not proper for certain mibs Product-Group=junos Severity=Minor	On MX10008 platforms, "show snmp mib get <>" output is not proper for certain mibs.
PR Number	Synopsis	Category: 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 Number	Synopsis	Category: Category for tracking Olympus-MX issues
1906557 Major	While collecting RSI, takes long time to produce output on MX platform Product-Group=junos Severity=Major	On MX platforms, the cli output for 'show services nat source summary' can take a long time to execute on a highly scaled environment. The issue aggravates when collecting RSI (request support information) and it takes more than an hour for the process to complete. In few instances, this also led to other processes like SNMP monitoring getting stuck.
1910534 Major	SPC3 crashes when three-color policer is attached to firewall filter Product-Group=junos Severity=Major	On MX platforms with SPC3, when three-color policer is configured and attached to firewall filter SPC3 crashes and flowd crash files are seen. This will cause service impact since SPC3 keeps crashing and may not come up if the configuration leading to crash is not deleted.
PR Number	Synopsis	Category: Optical Performance Monitoring
1896486 Major	The transportd daemon which runs on Routing Engine cards generates core dump repeatedly after installing line cards or PICs are swapped for a different type Product-Group=junos Severity=Major	On MX systems with long-haul optics installed which are supported by the Performance Monitoring feature, if the line card or PIC is removed and replaced with a line card or PIC of a different type, this leads to the transportd daemon crashes repeatedly and ultimately failing to launch.
PR Number	Synopsis	Category: JUNOS Network App Infrastructure (for ping, traceroute, etc)
1876690 Major	ntp process may restart when issue the "show system ntp threshold" command Product-Group=junos Severity=Major	The ntp (or xntpd) process is initialized when the "show system ntp threshold" command is issued. This has no impact to system operation.
PR Number	Synopsis	Category: Kernel Tunnel Interface Infrastructure
1897240 Major	Chassis-Control restart triggers when configuring GRE interface across multiple routing-instances leading to kernel crash Product-Group=junos Severity=Major	On Junos series devices, the kernel crash occurs when creating and configuring a identical GRE(Generic Routing Encapsulation) interface across different routing-instances.
PR Number	Synopsis	Category: Paradise pfe ddos protection feature
1828196 Major	Error messages are seen due to high CPU utilization Product-Group=junos Severity=Major	On Junos MX and PTX platforms (non-AFT based), error messages are seen with the operations that involve high CPU utilization on the RE and/or FPC. This issue has no impact on traffic.
PR Number	Synopsis	Category: Issues related to PKI daemon
1901098 Major	PFE Crash observed platforms where PKI and SSL-Proxy services are configured Product-Group=junos Severity=Major	In stressful conditions, FPC crash observed and core file generated when PKI (Public key infrastructure) and SSL-Proxy (Secure Sockets Layer) services are configured, on all Junos platforms supporting PKI and SSL-Proxy services (MX, PTX, SRX).
PR Number	Synopsis	Category: Periodic Packet Management Daemon
1909719 Critical	Junos and Junos OS Evolved platforms experience high CPU after FPC reboot causing unpredictable issues with protocols (OSPF/ISIS/BGP, etc.) managed by PPMD Product-Group=junos Severity=Critical	After upgrading or rebooting Junos/Junos OS Evolved platforms, a CPU spike may be observed in the PPMD (Periodic Packet Management Daemon) process due to repeated internal message failures. This can lead to BFD (Bidirectional Forwarding Detection) authentication failures. Additionally, other protocols that rely on authentication and PPMD for packet distribution may also be affected, potentially resulting in traffic loss.
1912250 Major	BFD sessions will not come up on Junos OS and Junos OS Evolved platforms due to keychain names overlapping Product-Group=junos Severity=Major	On Junos OS and Junos OS Evolved platforms, where BFD with authentication key chain names are overlapping due to which BFD (Bidirectional Forwarding Detection) sessions will not come up in few scenarios like restart bfdd, restart ppmd, restart FPC.
PR Number	Synopsis	Category: QFX L2 PFE
1866016 Minor	Model: qfx5120-32c \| Junos: 22.2R3-S4.10 \| Management lost \| JSD Coredumps observed Product-Group=junos Severity=Minor	A race in JSD When multiple clients connecting and disconnecting can cause JSD to crash.
PR Number	Synopsis	Category: 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 Number	Synopsis	Category: QFX EVPN / VxLAN
1897459 Minor	qfx5120-48y-8c/23.4R2-S3.9/Flooding back GARP BUM traffic towards source. Product-Group=junos Severity=Minor	When EVPN is configured on Broadcom-based platforms, GARP reply packets are flooded and may be sent back toward the source device. With this fix, GARP reply packets will be terminated rather than flooded.
PR Number	Synopsis	Category: QFX5200/5110/5120/5210 Platfom issues
1796218 Major	The 100G VCP will go down upon restarting or upgrading the device Product-Group=junos Severity=Major	On Junos QFX5K platforms in a Virtual Chassis scenario, the 100G VCP (Virtual Chassis Port) will go down and remain in a down state after a device or VCP restart or device upgrade.
PR Number	Synopsis	Category: Category for QFX5K EVO Platform Software PRs related to Chas
1816064 Major	QFX5130-48C/QFX5130-48CM: In rare cases, "FPC 0 Volt Sensor Fail" or "FPC 0 Voltage Threshold Crossed" alarm seen after bootup Product-Group=junos Severity=Major	In rare cases, "FPC 0 Volt Sensor Fail" or "FPC 0 Voltage Threshold Crossed" alarm is seen after bootup on QFX5130-48C/QFX5130-48CM.
PR Number	Synopsis	Category: RPD Interfaces related issues
1831337 Major	When configuring router-advertisement on PS interfaces, the system sends router advertisement with invalid source link-address option Product-Group=junos Severity=Major	On Junos OS and Junos OS Evolved platform, when router-advertisement is enabled on Pseudowire Subscriber(PS) interface configurations where Virtual Local Area Network (VLAN) tags are used, the system may incorrectly assign MAC (Media Access Control) addresses, causing routing and forwarding failures.
1913519 Major	EVPN routes are stuck in the KRT queue Product-Group=junos Severity=Major	When EVPN (Ethernet Virtual Private Network) routes attempt to transition between private (eg, management em1 - with IGP enabled) and public interfaces, it causes an error in next-hop resolution in the kernel, because the system deletes the old indirect next-hop and creates a new one. This happens as the kernel does not support changing an indirect next-hop between private and public interfaces directly.
PR Number	Synopsis	Category: KRT Queue issues within RPD
1868085 Major	The rpd process crashes and asserts are seen due to memory leak Product-Group=junos Severity=Major	On all Junos and Junos Evolved platforms, rpd process crashes and asserts are seen due to a memory leak when BGP sharding is enabled and 'show route' is performed continuously.
PR Number	Synopsis	Category: RPD route tables, resolver, routing instances, static routes
1907558 Major	The rpd process crashes in a vrf having EVPN-VXLAN routes with specific configuration. Product-Group=junos Severity=Major	In all Junos and Junos OS Evolved platforms, when EVPN-VXLAN (Ethernet Virtual Private Network-Virtual Extensible LAN) routes are present in a VRF (Virtual Routing and Forwarding), configuring a generate route in same vrf can cause rpd (Routing Protocol Daemon) to crash and restart. Generate route configuration has to be removed to recover from this behaviour.
PR Number	Synopsis	Category: Resource Reservation Protocol
1792192 Major	Missing HELLO object in RSVP Hello messages after RE failovers in the NSR mode Product-Group=junos Severity=Major	In rare unknown condition after RE switchover, rsvp hello can have local instance to be zero due to wrong information synced from master RE by mirroring process. When rsvp neighbor is created and never received hello exchange with neighbor, the replication entry which is synced to standby RE will have most of the information as zero, including the local instance, which is used to generate hello object. After RE switchover, rsvp hello will have local instance to be zero due to the wrong information synced from master RE by mirroring process. This is addressed by update the replication entry once all the parameters of the rsvp neighbor is filled, so standby RE will receive the right info, also for future protection, backup RE will avoid creating neighbor until after switchover and setting a new local instance if it is zero.
1893822 Major	Record Route Object displayed in show mpls lsp output is trucated if number of hops is sixteen or more Product-Group=junos Severity=Major	If the number of RSVP LSP hops is sixteen or higher, the RRO displayed in show mpls lsp extensive output may get truncated
1896022 Major	More bandwidth admitted onto a TE link when Label Switched Paths (LSPs) undergoing make-before-break re-route over the same link carrying the bypass LSP during local repair Product-Group=junos Severity=Major	On all Junos and Junos evolved platforms with Point of Local Repair Router, in a Multiprotocol Label Switching(MPLS) Label Switched Paths (LSPs) set-up if the ingress router is configured with link-protection , if Label Switched Paths (LSPs) undergo local repair and subsequently undergo global repair in make-before-break fashion such that the LSPs are re-routed over the same TE link that carries the bypass LSP that protect the LSPs during local repair, then more re-routed LSPs may be admitted on the TE link carrying the bypass LSP than that should be admitted. This may result in some re-routed LSPs remaining on the TE link causing additional traffic sent on the TE link than the capacity of the TE link.
PR Number	Synopsis	Category: MX SCBE3 specific timing and synchronization issues
1902478 Major	After the deactivation of the PTP protocol in the G.8275.1 profile configuration, SyncE remained in Holdover mode. Product-Group=junos Severity=Major	In G.8275.1 Hybrid mode of operation, when PTP only is deactivated, SyncE shall not lock to the SyncE source and DPLL shall remain in Holdover state.
PR Number	Synopsis	Category: SNMP Infrastructure (snmpd, mib2d)
1906065 Major	ifStackStatus is not reported correctly for one or more AE bundles Product-Group=junos Severity=Major	On all Junos, the ifStackStatus query is executed after the system reboot, the member link status is not reported correctly for one or more AE (Aggregated Ethernet) bundles and thus the relation between AE IFL (Logical Interface) and corresponding member link IFL's cant be fetched from ifStackTable. This is an error message and no traffic impact will be observed.
PR Number	Synopsis	Category: Bug and Review Tracking for Segment routing traffic eng
1881989 Major	Tactical Traffic Engineering does not work on aggregated-ethernet interfaces Product-Group=junos Severity=Major	On all Junos and Junos Evolved platforms, Segment Routing Tactical Traffic Engineering (TTE) does not work as expected for aggregated-ethernet interfaces. As a result, congestion is not alleviated or sent over TI-LFA paths.
PR Number	Synopsis	Category: SRX branch platforms
1878769 Minor	Disabled port becomes up after rebooting Junos SRX300, SRX320, SRX340, SRX345 and SRX380 platforms Product-Group=junos Severity=Minor	When a port with SFP-T is disabled, it shows admin down, but can be physical up state after rebooting.
PR Number	Synopsis	Category: SRX-1RU platfom related protocol, QoS, filtering features et
1886757 Minor	Alarms for high usage in /var partition are not generated Product-Group=junos Severity=Minor	On Junos SRX4600/SRX4700/SRX1600/SRX2300/SRX4300 platforms, alarms for high usage at /var partition storage is not reported.
1904696 Major	FPC flaps and the Ukern process will crash on certain SRX platforms when the policer action is changed from 'discard' to 'loss-priority' Product-Group=junos Severity=Major	On SRX4600, SRX4700, and SRX5K platforms, the Flexible PIC Concentrator (FPC) flaps and Ukern process will crash when the policer action is changed from 'discard' to 'loss-priority'. Traffic will be impacted when the FPC flaps.
1911845 Critical	SRX PFE crash is observed if nexthop limit is reached Product-Group=junos Severity=Critical	On all SRX platforms, SRX PFE ( Packet Forwarding Engine ) crash is observed if next-hops in the PFE next-hop table exceeds the limit 64k.
PR Number	Synopsis	Category: ZT/YT pfe infra issues
1897464 Major	Memory allocation failure in all the FPCs inside the NH partition Product-Group=junos Severity=Major	On all affected platforms, under rare conditions involving heavy control-plane churn and a large number of interfaces within a routing instance, memory allocation failures related to Next-Hop processing will occur. This can lead to traffic drops and, in severe cases, complete service disruption across multiple FPCs.
PR Number	Synopsis	Category: ZT/YT pfe multicast software
1912465 Major	Multicast traffic not forwarded to AE member interfaces when Multicast Latency Fairness feature is enabled Product-Group=junos Severity=Major	On all MX platforms using MPC10, MPC11, LC4800, LC9600, MPC10E-10C, or MPC10E-15C line cards, multicast traffic is not forwarded to Aggregated Ethernet (AE) member interfaces when the Multicast Latency Fairness (MLF) feature is enabled.This issue occurs when the multicast downstream list includes AE interfaces along with two or more physical downstream interfaces located on different Packet Forwarding Engines (PFEs).
PR Number	Synopsis	Category: Issues related to broadband edge apps (PPP, DHCP) on Trio ch
1905768 Major	FPC crash triggered when a line card reboots with a large number of static subscribers Product-Group=junos Severity=Major	On all MX platforms with the MPCs/Line cards except MPC10E, MPC11E, LC9600 and MX304. When a line card hosting an AE ( Aggregate Ethernet ) interface with a large number of static subscribers (around 4000) reboots, excessive processing load across multiple subscriber interfaces will cause delays that trigger the watchdog timer and result in an FPC ( Flexible PIC Concentrator ) crash.
PR Number	Synopsis	Category: Trio pfe l3 forwarding issues
1891110 Major	A GRE tunnel configured with a tunnel key drops MPLS-encapsulated traffic Product-Group=junos Severity=Major	On MX platforms with line cards MPC1-9, a Generic Routing Encapsulation (GRE) tunnel configured with a tunnel key drops Multi-Protocol Label Switching (MPLS) encapsulated traffic as it is unable to find the key.
1913870 Major	GRE-over-GRE tunnel is down due to keepalive packets dropped Product-Group=junos Severity=Major	On Junos MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020 and MX10003 platforms using a version of line cards MX2K-MPC(6/9)E, MX-MPC(2/3)E or MPC(3/5/7)E; when Generic Routing Encapsulation (GRE)-over-GRE is configured, end-to-end keepalive packets in the outer tunnel are dropped, and tunnel interface cannot pass traffic
PR Number	Synopsis	Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1902713 Minor	The mgd process crash observed on running commit check after replace operation of groups name for apply-groups-except Product-Group=junos Severity=Minor	On all Junos and Junos OS Evolved platforms, when replace operation was done on apply-groups-except object it was not clearing the entry of that object from apply-groups-info-tree, as a result 'mgd' process crash observed on commit check. There is no service impact due to this issue.
PR Number	Synopsis	Category: Issues related to NETCONF
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 Number	Synopsis	Category: MX10004 Chassis Category
1811485 Minor	Intermittent SFB I2C failure Alarm and Alarm cleared after 3 polls of 5 seconds due to ZF0 VDD 0.75V intermittent access failure Product-Group=junosvae Severity=Minor	Those sporadic raising and clearing SFB I2C Alarms are pure cosmetic and have no operational impact. The alarm threshold heuristic had been adapted to avoid such spurious Alarms. If there is no i2c access failure, reading out the voltage sensor, the error counter will be cleared after 24 hours. The Alarm will be only raised if the error is reported 3 times within 24 hours.
PR Number	Synopsis	Category: VMHOST platforms software
1898108 Major	"re_rainier_perform_misc_checks:Failed to perform RE memory size check" from chassisd are flooding continuously and do not stop Product-Group=junos Severity=Major	On Junos MX platforms, missing /bin/timeout utility can result in "re_rainier_perform_misc_checks:Failed to perform RE memory size check" from chassisd are flooding continuously.
PR Number	Synopsis	Category: ACX7000 hwd/chassisd software related issues.
1700839 Minor	ACX7100-32C/ACX7100-48L reports "/psm/0/ hwdre/0/cm/0/ psm_mcu /psm0/psm_cml_cmd_fault" even though the PSM is in working order Product-Group=junos Severity=Minor	On ACX7100-32C/ACX7100-48L platforms, "/psm/0 /hwdre/0 /cm/0 /psm_mcu/ psm0/psm_cml_cmd_fault" error is observed even though the PSM is in working order.
PR Number	Synopsis	Category: usf url filtering related issue
1814701 Major	, URL filtering sessions are bypassed on MX platform with SPC3 Product-Group=junos Severity=Major	On MX platform with SPC3, the packets matched under the URL-filtering configuration are bypassed rather than the action mentioned in the rule.
PR Number	Synopsis	Category: Unified Services Framework
1912459 Critical	The nsd process crash will be seen on MX platforms when configuration change is commited using ephemeral database Product-Group=junos Severity=Critical	On MX platforms with SPC3 line cards, when the ephemeral configuration-database is configured, parsing of the respective hierarchies by nsd (Network Security Domain) was faulty and leads to the daemon crash.

Extended Solution

23.4R2-S7 - List of Known issues

PR Number	Synopsis	Category: Software build tools (packaging, makefiles, et. al.)
1900881 Major	EX2300/EX3400: TFTP installation failure Product-Group=junos	EX2300/EX3400 : TFTP install can fail with a "No device tree blob found" error Resolved In: junos:24.4R2-S2 junos:25.2R1-S2 junos:25.2R2 junos:25.4R1 junos:25.4R2 junos:26.1R1
PR Number	Synopsis	Category: EX4000 HW issues
1902609 Minor	Intermittent kernel panic results in device reboot or fxpc crash Product-Group=junosvae	On all EX4000-48MP/EX4000-48P/EX4000-48T platforms, false ECC (Error-Correcting Code) alarms are observed due to the usage of un-initialised memory on the chip and intermittent kernel panic might result in vm core dump causing device reboot or fxpc crash. This results in impact on the traffic. Resolved In: junos:24.4R2 junos:24.4R2-S1 junos:24.4R2-S2 junos:25.2R1-S2 junos:25.2R2 junos:25.4B1 junos:25.4R1 junos:26.1R1
PR Number	Synopsis	Category: NFX Series Platform Software
1858495 Major	The auto-negotiation is not working properly on NFX350 platform using 1 Gigabit Ethernet SFP Product-Group=junos	On NFX350 platforms connected to certain peer devices over SFP 1 Gigabit Ethernet (GE) with auto-negotiation enabled at both ends, a communication issue occur during the initial connection between devices, causing a mismatch in their status. As a result, the port status on the peer device appear as up/down affecting the traffic. Resolved In: junos:24.2R2-S2 junos:24.4R2 junos:25.2R1-S1 junos:25.2R2 junos:25.4R1
PR Number	Synopsis	Category: MX YT-ZF Linecards Fabric Software Category
1891047 Minor	SFB is stuck in CMTY_SFB_STATE_OFFLINE_ACK_WAIT state and does not come offline or online Product-Group=junos	SFB ( Switch Fabric Board ) is stuck in transitioning to offline, when SFB offline (sfb slot X offline) is attempted after disabling fabric planes (fabric plane X offline). Resolved In: junos:24.2R2-S2-J5 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR Number	Synopsis	Category: Border Gateway Protocol
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.4R3-J1 junos:22.4R3-S4 junos:23.2R2-S3 junos:23.4R2-S1 junos:24.2R1-S2 junos:24.2R2 junos:24.3R1 junos:24.4R1 junos:25.2R1-S2 junos:25.2R2
1877261 Major	BGP updates missing graceful-shutdown community after quick sender knob flaps Product-Group=junos	On all Junos and Junos Evolved platforms, when the graceful-shutdown sender knob is repeatedly deleted and subsequently re-added in quick intervals under a BGP (Border Gateway Protocol) session, the router CLI (command line interface) incorrectly indicates that the graceful-shutdown community is being advertised. However, the actual BGP update messages sent over the session do not include the graceful-shutdown community. This results in the graceful-shutdown community not being propagated to BGP peers during graceful shutdown events, which will potentially cause traffic forwarding issues. Resolved In: evo:23.2R2-S5-EVO evo:24.2R2-S2-EVO evo:24.4R2-EVO evo:24.4X200-D10-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:23.2R2-S5 junos:24.2R2-J6 junos:24.2R2-S1-J4 junos:24.2R2-S2 junos:24.4R2 junos:24.4R2-S1 junos:25.2R1 junos:25.3R1
1881717 Major	Incorrect MPLS label derivation with inactive EBGP route advertisement Product-Group=junos	On Junos and Junos Evolved platforms, MPLS (Multiprotocol Label Switching) forwarding issues may occur when labels are assigned on a locally preferred IBGP (Interior Border Gateway Protocol) route, while an inactive EBGP (Exterior Border Gateway Protocol) route is advertised via Add-Path or advertise-external. When per-prefix-label allocation is either explicit or via SRGB (Segment Routing Global Block), this mismatch can result in incorrect label forwarding. Resolved In: evo:22.3X80-D49-EVO evo:22.4R3-S8-EVO evo:23.2R2-S5-EVO evo:23.4R2-S5-EVO evo:24.2R2-S2-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:21.4R3-S12 junos:22.4R3-S7-J1 junos:22.4R3-S8 junos:23.2R2-S5 junos:24.2R2-S2 junos:24.4R2 junos:25.2R1 junos:25.2R2 junos:25.3R1
PR Number	Synopsis	Category: BBE Remote Access Server
1813456 Minor	Error message is observed after device is restarted Product-Group=junos	On all Junos Evolved platforms, the error message "UI_SCHEMA_SEQUENCE_ERROR" is observed when device is restarted. There is no traffic impact due to this issue. Resolved In: evo:23.2R2-S4-EVO evo:24.2R2-S4-EVO evo:24.4R2-EVO evo:25.1R1-EVO evo:25.2R1-EVO junos:23.2R2-S6 junos:23.2R2-S6-JUNOS-TO-EVO-HELPER junos:24.2R2-S4 junos:24.4R2 junos:25.1R1 junos:25.2R1
PR Number	Synopsis	Category: Express BT PFE L3 Features
1886043 Major	Few telemetry paths are not exported after router reboot Product-Group=junos	Following a router reboot, the router management socket, telemetry infrastructure, and RE daemons (such as mib2d and rpd) become operational before telemetry producers. Consequently, the external telemetry collector can establish a connection (e.g. sensor: "/interfaces" ; sample-mode) with the device as soon as the telemetry infrastructure and management interface are up and running. Since producers require several minutes to come up. Therefore, na-grpcd sends a consolidated initial sync completion message to the external collector based on the local init-sync responses from the telemetry producers present at telemetry subscription time (mostly RE based producers). When an application (evo-aftman-bt) becomes operational, a sensor is installed within it (if applicable).However, it is possible that the application has not consumed, thus not exported the interfaces data at the initial sync time (local to the application). As zero-suppression is activated after initial sync, a few statistics with a zero value will not be exported by the device. Resolved In: evo:22.3X80-D47-EVO evo:22.3X80-D49-EVO evo:24.4R2-EVO evo:24.4X200-D20-EVO evo:24.4X200-D30-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:25.2R2 junos:25.3R1 junos:25.4R1
PR Number	Synopsis	Category: MX304 Routing Engine issues
1891577 Major	On MX304 platform ungraceful removal of standby RE results in communication loss between REs Product-Group=junos	On MX304 platform, the removal of backup RE causes RE (Routing Engine) to RE communication to break. This will cause the Backup RE to remain in present state and thus subsequent failover will lead to complete traffic loss. Resolved In: junos:24.4R2 junos:24.4R2-S5 junos:25.2R2 junos:25.4R1
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	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. Resolved In: junos:25.4R2 junos:26.1R1
PR Number	Synopsis	Category: Alias for DHCP issue on DNX based 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.4R2-S3-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 Number	Synopsis	Category: 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 Number	Synopsis	Category: Interface PRs defect & enhancement requests
1845336 Major	Memory leak during interface flap events on Junos Evolved Platforms Product-Group=junos	On all Junos Evolved platforms, a memory leak is observed during continuous interface creation and deletion. The internal interface management logic allocates memory during interface (IFD) creation but fails to properly release it during deletion. Over time, this leads to increased memory consumption across multiple system applications. In high-scale environmentswith approximately 30 million interface flaps observed in a real deploymentthis leads to memory exhaustion and result in application restarts, potentially impacting services. Resolved In: evo:23.4R2-S5-EVO evo:23.4R2-S7-EVO evo:23.4X100-D40-EVO
PR Number	Synopsis	Category: AAA, auditd issues
1786580 Major	Username in accounting logs is getting truncated to 16 characters Product-Group=junos	On all Junos OS Evolved platforms, if the username is more than 16 characters, username will be truncated to 16 characters in the accounting logs displayed for that user. Resolved In: evo:22.3X80-D42-EVO evo:22.3X80-D43-EVO evo:23.2R2-S4-J2-EVO evo:23.4R2-S4-J2-EVO evo:24.1B1-EVO evo:24.1R1-EVO evo:24.2R1-EVO junos:23.2R2-S5 junos:23.4R2-S4-J26 junos:23.4R2-S4-J27 junos:23.4R2-S5-J17 junos:23.4X30-D30 junos:23.4X9 junos:24.1B1 junos:24.1R1 junos:24.2R1 junos:24.4R2-S3
PR Number	Synopsis	Category: 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 Number	Synopsis	Category: EX interfaces issues
1771119 Major	Mixed speed support in PIC2 phyless 4x10G uplink module Product-Group=junos	1G and 10G are now default speeds in 10G ULM. Resolved In: junos:24.2R1-S1-J4 junos:24.2R1-S2-J1 junos:24.2R2 junos:24.4R1 junos:24.4R2 junos:25.1R1
1886889 Minor	snmp mib walk DomCurrentLaneAlarms does not show proper lanes Values in the latest builds Product-Group=junos	Resolved In: evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:24.2R2-S2 junos:24.4R2 junos:25.2R1-S1 junos:25.2R2 junos:25.3R1 junos:25.4R1
1909608 Minor	Auto-negotiation is not displayed in 'show interfaces' command output Product-Group=junos	On EX3400 and EX4400-48F, when using 1G optics, the auto-negotiation information does not appear in the output of the "show interfaces" command. Resolved In: junos:24.2R2-S4 junos:24.4R2-S3 junos:25.4R1 junos:25.4R2 junos:26.1R1
PR Number	Synopsis	Category: EX optics issues
1887303 Minor	[EX4400-48F] One of the 10gBase-T transceiver is not detected - showing as "Partial" Unknown in PFE Product-Group=junos	In the EX4400-48F systems, a 10G-BaseT transceiver that was earlier up may not come up post a reboot/image upgrade event; The transceiver may go undetected causing the interface to not be created in the system. Resolved In:
PR Number	Synopsis	Category: Express ASIC interface
1793344 Major	The 10g channelized Interface doesn't come up after router reboot on the PTX5000 platform Product-Group=junos	On Junos PTX5K platforms running 22.3X60 configured with FPC3-PTX-U2 and FPC3-PTX-U3, the 10g channelized Interface port doesn't come up after router reboot. In rare conditions, the interface might remain down when firmware attempts to configure the line-side lane configuration during the firmware mode set process. Resolved In: junos:22.3X60 junos:22.4R3-S5
PR Number	Synopsis	Category: MX MIC-3D-10GE-SFP-X driver
1906675 Major	Link failure due to auto-negotiation state getting stuck on MX platforms having Junos OS Product-Group=junos	On all Junos OS MX platforms that support MPC2E-NG, MPC2E-3D-NG-Q, MPC3E-NG and MPC3E-3D-NG-Q, the Auto-Negotiation (AN) process on certain PHY interfaces of the MIC (MIC-3D-10GE-SFP-E) may intermittently get stuck, preventing link establishment and causing traffic loss. This issue can be triggered by reinserting an SFP-T module, multiple times restarting the mic or by interface driver resets, which lead to inconsistent enable/disable sequences during Auto-Negotiation. Resolved In: evo:25.2R2-EVO evo:26.1R1-EVO junos:24.2R2-S4 junos:25.2R1-S2 junos:25.2R2 junos:26.1R1
PR Number	Synopsis	Category: Interface Information Display
1741282 Major	JUNOS MX \| iflset stats not getting cleared after issuing clear interfaces stats all and clear interfaces interface-set statistics all CLI command Product-Group=junos	JUNOS MX \| iflset stats not getting cleared after issuing clear interfaces stats all and clear interfaces interface-set statistics all CLI command Resolved In: evo:24.4R2-EVO evo:25.1R1-EVO junos:24.2R2-S1 junos:24.4R2 junos:25.1R1
PR Number	Synopsis	Category: ISIS routing protocol
1892136 Minor	Primary path temporarily disappear until the MLA timer expires for IPv6 SRv6 routes Product-Group=junos	On Junos and Junos EVO platforms having Segment Routing over IPv6 (SRv6) with the Intermediate System to Intermediate System (IS-IS) routing protocol and with the Microloop Avoidance (MLA) feature enabled, primary path for IPv6 SRv6 routes disappear until the MLA delay timer expires if Multiprotocol Label Switching (MPLS) is configured only at the global level. Traffic loss occur if network topology changes during this period. Resolved In: evo:25.2R2-EVO evo:25.4R1-EVO junos:25.2R2 junos:25.4R1
PR Number	Synopsis	Category: Issues related to JMRT and other Malware found by customers
1889037 Major	Temporary file /tmp/veriexec_test is not cleaning up on all platforms after "request system malware-scan integrity-check" Product-Group=junos	On all Junos OS and Junos OS Evolved platforms, temporary binary file /tmp/veriexec_test is created to test if veriexec (Verified Exec) is running as expected or not while running "request system malware-scan integrity-check". This temporary file isn't getting removed after the test execution. Resolved In: evo:26.1R1-EVO junos:25.4R1 junos:26.1R1
PR Number	Synopsis	Category: Flow Module
1834338 Major	GRE traffic is getting blocked due to a software programming issue and MTU going below minimum value Product-Group=junos	On Junos OS SRX platforms with GRE (Generic Routing Encapsulation) configured, due to a software programming issue, some threads have incomplete information while processing the data and even if "no-path-mtu-discovery" or "no-gre-path-mtu-discovery" is configured, the MTU going below minimum value (IPv4- 578, IPv6 1280) resulting in the GRE traffic being blocked i.e. complete traffic impact. Resolved In: junos:24.2R2 junos:24.4R2 junos:25.1R1 junos:25.2R1
1892015 Major	Junos MX/SRX flowd Crash After Tunnel Removal Leaves Stale Flows, Causing FPC Reboot Product-Group=junos	On Junos OS SRX and MX platforms, any tunnels such as GRE, IPIP, DS-Lite, or IPSEC tunnel has its configuration removed, the IKE SAs can go down causing invalid entires. These can later cause the flowd process to crash Resolved In: junos:22.4R3-S9 junos:23.2R2-S6 junos:23.4R2-S6 junos:24.2R2-S4 junos:24.4R1-S2-J9 junos:24.4R2-S1-J5 junos:24.4R2-S2 junos:24.4R2-S3 junos:25.2R1-S2 junos:25.2R2 junos:25.4R1 junos:26.1R1
PR Number	Synopsis	Category: IPSEC/IKE VPN
1877966 Minor	Some new VPN tunnels are not coming up on SRX5K platforms with SPC3 Product-Group=junos	On SRX5K platforms with SPC3 installed, IPSec (Internet Protocol Security ) tunnels with iked which reuses the same IKE (Internet Key Exchange) gateway peer IP, could be observed not re-establishing. Resolved In: junos:22.4R3-S8 junos:24.2R2-S2 junos:24.4R2-S2 junos:25.3R1
1912271 Major	State synchronization failure between SRX cluster nodes Product-Group=junos	On all SRX series platform in cluster with IKED package enabled, when the backup node becomes active, some tunnel configuration were missing. This occurs because, during cold synchronization, the IPC communication between IKED and SPU can have a chance to fail due to a kernl error which ultimately led to traffic disruption. Resolved In: junos:24.4R2-S2-J1 junos:24.4R2-S3 junos:25.4R1 junos:25.4R2 junos:26.1R1
PR Number	Synopsis	Category: Layer2 forwarding on EX/NFX/PTX/QFX
1816344 Major	EVPN : Traffic failure after multiple link flaps of core facing interfaces on scaled setup Product-Group=junos	ARP resolution failure when there is quick flap of core facing interface on scaled setup Resolved In: evo:24.2R2-S2-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO evo:26.1R1-EVO evo:26.2R1-EVO junos:24.2R2-S2 junos:24.4R2 junos:25.2R1 junos:25.3R1
1909786 Critical	EVPN traffic blackholing occurs due to incorrect ARP binding when VGA IP is used as re-ARP source Product-Group=junos	On all Junos platforms, In Ethernet VPN (EVPN) Virtual Extensible LAN (VXLAN) deployments using Integrated Routing and Bridging (IRB) interfaces with a virtual gateway IP address and virtual gateway Media Access Control (MAC) configuration, re-ARP packets may use the virtual gateway IP as the source IP while using the IRB MAC as the source MAC. This behavior can cause connected hosts to overwrite their Address Resolution Protocol (ARP) entries, resulting in traffic being forwarded to an incorrect leaf switch in all-active Link Aggregation Group (LAG) multihoming scenarios. This may lead to intermittent or complete traffic loss for hosts connected via LAG to dual-homed leaf devices. Resolved In: evo:23.4R2-S6-EVO junos:23.2R2-S6 junos:23.4R2-S6 junos:24.2R2-S4 junos:24.4R2-S2 junos:25.2R1-S2 junos:25.2R2 junos:25.4R1 junos:26.1R1
PR Number	Synopsis	Category: Label Distribution Protocol
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 Number	Synopsis	Category: PTX1000 platform
1770739 Critical	Reboot on PTX1k with image 22.3x60 causes fpc to reboot with "Fatal ASIC initialization error, Offlining FPC" Error message Product-Group=junosvae	Reboot on PTX1k with image 22.3x60 causes fpc to reboot with "Fatal ASIC initialization error, Offlining FPC" Error message times Resolved In: junos:22.2R3-S3 junos:22.2R3-S4 junos:22.3R3-S3 junos:22.3X60 junos:22.4R3-S2 junos:22.4R3-S8 junos:22.4X3 junos:22.4X4
PR Number	Synopsis	Category: Port-based link layer security services and protocols that a
1885185 Major	AE interface going down on specific MX platform with exclude-protocol being re-configured under MACsec. Product-Group=junos	When exclude protocol is configured with MACsec(Media Access Control Security) on IFD (Interface Device), a delete AE(Aggregated Ethernet) interface can cause the exclude protocol filters to not clean up on MX platforms with MPC10 and MPC11 linecards . When MACsec is reconfigured on the same link with AE, AE interface goes down. Resolved In: evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:25.2R2 junos:25.3R1 junos:25.4R1
PR Number	Synopsis	Category: SW PRs for MPC10E Interfaces
1908238 Minor	MPC10 reports "ifd 340; does not exist " after configuring an interface Product-Group=junos	MPC10 reports "ifd 340; does not exist " after configuring an interface Resolved In: junos:26.1R1
PR Number	Synopsis	Category: Multicast Routing
1876458 Major	MX960 mcsnoopd core dump during rt_mcnh_nh_release Product-Group=junos	When the mcsnoopd process (use for L2 multicast) creating a new NH , our system takes a reference to it. However, if this reference is released too quickly, the old NH might be deleted before its references are fully cleared. This may cause the mcsnoopd process to restart. Resolved In: evo:22.4R3-S8-EVO evo:23.4R2-S6-EVO evo:24.2R2-S2-EVO evo:24.4R2-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:22.4R3-S8 junos:23.2R2-S5 junos:23.4R2-S6 junos:24.2R2-S2 junos:24.4R2 junos:25.2R2 junos:25.3R1
PR Number	Synopsis	Category: Multicast for L3VPNs
1888630 Major	MVPN Source PE might incorrectly send mcast traffic on SPT while actual receiver is still on RPTree Product-Group=junos	In currently flow when a provider tunnel is being deleted, it is assumed the cmcast routes associated to the ptnl would've have been updated before. This is fine for inclusive tunnels, however for selective tunnels especially wild card scenarios the cmcast routes may not be updated. So in cases where the ptnl is deleted like configuration based removal or underlying tunnel going down, there is chance that the forwarding routes are still not deleted. The cmcasts are deleted later in the flow but when they are deleted the corresponding forwarding routes are still not deleted since there is no corresponding ptnl for the cmcast. This will create issues if forwarding is supposed to happen via different forwarding entry like a , G entry but since the more specific S, G stale entry exists, traffic will hit the later and lead to unexpected behavior like traffic black-holing if S, G is Pruned entry. Resolved In:* evo:24.2R2-S3-EVO evo:24.4R2-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:24.2R2-S3 junos:24.4R2 junos:25.2R2 junos:25.3R1 junos:25.4R1
1902405 Major	The rpd process crash is observed with MVPN and RIB sharding enabled Product-Group=junos	On Junos MX and Junos Evolved PTX platforms , with RIB sharding enabled and if either IPv4 or IPv6 address family is disabled in MVPN (multicast virtual private network), the unicast route flow from shard tries to access MVPN data structures without validation leading to rpd (Routing Protocol Daemon) process crash. Resolved In: evo:24.4R2-S1-EVO evo:25.2R1-S2-EVO evo:25.2R2-EVO evo:25.4R1-EVO junos:24.2R2-S3 junos:24.4R2-J2 junos:24.4R2-S1 junos:25.2R1-S2 junos:25.2R2 junos:25.4R1
PR Number	Synopsis	Category: Odin Timing software
1810429 Major	ACX710 PTP ports marked 'passive' instead of 'master' during T-GM selection Product-Group=junos	In a scenario where two T-GM devices (Telecom Grandmaster clocks) have identical BMCA (Best Master Clock Algorithm) parameters, except for steps removed or grandmaster ID, the ACX710 running the G.8275.1 profile can experience a failure in proper PTP (Precision Time Protocol) clock synchronization. This issue arises because the default BMCA is used instead of the expected Alternate BMCA profile in G.8275.1. This mismatch leads to incorrect PTP clock states, with master ports being marked as 'Passive' instead of 'Master'. Resolved In: junos:23.2R2-S3 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR Number	Synopsis	Category: OS IPv4/ARP/ICMPv4
1801129 Major	IP routes can get added to a deleted routing table Product-Group=junos	On all Junos platforms routes can get added to deleted routing tables. Resolved In: junos:24.2R2 junos:24.3R1
1918788 Major	[QFX5120] 23.4R2-S5 - PROXY-ARP not replying ARP-REQUEST from client. Product-Group=junos	PROXY-ARP not replying ARP-REQUEST from client. Working as designed. Resolved In:
PR Number	Synopsis	Category: "ifstate" infrastructure
1882329 Minor	The management interface is unreachable post switchover/RPD restart events Product-Group=junos	On all Junos platforms with management interface like em0/me0/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 Number	Synopsis	Category: IPv6/ND/ICMPv6 issues
1920718 Minor	Ksyncd core seen : "ROUTE subtype 18 : Can't assign requested address" due to a misconfiguration Product-Group=junos	Ksyncd core seen : " ROUTE subtype 18 : Can't assign requested address" due to a misconfiguration i.e giving subnet route as nexthop in below configuration which is incorrect.A valid nexthop has to be given. set protocols mpls static-label-switched-path ae131.0-v6 transit 1004040 next-hop fc00:: 220. This is applicable to all JUNOS platforms. Resolved In:
PR Number	Synopsis	Category: JUNOS Network App Infrastructure (for ping, traceroute, etc)
1924159 Major	Fetch command output format changed and completion percentage not displayed Product-Group=junos	On Junos and Junos OS Evolved platforms, the output format of the fetch command changed after upgrading to a newer upstream version of the utility. The earlier format displayed an explicit completion indicator (for example, 100%). The upgraded version removed this indicator. Resolved In: evo:25.4R2-EVO evo:26.1R1-EVO evo:26.2R1-EVO junos:25.4R1-S1 junos:25.4R2 junos:26.1R1
PR Number	Synopsis	Category: Phone-Home-Client Infrastructure
1811521 Major	PHC gets initiated and sends DNS request to Juniper server "redirect.juniper.net" even when device is supposed to get provisioned using ZTP with vendor specific option 43 Product-Group=junos	Rarely, on all Junos platforms, PHC (Phone Home Client) is signaled to attempt bootstrapping by AIU (Auto Image Upgrade) when legacy ZTP (Zero Touch Provisioning) fails if vendor specific options (option 43 is sent by DHCP server) are not valid. This is followed by PHC sending DNS request to resolve "redirect.juniper.net" which is the redirect Juniper Server even if DHCP is released by ZTP and no IP is expected to be present. Resolved In: evo:22.4R3-S5-EVO evo:23.2R2-S3-EVO evo:23.4R2-S5-EVO evo:24.2R2-EVO junos:21.4R3-S10 junos:22.2R3-S5 junos:22.3R3-S4 junos:22.4R3-S5 junos:23.2R2-S3 junos:23.4R2-S5 junos:24.2R2 junos:24.4R1
PR Number	Synopsis	Category: Protocol Independant Multicast
1880262 Major	PIM neighbors timeout on backup RE due to inconsistent state with master Product-Group=junos	On all Junos and Junos Evolved platforms with dual Routing Engines (REs), Protocol Independent Multicast (PIM) neighborship is not be maintained on the backup Routing Engine after a ppmd-agent restart. This can lead to loss of PIM neighbor state on the backup RE. Resolved In: evo:23.4R2-S6-EVO evo:24.2R2-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:22.4R3-S8 junos:23.2R2-S5 junos:23.4R2-S6 junos:24.2R2-S2 junos:25.2R2 junos:25.3R1
PR Number	Synopsis	Category: Issues related to PKI daemon
1876497 Minor	Wrong digest algorithm is used for ECDSA key based certificate requests using PKI Product-Group=junos	On all Junos and Junos Evolved platforms, when generating Elliptic Curve Digital Signature Algorithm (ECDSA) based Certificate Signing Request (CSR) using Public Key Infrastructure (PKI), SHA-384 digest is used even when other digest algorithm is specified in Command Line Interface (CLI). This issue will impact services that are based on these certificates when the services are configured for specific digest algorithm. Resolved In: evo:22.3X80-D49-EVO evo:24.2R2-S2-EVO evo:24.4R2-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:24.2R2-S2 junos:24.4R2 junos:25.2R2 junos:25.3R1
PR Number	Synopsis	Category: PPPoE functional plugin for bbe-smgd
1868007 Major	PPPoE subscriber login failures observed after interface flapping resulting in AC system errors on Junos MX Platforms Product-Group=junos	On Junos MX platform with subscriber management enabled, interface flapping causes PPPoE subscriber login failures, resulting in AC (Access Concentrator)System errors. Resolved In: evo:25.2R1-EVO evo:25.3R1-EVO junos:20.2R3-S11 junos:21.4R3-S12 junos:22.4R2-S1-J6 junos:22.4R3-S7 junos:23.2R2-S5 junos:24.2R2-S2 junos:24.4R2 junos:25.2R1 junos:25.3R1
PR Number	Synopsis	Category: QFX L2 PFE
1912846 Critical	LLDP neighborship will not be displayed post reboot of VXLAN VC devices. Product-Group=junos	In VXLAN VC environment, with Leaf multi-homed to CE devices via AE link, LLDP neighbors will not be successful post reboot of the devices. Resolved In: junos:24.4R2-S3 junos:25.4R1-S1 junos:25.4R2 junos:26.1R1
PR Number	Synopsis	Category: QFX5100 Platfom related issues. CPLD, FPGA, FRU, Host, RE
1888543 Minor	SNMP trap on Junos QFX5100 and EX4600 platforms report incorrect jnxOperatingState after PEM reinsertion on master switch Product-Group=junos	On Junos QFX5100 and EX4600 platforms with releases 21.4R3-S3, 21.4R3-S10, and 21.4R3-S11, the SNMP trap generated after reinserting a PEM on the master switch incorrectly reports the jnxOperatingState as 6 (down) instead of the expected value 2 (running). This behaviour is consistently reproducible across multiple versions and persists even after performing a mastership switchover. Resolved In: junos:21.4R3-S12 junos:26.1R1
PR Number	Synopsis	Category: RPD Interfaces related issues
1741485 Major	Unnecessary rsync messages causing issues Product-Group=junos	Resolved In: evo:24.1R1-EVO junos:24.1R1
1905553 Minor	Redundant prefix information is included within one router-advertisement packet when configuring accept-data in VRRPv6 Product-Group=junos	When configuring accept-data in VRRPv6, two entries for the same prefix value are included within one router-advertisement packet on all Junos platforms. Resolved In: evo:25.4R1-EVO evo:25.4R2-EVO evo:26.1R1-EVO junos:25.4R1 junos:25.4R2 junos:26.1R1
PR Number	Synopsis	Category: KRT Queue issues within RPD
1908681 Major	RIB and the FIB inconsistency results in traffic loss in IPsec scenario with st0 interface configured Product-Group=junos	On Junos OS SRX platforms having IPsec (Internet Protocol Security) with st0 (Secure Tunnel Interface) interface configured, traffic loss will be observed if the "next-hop-tunnel" configuration is removed and added within a few seconds. This happens due to a inconsistency between the RIB (Routing Information Base) and the FIB (Forwarding Information Base). Resolved In: evo:24.2R2-S4-EVO evo:25.2R2-EVO evo:25.4R1-EVO evo:26.1R1-EVO junos:22.4R3-S9 junos:23.2R2-S6 junos:24.2R2-S4 junos:25.2R2 junos:25.4R1 junos:26.1R1
PR Number	Synopsis	Category: 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:24.2R2-S4-EVO evo:24.4R2-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:25.2R2 junos:25.3R1
PR Number	Synopsis	Category: RPD Next-hop issues including indirect, CNH, and MCNH
1851629 Minor	Next-hop APIs to support LDP stitching cases over BGP routes pointing to list of indirects Product-Group=junos	On all Junos and Junos Evolved platforms this is an enhancement for Nexthop APIs to support LDP stitching cases over BGP routes pointing to list of indirects next-hops. Resolved In: evo:24.4R1-S3-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:24.4R1-S3 junos:24.4R2 junos:25.2R1 junos:25.2R2 junos:25.4DCB
PR Number	Synopsis	Category: 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-S3 junos:25.2R2 junos:25.3R1 junos:25.4R1 junos:25.4R2 junos:26.1DCB
PR Number	Synopsis	Category: Resource Reservation Protocol
1881609 Minor	RSVP hello messages uses secondary address when primary/preferred address are present for same interface Product-Group=junos	On all Junos and Junos OS Evolved platforms where RSVP (Resource Reservation Protocol) configuration is present and a RSVP enabled interface has 2 IP address of which one is configured as primary/preferred in that case the RSVP Hello message uses the secondary IP address to form neighborship. Resolved In: evo:25.3R1-EVO junos:25.3R1
1881906 Major	BFD session failure causes LSP to go down and the inactive route remains in the routing table leads to traffic black hole Product-Group=junos	On Junos OS and Junos OS Evolved platforms, when an RSVP (Resource Reservation Protocol) LSP (Label Switched Path) goes down due to a failure in the associated BFD (Bidirectional Forwarding Detection) session, and the corresponding route remains in the routing/forwarding table causing traffic black-holing. If there are other active LSPs to the same destination, those active routes are preferred over the inactive route associated with the failed LSP. Resolved In: evo:24.4R2-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:23.4R2-S6 junos:24.2R2-S2 junos:24.4R2 junos:25.2R2 junos:25.3R1
PR Number	Synopsis	Category: Sangria Platform including chassisd, RE, CB, power managemen
1913580 Major	Chassisd crash will happen when shutting down the FPC of PTX5000 and PTX3000 using online/offline button Product-Group=junos	When the FPC(Flexible PIC Concentrator)online/offline button is pressed on PTX5000 and PTX3000 twice in a short period, chassisd crash will happen. it is causing all FPCs to lose connectivity with the Routing Engine while remaining in an online state. As a result, service impact happened till all FPCs become online. Resolved In: junos:22.4R3-S9
PR Number	Synopsis	Category: Generic platform and infra issues for MS-MIC and MS-MPC(XLP)
1899178 Critical	Service session drops are observed when CPU throttling is configured on platforms with service cards installed Product-Group=junos	On all Junos MX platforms that have MS-MPC or MS-MIC service cards installed, the use of the CPU throttling can cause the production service sessions to be dropped. Resolved In: junos:21.2R3-S10 junos:21.2R3-S6-J16 junos:22.4R3-S7-J5 junos:22.4R3-S9
PR Number	Synopsis	Category: ZT/YT pfe firewall software
1704583 Major	Change in firewall filter triggers transient traffic drops in FPC Product-Group=junos	On all Junos MX platforms with MPC10E/MPC11E/LC9600 line cards and on MX304, change or modification in Firewall filters will trigger transient packet drops. Resolved In: evo:23.1R1-EVO evo:23.2R1-EVO junos:22.2R3-S3 junos:22.4R3 junos:23.1R1 junos:23.2R1
PR Number	Synopsis	Category: Authentication, Authorization, Accounting, PAM (RADIUS/tacplus)
1850776 Critical	Multiple Products: RADIUS protocol susceptible to forgery attacks (Blast-RADIUS) (CVE-2024-3596) Product-Group=junos	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. Resolved In: junos:21.4R3-S10 junos:21.4R3-S10-X1 junos:22.2R3-S6 junos:22.4R3-S6 junos:23.2R2-S3
PR Number	Synopsis	Category: Configuration mgmt, ffp, load-action, commit processing
1845657 Major	Baseline configuration commit takes more time with 256000 MAC configurations Product-Group=junos	On all Junos and Junos OS Evolved platforms with dual RE (Routing Engine), the baseline configuration commit takes more time when the device has 256000 MAC (Media Access Control) configurations configured under groups. It is a scaling issue, and occurs when a large number (256000 or more) of MAC configurations are configured. This has no impact to network traffic. Resolved In: evo:24.4R1-S2-EVO evo:24.4R2-EVO evo:25.2R1-EVO junos:24.4R1-S2 junos:24.4R2 junos:25.2R1
PR Number	Synopsis	Category: Issues related to YANG Data Models
1781023 Minor	Few yang package are occuring multiple place On Box Product-Group=junos	Few yang package are occuring multiple place On Box Resolved In:
PR Number	Synopsis	Category: Junos Fusion Aggregation Device Infra
1913169 Major	The smdp process crash is observed on MX Aggregation Device during Junos upgrade in a Junos Fusion Deployment Product-Group=junos	In all Junos MX platforms acting as the AD (Aggregation Device) in a Junos Fusion deployment, a Junos software upgrade causes the smdp (Satellite Platform and Management Daemon) process to crash impacting forwarding plane services. This issue is observed when AD nodes are moved to a higher Junos version while the SD (Satellite nodes) are still running a lower version. Resolved In: junos:22.4R3-S7-J7 junos:22.4R3-S9 junos:23.2R2-S6
PR Number	Synopsis	Category: MX10K linecard
1898825 Major	Timing defect in ukern thread handling causing LC reboot Product-Group=junos	On Junos platforms using line cards LC480 and LC2101, a timing defect in the embedded microkernel thread handling logic causes a panic when a thread attempts to yield execution while interrupt processing is still active. This panic results in a line card reboot. Resolved In: evo:24.4R2-S3-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:24.2R2-S4 junos:24.4R2-S3 junos:24.4R2-S4 junos:25.2R2 junos:25.2R2-S1 junos:25.3R1 junos:25.4R1
PR Number	Synopsis	Category: VMHOST platforms software
1795506 Minor	A non service impacting warning message 'Failed to set 'memory.limit' will be observed Product-Group=junos	On all Junos OS Evolved platforms a warning message "Failed to set 'memory.limit_in_bytes' attribute on '/user.slice' to '-1': Invalid argument" would be observed. Resolved In: evo:22.3R3-S4-EVO evo:22.3X50-EVO evo:22.3X80-D43-EVO evo:22.3X80-D44-EVO evo:24.2R1-EVO evo:24.2R1-S1-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:24.2X1 junos:24.4R1
PR Number	Synopsis	Category: QFX10002 Platform
1869232 Major	CRC errors increase continuously after interface flap on some 100G transceivers with Rx CDR LOL support Product-Group=junos	On Junos PTX10002-60C, and QFX10002-60C platforms, when using 100G QSFP modules with CDR LOL support, CRC errors have been observed on odd-numbered ports, leading to traffic disruptions. Resolved In: junos:22.4R3-S7-J1 junos:22.4R3-S9
PR Number	Synopsis	Category: usf flow and datapath issue on SPC3
1882490 Minor	BFD fail to establish over an IPsec tunnel on Juniper MX Series with the SPC3 Product-Group=junos	On Juniper MX Series platforms equipped with Services Processing Card version 3 (SPC3), Bidirectional Forwarding Detection (BFD) session establishment over an Internet Protocol Security (IPsec) tunnel may fail due to an unintended Time to Live (TTL) decrement on self-generated BFD traffic. Resolved In: junos:21.4R3-S13 junos:23.2R2-S5 junos:23.4R2-S6 junos:24.4R2 junos:25.2R1-S2 junos:25.2R2 junos:25.3R1 junos:25.4R1

Modification History

First publication 2026-01-16