Article Detail

Alert Type

SRN - Software Release Notification

RiskRisk Description

Low/Notification

Software Release Notification

ImpactImpact Description

Low/Notification

Software Release Notification

Product Affected

SRX vSRX

Alert Description

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

Review list of issues

NOTE: See TSB101868 [juniper.net] Do not upgrade to JUNOS version 23.4R2-S5 if you are using the following optic modules

JNP-SFP-25G-SR 740-068639
JNP-SFP-25G-LR 740-0715262
SFP-25G-SR-IT 740-106769
SFP-25G-LR-IT 740-106770

An interface using these optic modules will stay down after upgrade.

Solution

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

23.4R2-S5 - List of Fixed issues

PR Number	Synopsis	Category: NSD process
1857379 Critical	The nsd process crashes on SRX platforms during cluster reboot, failover, or policy addition causes traffic outage Product-Group=junos Severity=Critical	On all Junos OS SRX series platforms configured with the logical systems (LSYS), the network security daemon (nsd) process crashes due to cluster failover or reboot of node in a standalone firewall setup or while adding security policies. This crash generates a core dump and prevents the system from configuring security policies. As a result, all policy configurations are removed, leading to a traffic outage.
PR Number	Synopsis	Category: SRX1600 MACsec
1863576 Minor	Packet drops can occur when packets are received with a size equal to the default MRU Product-Group=junos Severity=Minor	On SRX1600, SRX2300 and SRX4300 platforms, when packets are received with a size matching the default MRU (Maximum Receive Unit) value of 1522 bytes, packets are dropped, leading to an impact on traffic.
PR Number	Synopsis	Category: SRX2300 4300 Broadcom TD3/SDK, data path related issue
1776223 Minor	Traffic fails on SRX2300/SRX4300 PIC1 ports with 1G SFP-SX transceivers Product-Group=junos Severity=Minor	On SRX2300 and SRX4300 platforms running Junos, when 1G SFP-SX transceivers are inserted into PIC1(Physical Interface Card) ports, traffic does not pass through the link. This issue affects data forwarding and may lead to network connectivity failure through the impacted ports.
PR Number	Synopsis	Category: SRX Macsec bug tracking
1873885 Major	Commit Delay Due to Incomplete MACsec Pre-Shared Key Configuration Product-Group=junos Severity=Major	Commit Delay Due to Incomplete MACsec Pre-Shared Key Configuration
PR Number	Synopsis	Category: "agentd" software daemon
1779722 Minor	The interface fails to come up after FPC reboot if the streaming server and export profile are not configured correctly Product-Group=junos Severity=Minor	On all Junos and Junos evolved platforms with telemetry enabled, if the streaming server and export profile for reporting-rate are not properly configured in the analytics settings, rebooting the FPC would prevent any of the interfaces from coming up.
PR Number	Synopsis	Category: the replication daemon (repd) for Shared Memory-base
1870183 Major	RPD might crash when upgrading using no-validate. Product-Group=junos Severity=Major	RPD might crash when upgrading without using no-validate. Use no-validate to avoid the crash.
PR Number	Synopsis	Category: Border Gateway Protocol
1849568 Minor	L3VPN routes are not advertised to peer when BGP sessions with route-target filter flaps Product-Group=junos Severity=Minor	On all Junos and Junos OS Evolved platforms, after Border Gateway Protocol (BGP) sessions configured with 'family route-target' flaps, delayed route deletion causes the loss of the Route Target Filter (RTF), preventing the node from advertising L3VPN (Layer 3 Virtual Private Network) and direct routes (e.g., loopbacks and interface routes) to the BGP peer, leading to VPN route loss and service disruption.
1853025 Major	Updating a source-file to load ROAs should be done by changing the name of the source file Product-Group=junos Severity=Major	Loading ROAs from a source-file was a feature introduced as a convenience feature and as such this only affects that feature. This feature is not in widespread use and was created to have a fallback ROA when all sessions go down. This problem scenario requires multiple reloads with the being modified back and forth to add and then delete and re-add the database configured in the import policy.
1860786 Major	BGP queue deadlock on Junos/Junos OS Evolved/cRPD platforms leading to route advertisement failure and traffic loss Product-Group=junos Severity=Major	On all Junos, Junos OS Evolved, and cRPD platforms, due to deadlock in internal processes, BGP (Border Gateway Protocol) route advertisement fails leading to traffic disruption.
1863551 Major	BGP route advertisement failure with as-override and peer-as configured at group level Product-Group=junos Severity=Major	On all Junos and Junos OS Evolved platforms, BGP ( Border Gateway Protocol ) fails to advertise routes to external peers in an L3VPN ( Layer 3 Virtual Private Network ) environment when as-override is configured for a neighbor on the local device, and peer-as is applied at the group level. Since the routes are not advertised to peers, traffic matching those routes are dropped, causing service disruption.
1864676 Major	The rpd process will crash due to memory leak Product-Group=junos Severity=Major	The rpd process will crash due to a memory leak when configuration using apply-groups or ephemeral database for "routing-options autonomous-system independent-domain".
1865114 Major	Valid BGP routes in RIB are displayed with verification state as Invalid Product-Group=junos Severity=Major	On Junos and Junos Evolved platforms, with resource public key infrastructure(RPKI ) enabled for the BGP, the valid routes are installed in the routing table with validation state invalid.However, the route is parsed by policy as a valid route.
1875144 Minor	Longer convergence is seen for a BGP neighbor having validation configured in its import policy Product-Group=junos Severity=Minor	On all Junos and Junos Evolved platform, when any BGP peer has validation policy configured for import, it is observed that there is an extra walk to re-evaluate the routes in the loc-rib for validation even though the policy/unrelated configuration is changed for an unrelated peer.
PR Number	Synopsis	Category: BGP BMP Software
1839288 Major	BMP soft assert due to counter reset by clear command Product-Group=junos Severity=Major	On all Junos and Junos Evolved platforms, when "clear bgp statistics" command is issued while one or more BMP peers are coming up the soft_assert will be hit. This issue has no impact on the traffic or services.
PR Number	Synopsis	Category: MX Platform SW - FRU Management
1801284 Major	The RE switchover will not be triggered in case of clock failure on SCBE3-MX Product-Group=junos Severity=Major	On MX platforms with SCBE3-MX (MX240, MX480 and MX960) due to a hardware failure of the Control Board, the Routing Engine(RE) switchover might not happen. This will result in the 19.4Mhz clock failure and has potential risk for chassis wide traffic impact. In worst case all revenue ports will be impacted. If the RE switchover is done in a timely manner then the device will recover because FPCs will try using the 19.4Mhz clock from the new master.
PR Number	Synopsis	Category: QFX Access Control related
1851299 Minor	EX3400 Dot1x Radius accounting send incorrect value to the server for Acct-Input-Gigawords/ Acct-Output-Gigawords Product-Group=junos Severity=Minor	With Dot1x Radius Authentication and Accounting, when the Stop Accounting (due to disconnect) is sent to the Radius server the Acct-Input-Gigawords and the Acct-Output-Gigawords contains unexpectedly large value.
1872280 Major	The l2ald process crash is observed on non L2NG Junos platforms configured with "native-vlan-id" and "bridge-domains" on an IFL Product-Group=junos Severity=Major	On non L2NG (Layer2 Next Generation) Junos EX, MX and SRX platforms, the l2ald (Layer 2 Address Learning Daemon) process crash is observed when an IFL (Logical Interface) configured with "native-vlan-id" and "bridge-domains" and when certain config change takes place in an IFL which maps VLAN (Virtual Local Area Network) index to NULL. The dereferencing of this NULL pointer causes the crash.
PR Number	Synopsis	Category: Device Configuration Daemon
1848768 Major	MTU configuration is not applied from the configuration group after commit and "warning" is seen Product-Group=junos Severity=Major	When configuring MTU on interfaces through a configuration-group and commit the changes, those are not saved on the configuration file.
PR Number	Synopsis	Category: Firewall Filter
1872347 Critical	System becomes unresponsive or crash due to frequent filter changes in a scale scenario having mib2d process in use Product-Group=junos Severity=Critical	On Junos OS platforms, The system experiences memory exhaustion due to an mbuf (Memory Buffer) leak, system logs error message. This condition can cause the system to become unresponsive (hang state) or potentially crash, resulting in a VMcore file and service disruption. The issue arises when a firewall filter is applied to approximately 1k (1000) logical interfaces (IFLs), each filter containing over 250 terms and these filters are updated every 2-3 minutes, triggering updates for all filter attachments.
PR Number	Synopsis	Category: BGP MPLS VPN specific issues
1853294 Major	Packet loss observed across multiple traffic items using SR profiles within the L3VPN Product-Group=junos Severity=Major	On ACX5448 and ACX710 platforms under L3VPN (Layer 3 Virtual Private Network) deployment using OSPF (Open Shortest Path First) or BGP (Border Gateway Protocol), when traffic is forwarded over SR (Segment Routing) profiles, packet loss is observed across multiple traffic items.
PR Number	Synopsis	Category: AF interface in Node Virtualization
1857225 Major	Input traffic on physical interface increases in the fabric statistics count despite locality bias feature configured Product-Group=junos Severity=Major	On all MX platforms having MPC10 or MPC11 the traffic coming from any physical interface belonging to these MPCs will always take a fabric hop before forwarding to any physical link in egress. As a result despite locality bias feature being configured, instead of avoiding fabric hops while sending out of local PFE links, it will still be chosen but the fabric hop is forced and the input traffic on that physical interface will still end up showing increase in the fabric statistics count. But there is no traffic impact due to this issue.
PR Number	Synopsis	Category: AAA, auditd issues
1862203 Minor	Radius authentication is failing when Challenge Token is entered Product-Group=junos Severity=Minor	On all Junos and Evo platforms, the Radius Multi-Factor Authentication (MFA) failing for user login if the password and token were provided in two separate steps.
PR Number	Synopsis	Category: mgd, ddl, odl infra issues
1864996 Major	Device sends RA msg even after deleting RA config from interface. Product-Group=junos Severity=Major	Device sends RA msg even after deleting RA config from interface.
PR Number	Synopsis	Category: EVPN control plane issues
1846096 Critical	RPD restart immediately on EVPN Designated Forwarder PE with Graceful-restart results in 100% traffic loss for 12-15 secs Product-Group=junos Severity=Critical	With a EVPN PE running 24.2, 24.4 releases with Graceful restart enabled, if RPD is restarted or flaps, traffic loss for 15s could be seen to Multihomed CEs
1870365 Major	'TLV type 00000052 not supported on IFL gr' seen repeatedly in syslog for EVPN routing-instance configured with gr- ifls Product-Group=junos Severity=Major	JUNOS/EVO platforms running 23.4R2 and later software, if they have EVPN routing-instances with gr- ifls as members, continuous 'TLV not supported' messages could be seen in syslog.
PR Number	Synopsis	Category: EVPN Layer-2 Forwarding
1833660 Major	Stale MAC entries may remain in the MAC table of EVPN routing instances after rapid MAC-IP move scenarios Product-Group=junos Severity=Major	On all Junos OS and Junos OS Evolved platforms with EVPN-MPLS (Ethernet Virtual Private Network - Multiprotocol Label Switching) setup , stale MAC entries may remain in the MAC table of the EVPN (Ethernet Virtual Private Network) routing instances during rapid MAC-IP move scenarios. This can cause MAC tables to reach their limits preventing new MAC addresses learning and user registration.
PR Number	Synopsis	Category: Express PFE FW Features
1855459 Major	On some PTX and QFX platform parity error causes packet drop Product-Group=junos Severity=Major	On Junos PTX1000, PTX5000, QFX10000, PTX10002-60C, QFX10002-60C, QFX10008, QFX10016 and PTX10000 platforms when IPv6 filter is configured that has a match condition of source/ destination address greater than 64 bits, it results in packet drops due to transient hardware parity error that occurs on the prefix table. This will only reject what is permitted, does not allow unpermitted packets unless default term is accept and is a rare issue.
PR Number	Synopsis	Category: Express PFE L2 fwding Features
1834429 Minor	VRRP fails on 802.1Q VLAN Layer 3 logical interface on QFX10002-60C Product-Group=junos Severity=Minor	On Junos QFX10002-60C platform, VRRP (Virtual Router Redundancy Protocol) fails to work on 802.1Q VLAN (Virtual Local Area Network) tagging due to the lack of support for VRRP on Layer 3 logical interface. As a result, the VRRP VIP (Virtual IP) is unreachable, causing VRRP functionality to fail.
PR Number	Synopsis	Category: SRX1500 platform software
1831955 Major	The SRX1500 drops the packet if MTU matches the MRU of the receiving device Product-Group=junosvae Severity=Major	On SRX1500 platforms, if the Maximum Transmission Unit (MTU) is configured to match the Maximum Receive Unit (MRU) of the receiving device, packet drops occur. This occurs because additional processing overhead increases the packet size beyond the MRU limit, causing the receiving device to drop the packets.
1876867 Major	FPC goes offline and srxpfe core dump is generated during the system normal operation or boot-up Product-Group=junosvae Severity=Major	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.
PR Number	Synopsis	Category: SRX4100/SRX4200 platform software
1706125 Major	ifHCOutOctets unexpected spikes in value Product-Group=junos Severity=Major	On SRX4100 and SRX4200 platforms, the ifHCOutOctets interface counter values may sometimes incorrectly spike and exceed interface speed.
PR Number	Synopsis	Category: Signature Database
1822319 Minor	Not able to update IDP signature DB when using Proxy server Product-Group=junos Severity=Minor	On all Junos and Junos OS Evolved platforms, the IDP signature download issue is seen with squid proxy server of a specific version like 6.6 is installed.
PR Number	Synopsis	Category: Libjtask for RPD tasks, scheduler, timers, memory, and slip
1846294 Major	Memory Leak: Memory leak is detected with rpd task blocks "rpd-trace" Product-Group=junos Severity=Major	Memory Leak: Memory leak is detected with rpd task blocks "rpd-trace"
PR Number	Synopsis	Category: Kernel software for AE/AS/Container
1845370 Major	Interface not added back to AE bundle with multiple changes in single commit Product-Group=junos Severity=Major	On all Junos platforms when speed is changed on an interface which is part of AE bundle, interface will be removed and added with the updated speed. When some other operation such as interface disable is configured along with speed change on the interface in the same commit, then the interface is not removed and added to the bundle, it can cause other AE interfaces flap and traffic drop.
PR Number	Synopsis	Category: IoT data filtering/streaming
1830246 Major	The PFE crash is observed on SRX platforms on dynamic-filter configuration Product-Group=junos Severity=Major	On SRX platforms when the dynamic filter is configured, the packet forwarding engine (PFE) crashes, impacting traffic.
PR Number	Synopsis	Category: jdhcpd daemon
1808289 Minor	Switch provisioned via ZTP going unreachable due to DHCP misbehaviour on upgrading to 21.4R3-S6 Product-Group=junos Severity=Minor	All IRB (Integrated Bridging and Routing) interfaces of EX3400-48P switches which pull initial configuration from Dynamic Host Configuration Protocol (DHCP) server via zero touch provisioning (ZTP) process, upon upgrade to 21.4R3-S6 do not send DHCPdiscover packet to obtain a new IP address after sending DHCPrelease packet resulting in interface not able to obtain IP address until rebooted.
1843596 Minor	DHCPv6 Renew from a dual-stack CPE may be ignored if DHCP server is using DUID type 3 (DUID-LL) and DHCPv6 binding doesn't exist Product-Group=junos Severity=Minor	DHCPv6 Renew packets from dual-stack CPE could be silently ignored by MX configured as DHCPv6 local server if such DHCPv6 binding doesn't exist.
1872292 Major	DNS resolution will fail for DNS entries written to "resolv.conf" Product-Group=junos Severity=Major	On all Junos platforms with ZTP (Zero-Touch Provisioning) configuration, when the configuration is completely removed, DNS (Domain Name System) resolution for DNS entries written to "resolv.conf" will fail.
PR Number	Synopsis	Category: JFlow bug tracker for SRX platforms
1843679 Minor	Application crash is observed due to insufficient memory when a large number of JFlow entries are created Product-Group=junos Severity=Minor	On Junos OS SRX platforms with JFlow configured with sampling interval set to 1, traffic impact is observed due to insufficient memory for the Layer 7 applications leading to application failure. The issue happens when a large number of JFlow entries are created exhausting memory potentially leading to crash.
PR Number	Synopsis	Category: Adresses ALG issues found in JSF
1852968 Major	The SRX platform may experience a flowd process crash and generate core dump files when the ALG feature is enabled Product-Group=junos Severity=Major	On SRX platforms running the Junos Operating System (OS) with Application Layer Gateway (ALG) enabled, in rare scenarios, flowd process can crash and crash files are generated. While the platform eventually recovers, traffic loss will occur during this process.
PR Number	Synopsis	Category: Adresses NAT/NATLIB issues found in JSF
1817417 Minor	Commit error is observed on Junos platforms with MS-MPC or SPC3 when last octet of source-ip of jflow-log collector is above 223 Product-Group=junos Severity=Minor	Configuration is not committed and shows commit error on Junos platforms with MS-MPC or SPC3 when last octet of source-ip of jflow-log collector is higher than 223.
PR Number	Synopsis	Category: Flow Module
1807505 Major	On SRX5000 series and SRX4600, the setting "apply-to-half-close-state" for TCP sessions is not taking effect. Product-Group=junos Severity=Major	On SRX5000 series and SRX4600, the setting "set security flow tcp-session time-wait-state apply-to-half-close-state" is not taking effect for sessions that are using express path (services-offload). This may lead to an increased number of sessions compared to earlier Junos releases which did not have an express path enabled by default.
1859163 Minor	Security forwarding process crash may occur when multicast traffic triggers a route resolution request that needs to be processed for a pending session Product-Group=junos Severity=Minor	When multicast traffic triggers a route resolution request for a pending session, and the route is subsequently resolved, a race condition may occur if that pending session is terminated by a different thread before processing can continue. This can result in a crash of the flowd (security forwarding process). However, the control plane remains online and unaffected.
1872613 Major	PFE crash is observed when PFE processes the traffic passing through the dedicated fabric link Product-Group=junos Severity=Major	On the Junos OS SRX4600 platform, when PFE (Packet Forwarding Engine) processes the IPv4/IPv6 traffic passes through the dedicated fabric link, PFE crash is observed. This issue happens when PMI (PowerMode IPsec) is enabled (by default) and flow session accessing stale values.
PR Number	Synopsis	Category: N/A:sw-jsr-flow-mcast
1854130 Major	PIM IP ESP packet fragments dropped in SRX platform Product-Group=junos Severity=Major	Protocol Independent Multicast (PIM) fragmented packets using IP Protocol 50 (Encapsulating Security Payload - ESP) are dropped when traversing SRX devices operating in flow mode.
PR Number	Synopsis	Category: High Availability/NSRP/VRRP
1850967 Major	L3MNHA with SRG1 IPSEC : MNHA ICL ipsec encryption link went down permanently after rebooting connected router through which ICL was established before. During this state IKE process got stuck at ~70% on MNHA Active node. Product-Group=junos Severity=Major	Generic MNHA issue not specific to CSDS
PR Number	Synopsis	Category: l2 flow module
1856200 Major	PFE crash due to invalid cached next hop during reinjection on SRX5k Product-Group=junos Severity=Major	On SRX5k devices, the PFE (Packet Forwarding Engine) may suddenly crash with a core dump written and force a restart against all line cards during massive interface or route changes when the system caches and reinjects an invalid next hop.
PR Number	Synopsis	Category: all logging related bugs on srx platforms
1860597 Major	Security log report messages w.r.t logical system is not generated Product-Group=junos Severity=Major	show security log report cli command for logical systems is not working for 24.2R2, 24.4R1-S2, if log report is disabled under root system. Work around is available for this issue.
PR Number	Synopsis	Category: Firewall Policy
1809563 Major	The "show security match-policies" command results in a timeout error Product-Group=junos Severity=Major	On all SRX platforms, when a scaled DNS (Domain Name System) configuration with approximately 500 entries is applied along with a policy configuration, issuing the "show security match-policies" command results in a timeout error. This issue has no functional impact.
1823591 Minor	Failed inter-process communication results in higher heap and buffer usage which impacts the functionality of processes Product-Group=junos Severity=Minor	On all Junos SRX platforms, when there is a broken Inter-Process Communication (IPC) link between the Routing Engine (RE) and Packet Forwarding Engine (PFE), heap and buffer utilization gradually increase to 99%, causing some software modules to start failing.
1837182 Minor	[SRX] - RE and PFE policy out of sync with specific configuration. Product-Group=junos Severity=Minor	With security meta-streaming policy configuration, RE and PFE out-of-sync false alarm was seen. This does not impact actual synchronization between RE and PFE. Also does not cause any traffic problem. set security policies from-zone LAN to-zone INTERNETapplication-services security-metadata-streaming-policy ADV_SEC set security policies from-zone DMZ to-zone INTERNETapplication-services security-metadata-streaming-policy ADV_SEC
1838698 Minor	Security flow sessions are impacted during ISSU on SRX platforms Product-Group=junos Severity=Minor	On Junos SRX platforms configured as chassis clusters, while performing ISSU (In-Service Software Upgrade), when the secondary node is being upgraded, synchronization between primary and secondary nodes is concluded without completion. Due to this, the security session flows are impacted when the secondary node takes over primary role and polices are realised and pushed to PFE (Packet Forwarding Engine).
1859554 Minor	Wrong service-name display in SRX RT_FLOW traffic log. Product-Group=junos Severity=Minor	On SRX platforms, wrong service-name might display in SRX RT_FLOW traffic log.
PR Number	Synopsis	Category: User Firewall related issues
1810310 Minor	NSD file handles incrementing consistently in database file causing a rare condition of ssh access failure Product-Group=junos Severity=Minor	On all Junos SRX branch platforms, Network Security Daemon(NSD) file handles increments consistently. Triggering a rare condition of ssh access failure of the device.
PR Number	Synopsis	Category: IPSEC/IKE VPN
1841364 Major	The kmd process crash is seen on random number generation by the third-party library API Product-Group=junos Severity=Major	On Junos and Junos evolved platforms on rare circumstances when device is busy kmd process crash is seen on random number generation used for VPN negotiation by the third-party library API.
1864322 Major	On rare circumstances the kmd or iked process crash will be observed on using the third-party library API Product-Group=junos Severity=Major	On all Junos platforms using ipsec-key-management (daemon name kmd) or the ike-key-management (daemon name iked) service for the IPSec VPN functionality, under very rare scenarios the device can be extremely overloaded so that it cannot generate a random number required for the VPN negotiation after repeated attempts. When this occurs, the VPN negotiation daemon kmd or iked can crash. The VPN operation may or may not be temporarily impacted and will recover automatically.
PR Number	Synopsis	Category: Security platform jweb support
1876075 Minor	Upgrade and Downgrade will fail from J-Web in SRX4600 Product-Group=junos Severity=Minor	On SRX4600, upgrades and downgrades will fail from J-Web with the error message: "Installation Progress failed at Receive Package File" from release 23.4 and above.
PR Number	Synopsis	Category: Layer 2 VPN related issues
1867040 Minor	Type 5 EVPN traffic is dropped on SRX when PMI is disabled or not supported Product-Group=junos Severity=Minor	On all SRX platforms, in an EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) environment, when PMI (Power Mode IPSec) is disabled or not supported, type 5 EVPN traffic gets dropped. The issue occurs due to flow context being cleared incorrectly, causing the overlay JEXEC nexthop to be pushed after the underlay one. This leads to the packet being treated as multicast and subsequently dropped.
PR Number	Synopsis	Category: lacp protocol
1874126 Major	AE member not able to discover lost LACP peer connection leading to traffic black-holing Product-Group=junos Severity=Major	On all Junos and Junos Evolved platforms, when a loop occurs in the transmission switch, the device starts receiving looped LACP (Link Aggregation Control Protocol) PDU's from itself, instead of messages from the actual peer device. This causes the system to mistakenly believe that a valid LACP connection exists, even though the peer device is not actually connected.As a result, it continues to forward traffic as if the peer were active. Since no valid peer connection is present, this can lead to traffic blackholing .
PR Number	Synopsis	Category: authd (AAA) library code
1860913 Major	The authd process crashes when /etc/resolv.conf file is empty Product-Group=junos Severity=Major	On Junos OS Evolved ACX platforms, when DHCP (Dynamic Host Control Protocol) local server is configured and the /etc/resolv.conf file is empty with no data/domain information the authd process crash observed. There will be no forwarding traffic impact due this issue and there will be no issue to existing sessions. However, new sessions will have login issue.
PR Number	Synopsis	Category: Issues related to Junos licensing infrastructure
1820329 Minor	License-service subsystem crash is observed when license keys are modified Product-Group=junos Severity=Minor	On all Junos and Junos Evolved platforms, upon adding invalid license keys, the license-check application crash is observed. There is no traffic impact observed due to this issue.
1845079 Minor	Unnecessary trace log files related to licenses are generated Product-Group=junos Severity=Minor	On Junos platforms agile-licensing infra, when upgrading to 23.4R1 and above, unnecessary trace log files related to licenses are generated. This issue has no impact on traffic.
1855728 Minor	License is Missed Post System Reboot Product-Group=junos Severity=Minor	On all Junos platforms, the license is lost after a reboot if it was installed using the 'set system license' method.
PR Number	Synopsis	Category: Port-based link layer security services and protocols that a
1850387 Minor	The dot1xd crash on MACsec enabled ports due to key length limit Product-Group=junos Severity=Minor	On Junos and Junos OS Evolved platforms supporting MACsec (Media Access Control security), when secret key-chain with more than 64 character is configured, it results in crash for dot1xd service causing traffic impact on all MACsec enabled ports.
PR Number	Synopsis	Category: Multiprotocol Label Switching
1854623 Major	The rpd process crashes due to memory exhaustion Product-Group=junos Severity=Major	On all Junos and Junos Evolved platforms, an out-of-memory condition in the rpd process caused by uncontrolled memory allocation leads to the rpd process crashing.
1859219 Major	RSVP-TE LSP path is not re-optimised to the path with best IGP metric Product-Group=junos Severity=Major	On all Junos and Junos Evolved platforms, when RSVP-TE (Resource Reservation Protocol - Traffic Engineering) is configured with MBB (make-before-break) setup, if the protected link of the primary LSP (Label Switched Path) goes down and if "clear mpls lsp" or "clear rsvp session" commands are executed, then LSP switches to new instance from the old which will be on higher IGP (Interior Gateway Protocol) metric. However, after re-optimization, LSP will not get switched to better IGP metric path and remain in old instance. Traffic drop can be seen due to this double fault events.
PR Number	Synopsis	Category: Multicast for L3VPNs
1861726 Major	The MVPN traffic forwarding is affected when BGP PIC is enabled Product-Group=junos Severity=Major	On all Junos OS and Junos OS Evolved platforms, enabling BGP-PIC (Border Gateway Protocol-Prefix Independent Convergence) is causing the issues with forwarding MVPN (Multicast Virtual Private Network) traffic.
PR Number	Synopsis	Category: Category for tracking Olympus-MX issues
1873938 Major	The SPC3 card resets due to kernel memory exhaustion in MX Series platforms with highly scaled routing tables and Inline Active Flow Monitoring configured Product-Group=junos Severity=Major	On MX240, MX480 and MX960 platforms with MX-SPC3 (Services Processing Card) service cards, when Inline Active Flow Monitoring (inline-jflow) is configured in a highly scaled routing environment (~4M routes), the SPC3 service card runs out of kernel memory, resulting in the PIC going offline or resetting and the services running on the SPC3 card gets disrupted.
PR Number	Synopsis	Category: OS IPv4/ARP/ICMPv4
1849296 Minor	The self-generated traffic on Junos platforms use the incorrect source IP with ECMP configuration Product-Group=junos Severity=Minor	On all Junos platforms configured with Equal-Cost Multi-Path (ECMP) routing, self-generated traffic selects an incorrect source (Internet Protocol) IP address. As a result, the peer device lacks the relevant route information, causing self-generated traffic to be dropped. This issue is specific to ECMP configurations and does not impact data traffic.
PR Number	Synopsis	Category: build tools
1874525 Major	FTP default mode changed from active to passive on 24.2R2 Product-Group=junos Severity=Major	An upgrade to libfetch caused the default FTP mode to move from active to passive. This PR corrects this as customers more than likely expect the previous active FTP functionality on their networks.
PR Number	Synopsis	Category: FreeBSD Kernel Infrastructure
1872010 Major	Junos OS: A local attacker with shell access can execute arbitrary code (CVE-2025-21590) Product-Group=junos Severity=Major	An Improper Isolation or Compartmentalization vulnerability in the kernel of Juniper Networks Junos OS allows a local attacker with high privileges to compromise the integrity of the device. Please refer to https://supportportal.juniper.net/JSA93446 [juniper.net] for more information.
PR Number	Synopsis	Category: Express Chip L3 software
1842744 Minor	Incorrect MTU value in the ICMP Next-Hop MTU field, regardless of the actual MTU of the outgoing interfaces Product-Group=junos Severity=Minor	On Junos PTX and QFX1000X platforms, when destination address is reachable through indirect/unilist next-hop and the MTU size of the outgoing interface is lesser than the packet size, then DUT (Device Under Test) will send the ICMP message back to sender with wrong MTU.
PR Number	Synopsis	Category: Path computation client daemon
1823220 Minor	Authentication failure will be seen for routing protocols when MD5 is configured for routing protocols and PCEP on Junos OS Evolved platforms post reboot Product-Group=junos Severity=Minor	When MD5 is configured for PCEP (Path Computation Element Protocol) on Junos OS Evolved platforms, MD5 will not work for other protocols after reboot. Authentication failure will be seen and it causes a connectivity issue or a service impact.
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 Severity=Major	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.
1871802 Critical	High memory and CPU usage due to unintended phone-home client activation Product-Group=junos Severity=Critical	On Junos OS Evolved platforms, high memory and CPU usage may occur if the phone-home client (PHC) is unintentionally triggered, such as when the device boots with factory default settings or when phone-home is manually configured. This can lead to system slowness, crashes, and eventual device reboots.
PR Number	Synopsis	Category: Protocol Independant Multicast
1826383 Major	Rapid increment of "Hardware input drops" on command output "show pfe statistics traffic" due to PFE trapcode "dlu.ucode.ip_mc_iif_mismatch" Product-Group=junos Severity=Major	The issue is due to the PIM Join-load-balance feature. When the router has multiple ECMP paths to reach the multicast source and is configured for PIM Join-load-balance, Load balancing of Join will be done creating an active upstream path and a standby upstream path. When multicast streams are received on the standby upstream path, an IIF_MISMATCH is generated, consequently Standby path gets converted into Active path & PIM Prune will be sent on old active path and periodic joins will be cancelled on old Active path. However, in this case, protocol PIM prematurely removes the old active path without sending a prune on that path and removing the periodic old active joins. There can be another scenario where there is transition from one standby path to another standby path. In that case also old standby path needs to be pruned and periodic joins needs to be cancelled.
PR Number	Synopsis	Category: Issues related to PKI daemon
1767584 Minor	Self-signed certificates created with ECDSA and SHA256 defaults to ECDSA and SHA128 Product-Group=junos Severity=Minor	On all Junos platforms when a self-signed certificate is created with the combination of ciphers ECDSA (Elliptic Curve Digital Signature Algorithm) with digest SHA-256 (Secure Hash Algorithm) the resulting certificate defaults to ECDSA and SHA-128 instead of the specified SHA-256, This can cause issues on any application in which the expected combination of ciphers is ECDSA - SHA-256 (for eg: the JWEB application, as JWEB expects SHA-256, the platform turns inaccessible as long as the certificate remains configured)
PR Number	Synopsis	Category: DHCP related Issues
1818909 Minor	An error log message is seen for every DHCP transaction Product-Group=junos Severity=Minor	On the QFX5120, QFX5110, EX4400, EX4100 and EX4300-48MP platforms, the "Error, DHCP packet re-insert failed" error log message is seen on every DHCP transaction.
PR Number	Synopsis	Category: RPD Interfaces related issues
1842546 Major	Memory leak is detected when interfaces are configured Product-Group=junos Severity=Major	On all Junos and Junos Evolved platforms, 72-byte size memory leak is seen when interface configuration is added. But there is no traffic impact due to this issue.
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 Next-hop issues including indirect, CNH, and MCNH
1861451 Major	BGP PIC failover is taking longer than expected when IS-IS as an IGP enabled with LFA Product-Group=junos Severity=Major	On all Junos and Junos Evolved platforms, in a BGP-L3VPN (Border Gateway Protocol - Layer 3 Virtual Private Network) setup when configured with BGP PIC (Prefix-Independent Convergence) on an ingress PE's (Provider Edge) VRF (Virtual Routing and Forwarding) routing-instance and having IS-IS (Intermediate System-to-Intermediate System) as an IGP (Interior Gateway Protocol) which if enabled with LFA (Loop Free Alternative), BGP PIC failover is taking loger time than expected due to lag in the route change for the BGP path to be used. This is causing traffic loss until global convergence.
1863248 Major	On all Junos OS Evolved platforms, traffic loss will be seen after switching the LSP from SRTE to L-ISIS Product-Group=junos Severity=Major	On all Junos OS Evolved platforms with Segment Routing Traffic-Engineering (SRTE) and Labeled- Intermediate System- Intermediate System (L-ISIS) configuration, when a service route is resolved over SRTE route in inet6color.0 and if the SRTE path in inet6color.0 is deactivated/goes down, the SRTE route is deleted and service route starts resolving over L-ISIS. However traffic loss for 20 minutes or more is seen after switching the Label Switched path (LSP) from SRTE to L-ISIS path.
PR Number	Synopsis	Category: Issues related route resolution routing infrastructure
1858032 Major	The rpd process crashes when generate routes are configured in a rib-sharding scenario Product-Group=junos Severity=Major	On all Junos and Junos Evolved platforms, rpd process crash is seen when Border Gateway Protocol (BGP) rib-sharding is enabled and generate routes are configured. This occurs due to issue in route resolution, the rpd crash impacts routing and rpd will restart when this issue occurs.
PR 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 Severity=Major	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.
1817450 Minor	Route on backup shard is not resolved under certain conditions Product-Group=junos Severity=Minor	after protocol BGP is deactivated, the resolution tables __raass_ at backup RPD are marked as deleted, and not resurrected post commit sync.
1845425 Major	Traffic blackhole is observed for IPv4 /32 LDP prefixes advertised over BGP-LU when BGP sharding is configured Product-Group=junos Severity=Major	On Junos OS MX and Junos OS Evolved PTX platforms with MPLS (Multiprotocol Label Switching) and BGP (Border Gateway Protocol) sharding configured, the route is not resolved as the resolver does not request PNH (Protocol Next Hop) information from RaaS (Routing as a Service) server although BGP added the route resolution in the inet.3 table. This issue leads to IPv4 /32 LDP (Label Distribution Protocol) prefixes advertised over BGP-LU (BGP Label Unicast) not being installed in the mpls.0 table i.e. corresponding labels being marked as hidden in the MPLS routing table (mpls.0), preventing proper traffic forwarding, leading to a traffic blackhole.
PR Number	Synopsis	Category: RPD route tables, resolver, routing instances, static routes
1847811 Minor	The rpd crash on commit when configuring router-advertisement with DNS search label under 3 characters Product-Group=junos Severity=Minor	On all Junos and Junos OS Evolved platforms, committing a configuration under protocols router-advertisement with a dns-search-list containing a domain label shorter than 3 characters causes the rpd (Routing Protocol Daemon) process crashes and restart. This results in configuration commit failure and temporary disruption to routing protocols.
1849202 Major	BGP route still seen in routing table when route not available Product-Group=junos Severity=Major	On all Junos and Junos Evolved platforms , the router learns routes through the BGP (Border Gateway Protocol) and has the feature: "BGP RIB Sharding" enabled for IPv4. These routes are stored in the Inet.0 routing table. Later, if the neighbor that announced this route or the protocols associated with the routing table of the used VRF (Virtual Routing and Forwarding) are removed, the route remains in the routing table, and hence traffic is forwarded to the stale routes.
PR Number	Synopsis	Category: Resource Reservation Protocol
1864949 Major	User traffic dropped after ISIS went down on one side with trapcode observed Product-Group=junos Severity=Major	On all JUNOS and JUNOS evolved Operating Systems, if a link along the path of a Label Switched Path (LSP) flaps briefly such that the router at upstream end of the flapping link does not detect the link down but only the router at the downstream end does, then the upstream router does not undertake necessary actions, like generating ResvTear message, that should be taken after next-hop link down. This will result in unexpected traffic blackholing on the router at the downstream end of the flapping link.
1866944 Major	Traffic blackholing in LSPs due to link failure before protection signalling is processed Product-Group=junos Severity=Major	On all Junos and Junos Evolved platforms, traffic blackholing occurs on MPLS (Multi-Protocol Label Switching) Label Switched Paths (LSPs) when link protection is enabled, under specific conditions during link failure events that occur just after the LSP is established.
PR Number	Synopsis	Category: Secure Web Proxy functionality on Junos
1851686 Minor	Traffic reduction observed for SWP sessions when traffic hits SWP as passthrough. Product-Group=junos Severity=Minor	In srx1500 platforms, passthrough TCP sessions associated with service web proxy (SWP) as a transparent-proxy can be seen as being reduced by a buffer leak under session handling. This lack of memory generates traffic reduction around 98% of the defined traffic.This is detected with the command "show service web-proxy statistics \|no-more" and a considerable decrease is observed in the number of sessions in "Active Transparent proxy sessions" compared to normal transactions.
PR Number	Synopsis	Category: Remote Access VPN issues on SRX
1825573 Major	Juniper Secure Connect will not get connected if loopback is configured as external interface Product-Group=junos Severity=Major	On all SRX platforms, if a loopback interface is configured as an external interface in Internet Key Exchange (IKE) gateway and there are one or more loopback addresses configured without an IPv6 address configured against it, remote access solution will not work, and Juniper Secure Connect (JSC) will report an "HTTPS request failed" error.
1867802 Minor	Traffic Drops on SRX Devices Using Remote Access with Secure Connect/NCP Product-Group=junos Severity=Minor	On SRX Series platforms configured for remote-access VPN using Juniper Secure Connect or NCP clients, users experience intermittent traffic drops affecting all VPN-connected clients. This issue occurs when tcp-encap is enabled. The traffic impact includes: Loss of connectivity to resources behind the SRX and VPN session instability or resets for all active remote-access users. Additionally, the issue can cause a core dump in the VPN process, specifically within the sslvpn daemon. This indicates internal handling errors during encapsulated traffic processing.
PR Number	Synopsis	Category: SRX branch platforms
1836235 Minor	SRX default named.conf file is created with non dns-proxy related configuration changes Product-Group=junos Severity=Minor	On SRX platforms with dns-proxy configured, default named.conf file is created with non dns-proxy related configuration changes. This leads to halting of dns-proxy operation.
1853238 Minor	Flexible-vlan-tagging option is missing under interface hierarchy on SRX3xx series Product-Group=junos Severity=Minor	On SRX3xx series configured with flexible-vlan-tagging, after upgrading the device to Junos version 23.4R2 or higher the flexible-vlan-tagging option is missing under the interface hierarchy. This leads to a syntax error, stopping users from setting the flexible-vlan-tagging.
1873583 Minor	TCP RST packet gets dropped when used with rst-invalidate-session Product-Group=junos Severity=Minor	On all SRX platforms, when the rst-invalidate-session option is enabled, SRX devices drop a TCP (Transmission Control Protocol) RST(Reset) packet that arrives immediately after a TCP SYN (TCP Synchronize) packet, before a full session is established, leading to TCP protocols errors resulting in connectivity issues.
1877323 Major	Unexpected primary role assignment on SRX after node0 reboot Product-Group=junos Severity=Major	On all Branch SRX series platforms(SRX300/SRX320/SRX340/SRX345/SRX380), rebooting node0 with chassis cluster enabled causes the High Availability (HA) control link to establish after the initial hold timer expires. As a result, node0 assumes the primary role unexpectedly, leading to a split-brain condition where both nodes operate as primary.
PR Number	Synopsis	Category: SRX-1RU platfom datapath SW defects
1842873 Minor	Load balance hash-key forwarding persists when switching to Layer 3-only Product-Group=junos Severity=Minor	On Junos SRX4600, SRX1600, SRX2300 and SRX4300 platforms, when switching load balance from L3+L4 to L3, hash-key forwarding fails; the device retains L3+L4.
PR Number	Synopsis	Category: SRX-1RU platfom related protocol, QoS, filtering features et
1641517 Minor	Multiple J-UKERN core files might be generated during the sanity test Product-Group=junos Severity=Minor	On SRX4600 platform, the CPU may overrun while performing sanity check due to incompatibility issues between ukern scheduler and Linux driver which might lead to traffic loss.
1837840 Major	Incorrect color-aware srTCM marking with yellow packet loss priority Product-Group=junos Severity=Major	There was a software side limitation on the highest CBS that can be configured for MPCs that have LU type lookup chips due to a hardware PR. The Hardware PR was resolved in MX240/ MX480/ MX960/ MX2008/ MX2010/ MX2020/ MX10003/ MX10008/MX10016/EX9200/EX9204/EX9208/EX9214/EX9251/EX9253/SRX5400/SRX5600/SRX5800 platforms, but the software-side limitation was not removed for the same. Due to this limitation, whenever the CBS was configured above its limit (earlier 33m), the low-level parameters used to get configured such that the packets would not have any credits available, resulting in them getting marked as RED.
PR Number	Synopsis	Category: Trio pfe bridging, learning, stp, oam, irb software
1856573 Minor	The 'show snmp mib walk jnxMac' shows incorrect entries and VLAN ID to be 0 Product-Group=junos Severity=Minor	On all MX platforms having MPC10E, MPC11E, LC9600 and MX304, when the SNMP query is run using the command "show snmp mib walk jnxMac" . The output of jnxMacStatsEntry provides statistics from one of logical unit only even if there are multiple logical units configured and the VLAN ID information shows up as "0", instead of the actual VLAN ID. This is a display issue with no impact.
1865605 Critical	ARP packet drops seen if proxy-arp restricted is configured on an IRB interface. Product-Group=junos Severity=Critical	On the Junos MX and EX9K platforms, when a Bridge Domain(BD) is configured with an integrated Routing and Bridging(IRB) interface that has proxy ARP set to restricted mode, the switch forwards ARP requests only to the Routing Engine(RE) without broadcasting them across the VLAN. Thus, impacting the hosts within the same VLAN.
1874503 Major	An IPv6 neighbor solicitation packet is dropped at the ingress PE router when it is received with more than two VLAN tags. Product-Group=junos Severity=Major	On Junos platforms having 'arp-supression' suppression enbabled, when IPV6 neighbor solicitation packets are received with more than two tags in an EVPN (EThernet Virtual Private Network) instance, the NDP (Neighbour Discovery Protocol) packets that are suppressed to the host path are incorrectly processed through a wrong DDOS policer, as the hop-limit value from the IPV6 header is not properly retrieved, causing them to be dropped by the packet forwarding engine.
PR Number	Synopsis	Category: Trio pfe l3 forwarding issues
1841876 Major	Q-in-Q transit traffic will be lost when Tag Protocol ID (TPID) is different than 0x8100 Product-Group=junos Severity=Major	In different MX series routers references, when Q-in-Q is configured with outer Vlan Tag protocol ID (TPID) different than 0x8100, the traffic is lost and will not find its destination.
1858741 Minor	IPv6 link cannot be used for around 10 seconds after DAD finishing due to NS delay. Product-Group=junos Severity=Minor	If both IPv4/IPv6 addresses are configured and both IPv4/IPv6 traffic is sent, there may be a 10 second delay in NS completion. This may occur when the egress interface is disabled/enabled and triggers NH resolution.
1861238 Major	[MX] IPv6 Inline Distributed BFD sessions for ISIS fail to establish after applying CoS transmit-rate rate-limit configuration. Product-Group=junos Severity=Major	On MX platforms with Trio-based line cards (MPC1-9), the IPv6 BFD (Bidirectional Forwarding Detection) sessions for ISIS over link-local addresses working in Distributed Inline mode may not come up when transmit-rate rate-limit is configured under class-of-services.
1864237 Critical	Observing out-of-order packets when the TCP traffic gets passed over AE bundle and tunnelled via MPLSoUDP tunnel Product-Group=junos Severity=Critical	On Junos OS platforms, When "dynamic tunnels" configured and "set chassis loopback-dynamic-tunnel" knob is used and when TCP (Transmission Control Protocol) traffic passed via MPLSoUDP (Multi-Protocol Label Switching Over User Datagram Protocol) tunnel through an outgoing AE (Aggregated Ethernet) bundle interface having member interfaces, use of either inner or outer header hash calculations lead to out-of-order packets at the egress. It causes service impact on related flow of traffic due to out-of-order packets.
PR Number	Synopsis	Category: Configuration mgmt, ffp, load-action, commit processing
1829886 Major	Commit error check-out failed does not get triggered when a complete bridge-domain is configured in instance-type vrf. Product-Group=junos Severity=Major	Commit error check-out failed does not get triggered when a complete bridge-domain is configured in instance-type vrf.
1839362 Minor	The commit error is seen in backup RE on MX platforms Product-Group=junos Severity=Minor	On all MX platforms, the commit fails in Backup RE during configuration commit where "fast-synchronise" and "graceful-switchover" are being committed together.
PR Number	Synopsis	Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1854070 Minor	cli coredump genarated when the size of buffer area (user input) increased to 1GB Product-Group=junos Severity=Minor	Cli coredump genarated when the size of buffer area (user input) increased to 1GB.
1861063 Critical	Unexpected issues such as login failures or disabled interfaces observed following abrupt reboot during commit operation Product-Group=junos Severity=Critical	On Junos platforms with boot-time optimization enabled, an abrupt reboot during a commit operation can cause configuration file corruption, potentially leading to issues like login failures or disabled interfaces.
PR Number	Synopsis	Category: web filterig issues
1854519 Major	FPC crashing when web filtering type set to "juniper-enhanced" or "NG-juniper" Product-Group=junos Severity=Major	On all SRX platforms, when the web-filtering type set to "juniper-enhanced" or "NG-juniper" (NextGen-juniper), it might cause FPC (Flexible Port Concentrator) card crash and with "srxpfe" or "lcore" crash files generated.
PR Number	Synopsis	Category: VMHOST platforms software
1856565 Minor	High memory consumption in VMhost causes FPC reboot Product-Group=junosvae Severity=Minor	On all VMhost based platforms, excessive file accumulation in the /var/tmp directory of the host side triggers FPC reboots, resulting in network traffic disruption. This condition occurs when available space falls below 65% (usage exceeds 35%).
PR Number	Synopsis	Category: VSRX platform software
1855010 Minor	Split brain scenario is observed on vSRX3.0 with public cloud MNHA deployment Product-Group=junos Severity=Minor	On vSRX3.0 platforms with public cloud (Azure/AWS/GCP) MNHA (Multinode High Availability) setup when manually failed over, split brain scenario will be observed.
PR Number	Synopsis	Category: Track Windriver Linux issues
1631579 Critical	A few line cards will be stuck in the 'Present' state and later go 'Offline' Product-Group=junos Severity=Critical	A system equipped with specific line cards, the line cards will be stuck in the 'Present' state and later go 'Offline' after the line card or router is rebooted. Ideally, the Line Card should go 'Online' instead it goes 'Offline'.
PR Number	Synopsis	Category: usf nat related issues
1841231 Minor	PCP mapping fails for specific internal IPv4 addresses in DS-lite scenario Product-Group=junos Severity=Minor	On MX240, MX480 and MX960 with Unified-Services Framework (USF) and Dual-stack lite (DS-lite) enabled, Port Control Protocol (PCP) mapping fails for any internal IPv4 with fourth octet greater than ".223".

Extended Solution

23.4R2-S5 - List of Known issues

PR Number	Synopsis	Category: EX2300/3400 PFE
1878355 Minor	dhcp-snoop routes are not installed when IPSG group is full Product-Group=junos	dhcp-snoop routes are not installed when IPSG group is full when IPv4/v6 source guard is enabled along with DAI/NDI. When dhcp snooping binding entries exceed 512, even new bindings show up in the binding table, the dhcp-snoop route is not installed in HW. New bindings will be dropped due to DAI/NDI. This behavior is expected. As we are running out of space of FP entries in HW, routes are NOT installed beyond the scale. IPv4 and IPv6 uses the same VFP in HW. switch> request pfe execute command "show filter hw groups" target fpc0 Unit:0 Group Information: > VFP groups: Dynamic group id: 1. Pipe: 0 Entries: 1 Total_available: 512 Pri: 0 Def Entries: 0 VFP group for COS id: 143. Pipe: 0 Entries: 7 Total_available: 512 Pri: 2 Def Entries: 0 VFP group for DYN IPSG group id: 391. Pipe: 0 Entries: 512 Total_available: 512 Pri: 3 Def Entries: 0 <--- full group with 512 entries Resolved In:
PR Number	Synopsis	Category: NFX Series Platform Software
1850987 Major	INSIGHTD messages logged every 5 seconds on NFX 250 Product-Group=junos	INSIGHTD messages logged every 5 seconds on NFX 250, these are harmless and can be hidden from syslog. jinsightd[19158]: JINSIGHTD_SENSOR_RESUBSCRIPTION: RetrySubscription: Triggering Re-subscription. retry_count 40005 jinsightd[19158]: JINSIGHTD_SENSOR_RESUBSCRIPTION: RetrySubscription: Triggering Re-subscription. retry_count 40006 Resolved In: junos:24.2R2-S2 junos:24.4R2 junos:25.2R1 junos:25.3R1
PR Number	Synopsis	Category: SRX Fleming L2NG platform support
1868103 Minor	CoS shaping is not functional on IRB interfaces when the SRX1600 is in switching mode Product-Group=junos	On SRX1600 platform, Class of Service (CoS) shaping does not work on IRB (Integrated Routing and Bridging) interfaces. Resolved In: junos:24.2R2-S1 junos:24.4R2 junos:25.2R1 junos:25.3R1
PR Number	Synopsis	Category: "agentd" software daemon
1873990 Major	EX9208: Syslog message 'JINSIGHTD_SENSOR_RESUBSCRIPTION' every 5 sec Product-Group=junos	On EX9200 series switch, syslog message 'JINSIGHTD_SENSOR_RESUBSCRIPTION' is seen every 5 sec Resolved In: evo:25.2R1-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:24.2R2-S2 junos:25.2R1 junos:25.2R2 junos:25.3R1
PR Number	Synopsis	Category: firewall filter for australia platform
1871431 Minor	Protocols involved with TCP/IP on a lsi interface have issues as TCP 3-way handshake cannot be completed Product-Group=junos	On all SRX platforms, when a firewall filter is attached to a logical tunnel interface or a virtual routing instance to perform selective packet mode, it causes TCP packets on lsi interface to be discarded due to the TCP 3-way handshake is not established. Resolved In: junos:24.2R2-S2 junos:24.4R2 junos:25.2R1 junos:25.3R1
PR Number	Synopsis	Category: Border Gateway Protocol
1861799 Major	The "advertise-inactive" configuration does not work as expected when "add-path multipath" is configured and negotiated with the neighbor Product-Group=junos	On all Junos and Junos Evolved platforms with "advertise-inactive" configured under Border Gateway Protocol (BGP), inactive routes are not advertised to peers when "add-path multipath" is configured and negotiated with the neighbor. Resolved In: evo:22.3X50-EVO evo:22.3X50-J3-EVO evo:25.2R1-EVO junos:20.3X75-D52 junos:25.2R1
1877111 Major	The Aggregate-Bandwidth feature inconsistency on BGP Route Reflectors with VRF L3VPN Multipath Product-Group=junos	On all Junos and Junos Evolved platforms, the aggregate-bandwidth feature does not function as expected with the device configured as a BGP (Border Gateway Protocol) Route Reflector (RR). This issue is observed specifically in scenarios involving BGP multipath bandwidth aggregation for routes originating from VRF (Virtual Routing and Forwarding) instances under the L3VPN (Layer 3 Virtual Private Network) address family. Resolved In: evo:23.4X100-D40-EVO evo:25.2R1-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:25.2R1 junos:25.2R2 junos:25.3R1
1877332 Major	EBGP MULTIPATH is not set on ACTIVE route Product-Group=junos	On Junos platforms, in BGP multipath scenario, it is observed that due to a software issue, the forwarding table does not show multipath next-hop for newly added route in case of high number of next-hop. Resolved In: evo:25.2R1-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:23.2R2-S5 junos:25.2R1 junos:25.2R2 junos:25.3R1
PR Number	Synopsis	Category: OpenSSH and related subsystems
1872685 Minor	vmhost software upgrade failure if [ssh hostkey-algorithm-list ecdsa-sha2-nistp<>" is configured Product-Group=junos	With respect to the VMHOST platforms while upgrading between the JUNOS releases, please always ensure that one of the hostkey-algorithms exist in the configuration if [ssh hostkey-algorithm-list] has to be used: rsa-sha2-512, rsa-sha2-256, ssh-rsa, ecdsa-sha2-nistp256, ssh-ed25519. Note: If this knob has not been configured at all, then that case is also fine. Resolved In:
PR Number	Synopsis	Category: Layer 3 forwarding, both v4+v6
1881742 Major	ACX5448/ACX710 50% Packet Loss with Explicit Null disabled for BGP-LU Labeled Routes in ECMP Scenarios Product-Group=junos	Transit traffic drop is observed for the BGP-LU route prefixes with ECMP forwarding path on Junos ACX5448/ACX710 platforms Resolved In: junos:23.4R2-S2-J16 junos:24.2R2-S2 junos:24.4R2 junos:25.2R2 junos:25.3R1
PR Number	Synopsis	Category: EVPN control plane issues
1796532 Major	EVPN mac-ip entry flag "Duplicate-Not-Best" not updated after deleting duplicated IRB IP in EVPN_VXLAN MAC-VRF Product-Group=junos	On all Junos and Junos Evolved platforms, duplicate mac-ip detection for IRB IP is not working since the IP move is not triggered after adding an IP address to the IRB interface. Resolved In: evo:23.4R2-S4-EVO evo:23.4X100-D30-EVO evo:24.2R1-EVO evo:24.3R1-EVO junos:23.4R2-S4 junos:24.2R1 junos:24.3R1
1816672 Minor	[Junos OS Evolved] LACP on non-DF ACX router comes out of "out-of-sync" state by deactivating one of the EVPN instances, causing CE device to move to Collecting distributing Product-Group=junos	There are multiple EVPN instances each having separate IFL of AE IFD. AE is configured with per-esi lacp-oos-on-ndf on the AE IFD. On deactivating one of the instances, LACP on non-DF router comes out of "out-of-sync" state, causing CE device to move to Collecting distributing. Resolved In: evo:23.2R2-S3-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:22.2R3-J14 junos:23.2R2-S3 junos:23.4R2-S4 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR Number	Synopsis	Category: EX4000 PFE issues
1847159 Major	Reachability issues are seen on interfaces that are aggregated without address-family Product-Group=junos	On Junos platforms, specifically on EX and QFX series aggregated interfaces configured without address-family results in reachability issues. Resolved In: junos:21.4R3-S10 junos:22.2R3-S7 junos:24.4R1 junos:24.4R1-S2 junos:24.4R2 junos:25.1R1 junos:25.2R1 junos:25.3R1
PR Number	Synopsis	Category: EX4100 Interface, Optics, MacSec, POE
1657766 Minor	On EX4100 in an interoperability scenario when using 1G SFP Optic on PIC-2, auto-negotiation should be disabled on the peer Product-Group=junos	EX4100-24mp, 48mp, 24p/t, 48p/t, F-24p/t, F-48-p/t: In an interop scenario, when using 1G SFP Optic on PIC-2, auto-negotiation should be disabled on the peer Resolved In:
PR Number	Synopsis	Category: EX interfaces issues
1580560 Major	On EX2300, EX3400, :EX4300-48MP and EX4300 , Pause frames counters does not get incremented when pause frames are sent. Product-Group=junos	On EX2300, EX3400, :EX4300-48MP and EX4300 , Pause frames counters does not get incremented when pause frames are sent. Resolved In:
1833177 Major	EX2300/EX3400 : The status LED of uplink port is not working properly Product-Group=junos	On EX2300 and EX3400, the status LED of uplink port always displays green regardless of the status of the link. Resolved In: junos:23.2R2-S5 junos:24.2R2-S2 junos:24.4R2 junos:25.2R1 junos:25.2R2 junos:25.3R1
PR Number	Synopsis	Category: EX4400 platform
1814463 Minor	EX4400: MIST: Wrong PSU state is updating in the mist Product-Group=junos	Unsupported PEM/PSU is shown as online (green)in the MIST Dashboard and the output of "show chassis environment" for that PSU shows the status as present/OK. No functional impact. Resolved In: junos:24.2R2 junos:24.4R1 junos:25.1R1
PR Number	Synopsis	Category: Express PFE CoS Features
1719956 Major	Convergence delay is seen when FPC is offlined under heavy traffic and scaled scenario Product-Group=junos	On Junos PTX3000, PTX5000, PTX10008, and PTX10016 routers, when the Flexible PIC Concentrator (FPC) is offlined with scale configuration and heavy traffic, a delay in convergence (into tens of minutes) is seen on all the live FPCs in the chassis other than the offlined one. This impacts traffic. Resolved In: evo:22.1R3-S3-EVO evo:22.3R3-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:18.2X75-D67 junos:20.3X75-D36 junos:20.3X75-D51 junos:21.2R3-S5-J4 junos:21.2R3-S5-J5 junos:21.2R3-S6 junos:21.3R3-S5 junos:21.4R3-S6 junos:22.1R3-S3 junos:22.2R3-S1 junos:22.3R2-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1-S1 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR Number	Synopsis	Category: Express PFE FW Features
1885906 Major	Unable to add the filter secondarymatch to the hardware Product-Group=junos	On QFX10K platform, only 4 secondary filter matches are supported per term. Ranged ttl match conditions can be configured, however, it takes up more resources as it needs to create entry for the range to match as well as the range to not match. For example, the filter installation in PFE will fail if there are 3 ranged ttl conditions in a single term. set firewall family inet filter FIREWALL_FILTER term TTL_INVALID from ttl 1-32 set firewall family inet filter FIREWALL_FILTER term TTL_INVALID from ttl 64-96 set firewall family inet filter FIREWALL_FILTER term TTL_INVALID from ttl 128-254 With only 2 ranged ttl conditions, there will be no problem with PFE filter installation. Resolved In:
PR Number	Synopsis	Category: SRX1500 platform software
1831955 Major	The SRX1500 drops the packet if MTU matches the MRU of the receiving device Product-Group=junos	On SRX1500 platforms, if the Maximum Transmission Unit (MTU) is configured to match the Maximum Receive Unit (MRU) of the receiving device, packet drops occur. This occurs because additional processing overhead increases the packet size beyond the MRU limit, causing the receiving device to drop the packets. Resolved In: junos:22.2R3-S7 junos:22.4R3-S7 junos:23.2R2-S4 junos:23.4R2-S5 junos:24.2R2-S1 junos:24.4R1-S3 junos:24.4R2 junos:25.2R1 junos:25.3R1
PR Number	Synopsis	Category: Kernel software for AE/AS/Container
1762490 Minor	JDI-RCT-MPC10E: Ksyncd crash on backup RE after fpc reboot Product-Group=junos	On MX series, when PS over RLT is configured where all member LTs are hosted on the same FPC and user restarts this FPC then on rare occasion, ksyncd crash can occur on backup RE. However, there is no impact on the master and only backup RE is affected. This issue is not consistent and seen only once out of ~10 or 15 fpc restart operations. Resolved In: evo:24.4R2-EVO evo:25.2R1-EVO junos:24.4R2 junos:25.1R1 junos:25.2R1
PR Number	Synopsis	Category: jdhcpd daemon
1714260 Major	The DHCPv4 relay will send two option-82 to the server and the DHCP session will not be established Product-Group=junos	On all Junos and Junos OS Evolved platforms, when Dynamic Host Configuration Protocol (DHCPv4) Relay is configured with forward-only mode along with "trust-option-82", DHCP-relay should not add another option 82 to the packet sent to the DHCP server. The DHCP server upon receiving the packet with two option-82 will respond only with 1st header of option-82 which might get dropped by the relay, thus the packet is not forwarded to the DHCP client and the DHCP session won't get established. Resolved In: evo:21.3R3-S5-EVO evo:21.4R3-S4-EVO evo:22.2R3-S1-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO evo:23.4R2-S4-EVO junos:21.2R3-S5 junos:21.3R3-S4 junos:21.4R3-S2-J10 junos:21.4R3-S4 junos:22.1R3-S2 junos:22.2R3-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
1769598 Major	The jdhcpd prcoess crash will be observed due to double free of memory allocation when DHCP ALQ is configured Product-Group=junos	On MX platforms , when DHCP ALQ ( Dynamic Host Configuration Protocol Active Lease Query ) is configured and subscriber management is enabled, the jdhcpd process crash will be observed due to double free of memory allocation. The DHCP services will be down and it will restore once jdhcpd process is restarted. Resolved In: junos:21.2R3-S9 junos:21.4R3-S6 junos:22.1R3-S6 junos:22.2R3-S3 junos:22.3R3-S3 junos:22.4R3-S1 junos:23.2R2 junos:23.4R2 junos:24.1R1 junos:24.2R1
PR Number	Synopsis	Category: Juniper Device Manager VM Mgmt and infrastructure function
1774177 Critical	Performance degradation on NFX platform running WRL LTS19 Product-Group=junos	Degradation on all NFX platform running Wind River Linux (WRL) Long Term Support (LTS) 19, due to several components in LTS19 taking up more CPU/memory and reducing performance. Resolved In:
PR Number	Synopsis	Category: Flow Module
1847419 Minor	Type 5 VXLAN traffic drops are observed when SRX run as L3-VNI gateway and the ingress and egress traffic goes to the same Type-5 VXLAN peer Product-Group=junos	On Junos OS SRX platforms running as L3-VNI (Layer 3 - Virtual Network Identifier) gateway in EVPN-VxLAN (Ethernet Virtual Private Network - Virtual Extensible LAN) scenario, traffic drops will be observed if traffic passes through two VxLAN tunnels and traffic fails to cross the two VxLAN tunnels when the PFE (Packet Forwarding Engine) is processing the packet having same remote IPs for two VXLAN tunnels. Resolved In: junos:23.2R2-S2-J8 junos:23.2R2-S4 junos:24.4R2 junos:24.4R2-S1 junos:25.1R1 junos:25.2R1 junos:25.3R1
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:24.2R2-S2 junos:25.3R1
PR Number	Synopsis	Category: authd (AAA) library code
1860913 Major	The authd process crashes when /etc/resolv.conf file is empty Product-Group=junos	On Junos OS Evolved ACX platforms, when DHCP (Dynamic Host Control Protocol) local server is configured and the /etc/resolv.conf file is empty with no data/domain information the authd process crash observed. There will be no forwarding traffic impact due this issue and there will be no issue to existing sessions. However, new sessions will have login issue. Resolved In: evo:23.4R2-S5-EVO evo:24.2R2-S2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:23.2R2-S5 junos:24.2R2-S2 junos:25.2R1 junos:25.3R1
PR Number	Synopsis	Category: SW PRs for MPC10E PMB
1731258 Major	MPC10 and MPC11 line cards experiencing unexpected reboots Product-Group=junos	Line cards such as MPC10 and MPC11 experience unexpected reboots because of CPU C-states which are enabled by default thus impacting the customer production traffic. Resolved In: evo:23.4R2-EVO evo:24.1R1-EVO junos:20.3X75-D441 junos:20.3X75-D46 junos:20.3X75-D52 junos:21.4R3-S7 junos:22.2R3-S4 junos:22.2R3-S5 junos:22.4R3 junos:22.4R3-S1 junos:22.4R3-S2 junos:23.2R2 junos:23.4R2 junos:24.1R1
PR Number	Synopsis	Category: Multicast Routing
1876458 Major	MX960 mcsnoopd core dump during rt_mcnh_nh_release Product-Group=junos	The root cause is, when the system comes up after reboot, in MCSNOOPD (/usr/sbin/mcsnoopd used for L2 multicast), the lsi interfaces are learned. In MCSNOOPD, when there are 4 lsi interfaces learned, we create a nexthop(assume VE NH1) with all these 4 lsi as members and we use it in the routes for forwarding the traffic. When MCSNOOPD learns 5th lsi interface, as per internal NH(nexthop) allocation logic, we allocate a new nh(assume VE NH2) containing all these 5 lsi interfaces and free the old NH(VE NH1). The old freed NH(VE NH1) is accessed and tried to be freed again in another part of the code flow which is causing MCSNOOPD core(/usr/sbin/mcsnoopd). The fix is to free the old NH(VE NH1) in a common place instead of freeing in multiple places. Resolved In: evo:22.4R3-S8-EVO evo:24.2R2-S2-EVO evo:24.4R2-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:23.2R2-S5 junos:24.2R2-S2 junos:24.4R2 junos:25.2R2 junos:25.3R1
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
PR Number	Synopsis	Category: OSPF routing protocol
1827435 Major	OSPF LSA flooding is impacted after database recovers from 'ignore' state when 'database-protection' is triggered Product-Group=junos	On all Junos and Junos OS Evolved platforms, when the LSA (Link State Advertisement) count exceeds the maximum number configured under 'database-protection' feature in OSPFV2 (Open Shortest Path First Version 2), the OSPF database (DB) enters into 'ignore' state. When the DB is recovered, OSPF LSA flooding is stopped on some interfaces. Resolved In: evo:24.2R2-EVO evo:24.4R1-EVO junos:21.2R3-S9 junos:22.2R3-S5 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR Number	Synopsis	Category: QFX EVPN / VxLAN
1856424 Major	The dcpfe process crashes on specific Junos QFX and EX platforms due to memory corruption Product-Group=junos	A memory corruption issue can result random dcpfe (dense concentrator packet forwarding engine) process crashes on specific Junos QFX and EX platforms configured with VXLAN (Virtual Extensible Local Area Network) configuration. Resolved In:
PR Number	Synopsis	Category: QFX5K JUNOS Interface, MACSec, Optics, SDK, PHY
1867979 Critical	cuc_3617: Qfx5120-48y-VC: After performing split and make of VC , BUM traffic on FPC1 is getting replicated more than expected . Product-Group=junos	Problem: Performing VC split and Merge operation causes traffic to be affected for Broadcast, Unknown-unicast and Multicast traffic. RCA: When the Link is Brought down, each FPC will try to re-synchronize the IFDs, in addition resources are busy with updating for the new role. This can cause some synchronization issues with for IFDs/IFLs and other such lists. Test: This can be seen by the VTY command "show ifd brief" and "show ifl brief" for all the FPCs Workaround: It is recommended to wait at least 240 seconds after Splitting the VC ad merging it back again. This ensures that the system can get enough time to synchronize the IFDs/IFLs etc. from the kernel. Resolved In:
PR Number	Synopsis	Category: QFX5200/5110/5120/5210 Platform optics related issues
1847904 Major	CTLE Values mismatch for 100G-BASE-SR4/100G-BASE-SR4-T2 in QFX5120-48T Product-Group=junosvae	The CTLE for 100G-BASE-SR4/100G-BASE-SR4-T2 is set wrong value on QFX5120-48T platform. Resolved In: junos:22.2R3-S7 junos:24.4R2 junos:25.2R1
PR Number	Synopsis	Category: QFX5200/5110/5120/5210 Platfom issues
1758400 Major	JUNOS_REG: QFX51200-48YM: Fan status output was not same after/before device vc-switch over. Product-Group=junos	In a QFX51200-48YM-8C VC setup, after a a mastership switch over fan tray of linecard may not be displayed in show chassis hardware and show chassis environment. There is no functional impact Resolved In:
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	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. Resolved In: evo:23.4R2-S5-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:24.4R2 junos:25.2R1 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
PR Number	Synopsis	Category: RPD route tables, resolver, routing instances, static routes
1840635 Major	Vmhost upgrade fails due to vrf instance validation error Product-Group=junos	During vmhost image upgrades on Junos PTX10008/PTX10016 routers running Junos 22.4R3 and above versions, when more than two VRF(Virtual Routing and Forwarding) instances are configured, the configuration validation fails with the "RT Instance: Maximum 2 vrf instances are supported" error. This impacts the vmhost image upgrade on the device. via CLI when using the "request vmhost software add reboot" command. Resolved In: junos:20.3X75-D36
PR Number	Synopsis	Category: show route table commands, tracing, and syslog facilities
1757389 Minor	"show route detail" shows "State: " for routes when route-record is enabled Product-Group=junos	On all Junos and Junos OS Evolved platforms with route-record enabled, some routes will be seen in State: due to race condition. There is no functionality issue, this is a display issue. Resolved In: evo:22.4R3-EVO evo:22.4R3-S1-EVO evo:23.2R1-S2-EVO evo:23.2R2-EVO evo:23.4R1-S1-EVO evo:24.1R1-EVO evo:24.4R2-EVO junos:23.2R1-S2 junos:23.2R2-J14 junos:23.4R1-S1 junos:24.1R1
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	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. Resolved In: evo:22.4R3-S7-EVO evo:23.2R2-S4-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:22.4R3-S7 junos:23.2R2-S4 junos:24.4R2 junos:25.2R1 junos:25.3R1
PR Number	Synopsis	Category: Bug and Review Tracking for Segment routing traffic eng
1840503 Major	Tactical Traffic Engineered load sharing utilization displays incorrect percentage on MX platforms Product-Group=junos	On MX platforms is configured with SRv6 (Segment Routing) along that Tactical Traffic Engineered(TTE) load sharing is enabled for SRv6, in some circumstances, TTE value displays percentage in 10 digit ( example 8889140224.00% ) when executing "show congestion-protection interface detail". It does not cause any traffic impact. Resolved In: evo:24.4R2-EVO evo:25.2R1-EVO junos:24.4R1-S2 junos:24.4R2 junos:25.2R1
PR Number	Synopsis	Category: MPC7E, MPC8E and MPC9E timing and synchronization
1830281 Major	Sourceport-ID comparison resulting in higher value for MPC7E compared to MPC5E for distributed PTP architecture Product-Group=junos	SourcePort-ID comparison across line cards between MPC7E and MPC5E/6E/3E-NG/2E-NG shall result in selecting MPC5E/6E/3E-NG/2E-NG compared to MPC7E/8E/9E/10E. Resolved In: evo:24.2R2-EVO evo:24.4R1-EVO evo:25.1R1-EVO junos:21.2R3-S9 junos:21.4R3-S10 junos:24.2R2 junos:24.4R1 junos:25.1R1
PR Number	Synopsis	Category: ZT/YT pfe firewall software
1848740 Critical	Support FW_Continue with HW Segmented Filters on AFT TRIO platform Product-Group=junos	This PR is a performance optimization PR for AFT Trio-based systems. Software Segmented Firewall enables FLT support for a maximum of 3584 terms, this PR adds support for HW segmented filter with support to up to a maximum of 8192 terms and better performance than the software segmented filters. Resolved In: evo:24.4R2-EVO evo:25.1R1-EVO evo:25.2R1-EVO junos:24.4R2 junos:25.1R1 junos:25.2R1
PR Number	Synopsis	Category: DDos Support on MX
1733477 Minor	Harmless logs "DDOS : Failed to insert flow to lkup map for proto: 3c00" observed in syslog Product-Group=junos	"Failed to insert flow to lkup map for proto: 3c00" messages reported repeatedly in the syslog/messages file without any functional impact. Resolved In: evo:21.4R3-S6-EVO evo:23.4R2-EVO evo:24.1R1-EVO junos:21.2R3-S9 junos:21.4R3-S7 junos:22.4R3-S2 junos:23.2R2 junos:23.4R2 junos:24.1R1
PR Number	Synopsis	Category: Authentication, Authorization, Accounting, PAM (RADIUS/tacplus)
1850776 Major	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:22.2R3-S6 junos:22.4R3-S6 junos:23.2R2-S3
PR Number	Synopsis	Category: Configuration management, ffp, load action
1854461 Major	TFTP server crashes when configuration to limit connections are not reflected Product-Group=junos	On all Junos and Junos Evolved platforms configured as Trivial File Transfer Protocol (TFTP) server , "connection-limit" or "rate-limit" values are not updated as per configured values and server crashes. Resolved In: evo:24.4R2-EVO evo:25.1R1-EVO evo:25.2R1-EVO junos:20.3X75-D442 junos:22.2R3-S7 junos:24.4R2 junos:25.1R1 junos:25.2R1
PR Number	Synopsis	Category: Configuration mgmt, ffp, load-action, commit processing
1751574 Major	Netconf RPC commit fails due to commit warning received for unprotect operation, CLI commit completes with warning Product-Group=junos	In Netconf private edit configuration session, commit RPC fails when unprotect operation is performed. Resolved In:
1818692 Major	Configuration commit fails due to mustd process crash Product-Group=junos	Core dumps in mustd seen commiting a change to a large prefix-list used by BGP Resolved In: evo:22.3R3-S4-EVO evo:22.3X50-EVO evo:22.3X80-D47-EVO evo:22.3X80-D49-EVO evo:22.4R3-S5-EVO evo:23.2R2-S3-EVO evo:23.4R2-S3-EVO evo:23.4X100-D20-EVO evo:24.2R2-EVO evo:24.4R1-EVO junos:21.2R3-S9 junos:21.2X32-D30 junos:21.4R3-S9 junos:22.2R3-S5 junos:22.3R3-S4 junos:22.4R3-S5 junos:23.2R2-S3 junos:23.4R2-S3 junos:24.2R1-S1 junos:24.2R2 junos:24.4R1
PR Number	Synopsis	Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1593200 Critical	Junos OS: A low privileged user can elevate their privileges to the ones of the highest privileged J-Web user logged in Product-Group=junos	A Generation of Error Message Containing Sensitive Information vulnerability in the CLI of Juniper Networks Junos OS allows a locally authenticated attacker with low privileges to elevate these to the level of any other user logged in via J-Web at this time, potential leading to a full compromise of the device. Refer to https://kb.juniper.net/JSA11270 [juniper.net] for more information. Resolved In: evo:21.1R2-S1-EVO evo:21.2R1-S2-EVO evo:21.2R2-EVO evo:21.2R3-EVO evo:21.3R1-EVO evo:21.3R2-EVO evo:21.4R1-EVO junos:15.1R7-S11 junos:18.3R3-S6 junos:18.4R2-S9 junos:18.4R3-S10 junos:19.1R2-S3 junos:19.1R3-S7 junos:19.2R1-S8 junos:19.2R3-S4 junos:19.3R3-S4 junos:19.4R3-S6 junos:20.1R3-S2 junos:20.2R3-S3 junos:20.3R3-S1 junos:20.3X75-D442 junos:20.4R3-S1 junos:21.1R2-S1 junos:21.1R3 junos:21.2R1-S1 junos:21.2R2 junos:21.2R3 junos:21.3R1 junos:21.3R2 junos:21.4R1
PR Number	Synopsis	Category: Issues related to NETCONF
1800859 Minor	Configuration push to device using RPC resulted in incorrect policy order Product-Group=junos	On all Junos and Junos OS Evolved platforms, RPC command with default-operation replace uses load update instead of load override from Junos 21.1 onwards. Policies could get incorrectly reordered impacting traffic, because load update does not honor the replace: tag present in configuration file loaded. Resolved In: evo:22.3X50-EVO evo:22.4R0-J0-EVO evo:22.4R3-S5-EVO evo:23.2R2-S3-EVO evo:23.4R2-S3-EVO evo:23.4X100-D20-EVO evo:24.2R1-S1-EVO evo:24.2R2-EVO evo:24.3R1-EVO junos:21.2R3-S9 junos:21.2X32-D30 junos:21.4R3-S9 junos:22.2R3-S7 junos:22.4R3-S5 junos:22.4R3-S7 junos:23.2R2-S3 junos:23.4R2-S3 junos:24.2R1-S1 junos:24.2R2 junos:24.3R1 junos:25.1R1
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: MX10K linecard
1784824 Major	[./sw-vale-mx-indus] [generic] MX10004 :: LC480 line card crashed with reference to posix_interface_abort () at ../src/pfe/platform/linux/posix_interface.c:2729 Product-Group=junos	n/a Resolved In: evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:23.2R2-S5 junos:24.4R2 junos:25.2R1 junos:25.3R1
PR Number	Synopsis	Category: VMHOST platforms software
1787608 Major	The chassisd crashes at first boot up after reboot Product-Group=junos	Additional logging has been added to the primry Routing Engine. This is to help narrow down the issue which chassisd process restarted unexpectedly at snmp_init_oids( ) function on the primary Routing Engine while booting up. Resolved In:
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.4R1

Modification History

2025-08-20 / 2025-09-16- Update the "Call to Action" section - warning about optic software issue. TSB101868 [juniper.net]

First publication 2025-06-24