Alert Type

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

Product Affected

ACX PTX QFX running Junos Evolved Software

Alert Description

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

Junos Selective Update (JSU) feasible

Not applicable

Call to Action

For your review

Solution

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

23.4R2-S7-EVO - List of Fixed issues

PR NumberSynopsisCategory: EVO L3 routing for BCM XGS Platforms
1900568
Major		Vxlan packet sent to host does not protect overlay BFD packets trigger BFD session flap
Product-Group=evo
Severity=Major		On all Junos Evolved QFX platforms that supports VXLAN, the host-path vxlan overlay packets are throttled at 2kpps but do not protect control traffic like BFD packets which triggers BFD session flapping and induces other protocol flaps like BGP etc.
PR NumberSynopsisCategory: PFE COS features on BT based platforms
1918366
Minor		10G channelized interface fails to reach full line rate due to low-rate queue overscheduling
Product-Group=evo
Severity=Minor		On Junos OS Evolved PTX10004, PTX10008 and PTX10016 platforms using LC1201 or LC1202 line cards, a 10G channelized interface created from a 100G or 400G port may fail to reach full line rate. This issue occurs because the interface cannot fully utilize the link due to scheduler behavior when the interface has more than 4 channels and one or more output queues are set to a 5% or lower rate limit and receive a very high offered load compared to other queues.
PR NumberSynopsisCategory: Express BX PFE L3 Features
1886060
Major		PFEs will enter FAULT state when multiple PFEs are on-lined / off-lined / restarted at the same time
Product-Group=evo
Severity=Major		On all Junos-Evolved PTX platforms, If multiple PFEs ( packet forwarding engine ) are on-lined / off-lined / restarted at the same time, without any delay in between the PFE activities ( on-lined / off-lined / restarted ) then one or more PFE will go fault state and all ports belonging to those PFEs become unusable.
PR NumberSynopsisCategory: Alias for DHCP issue on DNX based platform.
1889637
Major		DHCP clients do not come up when VRF leak and "dhcp-relay" with "no-snoop" are configured under a routing-instance
Product-Group=evo
Severity=Major		On all Junos OS Evolved ACX7K Series platforms, when DHCP (Dynamic Host Configuration Protocol) relay mode is used within a routing-instance scenario, DHCP clients fail to come up because DHCP offer packets are being dropped.
PR NumberSynopsisCategory: EVPN ELAN/E-TREE
PR NumberSynopsisCategory: Layer 3 forwarding, both v4+v6
1824219
Minor		MPLS payload ether-pseudowire configured along with any other MPLS payload type does not work as expected
Product-Group=evo
Severity=Minor		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.
1908282
Major		Next hop is missing when ECMP uses an IRB interface in an EVPN-VXLAN scenario
Product-Group=evo
Severity=Major		On all Junos OS Evolved ACX7K Series platforms, the Next hop is wrongly programed when Equal Cost Multi Path (ECMP) is configured, and IRB (Integrated Routing and Bridging) interface is used as a Next hop. Since the Next hope is not being programed properly, routes are unable to have a next hop causing service disruption.
PR NumberSynopsisCategory: ACX IFL, IFF creation
1891275
Major		Framing error observed on AE interface after performing RE switchover on Junos OS Evolved ACX7509 platform
Product-Group=evo
Severity=Major		Continuous increase in framing errors observed on AE interface after doing RE switchover on Junos OS Evolved ACX7509 platform.
PR NumberSynopsisCategory: EVO Netstack FIB Service Daemon
1785913
Critical		Junos OS Evolved: TCP session state is not always cleared on the Routing Engine leading to DoS (CVE-2024-47502)
Product-Group=evo
Severity=Critical		An Allocation of Resources Without Limits or Throttling vulnerability in the kernel of Juniper Networks Junos OS Evolved allows an unauthenticated, network based attacker to cause a Denial of Service (DoS). Please refer to https://supportportal.juniper.net/JSA88132 [juniper.net] for more information.
PR NumberSynopsisCategory: software upgrade infra issues
1878365
Major		Log messages getting disappeared after upgrade
Product-Group=evo
Severity=Major		On all Junos Evolved platforms, log messages disappear when an upgrade without the "no-validate" option is performed. This issue has no impact on traffic.
PR NumberSynopsisCategory: Interface PRs defect & enhancement requests
1845336
Major		Memory leak during interface flap events on Junos Evolved Platforms
Product-Group=evo
Severity=Major		On all Junos Evolved platforms, a memory leak is observed during continuous interface creation and deletion. The internal interface management logic allocates memory during interface (IFD) creation but fails to properly release it during deletion. Over time, this leads to increased memory consumption across multiple system applications. In high-scale environmentswith approximately 30 million interface flaps observed in a real deploymentthis leads to memory exhaustion and result in application restarts, potentially impacting services.
PR NumberSynopsisCategory: EVO Services Jflow PRs for defect & enhancement requests
1874737
Minor		[ptx-10008-evo] ingress mpls IPFIX flows have TopLabelAddr V6: ::
Product-Group=evo
Severity=Minor		Root Cause: In this issue, there can be two routes published for the same MPLS label (one each for BOS=0 and BOS=1). So, in JFLOW, it learns both of them as a single route, resulting in overwriting the routes based on the sequence of updates. Fix Details: On route update in the onModify routine, if the route is present, then update the Prefix & fec PrefixLen only if the FEC prefix is not NULL. No workaround is available.
PR NumberSynopsisCategory: EVO L2 Control Plane PRs
1899530
Major		MAC learning failure when moving the AE interface from one VLAN to another VLAN in a single commit
Product-Group=evo
Severity=Major		On Junos OS Evolved platforms, when an Aggregated Ethernet (AE) logical interface (IFL) is moved from one Virtual LAN (VLAN) to another VLAN in a single commit, Layer 2 forwarding tables fail to update correctly. This causes Media Access Control (MAC) learning failure and traffic disruption.
PR NumberSynopsisCategory: Lacp related problems and issues.
1898531
Major		AE interfaces flap during GRES following an RE reboot on all Junos Evolved platforms
Product-Group=evo
Severity=Major		On all Junos Evolved platforms, Aggregate Ethernet (AE) interfaces with LACP configured will experience a flap due to a timing issue when Graceful Routing Engine Switchover (GRES) is performed after a Routing Engine (RE) reboot, resulting in traffic loss during the flap.
PR NumberSynopsisCategory: EVO-AFT Infrastructure PFE related issues
1898307
Major		PFEs fail to come online after a rapid restart or power cycle
Product-Group=evo
Severity=Major		On Junos OS Evolved PTX platforms, Packet Forwarding Engines (PFEs) may fail to come online when subjected to rapid power-on/power-off cycles or rapid restart of multiple PFEs.
PR NumberSynopsisCategory: Configd, ffp issues
1900883
Major		Traffic loss occurs due to missing apply-path handling during reboot or configd restart
Product-Group=evo
Severity=Major		On platforms running Junos OS Evolved 20.2R1-EVO and later releases, apply-path configurations with wildcards after leaf nodes are not evaluated correctly during reboot or configd restart. This is due to missing special handling required for evaluating such configurations during reboot and configd restart, this causes failure of routing and forwarding functions that rely on apply-paths, leading to traffic loss post reboot or configd restart.
PR NumberSynopsisCategory: mgd, ddl, odl infra issues
1867821
Major		The "ui-gnmi-pubd.log" file growth may cause disk space issues on all Junos OS Evolved platforms
Product-Group=evo
Severity=Major		On all Junos OS Evolved platforms, when telemetry is enabled and an active gNMI subscription includes a configuration path, the "ui-gnmi-pubd.log" file will grow continuously without log rotation or archival. This behaviour will lead to potential disk space exhaustion over time, however, there is no traffic impact due to this issue.
1884781
Major		Slow configuration commit observed on devices with a single Routing Engine (RE)
Product-Group=evo
Severity=Major		On all Junos OS Evolved platforms with single RE and the system type is cluster, a commit delay is observed when operating with a single RE. This occurs because the system attempts to synchronize with the second RE by default, but since it's not present, the process waits and causes the delay in commit.
PR NumberSynopsisCategory: SNMP, mib2d issues
1875093
Major		[PTX10K EVO] Cold start SNMP trap is unexpectedly sent when doing mastership switchover from RE1 to RE0, or backup RE reboot followed by mastership switchover
Product-Group=evo
Severity=Major		On PTX10K EVO platforms with dual REs, cold start SNMP trap is unexpectedly sent when doing mastership switchover from RE1 to RE0 by bring down master RE1, or backup RE reboot followed by mastership switchover
PR NumberSynopsisCategory: Express PFE FW Features
1882315
Minor		Firewall policy configured to match IP payloads fail matching on MPLS packets
Product-Group=evo
Severity=Minor		On Junos Evolved PTX platforms, when configuring a firewall policy, specifying family any, and matching on inner IP payload (IPv4 or IPv6), matching does not work on Multiprotocol Label Switching (MPLS) packets
PR NumberSynopsisCategory: ACX7332 & ACX7348 Platform Software
1918410
Minor		ACX7348 - Minor alarm not clearing for "Host 0 Active Disk Usage Exceeded"
Product-Group=evo
Severity=Minor		When multiple partitions exceeded 90%, only one alarm was shown because all partitions shared the same descriptor and when any one partition dropped below 90%, the alarm was cleared globally, even if other partitions were still above the threshold. This caused incorrect alarm behavior in multi-partition scenarios.
PR NumberSynopsisCategory: ACX7509 Linecard (FPC) related issues
1893886
Major		Auto-negotiation mismatches leading to connectivity issues on Junos OS Evolved ACX7509, ACX7332, and ACX7348 platforms
Product-Group=evo
Severity=Major		On Junos OS Evolved ACX7509, ACX7332, and ACX7348 platforms having auto-negotiation is configured on a 1G interface, connectivity issues will occur under certain conditions: system reboots or FPC (Flexible PIC Concentrator) restarts or changes in auto-negotiation settings on the peer side. In these scenarios, ARP (Address Resolution Protocol) resolution will fail due to a mismatch in the auto-negotiation state between the local and peer interfaces. The local interface will incorrectly appear as UP, while the peer interface shows as DOWN, leading to link-level inconsistencies and loss of connectivity.
1898908
Major		The other port in a port group goes down after an RE switchover if one of the port in the port group is already down on an ACX7509
Product-Group=evo
Severity=Major		On Junos OS Evolved ACX7509 platforms, when one port in a channelized group (like ports 0 in a port group consisting of port 0 and port 1) is already in 'down' state in a ACX7509-FPC-16C with 16x100G-QSFP, performing a Routing Engine (RE) switchover or restarting the picd process can cause the other port in the port group to go down. This will lead to disruption of services running on the port.
PR NumberSynopsisCategory: ACX7509 Platform related issues
1907310
Major		After RE switchover on the device, the capacity of DC PSM is observed to be zero after toggling the input power
Product-Group=evo
Severity=Major		On all Junos OS Evolved platforms, whenever a Routing Engine (RE) switchover occurs and the DC input supply to one of the Power Supply Modules (PSMs) is toggled or flapped, the output capacity of that PSM becomes zero. If the remaining PSMs are unable to provide sufficient power to the chassis, all Flexible PIC Concentrators (FPCs) go offline, resulting in traffic impact.
PR NumberSynopsisCategory: ACX7509 platform, FEB, RCB and linecaard resi
1846199
Major		Device will not boot from secondary disk
Product-Group=evo
Severity=Major		On Junos OS Evolved platforms, the system may access the backup SSD (/dev/sdb) frequently which will reduce the useful life of the SSD.
PR NumberSynopsisCategory: ACX7509 timing related issues
1892751
Minor		On Junos OS Evolved ACX7509 system's clock break synchronization
Product-Group=evo
Severity=Minor		On Junos OS Evolved ACX7509 platforms, clockd uses an older API to communicate with the Zarlink DPLL (Digital Phase-Locked Loop) timing registers, and because this API lacks proper locking, it can impact Zarlink register synchronization and lead to time-synchronization issues for PTP (Precision Time Protocol) and SyncE (Synchronous Ethernet).
PR NumberSynopsisCategory: Layer2 forwarding on EX/NFX/PTX/QFX
1905196
Minor		Stale entry in MAC-IP table affects ARP resolution
Product-Group=evo
Severity=Minor		On all Junos OS platforms, when an IP address already exists in the MAC-IP table as a remote entry and then an IRB (Integrated Routing and Bridging) interface is configured with the same IP address but a different MAC address, then the L2ALD (Layer 2 Address Learning Daemon) does not handle the update correctly, leading to incorrect ARP (Address Resolution Protocol) resolution.
PR NumberSynopsisCategory: Port-based link layer security services and protocols that a
1911538
Major		Show command execution failure for show system macsec license on MX platforms
Product-Group=evo
Severity=Major		On all Junos MX10004, MX10008, MX304, MX301 platforms on executing the command "show system maces license" fails and doesn't fetch any information however it doesn't cause any service disruption. This is a Day-1 issue.
PR NumberSynopsisCategory: Category for tracking Olympus-MX issues
1906557
Major		While collecting RSI, takes long time to produce output on MX platform
Product-Group=evo
Severity=Major		On MX platforms, the cli output for 'show services nat source summary' can take a long time to execute on a highly scaled environment. The issue aggravates when collecting RSI (request support information) and it takes more than an hour for the process to complete. In few instances, this also led to other processes like SNMP monitoring getting stuck.
PR NumberSynopsisCategory: Periodic Packet Management Daemon
1909719
Critical		Junos and Junos OS Evolved platforms experience high CPU after FPC reboot causing unpredictable issues with protocols (OSPF/ISIS/BGP, etc.) managed by PPMD
Product-Group=evo
Severity=Critical		After upgrading or rebooting Junos/Junos OS Evolved platforms, a CPU spike may be observed in the PPMD (Periodic Packet Management Daemon) process due to repeated internal message failures. This can lead to BFD (Bidirectional Forwarding Detection) authentication failures. Additionally, other protocols that rely on authentication and PPMD for packet distribution may also be affected, potentially resulting in traffic loss.
PR NumberSynopsisCategory: QFX L2 PFE
1866016
Minor		Model: qfx5120-32c | Junos: 22.2R3-S4.10 | Management lost | JSD Coredumps observed
Product-Group=evo
Severity=Minor		A race in JSD When multiple clients connecting and disconnecting can cause JSD to crash.
PR NumberSynopsisCategory: PTX10K Line Card specific interface PRs
1914013
Major		Incorrect optics module fault triggered due to transient I2C read error
Product-Group=evo
Severity=Major		On all junos Evolved platforms and MX platforms with ULC cards, The system encountered a momentary I2C communication issue while reading information from the optics module. Instead of treating it as a brief, recoverable read problem, the software incorrectly classified it as a hardware failure and prematurely marked the optics module as faulty.
PR NumberSynopsisCategory: PTX10K specific platform PRs
1900735
Major		Evo PTX PFE instance stuck in fault state after restart
Product-Group=evo
Severity=Major		One or more PFEs may transition to fault state if multiple PFEs are restarted rapidly.
PR NumberSynopsisCategory: ACX7000 platform software related issues.
1889258
Minor		SSD firmware for both primary & secondary SSD is not displayed
Product-Group=evo
Severity=Minor		SSD firmware for both primary & secondary SSD is not displayed

 

23.4R2-S7-EVO - List of Known issues

PR NumberSynopsisCategory: Issues with pluggable optics
1883912
Major		2x100G-LR4 optical modules based on CMIS 4.0 and above won't intialize properly
Product-Group=evo		All 2x100G-LR4 modules based on CMIS 4.0 and above require new SFF 8024 codes for the CAUI-4 host interface for initialization. This change does not apply to CMIS 3.X modules. All Junos Evolved platforms, including PTX, ACX, QFX, and Junos-based platforms such as MX304 and MX with MPC11/LC9600/LC4800 line cards, are impacted by this issue.

Resolved In: evo:23.2R2-S4-J2-EVO evo:23.2R2-S5-EVO evo:23.4R2-S4-J2-EVO evo:23.4R2-S6-EVO evo:24.4R2-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:24.4R2 junos:25.2R2
PR NumberSynopsisCategory: Bi Directional Forwarding Detection (BFD)
1807182
Minor		Interface and protocol flaps is observed when BFD authentication is enabled
Product-Group=evo		On all Junos and Junos OS Evolved platforms with BFD (Bidirectional Forwarding Detection) authentication enabled, interface flap is observed and subsequent protocols will go down. This could result in traffic disruption for that protocol leading to outages.

Resolved In: evo:24.2R2-EVO evo:24.3R1-EVO junos:20.3X75-D46 junos:21.2R3-S9 junos:23.4R2-S4 junos:24.2R2 junos:24.3R1
1846448
Major		The S-BFD responder session cannot be distributed to PFE and failing S-BFD session to establish
Product-Group=evo		On al MX and PTX platforms, If S-BFD(Seamless-Bidirectional Forwarding Detection) responder is configured without the "lo0.0" on device and with any other "lo0.x " then this S-BFD responder session cannot be distributed to PFE(Packet Forwarding Engine) and fails to come up in distributed mode. Hence BFD service will be impacted.

Resolved In: evo:22.4R3-S6-EVO evo:23.2R2-S3-EVO evo:24.2R2-EVO evo:24.4R1-EVO evo:25.1R1-EVO junos:22.4R3-S6 junos:23.2R2-S3 junos:24.2R2 junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: PFE COS features on BT based platforms
1901728
Critical		FPC unresponsive due to memory exhaustion on PTX platforms
Product-Group=evo		On all Junos Evolved PTX platforms, executing the show interface command from the FPC (Flexible PIC Concentrator) vty (Virtual Teletype) prompt triggers memory exhaustion, causing the FPC to become unresponsive.

Resolved In: evo:23.4R2-S4-J31-EVO evo:24.4X200-D20-EVO evo:25.2R2-EVO evo:25.4R1-EVO junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: Express BT PFE L3 Features
1839283
Minor		The multi-homed non-DF PE which is configured with ESI-LAG and MPLS encapsulated is not forwarding packets towards the CE device
Product-Group=evo		On all Junos OS Evolved PTX platforms, when 2 multi-homed PE (Provider Edge) routers connected to a CE (Customer Edge) device with ESI-LAG (Ethernet Switch Identifier-Link Aggregation Group), it is observed that non-DF (Designated Forwarder) PE device is not forwarding packets towards the CE device. The ping from non-DF PE device to CE device is failed. This is observed only when packets are encapsulated with MPLS (Multiprotocol Label Switching) and EVPN (Ethernet Virtual Private Network)-MPLS is configured on IRB (Integrated Routing and Bridging) interface.

Resolved In: evo:23.4R2-S4-EVO evo:24.2R2-EVO evo:24.4R1-EVO
1886043
Major		Few telemetry paths are not exported after router reboot
Product-Group=evo		Following a router reboot, the router management socket, telemetry infrastructure, and RE daemons (such as mib2d and rpd) become operational before telemetry producers. Consequently, the external telemetry collector can establish a connection (e.g. sensor: "/interfaces" ; sample-mode) with the device as soon as the telemetry infrastructure and management interface are up and running. Since producers require several minutes to come up. Therefore, na-grpcd sends a consolidated initial sync completion message to the external collector based on the local init-sync responses from the telemetry producers present at telemetry subscription time (mostly RE based producers). When an application (evo-aftman-bt) becomes operational, a sensor is installed within it (if applicable).However, it is possible that the application has not consumed, thus not exported the interfaces data at the initial sync time (local to the application). As zero-suppression is activated after initial sync, a few statistics with a zero value will not be exported by the device.

Resolved In: evo:22.3X80-D47-EVO evo:22.3X80-D49-EVO evo:24.4R2-EVO evo:24.4X200-D20-EVO evo:24.4X200-D30-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: Express BX PFE L3 Features
1917717
Major		Family v4 stats getting streamed as 0
Product-Group=evo		When cli "set forwarding-options family inet route-accounting" is enabled for v4 stats accounting, the streaming of path /interfaces/interface/subinterfaces/subinterface yield v4 stats as 0: interfaces/interface[name=et-4/0/1]/subinterfaces/subinterface[index=0]/ipv4/state/counters/in-octets: 0 interfaces/interface[name=et-4/0/1]/subinterfaces/subinterface[index=0]/ipv4/state/counters/in-pkts: 0 interfaces/interface[name=et-4/0/1]/subinterfaces/subinterface[index=0]/ipv4/state/counters/out-octets: 0 interfaces/interface[name=et-4/0/1]/subinterfaces/subinterface[index=0]/ipv4/state/counters/out-pkts: 0

Resolved In: evo:22.3X80-D49-EVO evo:25.4R1-S1-EVO evo:26.2R1-EVO
PR NumberSynopsisCategory: CoS support on DNX
1776127
Major		Multihop BFD packets always uses the network-control egress queue
Product-Group=evo		Multihop BFD packets by default uses the network-control queue in EVO ACX. This setting will remain same despite configuring the host-outbound-traffic to a different forwarding-class.

Resolved In: evo:24.2R2-EVO evo:24.4R1-EVO
PR NumberSynopsisCategory: DNX L2 related features
1841573
Minor		High CPU utilization observed on all Junos Evolved ACK7k platforms
Product-Group=evo		On all Junos Evolved ACX7k platforms, high CPU utilization is observed when multiple IFLs (logical interface) are configured over the same IFD (physical interface device). The Broadcom (Brcm) MACs become out of sync with Routing Engine (RE) MACs, performance is affected, and then there is potential traffic disruption.

Resolved In: evo:24.2R2-EVO evo:24.4R1-EVO evo:24.4R2-EVO evo:25.1R1-EVO evo:25.2R1-EVO
PR NumberSynopsisCategory: Binding Queue
1885455
Major		application rpd-agent may restart with a coredump after interface related event changes.
Product-Group=evo		The rpd-agen application may restart either immediately or latently - after interface are activate, deactivated, created, or removed.via.

Resolved In: evo:24.2R2-S4-EVO evo:24.4R2-S1-EVO evo:24.4R2-S2-EVO evo:25.2R1-S1-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: System Management daemon and related issues
1852221
Minor		The l2cpd-agent crashes due to its state cleaned up during shutdown
Product-Group=evo		On all Junos Evolved platforms, due to a timing issue, it is observed that the l2cpd agent crashes when the app's state is being cleaned by external garbage collection as app is about to shutdown. But there is no traffic impact due to this issue.

Resolved In: evo:24.4R2-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO evo:25.4R2-EVO
1905807
Minor		System stops responding to "show system applications app ndp detail" command or prevents applications from start/stop/restart
Product-Group=evo		On all Junos OS Evolved platforms with release >=24.1R1, a failure in internal process communication will cause the system to stop responding to the "show system applications app ndp detail" CLI command or prevent applications from start/stop/restart. This issue occurs when systemd becomes unresponsive to requests initiated by sysman. There is no impact to traffic forwarding.

Resolved In: evo:24.2R2-S3-EVO evo:24.2X2-EVO evo:24.4R2-S1-J1-EVO evo:24.4R2-S2-EVO evo:25.2R2-EVO evo:25.4R1-EVO evo:26.1R1-EVO junos:25.2R2 junos:25.4R1 junos:26.1R1
PR NumberSynopsisCategory: EX interfaces issues
1886889
Minor		snmp mib walk DomCurrentLaneAlarms does not show proper lanes Values in the latest builds
Product-Group=evo

Resolved In: evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:24.2R2-S2 junos:24.4R2 junos:25.2R1-S1 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: ACX7332 & ACX7348 Platform Software
1914062
Major		[ACX] HWD_ALARM_CLEAR_NOTICE: ClearFault: Fault(Location: /Chassis[0]/Psm[0] Device: psm0 Error: psm_cml_pec_fault) cleared
Product-Group=evo		[ACX] HWD_ALARM_CLEAR_NOTICE: ClearFault: Fault(Location: /Chassis[0]/Psm[0] Device: psm0 Error: psm_cml_pec_fault) cleared

Resolved In: evo:24.2R2-S4-EVO evo:24.4R2-S3-EVO evo:25.2R2-EVO evo:25.4R2-EVO evo:26.1R1-EVO evo:26.2R1-EVO
PR NumberSynopsisCategory: Category for JET(JUNOS Extension Toolkit) related issues
1813021
Major		JDI-REG : VIRTUAL : JUNOS : Observing jsd.core with backtrace @exec_ctx_run, @pollset_work, @grpc_pollset_work
Product-Group=evo

Resolved In:
PR NumberSynopsisCategory: Layer2 forwarding on EX/NFX/PTX/QFX
1816344
Major		EVPN : Traffic failure after multiple link flaps of core facing interfaces on scaled setup
Product-Group=evo		ARP resolution failure when there is quick flap of core facing interface on scaled setup

Resolved In: evo:24.2R2-S2-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO evo:26.1R1-EVO evo:26.2R1-EVO junos:24.2R2-S2 junos:24.4R2 junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: Multiprotocol Label Switching
1889546
Major		MPLS ping/trace not working for direct peers via routing-instance over MPLS protocols
Product-Group=evo		On all Junos and Junos OS Evolved platforms, when a routing instance is configured at the destination device, an echo request packet is received over this routing instance interface. This routing instance should have a valid route to reach the source device. But the default routing instance should not have a valid route to reach the source device. This issue is not specific to MPLS ping over SR alone. This issue is applicable for all the protocols MPLS ping.

Resolved In: evo:24.4R2-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:23.4R2-S7 junos:24.4R2-S2 junos:25.2R1-S2 junos:25.2R2 junos:25.3R1 junos:25.4R1
1908506
Major		Frequent link-protection flaps are observed for container LSP's with no change in member LSP
Product-Group=evo		This is a timing issue seen on all Junos and Junos OS Evolved platforms when the optimisation timer expires for a member LSP (Label-Switched Path) when normalisation is in progress for a container LSP, this generates an unrequired route update leading to the link protection route of the LSPs to flap. LSP flap will result in impact on the traffic.

Resolved In: evo:25.2R1-S2-EVO evo:25.2R2-EVO evo:25.4R1-EVO evo:26.1R1-EVO junos:23.2R2-S6 junos:24.2R2-S4 junos:25.2R1-S2 junos:25.2R2 junos:25.4R1 junos:26.1R1
PR NumberSynopsisCategory: Periodic Packet Management Daemon
1912250
Major		BFD sessions will not come up on Junos OS and Junos OS Evolved platforms due to keychain names overlapping
Product-Group=evo		On Junos OS and Junos OS Evolved platforms, where BFD with authentication key chain names are overlapping due to which BFD (Bidirectional Forwarding Detection) sessions will not come up in few scenarios like restart bfdd, restart ppmd, restart FPC.

Resolved In: evo:25.2R2-EVO evo:25.4R1-EVO evo:26.1R1-EVO junos:23.4R2-S6-J1 junos:23.4R2-S7 junos:24.4R2-S3 junos:25.4R1
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1883895
Major		JDI-RCT:MemLeak:M/Mx: observed memory leak in rt_instance block ( rt_locate_instance )
Product-Group=evo		In large scale routing instance config, please provide interval of 20-30 mins for system to stabalize

Resolved In:
PR NumberSynopsisCategory: show route table commands, tracing, and syslog facilities
1757389
Minor		"show route detail" shows "State: " for routes when route-record is enabled
Product-Group=evo		On all Junos and Junos OS Evolved platforms with route-record enabled, some routes will be seen in State: due to race condition. There is no functionality issue, this is a display issue.

Resolved In: evo:22.4R3-EVO evo:22.4R3-S1-EVO evo:23.2R1-S2-EVO evo:23.2R2-EVO evo:23.4R1-S1-EVO evo:24.1R1-EVO evo:24.4R2-EVO junos:23.2R1-S2 junos:23.2R2-J14 junos:23.4R1-S1 junos:24.1R1
PR NumberSynopsisCategory: Resource Reservation Protocol
1792192
Major		Missing HELLO object in RSVP Hello messages after RE failovers in the NSR mode
Product-Group=evo		In rare unknown condition after RE switchover, rsvp hello can have local instance to be zero due to wrong information synced from master RE by mirroring process. When rsvp neighbor is created and never received hello exchange with neighbor, the replication entry which is synced to standby RE will have most of the information as zero, including the local instance, which is used to generate hello object. After RE switchover, rsvp hello will have local instance to be zero due to the wrong information synced from master RE by mirroring process. This is addressed by update the replication entry once all the parameters of the rsvp neighbor is filled, so standby RE will receive the right info, also for future protection, backup RE will avoid creating neighbor until after switchover and setting a new local instance if it is zero.

Resolved In: evo:22.4R3-S7-EVO evo:23.2R2-S4-EVO evo:24.2R2-S4-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:22.4R3-S7 junos:23.2R2-S4 junos:23.4R2-S7 junos:24.4R2 junos:25.2R1 junos:25.3R1
1893822
Major		Record Route Object displayed in show mpls lsp output is trucated if number of hops is sixteen or more
Product-Group=evo		If the number of RSVP LSP hops is sixteen or higher, the RRO displayed in show mpls lsp extensive output may get truncated

Resolved In: evo:23.4R2-S4-J2-EVO evo:24.2R2-S3-EVO evo:24.4R2-EVO evo:25.2R1-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:22.4R3-S7-J1 junos:22.4R3-S8 junos:23.2R2-S5 junos:23.4R2-S7 junos:24.2R2-S3 junos:24.4R2 junos:25.2R1-S2 junos:25.2R2 junos:25.3R1 junos:25.4R1
1896022
Major		More bandwidth admitted onto a TE link when Label Switched Paths (LSPs) undergoing make-before-break re-route over the same link carrying the bypass LSP during local repair
Product-Group=evo		On all Junos and Junos evolved platforms with Point of Local Repair Router, in a Multiprotocol Label Switching(MPLS) Label Switched Paths (LSPs) set-up if the ingress router is configured with link-protection , if Label Switched Paths (LSPs) undergo local repair and subsequently undergo global repair in make-before-break fashion such that the LSPs are re-routed over the same TE link that carries the bypass LSP that protect the LSPs during local repair, then more re-routed LSPs may be admitted on the TE link carrying the bypass LSP than that should be admitted. This may result in some re-routed LSPs remaining on the TE link causing additional traffic sent on the TE link than the capacity of the TE link.

Resolved In: evo:23.2R2-S6-EVO evo:23.4R2-S4-J2-EVO evo:24.2R2-S3-EVO evo:24.4R2-S1-EVO evo:25.2R1-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:22.4R3-S7-J1 junos:23.2R2-S6 junos:23.4R2-S7 junos:24.2R2-S3 junos:24.4R2-S1 junos:25.2R1-S2 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: PTX10K specific platform PRs
1749781
Minor		The Switch Interface Board (SIB) PWR and STAT LEDs will be unlit on PTX10K4/8/16 EVO platforms
Product-Group=evo		On Junos OS Evolved PTX10004/PTX10008/PTX10016 platforms with dual Routing Engines, the Switch Interface Board (SIB) PWR and STAT LEDs will be unlit state after an RE Switchover. This will not have any functional impact.

Resolved In: evo:21.4R3-S6-EVO junos:24.1R1
PR NumberSynopsisCategory: Issues related to control plane security
1860970
Minor		SIB HA wait timeout error upon graceful RE switchover
Product-Group=evo		SSH issue from the Routing Engine to the FPC causes SIB HA timeout error upon RE switchover. All the SIBs will be reset as a result of that.

Resolved In:
PR NumberSynopsisCategory: Bug and Review Tracking for Segment routing traffic eng
1860334
Major		A momentary drop in traffic is observed when changes are applied on multipath SR-TE LSPs
Product-Group=evo		On all Junos and Junos OS EVO (Evolved) platforms, when using SR-TE (Segment Routing-Traffic Engineering) LSP (Label-Switched Path) within a multipath container, a configuration or state change (Eg: modifying the maximum-ecmp value) or a change to the segment-list on one SR-TE LSP, may impact other LSP traffic which are pointing to the same BGP Protocol next-hop. During such event, SR-TE routes are temporarily moved to a hidden state, leading to brief traffic disruption. This occurs because SR-TE is populating route parameters with an unusable next-hop.

Resolved In: evo:23.2R2-S4-EVO evo:24.2R2-S2-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:21.2R3-S6-J26 junos:23.2R2-S4 junos:24.2R2-S2 junos:24.4R2 junos:25.2R1 junos:25.3R1
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:
1798178
Minor		IS-IS Level 2 disabled after upgrade due to OpenConfig YANG model change
Product-Group=evo		On Junos and Junos Evolved platforms that support OpenConfig IS-IS configuration, upgrading to a release where the enabled leaf under the IS-IS levels hierarchy (levels/level/config/enabled) has been deprecated may cause IS-IS Level 2 adjacencies to be disabled during configuration load via load override. This behavior is due to the deprecated YANG model leaf being processed incorrectly during load operations, resulting in Level 2 being automatically disabled and impacting inter-area routing. Configurations applied using manual set commands are not affected.

Resolved In: evo:22.3X80-D42-EVO evo:22.3X80-D43-EVO evo:22.3X80-D47-EVO evo:24.4R2-EVO evo:25.2R2-EVO evo:25.4R1-EVO junos:24.4R2 junos:25.2R1-S2 junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: Issues related to Logging/Tracing, errmsg, eventd infrastruc
1853209
Major		Syslog forwarding intermittently stops post DUT reboot on virtual devices.
Product-Group=evo		On virtual devices, on reboot, vpn may take time to come up. Meanwhile since mgmt_junos is first in the routing table, syslog gets bound to mgmt_junos and hence forwarding stops.

Resolved In: evo:22.3X80-D49-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:22.3X60 junos:23.4R2-S6 junos:24.4R2-S3 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: Issues related to NETCONF
1879816
Major		GNMI get native configuration garbage reply when there is no configuration related to openconfig
Product-Group=evo		The native configuration is observed when there is no configuration related to openconfig but if there are configuration related to openconfig, the native config is not seen. This is just a corner case and no service impact is observed.

Resolved In: evo:24.4R2-EVO evo:25.2R1-S1-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:24.4R2 junos:25.2R1-S1 junos:25.2R2 junos:25.2X30 junos:25.3R1 junos:25.4R1
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:
PR NumberSynopsisCategory: ZT pfe l3 forwarding issues
1474146
Major		For the MPC10E line card, the IS-IS and micro-BFD sessions do not come up during baseline.
Product-Group=evo		For the MPC10E card line, the IS-IS and micro-BFD sessions do not come up during baseline.

Resolved In:

 

Modification History

First publication 2026-01-16