23.4R1-S2: Software Release Notification

Alert Type

PSN - Product Support Notification

RiskRisk Description

Low/Notification

Software Release Notification

ImpactImpact Description

Low/Notification

Software Release Notification

Product Affected

ACX EX MX PTX SRX vSRX

Alert Description

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

Note: Junos Software for QFX platforms is a limited software release. Contact JTAC for availability of the QFX Software.

Solution

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

23.4R1-S2 - List of Fixed issues

PR Number	Synopsis	Category: EX2300/3400 platform
1789272	Watchdog SPI transaction is causing the interface flap in the system Product-Group=junos	On EX2300-MP platforms, when the SPI (Serial Peripheral Interface) bus is accessed by multiple processes simultaneously results in watchdog reset due to the lack of lock-unlock operations. Consequently, this can lead to interface flaps affecting the traffic flow.
PR Number	Synopsis	Category: NFX Layer 3 Features Software
1776815	The PFE process crash happens in NFX platforms Product-Group=junos	On all NFX series platforms, the pfe (packet forwarding engine) process crashes due to memory exhaustion when configured with custom mode templates like flex mode or any other custom mode.
PR Number	Synopsis	Category: SRX2000/50000 issue
1784775	The chassis cluster failover is seen post ISSU Product-Group=junos	On SRX5K platforms with SPC3, chassis cluster failover is seen post ISSU. The SPC3 connects to the wrong Routing Engine which impacts all the PICs affecting the complete traffic.
PR Number	Synopsis	Category: PFE COS features on BT based platforms
1797592	More than 8 forwarding-classes cannot be configured with CBF Product-Group=junos	On PTX10001-36MR, error will be displayed when we commit more than 8 forwarding-classes (FCs) which are configured with Class Based Forwarding (CBF) even though the product supports upto 16 forwarding-classes configured with CBF.
PR Number	Synopsis	Category: CoS support on DNX
1772177	On ACX710/5448 with hierarchical-scheduler EVPN ETREE (Ethernet virtual private network Etree feature) leaf-to-leaf communication is allowed Product-Group=junos	EVPN ETREE (Ethernet virtual private network Etree feature) leaf to leaf communication on AE (Aggregated Ethernet) interface happens if hqos (Hierarchical class of service) is enabled on AE.
PR Number	Synopsis	Category: Dynamic rendering infrastructure
1745615	Telemetry data is not exported in an IS-IS scaled Segment Routing scenario Product-Group=junos	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: Configd, ffp issues
1797425	Commit of "openconfig-interfaces:interfaces interface <> config openconfig-vlan:tpid <>" configuration fails with commit scripts error on glenrothes Product-Group=junos	Commit of "openconfig-interfaces:interfaces interface <> config openconfig-vlan:tpid <>" configuration fails with commit scripts error on glenrothes
PR Number	Synopsis	Category: SRX1500 platform software
1751496	On SRX1500 PEM Alarms are displayed due to hardware limitations to read I2C Product-Group=junosvae	On SRX1500 Hardware Limitation leads to PEM I2C Failure Alarm triggered as result of failure in I2C reading operations.
PR Number	Synopsis	Category: SRX4100/SRX4200 platform software
1739559	SRX4100/4200 accepts the datapath-debug configuration although it does not support it Product-Group=junos	It is possible to set and commit the datapath-debug configuration on platforms SRX4100/SRX4200 although datapath debugging is not supported on those platforms. because of this unsupported configuration being accepted the RE (Routing Engine) load can go high and cause traffic outage. The workaround is to remove the datapath-debug configuration and perform a commit.
PR Number	Synopsis	Category: IDP policy
1786822	The flowd process crash is observed when the device is rebooted Product-Group=junos	On all Junos SRX platforms, flowd crash is seen when the device is rebooted and a CLI request for Intrusion Detection and Prevention (IDP) counters reaches the Packet Forwarding Engine (PFE) before the IDP memory module is initialized (even if IDP is not configured). The flowd process restarts affecting the traffic.
PR Number	Synopsis	Category: Flow Module
1762568	Unable to download a file completely from SaaS server to LAN Product-Group=junos	TCP sessions are not refreshed when enabled the "set security flow gre-perf-acceleration" is configured.
1777565	Packet drops will be observed in GRE scenarios on SRX and vSRX platforms Product-Group=junos	On SRX and vSRX platforms, when Generic Routing Encapsulation (GRE) tunnels are configured, packet drops will be observed when packets enter to a tunnel.
PR Number	Synopsis	Category: IPSEC/IKE VPN
1785346	Traffic loss after deleting the traffic selector from the VPN configuration Product-Group=junos	On SRX platforms (except SRX5k platforms with SPC3 card), traffic loss will be observed after deleting the traffic selector from the VPN (Virtual Private Network) configuration but the traffic selector was not getting deleted from PFE (Packet Forwarding Engine) due to which the deleted remote subnet still shows up in the routing table, forwarding table and the firewall tries to negotiate deleted traffic selectors. The issue happens when the "ipsec-key-management service" is configured and the VPN name has 32 characters.
PR Number	Synopsis	Category: Multiprotocol Label Switching
1793982	RPD process might crash when TED-INFRA-COOKIE gets the memory exhausted Product-Group=junos	On all Junos, Junos-EVO platforms, When ISIS with IPv6 is enabled, there will be a memory leak of 240 bytes with each link flap. There is no service impact until all the system memory is exhausted, however when system memory is exhausted RPD restarts.
PR Number	Synopsis	Category: vMX Platform Infrastructure related issue tracking
1729152	The FPC crash or flap in protocols will be seen as soon as port-mirroring or firewall filters with syslog action is enabled Product-Group=junos	On MX150 platform, when port-mirroring or firewall with syslog configuration is enabled, there will be a memory leak which will cause depletion of buffer memory which will lead to flap in the protocols or the (Flexible PIC Concentrators) FPC crash. This will impact the traffic.
PR Number	Synopsis	Category: SRX branch platforms
1714620	High latency will be observed while pinging to peer device Product-Group=junos	On Branch SRX Platforms, The delay will be observed while pinging to peer device due to high latency when VLAN(Virtual Local Area Network) tagged DHCP(Dynamic Host Configuration Protocol) packets arrive at IRB (Integrated Routing and Bridging) interface.
1780326	IP Monitoring fail to install route after SRX cluster reboot Product-Group=junos	On Junos SRX branch series platforms in cluster, the IP Monitoring fails to install route after the SRX cluster reboots.
PR Number	Synopsis	Category: Authentication, Authorization, Accounting, PAM (RADIUS/tacplus)
1797496	Config login class with allow/deny-configuration-regexps not working as expected with Routing-instances Product-Group=junos	Config login class with allow/deny-configuration-regexps not working as expected with Routing-instances
PR Number	Synopsis	Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1794536	The device goes into configuration locked state due to stale mgd Product-Group=junos	The device is went into config locked state due to stale mgd. For netconf sessions with , if ungraceful exit happens, the lock is not released. There is auto cleanup supported for such cases, But it is not triggered under problem conditions as faced in this PR. This leads to device remain in locked state due to stale entry. "request system logout pid " can be used for cleanup and to recover from this state.

23.4R1-S2 - List of Known issues

PR Number	Synopsis	Category: EX4300 Platform implementation
1789999	[interfaces]:Ex-Hardening:Local/Remote fault insertion from TG is failing Product-Group=junos	Ex-Hardening:Local/Remote fault insertion from TG is failing Resolved In:
PR Number	Synopsis	Category: EX2300/3400 platform
1580560	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:
PR Number	Synopsis	Category: NFX Layer 3 Features Software
1792616	JUNOS_REG: NFX350: Core "localhost.srxpfe.88692.1708200605.core.tgz" seen in NFX350 boxes. Product-Group=junos	JUNOS_REG: NFX350: Core "localhost.srxpfe.88692.1708200605.core.tgz" seen in NFX350 boxes. Resolved In:
PR Number	Synopsis	Category: Border Gateway Protocol
1785231	PE Routers continue to drop prefixes in a L3 VPN scenario Product-Group=junos	On all Junos and Junos OS Evolved platforms configured as a Provider Edge (PE) in an L3VPN scenario peering with a route-reflector (RR) as a client, when there are no external BGP peers configured with a static route-target-filter as `local`, VPNv4 prefixes advertised by RR is being dropped which is as per design and expected behavior. However, when an external BGP session is established on the PE, because 'advertise-from-main-vpn-tables' is configured, the PE doesn't flap all existing BGP sessions, and the refresh of prefixes advertised by RR does not happen. As a result, prefixes advertised by RR continue to be dropped at PE. Resolved In: junos:23.4R2 junos:24.1R2 junos:24.2R1
PR Number	Synopsis	Category: MX304 Chassis specific platform
1799431	JDI-REGRESSION:MX304: cty core seen during usb upgrade from 23.1R1.8 to 23.2R2.18 Product-Group=junos	cty is a log collecter daemon process Which might get crashed during bootup It does not make any impact on the performance as its an independent process to collect logs only Resolved In: junos:22.4R3-S2 junos:23.2R2-S1 junos:23.4R2 junos:24.1R2 junos:24.2R1 junos:24.3R1
PR Number	Synopsis	Category: Virtual-chassis platform/chassisd infrastructure PRs for MX
1774302	MXVC:MPC10E can not reach VC-Mm when re1 is VC-Mm Product-Group=junos	MXVC:MPC10E can not reach VC-Mm when re1 is VC-Mm. The issue happens only for Linux Based cards and Ukern ie non Linux based cards will work fine. Resolved In: junos:22.4R3-S3 junos:23.2R2
PR Number	Synopsis	Category: Layer 2 Control Module
1787892	Interface configured with BPDU-disable goes down during VC mastership switchover Product-Group=junos	On Junos EX3400/EX4300/EX2300 platforms configured with VC (Virtual Chassis) and NSB (Nonstop-Bridging) enabled, when VC mastership switchover is triggered, the configuration under 'set protocols layer2-control bpdu-block interface ' will not take effect due to which the interface will go down and will impact the traffic. The configuration 'set protocols layer2-control bpdu-block interface all' will not have any impact. Resolved In: evo:22.3R3-S3-EVO evo:23.4R2-EVO evo:24.1R1-EVO evo:24.2R1-EVO junos:21.4R3-S7 junos:22.1R3-S6 junos:22.2R3-S4 junos:22.3R3-S3 junos:22.4R3-S2 junos:23.2R2 junos:23.2R2-S1 junos:23.4R2 junos:24.1R1 junos:24.2R1
PR Number	Synopsis	Category: Layer2 forwarding on EX/NTF/PTX/QFX
1790064	The l2ald process will crash, with rapid configuration changes followed by rpd and l2ald restart process Product-Group=junos	On all Junos and Junos OS Evolved platforms with EVPN -VXLAN and high scaling configuration, rapid configuration changes followed by restart of rpd and l2ald will result in l2ald process crash and traffic drop will be observed. Resolved In: evo:21.4R3-S7-EVO evo:22.2R3-S3-EVO evo:22.4R3-S1-EVO evo:23.2R2-EVO evo:23.4R1-S1-EVO evo:23.4R2-EVO evo:24.1R1-EVO evo:24.2R1-EVO junos:21.4R3-S7 junos:22.1R3-S6 junos:22.2R3-S3 junos:22.2R3-S4 junos:22.2R3-S7 junos:22.3R3-S3 junos:22.4R3-S2 junos:23.2R2 junos:23.4R1-S1 junos:23.4R2 junos:24.1R1 junos:24.2R1
PR Number	Synopsis	Category: SRX branch platforms
1770303	Inter and intra VLAN traffic drop can be seen on the SRX branch series Product-Group=junos	On all Junos SRX branch series devices, intra and inter-VLAN (Virtual Local Area Network) traffic drop will be seen when the devices are running in ethernet-switching mode and STP(Spanning Tree Protocol) is configured on the respective interface for the VLANs. Resolved In: junos:20.2R3-S9 junos:20.4R3-S10 junos:21.2R3-S7 junos:21.4R3-S6 junos:22.1R3-S5 junos:22.2R3-S3 junos:22.2R3-S4 junos:22.3R3-S2 junos:22.3R3-S3 junos:22.4R3-S2 junos:23.2R2 junos:23.4R2 junos:24.1R1
1776656	Interfaces stay down when 1G SFP fiber transceiver connected to SRX380 platform Product-Group=junos	Ports are staying down on SRX380 platform with 1G SFP fiber transceiver while trying to connect to a device that doesn't support auto-negotiation and/or having hard-coded speed and duplex setting Resolved In: junos:21.2R3-S7 junos:21.4R3-S6 junos:21.4R3-S7 junos:22.1R3-S5 junos:22.2R3-S3 junos:22.3R3-S3 junos:22.4R3-S2 junos:23.2R2 junos:23.4R2 junos:24.1R1
PR Number	Synopsis	Category: ZT/YT pfe firewall software
1802341	Filter will be configured with incorrect vlan-IDs and commit error will not be displayed Product-Group=junos	On mx10008 platform, filter will be configured with incorrect vlan-IDs and commit error will not be displayed if vlan-ID is not configured in the range of 0-4095 which is syntactically incorrect. Resolved In: junos:23.4R2 junos:24.2R1 junos:24.3R1
PR Number	Synopsis	Category: Issues related to NETCONF
1792362	RPC request for file copy with routing instances is failing Product-Group=junos	On Junos OS and Junos OS Evolved platforms configured with routing instances, RPC (Remote Procedure Call) request for file copy using routing instance fails. There is no service/traffic impact due to this issue. Resolved In:

Modification History

First publication 2024-06-04