Alert Type

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

Product Affected

ACX PTX QFX platforms running Junos Evolved software

Alert Description

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

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 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

Solution

 

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

23.4R2-S2-EVO - List of Fixed issues 

PR NumberSynopsisCategory: ACX BFD specific issues
1812652ACX7100-not able to have more than 256 single-hop BFD sessions
Product-Group=evo
Severity=Minor		ACX7100-not able to have more than 256 single-hop BFD session
PR NumberSynopsisCategory: Layer 3 forwarding, both v4+v6
1824219MPLS payload ether-pseudowire configured along with any other MPLS payload type does not work as expected
Product-Group=evo
Severity=Major		On all Junos Evolved platforms, MPLS (Multiprotocol Label Switching) payload type ether-pseudowire configured along with any other MPLS payload type does not work as expected and traffic will be impacted.
PR NumberSynopsisCategory: Dynamic rendering infrastructure
1745615Telemetry data is not exported in an IS-IS scaled Segment Routing scenario
Product-Group=evo
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 NumberSynopsisCategory: Express ptx-evo PFE L3 Features
1816310VRRP is not working for VRRP group 0 when specific Junos OS Evolved platforms are working as master
Product-Group=evo
Severity=Major		VRRP (Virtual Router Redundancy Protocol) will not work when VRRP group 0 is configured and specific Junos OS Evolved platforms (PTX10001/PTX10003/PTX10004/PTX10008/PTX10016) are working as master.
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1816049MAC 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=evo
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
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1821845The system scripts refresh will fail when using load CLI option
Product-Group=evo
Severity=Major		On all Junos and Junos OS Evolved platforms when the 'edit system scripts' hierarchy configuration is changed using loading a configuration from a file or the terminal using 'load' option, the scripts refresh will fail.
1825728When using an FQDN (Fully qualified domain Name) in conjunction with the ephemeral configuration database, the MGD process may crash.
Product-Group=evo
Severity=Critical		The MGD process (Junos CLI) will crash if the switch has an ephemeral configuration database instance and an FQDN (Fully Qualified Domain Name) is used for NTP, radius-server, tacplus-server, etc. in either the main static configuration or the ephemeral configuration database.


Note: CVE-2024-3596 is fixed in this software release

 

23.4R2-S2-EVO - List of Known issues 

PR NumberSynopsisCategory: Border Gateway Protocol
1788543BGP outputqueue counter does not go back to "0" after converged
Product-Group=evo
Severity=Major		When BGP first initial convergence after a system reboot, the OutQ counter of one of the peers in a group may be non-zero. This is a cosmetic issue since no missing routes at the BGP 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 NumberSynopsisCategory: EVO L3 routing for BCM XGS Platforms
1820266AI_Cluster_JVD: with 2 lossless queues per port ECN is not triggered during congestion
Product-Group=evo
Severity=Major		On QFX5220/5230/5240/5130/5700 platforms, for lossless queues packet admission control is based on ingress priority group thresholds only. Once lossless packet is accepted by ingress, there will not be any further admission control checks based on egress queue thresholds. So dynamic threshold (alpha) setting configured at egress queue level, will not make any impact for lossless queues. For lossless queue, peak shared buffer utilisation will be always based on the ingress priority group dynamic threshold. Do not configure per queue alpha via "buffer-dynamic-threshold" for lossless queues. On QFX5220/5230/5240/5130/5700 platforms, ECN threshold is static. However PFC thresholds are dynamic. For effective DCQCN behaviour, make sure ECN threshold is always lower than the PFC XOFF threshold. Specifically when multiple ingress and egress ports involved in lossless queue congestion, there is high chance for PFC XOFF threshold hitting before ECN threshold. Proper ECN marking thresholds can be arrived by monitoring the peak buffer utilisation of congested lossless queues and fine tuning the ECN thresholds accordingly.

Resolved In: evo:23.4X100-D20-EVO evo:23.4X31-EVO evo:24.2R2-EVO evo:24.4R1-EVO evo:25.1R1-EVO junos:24.2R2
PR NumberSynopsisCategory: QOS issues in EVO for BCM XGS Platforms
1709097CoS:Dedicated-Buffer: Unexpectedly egress dedicated cells are distributed to queue's in some case
Product-Group=evo
Severity=Major		When per queue level dedicated buffer calculated based on scheduler "buffer-size" configuration, any fractional dedicated buffer value rounded-off to closest lower full integer and programmed in hardware to avoid over allocation. Any unused port dedicated buffers after allocating dedicated buffers to all configured queues will be allocated to first configured queue.

Resolved In:
PR NumberSynopsisCategory: EVO MBB infra related issues and enhancements
1820376Multicast routes can be out of sync due to the quick AE interface flap
Product-Group=evo
Severity=Critical		On Junos Evolved PTX platforms, due to quick Aggregated Ethernet (AE) interface flap, Multicast routes can be out of sync between the control plane and the forwarding plane (rpd and Packet Forwarding Engine (PFE)) resulting in traffic drops.

Resolved In: evo:21.4R3-S9-EVO evo:21.4X9-EVO evo:22.2R3-S5-EVO evo:22.3R3-S4-EVO evo:22.4R3-S4-EVO evo:22.4R3-S5-EVO evo:23.2R2-S2-EVO evo:23.4R2-S3-EVO evo:24.2R1-S2-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.3R2-EVO evo:24.4R1-EVO junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: Express PFE CFM
1785008CFM Inline : AE anchor child interface change , CFM sessions go down
Product-Group=evo
Severity=Major		When AE bundle has multiple child links, and thea anchor child link is chaged die to any underlying activity like pfe restart of pfe hosting current anchor child, CFM inline sessions fail to come up on the newly selected anchor child link.

Resolved In: evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: JDHCP is a daemon for EVO platform to handle DHCP protocol
1816246ACX7509:DHCPv4/v6 Relay subscriber may not login if DHCP configuration is completly removed and readded.
Product-Group=evo
Severity=Major		Under certain conditions when DHCP configuration is completely removed Session Database is left in an unusable state. On subsequent reconfiguration of DHCP subscriber logins will fail. In this case a system reboot is required.

Resolved In:
PR NumberSynopsisCategory: Bug and Review Tracking for Segment routing traffic eng
1820791Per-Segment-list telemetry for colored tunnel doesn't work
Product-Group=evo
Severity=Major		Per-Segment-list telemetry for colored tunnel doesn't work on PTX-Series platform with Junos OS Evolved such as PTX10004, PTX10003, PTX10001, but it works on PTX10008 and PTX10016.

Resolved In: evo:23.4R2-S3-EVO evo:24.2R2-EVO evo:24.4R1-EVO junos:24.2R2 junos:24.4R1
NumberSynopsisCategory: QFX5000 EVO Interfaces
1862907QFX5000s ZTP failed on WAN ports, interfaces do not come up

QFX5000s ZTP failed on WAN ports, interfaces do not come up

Resolved In: 

Modification History

First publication 2024-09-06