23.4R2-S2: Software Release Notification for JUNOS Software

Alert Type

PCN - Product Change Notification

RiskRisk Description

Low/Notification

Software Release Notification

ImpactImpact Description

Low/Notification

Software Release Notification

Product Affected

ACX EX MX NFX PTX QFX SRX vSRX

Alert Description

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

Solution

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

23.4R2-S2 - List of Fixed issues

PR Number	Synopsis	Category: Dynamic rendering infrastructure
1745615	Telemetry data is not exported in an IS-IS scaled Segment Routing scenario Product-Group=junos Severity=Major	On all Junos and Junos OS Evolved platforms configured with SR-ISIS and with gRPC/gNMI telemetry, subscription to the path: "/junos/services/segment-routing/sid/usage/" will not work and the output could not be proper. The issue could happen only in scaled configuration (Approximately, 4000 or more per-sid ingress sensors and 4000 or more IPv4/IPv6 per-sid egress sensors are configured).
PR Number	Synopsis	Category: Layer2 forwarding on EX/NTF/PTX/QFX
1816049	MAC addresses learnt on interfaces part of VLAN with MAC limiting by interface and "drop-and-log" action configured are cleared after VLAN description is changed Product-Group=junos Severity=Major	On all Junos and Junos Evolved platforms, when "set vlans switch-options interface-mac-limit packet-action drop-and-log" is configured, changing the Virtual Local Area Network (VLAN) description will cause flush of Media Access Control (MAC) addresses learnt on the interfaces part of the VLAN and traffic impact

23.4R2-S2 - List of Known issues

PR Number	Synopsis	Category: Border Gateway Protocol
1788543	BGP outputqueue counter does not go back to "0" after converged Product-Group=junos Severity=Major	After the initial convergence of system reboot, there is some values stuck in the OutQ counter of one of the peers in a group. show bgp sumary> 200.25.16.2 7195 276612 451961 23 0 28:51 Establ >>> We could see that values is stuck at 23. inet.0: 8/941037/941037/0 inet6.0: 5/5/5/0 This issue is cosmetic issue since we could see that there are not missing routes in peer. Resolved In: evo:23.4R2-S3-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:24.2R2 junos:24.3R1 junos:24.4R1
PR Number	Synopsis	Category: EVO L2 Control Plane PRs
1817677	MX and ACX platforms running EVPN-VXLAN in DCI stitching environments will experience traffic outage Product-Group=junos Severity=Critical	On MX and ACX platforms with Ethernet VPN-Virtual Extensible LAN (EVPN-VXLAN), symmetric route stitching between data center networks enables the Control Word (CW) flag changes, which will cause traffic disruption in the Packet Forwarding Engine (PFE). Resolved In: evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:24.2R2 junos:24.3R1 junos:24.4R1
PR Number	Synopsis	Category: SRX4100/SRX4200 platform software
1808353	Traffic drop is seen when "monitor traffic interface" command is issued for a child interface on Junos SRX platforms Product-Group=junosvae Severity=Major	On Junos SRX4100/SRX4200 platform, starting and stopping the "monitor traffic interface", causes the VPN tunnel or tagged traffic to be dropped. However, keeping the "monitor traffic interface" running, ensures that traffic will function properly. Issue occurs when monitor interface command on child interface is performed on devices that has vlan-tagging configured. Resolved In: junos:21.4R3-S9 junos:22.4R3-S4 junos:23.2R2-S2 junos:23.4R2-S3 junos:24.2R1-S1 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR Number	Synopsis	Category: Layer2 forwarding on EX/NTF/PTX/QFX
1817705	The l2ald crash is observed when adding scaled EVPN-VXLAN configuration on Junos platforms Product-Group=junos Severity=Critical	On Junos platforms, if disk is full, when scaling configuration is moved to baseline configuration and move back to scaling configuration, l2ald try to create a source VTEP, but old VTEP is still in the middle of deletion, so kernel return EBUSY and l2ald will retry. If retry too many times, l2ald insist and core. Resolved In: evo:24.3R1-EVO evo:24.4R1-EVO junos:24.3R1 junos:24.4R1
PR Number	Synopsis	Category: Path computation client daemon
1823220	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=Major	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:24.2R2-EVO evo:24.4R1-EVO junos:24.2R2 junos:24.4R1
PR Number	Synopsis	Category: QFX5K JUNOS Interface, MACSec, Optics, SDK, PHY
1799073	Auto-channelization is showing inconsistent behaviour on QFX platforms when there is fault on the channels Product-Group=junos Severity=Major	On all QFX platforms, auto-channelization failure is seen due to faults on any channels of breakout channels, leading to link downtime and traffic disruption. Resolved In: junos:21.4R3-S9 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR Number	Synopsis	Category: RPD infrastructure issues related to NSR, GRES, switchover,
PR Number	Synopsis	Category: KRT Queue issues within RPD
1805427	The rpd process crashes during rpd restart on Junos and Junos Evolved platforms Product-Group=junos Severity=Major	On all Junos and Junos Evolved platforms, due to timing issue during the restart of the rpd process may cause it to crash. This can temporarily impacts traffic until the process recovers. Resolved In: evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:24.2R1 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR Number	Synopsis	Category: Track usability related J-Web PR, like UI layout, workflow
1823264	Unable to Define NAT Policy Address Names Containing Dots or Slashes in J-Web Product-Group=junos Severity=Major	On all SRX series platforms enabled with J-Web, NAT (Network Address Translation) policies cannot be edited/added using J-Web if the destination address name contains '.' dot or '/' slash. Resolved In: junos:21.4R3-S9 junos:22.4R3-S4 junos:23.2R2-S2 junos:24.2R2 junos:24.3R1 junos:24.4R1

Note: You can find the definition of "Severity" from "KB86335 [juniper.net] "

Modification History

First publication 2024-08-29