Alert Type

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

Product Affected

See 23.4R2-S3-SRN - TSB91374 [juniper.net]

Alert Description

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

This Software Release Notification is for KNOWN ISSUES for Junos 23.4R2-S3

For the list of FIXED issues, please see TSB91374 [juniper.net]

Download Junos Software Service Release:

  1. Go to Junos Platforms - Download Software page
  2. Input your product in the "Find a Product" search box
  3. From the Type/OS drop-down menu, select Junos SR
  4. From the Version drop-down menu, select your version
  5. Click the Software tab
  6. Select the Install Package as needed and follow the prompts

NOTE: Starting August 30th, 2024, we include PR severity with each entry. See KB86335 [juniper.net] for the definition of PR's Severity

Solution

23.4R2-S3 - List of Known issues 

PR NumberSynopsisCategory: NFX Series Platform Software
1753117
Major		NFX: "request vmhost reboot disk" doesn't work sometimes when one partition has pre-23.4R1 image and the other has a 23.4R1 image installed
Product-Group=junos		NFX: "request vmhost reboot disk" doesn't work sometimes when one partition has pre-23.4R1 (Wind River 8 based) image version and the other has a 23.4R1 (Wind River LTS19 based) or later image version installed.

Resolved In:
PR NumberSynopsisCategory: access node control protocol daemon
1841954
Major		An Enhancement to 'show ancp subscriber detail' command to display port-up/down timestamp and port-down cause
Product-Group=junos		The "show ancp subscriber detail" command is enhanced to display the port-up / port-down timestamps and port-down cause. It's neither an issue nor a regression an additional display output to enhance debuggability.

Resolved In: evo:24.2R2-EVO evo:24.4R1-EVO evo:25.1R1-EVO junos:24.2R2 junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: Border Gateway Protocol
1826686
Major		Traffic impact due to BGP route stuck in hidden state
Product-Group=junos		On all Junos and Junos Evolved platforms, with BMP (BGP Monitoring Protocol) 'exclude-non-eligible' configured, the BGP route gets stuck in a hidden state with the next hop state as 'Next hop type unusable' leading to traffic drop.

Resolved In: evo:22.4R3-S5-EVO evo:23.2R2-S3-EVO evo:23.4R2-S3-EVO evo:24.2R2-EVO evo:24.4R1-EVO evo:25.1R1-EVO junos:20.3X75-D441 junos:20.3X75-D52 junos:21.2R3-S9 junos:22.4R3-S5 junos:23.2R2-S3 junos:24.2R2 junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: Track PRs in BGP BMP area & is part of BGP inside RPD.
1819305
Critical		BMP gets stuck and does not send data to BMP collector
Product-Group=junos		On all Junos OS and Junos OS Evolved platforms which supports BMP (BGP Monitoring Protocol), the BMP session stop sending data to an BMP Station. Please refer to TSB83918 [juniper.net] for more details.

Resolved In: evo:21.4R3-S9-EVO evo:22.2R3-S5-EVO evo:22.3X50-EVO evo:22.4R2-S1-J10-EVO evo:22.4R3-S4-EVO evo:23.2R2-J13-EVO evo:23.2R2-S2-EVO evo:23.4R2-S3-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:21.2R3-S3-J32 junos:21.2R3-S9 junos:21.4R3-S9 junos:22.2R3-S5 junos:22.4R3-S2-J4 junos:22.4R3-S2-J5 junos:22.4R3-S4 junos:23.2R2-S2 junos:23.4R2-S1 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: MX Platform SW - FRU Management
1784438
Major		MX304 not reachable with the power-off failure on the PIC
Product-Group=junos		When an MX304 LMIC is offline due to a power issue, it may take up to 20 minutes for the LMIC to come back online. You can configure event-options to reduce the time to restart the LMIC. See also: TSB83899 [juniper.net]

Resolved In: evo:23.2R2-S2-EVO evo:24.2R1-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:22.2R3-S5 junos:22.4R3-S4 junos:23.2R2-J15 junos:23.2R2-S2 junos:23.4R2-S1 junos:24.2R1 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: EX interfaces issues
1793137
Major		Interfaces down with LOCAL-FAULT alarm after power cycle
Product-Group=junos		On EX4100-48T, EX4100-48P, EX4100-48MP, and EX4100-24MP platforms, after a power cycle, the uplink interfaces may go down with a LOCAL-FAULT alarm. This issue is caused by an anomaly in the Broadcom PHY (bcm82756) third-party SDK code used on these devices.

Resolved In: junos:24.3R1
PR NumberSynopsisCategory: idp flow creation, deletion, notification, session mgr intfce
1826377
Critical		Memory leak will be observed on all SRX platforms when IDP is configured
Product-Group=junos		On SRX platforms with IDP (Intrusion Detection and Prevention) enabled, while processing IDP traffic a memory leak can occur which would lead to regular flow processing being affected as memory depletes eventually. This issue affects the following Junos releases: 21.2R3-S8, 21.4R3-S7/8, 22.2R3-S3/4, 22.3R3-S3, 22.4R3-S2/3, 23.2R2, 23.2R2-S1 and 24.2R1. All other releases are not affected by this issue.

Resolved In: junos:21.2R3-S9 junos:21.4R3-S7-J6 junos:21.4R3-S7-J7 junos:21.4R3-S9 junos:22.2R3-S5 junos:22.3R3-S4 junos:22.4R3-S4 junos:23.2R2-S2 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: MX Inline Jflow
1444849
Major		Sampling applications like port-mirror and inline-jflow are not supported on VPLS tunnel interfaces in ingress direction where ingress packets are sent to the IRB interface for routing. Configuration of sampling application on VPLS tunnel interfaces in such scenario causes packet to drop in ingress direction.
Product-Group=junos		Sampling applications like port-mirror and inline-jflow are not supported on VPLS tunnel interfaces in ingress direction where ingress packets are sent to the IRB interface for routing. Configuration of sampling application on VPLS tunnel interfaces in such scenario causes packet to drop in ingress direction.

Resolved In:
PR NumberSynopsisCategory: Integrated Routing & Bridging (IRB) module
1815250
Major		ARP resolution issues might happen when VxLAN and non-VxLAN are both configured on the same ifd but different ifl
Product-Group=junos		Due to a conflict in the config between the VXLAN (Virtual Extensible LAN) hardware token and the VLAN (Virtual Local Area Network) traffic loss could happen as consequence of wrong path for ARP (Address Resolution Protocol)

Resolved In: junos:24.2R2 junos:24.4R1
1827648
Major		ARP not learned on Switch Leading to Traffic Drop in EVPN-VXLAN Setup
Product-Group=junos		On all Junos QFX series platforms in an EVPN (Ethernet Virtual Private Network) VXLAN (Virtual Extensible Local Area Network) setup with CRB (Centralized Routing Bridge) architecture, ARP packets are not being learned, leading to traffic forwarding issues. This problem arises when ARP packets are sent from the firewall to the spine switches. The issue is linked to IRB (Integrated Routing and Bridging) handling and bridge domain re-incarnation, which triggers ARP request failures and impacts L3 forwarding.

Resolved In: junos:22.2R3-S5 junos:24.2R2 junos:24.3R1 junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: 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 NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1820882
Major		Traffic drop is seen in an EVPN multihoming scenario when mac-pinning is enabled
Product-Group=junos		On all Junos and Junos Evolved platforms, in Ethernet VPN (EVPN) multihoming scenario with mac-pinning enabled, traffic drop will be seen when the Designated Forwarder role (DF) is changed.

Resolved In: evo:21.4R3-S10-EVO evo:23.4X100-D20-EVO evo:24.2R2-EVO evo:24.4R1-EVO junos:21.2R3-S9 junos:21.4R3-S10 junos:21.4R3-S8-J1 junos:21.4R3-S9-J1 junos:23.2R1-S2-J7 junos:24.2R1-S1-J3 junos:24.2R2 junos:24.4R1
PR NumberSynopsisCategory: lldp sw on MX platform
1811545
Major		The LLDP neighborship does not recover on AE interfaces
Product-Group=junos		When LLDP is configured on interface all and there are AE interfaces configured, to disable LLDP on one of the AE "set protocols lldp interface is done". To enable it back when rollback is done for reverting disable config, AE is not participating in LLDP neighborship and this happening because PFE stopped sending packets to control plane because on rollback L2CPD did not sent LLDP ENABLE for its child interface to PFE and LLDP on child interface was still set to disabled for PFE.

Resolved In: evo:22.3X50-EVO evo:22.4R3-S6-EVO evo:23.2R2-S3-EVO evo:23.4R2-EVO evo:24.2R1-S2-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:21.2R3-S7-J17 junos:21.2R3-S8-J2 junos:22.4R3-S6 junos:24.2R1-S2 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: MPC11 ULC fabric software related issues.
1812046
Minor		On MX2K, offline manually SFB2 or SFB3 or Plane to recover from a fabric link training failure, fabric mananger is not able to turn off the fabric links on a neighbor slot FPC
Product-Group=junos		Once SFB2 or SFB3 or plane is manually offline in an attempt to recover from a Fabric Training Failure of one FPC, the neighbor slot FPC is not be able to stop the high speed link and is ending up with training failure as well.

Resolved In: junos:21.2R3-S9 junos:22.2R3-S3-J3 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: Multiprotocol Label Switching
1814358
Major		LSP keep retrying over the transit router marked as "overload" resulting in traffic drops or using the suboptimal path for the LSP
Product-Group=junos		On Junos and Junos Evolved platforms with RSVP-TE (Reservation Protocol-Traffic Engineering) configured, when IGP (Interior Gateway Protocol) "overload" is configured on the transit router, the traffic should move away from the transit router. But in the issue scenario, the LSP (Label Switched Path) continues to stay across the transit router which has been marked as overload and traffic continues across the transit router resulting in traffic drops or using the suboptimal path for the LSP. The issue happens when Patherr is received for the re-optimized path and CSPF (Constrained Shortest Path First) computation is triggered before the backoff timer.

Resolved In: evo:22.3X50-EVO evo:22.4R3-S5-EVO evo:23.2R2-S3-EVO evo:23.4R2-S3-EVO evo:24.2R2-EVO evo:24.4R1-EVO junos:20.3X75-D52 junos:22.4R3-S5 junos:23.2R2-S3 junos:24.2R2 junos:24.4R1
PR NumberSynopsisCategory: Path computation client daemon
1823220
Major		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		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.

Resolved In: evo:23.2R2-S3-EVO evo:24.2R2-EVO evo:24.4R1-EVO junos:24.2R2 junos:24.4R1
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platform optics related issues
1810740
Major		Link wont come up on bounce of fec91 on QFX5120 platform
Product-Group=junos		On QFX5120-48T, Interface links are not coming up at DUT after restoring the FEC configuration from mistmatched FEC configuration at non-dut.

Resolved In: junos:24.2R2 junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: RPD policy options
1832853
Major		Commit delay will be observed when the configuration is changed for the logical system
Product-Group=junos		On all Junos and Junos Evolved Platforms, whenever the configuration is changed for the logical system, a commit delay of >30 seconds will be observed in the subsequent configuration commit in the logical system.

Resolved In: evo:25.1R1-EVO junos:24.2R2 junos:25.1R1
PR NumberSynopsisCategory: SRX RTCOM module bugs
1814271
Major		The srpfe crash during SAV longevity testing
Product-Group=junos		On SRX platforms, when Sophos antivirus (SAV) was enabled srpfe crash was observed. If a new packet tries to access the memory before it gets free, it may lead to the race condition, where it tries to fetch a null memory. The issue is hardly reproducible.

Resolved In: junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: SRX-1RU infrastructure SW defects
1839346
Major		Following ISSU on SRX4600, the SPM may no longer be operational
Product-Group=junos		After performing an ISSU upgrade from an SRX4600 platform, the SPM (fpc 0) against the node that was upgraded first may experience issue states where it can either cycle through Present or Offline or it will not report any errors but will be unable to perform any PFE (packet forwarding engine) functions such as session management.

Resolved In: junos:21.4R3-S10 junos:24.2R2 junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: ZT/YT pfe firewall software
1793044
Major		ASIC-level memory leak occurs and error messages are displayed when when changing or deleting fast-lookup-filters (FLT filters) interface-specific filter.
Product-Group=junos		On MX platforms with MPC10, MPC11, LC9600 and MX304 platform, the ASIC-level memory leak occurs and error messages are displayed while configuring (deleting or changing) interface-specific filters with a fast-lookup-filter knob.

Resolved In: evo:24.1R2-EVO evo:24.2R1-EVO evo:24.3R1-EVO junos:24.1R2 junos:24.2R1 junos:24.3R1
PR NumberSynopsisCategory: Track Windriver Linux issues
1807939
Minor		[MX] daemon.err rshd[618008]: Second port outside reserved range.
Product-Group=junos		RE uses enhanced mode RCMD protocol to communicate with the FPCs, by default. However, the FPC line cards do not understand the enhanced mode rcmd protocol. Hence the below logs generated. daemon.err rshd[618008]: Second port outside reserved range. After the failure, the communication falls back to the normal mode from enhanced mode.There is no production impact due to this issue. The fix has been implemented in the resolved versions, wherein the communication between RE and the FPC will now happen through the normal mode by default.

Resolved In: evo:23.4R2-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO evo:25.1R1-EVO junos:23.4R2 junos:24.2R2 junos:24.3R1 junos:24.4R1 junos:25.1R1

 

Modification History

First published 2025-01-23