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

See TSB95590 [juniper.net] for the list of Fixed Issues

23.4R2-S4-EVO - List of Known issues

PR NumberSynopsisCategory: EVO interface software
1736206
Major		The interface comes up with a mismatch FEC after setting FEC91 on one end and will be stuck in down state after deleting FEC91
Product-Group=evo		The interface comes up with a mismatch FEC after setting FEC91 on one end and will be stuck in down state after deleting FEC91.

Resolved In: evo:22.3X50-EVO evo:22.3X80-D41-EVO evo:22.3X80-D42-EVO evo:23.4R1-EVO evo:24.1R1-EVO
PR NumberSynopsisCategory: Border Gateway Protocol
1817834
Major		The rpd crashes when stale label entry keeps increasing when knob stale-labels-holddown-period is configured
Product-Group=evo		On all Junos and Junos Evolved platforms configured with the "stale-labels-holddown-period" setting and extensive label configurations (such as Multiprotocol Label Switching labels), the Routing Protocol Daemon (RPD) may crash if stale labels are not cleared periodically and keep accumulating. Due this, temporary traffic impact will be seen until the rpd process restarts.

Resolved In: evo:22.4R3-S6-EVO evo:23.2R2-S3-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:21.4R3-S10 junos:22.4R3-S6 junos:23.2R2-S3 junos:23.4R2-S3 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: Express BT PFE L3 Features
1723808
Major		Incorrect PPS value is observed on EVO platforms for a few seconds
Product-Group=evo		The PPS reported for the interface may fluctuate for a few seconds and show either higher or lower value. The chance of this happening is very rare.

Resolved In: evo:21.4R3-S4-EVO evo:22.1R3-S3-EVO evo:22.2R3-S1-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.3X80-D38-EVO evo:22.3X80-D39-EVO evo:22.4R3-EVO evo:23.1R1-S1-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1 junos:24.3R1
PR NumberSynopsisCategory: Alias for DHCP issue on DNX based platform.
1858942
Major		Routing process daemon or RPD restart may affect the broadcast/flood traffic for EVPN VXLAN
Product-Group=evo		Routing process daemon or RPD restart may affect the broadcast/flood traffic for EVPN VXLAN

Resolved In:
PR NumberSynopsisCategory: Layer 3 forwarding, both v4+v6
1854763
Major		The post-convergence-lfa configuration causes a suboptimal-routing
Product-Group=evo		A suboptimal routing of traffic can be seen post configuring the post-convergence-lfa due to failover ID miss programming in the PFE.

Resolved In: evo:23.2R2-S4-EVO evo:24.2R2-EVO evo:24.4R1-S2-EVO evo:24.4R2-EVO evo:25.2R1-EVO
PR NumberSynopsisCategory: EVO MACSEC Platform Independent Implementation
1839514
Major		EVO PTX platform BGP keeps flapping with hold timer expiration after software upgrade due to MACsec MTU mismatch
Product-Group=evo		EVO releases with 23.1 and higher have increased the BGP TCP Socket Buffer size from 16k to 32k for performance improvements. If two EVO peers are at 23.1 or higher and MACsec interface MTU is not accommodated for the 32Byte overhead, BGP session might start flapping with hold timer expatriation.

Resolved In:
PR NumberSynopsisCategory: Express ptx-evo PFE L3 Features
1836337
Major		Packet loss is observed when the "indirect-next-hop-change-acknowledgements" command is missing from the junos-default configuration
Product-Group=evo		On Junos Evolved PTX10003 platform the command "indirect-next-hop-change-acknowledgements" is required in the junos-default configuration. If the said command is missing, it will result in packet loss.

Resolved In: evo:25.1R1-EVO junos:25.1R1
PR NumberSynopsisCategory: mgd, ddl, odl infra issues
1701214
Minor		Junos Evolved software:: System is hanging when extend-db is configured and config > 680MB is loaded.
Product-Group=evo		In EVO, during scaled config commit, Configd daemon in UI-infra is taking more time to process the commit. To optimise the processing time, most likely there will be design change required. There is no LKWR/pass instance. Also based on the configuration scale and the time taken for the commit to complete, it seems that this is a Day-1 issue.

Resolved In:
1825793
Minor		[EVO] The timestamp of the "show system configuration rescue" output shows wrong time.
Product-Group=evo		"show system configuration rescue" may show strange "Last changed" timestamp. It may happen under any time zone potentially and looks like there are some patterns. In case of "Asia/Tokyo", Last changed timestamp may show "1970-01-01 08:59:59 JST".

Resolved In: evo:23.2R2-S3-EVO evo:23.4X100-D30-EVO evo:24.2R2-EVO evo:24.4R1-EVO junos:23.2R2-S3 junos:23.4R2-S3 junos:23.4R2-S4 junos:23.4X30-D20 junos:24.2R1-S2 junos:24.2R2 junos:24.4R1
PR NumberSynopsisCategory: EVPN control plane issues
1816672
Major		[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=evo		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 NumberSynopsisCategory: N/A:sw-gamora-ptp
1847743
Major		Transit PTP traffic is getting impacted on ACX7K EVO platforms
Product-Group=evo		Transit PTP (Precision Time Protocol) traffic is getting affected on Junos OS Evolved ACX7K platforms running 23.4Rx-EVO releases while enabling/disabling PTP or without PTP configuration.

Resolved In:
PR NumberSynopsisCategory: MPC11 ULC fabric software related issues.
1827058
Major		The PFE gets disabled due to large number of fabric self ping errors
Product-Group=evo		On MX platforms with MPC11E and LC9600 and MX304, when multiple fabric self ping errors and timeouts are seen, device attempts to recover by performing port bounces at fabric end. But when there are large number of self ping errors and timeouts are seen which require more than 256 port bounces, the affected PFE(Packet Forwarding Engine) will get disabled resulting in traffic loss.

Resolved In: evo:24.2R2-EVO evo:24.4R1-EVO junos:23.4R2-S4 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: Multicast for L3VPNs
1861726
Major		The MVPN traffic forwarding is affected when BGP PIC is enabled
Product-Group=evo		On all Junos OS and Junos OS Evolved PTX series platforms, enabling BGP-PIC (Border Gateway Protocol-Prefix Independent Convergence) is causing the issues with forwarding MVPN (Multicast Virtual Private Network) traffic.

Resolved In: evo:24.4R2-EVO evo:25.1R1-EVO evo:25.2R1-EVO junos:24.4R2 junos:25.1R1 junos:25.2R1
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=evo		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: PTX10K Routing Engine
1770585
Major		Junos vmhost upgrade will continue to reboot the box even if the upgrade has failed due to tar errors when the reboot option is used
Product-Group=evo		Issue identified when upgrading vmhost, but applies to all Junos platforms that support vmhost. When there are tar errors during the upgrade, and the reboot option is used in the upgrade command, the machine will still reboot the RE despite that the upgrade was not completed correctly. This will break the routing engine. It is necessary to stop the reboot, if error or tar problems occurred during the upgrade.

Resolved In: junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: ZT/YT LUSS SW driver
1765394
Major		Fatal(MQSS and XQSS errors) error on FPC leads to PIC card offline and traffic impact
Product-Group=evo		On Junos MX304 and MX platforms with LC9600 linecards, With the current error handling mechanism upon receiving fatal error on Flexible pic concentrators(FPC), leads to disable both the Packet Forwarding Engine(PFE) on a Physical Interface Cards(PIC) card and seen traffic impact.

Resolved In: evo:24.1R1-EVO junos:22.4R3-S7 junos:23.4R2-S4 junos:24.1R1
PR NumberSynopsisCategory: Trio pfe l3 forwarding issues
1816378
Major		XQSS_CMERROR errors will be seen which might disable PFE
Product-Group=evo		On MX204, MX10003 and MX platforms with MPC7, MPC8, MPC9, LC480, LC2101, LC2103, MPC10 and MPC11 line cards or EX92xx platforms with EX9200-40XS, EX9200-12QS, EX9253-6Q12C, EX9253-6Q12C-M line cards, SRX5400, SRX5600, SRX5800 platforms with SRX5K-IOC4-10G, SRX5K-IOC4-MRAT line cards, in a scenario where there could be fabric drops because of over-subscription or CRC errors, there could be case when the same tail entry get re-used across packets leading to packet corruption and CM error. This is a corner case and might lead to PFE(Packet Forwarding Engine) disable resulting in traffic loss.

Resolved In: evo:24.3R1-EVO junos:21.4R3-S10 junos:22.4R2-S1-J8 junos:22.4R3-S4 junos:23.2R2-S3 junos:23.4R2-S4 junos:24.2R1-S1 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: 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=evo		In Netconf private edit configuration session, commit RPC fails when unprotect operation is performed.

Resolved In:
PR NumberSynopsisCategory: Issues related to NETCONF
1792554
Minor		JUNOS: Netconf: Edit-config with operation attribute create for existing hierarchy is not working as per RFC 6241
Product-Group=evo		JUNOS: Netconf: Edit-config with operation attribute create for existing hierarchy is not working as per RFC 6241

Resolved In:
1796297
Major		Error message not prompted on commit confirmed RPC sent in private mode on all Junos and Junos Evolved platforms
Product-Group=evo		On all Junos and Junos Evolved platforms, commit confirmed command executed with remote procedure call (RPC) in private configuration mode is being allowed where ideally it should not be.

Resolved In: evo:22.2R3-S6-EVO evo:22.3X80-D45-EVO evo:22.3X80-D46-EVO evo:23.2R2-S3-EVO evo:23.4X100-D30-EVO evo:24.2R1-EVO evo:24.2R2-EVO evo:24.3R1-EVO junos:21.2R3-S9 junos:21.4R3-S10 junos:22.2R3-S6 junos:23.2R2-S3 junos:23.4R2-S4 junos:24.2R1 junos:24.2R2 junos:24.3R1 junos:25.1R1
1800859
Major		Configuration push to device using RPC resulted in incorrect policy order
Product-Group=evo		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.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.4R3-S5 junos:23.2R2-S3 junos:23.4R2-S3 junos:24.2R1-S1 junos:24.2R2 junos:24.3R1 junos:25.1R1
PR NumberSynopsisCategory: Issues related to YANG Data Models
1781023
Minor		Few yang package are occuring multiple place On Box
Product-Group=evo		Few yang package are occuring multiple place On Box

Resolved In:
1826630
Major		Annotations are improperly structured in NETCONF after enabling YANG compliance
Product-Group=evo		When the YANG(Yet Another Next Generation)-compliant knob is configured, annotations containing non-alphanumeric characters are written as-is, instead of being escaped into their corresponding formats.

Resolved In: evo:22.4R3-S5-EVO evo:23.2R2-S3-EVO evo:23.4X100-D30-EVO evo:24.2R2-EVO evo:24.4R1-EVO evo:25.1R1-EVO junos:22.4R3-S5 junos:23.2R2-S3 junos:23.4R2-S4 junos:24.2R1-S2 junos:24.2R2 junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: MX10K linecard
1809511
Major		Ethernet interfaces configured with loopback option remains down after multiple iteration of line card boot is performed
Product-Group=evo		On MX platforms with LC2101 line cards and 10-gigabit ethernet interfaces configured in loopback mode, when Line card is booted multiple times, the ethernet interfaces on line card remains down and traffic on those interfaces will be impacted.

Resolved In: evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:21.4R3-S10 junos:23.4R2-S4 junos:24.2R2 junos:24.3R1 junos:24.4R1