Alert Type

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

Product Affected

PTX QFX running Junos Evolved Software

Alert Description

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

 

Junos Selective Update (JSU) feasible

Not applicable

Call to Action

RECALL: 2025-08-25

We have removed the Junos Evolved software version 23.2R2-S4.7-EVO for PTX10004, PTX10008, and PTX10016 from the Software Download site. The recall is due to an isssue which PTX10016's SIB slot 3 and SIB slot 4 (SIB3 and SIB4) do not come on-line after upgrade to version 23.2R2-S4.7-EVO. While this issue affects PTX10008, and PTX10016, we included PTX10004 since the image is shared for the PTX10004, PTX10008, and PTX10016. This issue is being tracked via PR1900242.

Please discard the software image version 23.2R2-S4.7-EVO that you have downloaded. 

The replacement images are version 23.2R2-S4.8-EVO. These images have been posted on 2025-09-04.

The symptom impacting the SIB3 and SIB4 has the following alarms:

root@ptx10016-re0> show system alarms no-forwarding

72 alarms currently active
Alarm time               Class  Description
2025-08-01 00:00:06 UTC  Major  FPC 0 Self_FOAM fault detected
2025-08-01 00:00:08 UTC  Major  FPC 1 Self_FOAM fault detected
2025-08-01 00:00:08 UTC  Major  FPC 10 Self_FOAM fault detected
2025-08-01 00:00:15 UTC  Major  FPC 11 Self_FOAM fault detected
2025-08-01 00:00:15 UTC  Major  FPC 12 Self_FOAM fault detected
2025-08-01 00:00:20 UTC  Major  FPC 13 Self_FOAM fault detected
2025-08-01 00:00:27 UTC  Major  FPC 14 Self_FOAM fault detected
2025-08-01 00:00:29 UTC  Major  FPC 15 Self_FOAM fault detected
2025-08-01 00:00:49 UTC  Major  FPC 2 Self_FOAM fault detected
2025-08-01 00:00:49 UTC  Major  FPC 3 Self_FOAM fault detected
2025-08-01 00:00:48 UTC  Major  FPC 4 Self_FOAM fault detected
2025-08-01 00:00:48 UTC  Major  FPC 5 Self_FOAM fault detected
2025-08-01 00:00:49 UTC  Major  FPC 6 Self_FOAM fault detected
2025-08-01 00:00:47 UTC  Major  FPC 7 Self_FOAM fault detected
2025-08-01 00:00:49 UTC  Major  FPC 8 Self_FOAM fault detected
2025-08-01 00:01:04 UTC  Major  FPC 9 Self_FOAM fault detected

 

Solution

Junos Software service Release version 23.2R2-S4-EVO is now available.

23.2R2-S4-EVO - List of Fixed issues 

PR NumberSynopsisCategory: MX YT-ZF Linecards Interface Software Category
1846164
Minor		Continuous logging of alarms during a fiber cut with transport devices
Product-Group=evo
Severity=Minor		When a fiber link with transport devices -- such as a repeater -- experiences a cut, the router detects power without valid data, leading to repeated reinitialization attempts and frequent alarms. To avoid continuous logging, alarms are suppressed after several retries while reconnection efforts continue. Normal logging resumes once the physical link is restored.
PR NumberSynopsisCategory: ACX7020 Lite Platform interface issues
1855426
Minor		All the physical links remain down post performing "restart evo-pfemand"
Product-Group=evo
Severity=Minor		On Junos Evolved ACX platforms, all the physical links remain in down condition post restarting "evo-pfemand", due to ports were enabled before the PFE (Packet Forwarding Engine) related modules bringups and configurations.
PR NumberSynopsisCategory: EVO interface software
1857212
Major		Optic Firmware Upgrade script update - to support modules without auto-paging
Product-Group=evo
Severity=Major		This change brings in a software to support firmware upgrade for an optic module with or without auto-paging capability - irrespective of any vendor.
PR NumberSynopsisCategory: PTX10001-36MR Timing
1872162
Major		PTX10001-36MR upon system reboot PTP stays permanent in Frequency Locked Phase Acquiring mode
Product-Group=evo
Severity=Major		On Junos OS Evolved PTX10001-36MR platform having PTP (Precision Time Protocol) with with G.8275.1 profile and SyncE (Synchronous Ethernet) configured, PTP clock synchronization requires proper timestamp between the PTP clock mode and the PFEs (Packet Forwarding Engine). When the device reboots, the PTP clock mode could be initialized before the PFEs are online. This will not activate PTP clock mode in the PFEs, resulting in the PTP lock state being stuck in Acquiring mode, for which PTP synchronization will be impacted.
PR NumberSynopsisCategory: Border Gateway Protocol
1788543
Minor		BGP OutQ counter of one of the BGP peers gets stuck after system reboot/restart routing/clear bgp neighbor
Product-Group=evo
Severity=Minor		On all Junos and Junos Evolved platforms, when there is a high route churn and the system reboot/restart routing/clear bgp neighbor is done, there are some values stuck in the OutQ counter of one of the peers in a group. Due to this, the route updates are not sent which might result in traffic/service impact.
1826685
Minor		Unexpected behaviour after BGP sessions reset for catastrophic BGP configuration changes
Product-Group=evo
Severity=Minor		On Junos and Junos Evolved platforms, when a catastrophic Border Gateway Protocol (BGP) configuration change occurs, creating a new peer structure due to this configuration change, the BGP state transitions from open-sent to established multiple times (until the local device finishes cleaning the old BGP session). This results in traffic impact as the peer is reset multiple times (until a new peer connection is established).
1848939
Major		The CPU for the rpd stuck at 100% on Junos platforms
Product-Group=evo
Severity=Major		On Junos platforms, where BGP import policy is running on a BGP multipath setup and BMP post-policy exclude-non-eligible knob is configured. In such cases when the route change from usable to non-usable state and vice-versa, the route is moved to the end of the peer gateway route list for BMP to process it latter. At the same time, BGP stop_rt cursor (used by BGP import policy) is moved to the end of the peer gateway route list. With some network churn and on-going multipath evaluations, the stop_rt cursor keeps moving to the end of the list for ever. This causes BGP import policy to never converge and CPU remains high for a long time.
1849568
Minor		L3VPN routes are not advertised to peer when BGP sessions with route-target filter flaps
Product-Group=evo
Severity=Minor		On all Junos and Junos OS Evolved platforms, after Border Gateway Protocol (BGP) sessions configured with 'family route-target' flaps, delayed route deletion causes the loss of the Route Target Filter (RTF), preventing the node from advertising L3VPN (Layer 3 Virtual Private Network) and direct routes (e.g., loopbacks and interface routes) to the BGP peer, leading to VPN route loss and service disruption.
1859020
Minor		Incorrect subcode NOTIFICATION is sent when local interface is disabled for which multihop is configured for directly connected peer
Product-Group=evo
Severity=Minor		On all Junos and Junos OS Evolved platforms, when 'multihop' is configured on a directly connected interface towards a peer and the session goes in IDLE state due to no local interface (interface is disabled or down), the log messages shows 'subcode 6 'Other Configuration Change'' instead of 'subcode 9 'Hard Reset''.
1860786
Major		BGP queue deadlock on Junos/Junos OS Evolved/cRPD platforms leading to route advertisement failure and traffic loss
Product-Group=evo
Severity=Major		On all Junos, Junos OS Evolved, and cRPD platforms, due to deadlock in internal processes, BGP (Border Gateway Protocol) route advertisement fails leading to traffic disruption.
1863551
Major		BGP route advertisement failure with as-override and peer-as configured at group level
Product-Group=evo
Severity=Major		On all Junos and Junos OS Evolved platforms, BGP ( Border Gateway Protocol ) fails to advertise routes to external peers in an L3VPN ( Layer 3 Virtual Private Network ) environment when as-override is configured for a neighbor on the local device, and peer-as is applied at the group level. Since the routes are not advertised to peers, traffic matching those routes are dropped, causing service disruption.
PR NumberSynopsisCategory: BGP BMP Software
1839288
Major		BMP soft assert due to counter reset by clear command
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms, when "clear bgp statistics" command is issued while one or more BMP peers are coming up the soft_assert will be hit. This issue has no impact on the traffic or services.
PR NumberSynopsisCategory: BBE Remote Access Server
1812697
Minor		authd core after running ZTP
Product-Group=evo
Severity=Minor		On Junos Evolved platforms, after device has finished booting up with Zero Touch Provisioning (ZTP), authd process will crash and generate a core file.
1813456
Minor		Error message is observed after device is restarted
Product-Group=evo
Severity=Minor		On all Junos Evolved platforms, the error message "UI_SCHEMA_SEQUENCE_ERROR" is observed when device is restarted. There is no traffic impact due to this issue.
PR NumberSynopsisCategory: EVO L3 routing for BCM XGS Platforms
1797319
Major		Traffic drop on AE interfaces when MPLS FRR is enabled
Product-Group=evo
Severity=Major		On the QFX5220 platform, when enabling fast reroute (FRR) on an Multiprotocol Label Switching (MPLS) label-switched path (LSP), traffic drop will be seen if an aggregated ethernet (AE) interface is part of an equal-cost multipath (ECMP) group.
PR NumberSynopsisCategory: Express BT PFE L3 Features
1812239
Critical		The evo-aftmand process crashes on Junos Evolved PTX10002-36QDD, PTX10004, PTX10008, and PTX10016 platforms
Product-Group=evo
Severity=Critical		On Junos Operation System (OS) Evolved PTX10002-36QDD, PTX10004, PTX10008, and PTX10016 platforms, due to a timing issue after rebooting the FPC, the evoaftmand process crashes due to a brief desynchronization between evo-aftman and IfLib, impacting traffic on the affected Flexible Physical Interface Card (PIC) Concentrator (FPC).
1812399
Minor		The evo aftmand-bt crash is observed on Junos Evolved PTX platforms
Product-Group=evo
Severity=Minor		On Junos OS Evolved PTX10001-36MR, PTX10002-36QDD, PTX10003, PTX10004, PTX10008 and PTX10016 platforms, if the device is having hierarchical unilist, then the evo aftmand-bt crash is observed on device reboot and as FPCs keep trying to go into the steady state on reboot, continuous crash can be seen on FPCs as well. This causes impact on service.
1820118
Major		The aftman process crash is observed when IPv6 (IPv6 address with prefix length <= 88) filter configuration on the dsc interface
Product-Group=evo
Severity=Major		On Junos OS Evolved PTX10001-36MR/PTX10008/PTX10016/PTX10004 platforms, the incorrect size lookup for IPv6 address with prefix length <= 88 causes aftman (Advanced Forwarding Management Process) process crash, resulting in traffic impact. The issue happens when IPv6 (IPv6 address with prefix length <= 88) filter configuration on the dsc interface.
1856732
Major		Post configuration changes on an AE interface MPLS traffic is discarded for other interfaces/AE interface on a different FPC
Product-Group=evo
Severity=Major		On Junos Evolved PTX10008, PTX10016, and PTX10004 platforms with JNP10K-LC1201/LC1202 line cards, certain changes to AE interfaces with MPLS (e.g., removing family MPLS, changing MTU, toggling vlan-tagging/encapsulation, or deactivating the AE interface) can cause MPLS traffic drops on other interfaces sharing the same PIC and port number. These drops appear as "normal discard" in show pfe statistics traffic. PTX10003, PTX10001-36, and PTX10002-36QDD are not affected. See also https://kb.juniper.net/TSB93659 [juniper.net]
PR NumberSynopsisCategory: MX304 line card platform software
1849915
Major		FPC reboot due to memory leak from telemetry sensor installation/uninstallation
Product-Group=evo
Severity=Major		On Junos MX204, MX304, MX2010, MX2020, MX10004, MX10008, MX10016 with MPC11, LC2301/LC9600, LMIC16 and LC480 line cards, when installing and uninstalling specific telemetry sensors that export data from LC (Line Card), a few bytes of memory are allocated but not freed, leading to a memory leak. This issue is seen when "sensor-based-stats" is configured and LSP (Link State Path) flaps occur. Each flap triggers repeated installation and uninstallation of the telemetry sensor, accelerating memory consumption. Over time, this exhausts the memory allocated to aft-ulcd process causing FPC (Flexible PIC Concentrator) to reboot.
PR NumberSynopsisCategory: QFX Access Control related
1872280
Major		The l2ald process crash is observed on non L2NG Junos platforms configured with "native-vlan-id" and "bridge-domains" on an IFL
Product-Group=evo
Severity=Major		On non L2NG (Layer2 Next Generation) Junos EX, MX and SRX platforms, the l2ald (Layer 2 Address Learning Daemon) process crash is observed when an IFL (Logical Interface) configured with "native-vlan-id" and "bridge-domains" and when certain config change takes place in an IFL which maps VLAN (Virtual Local Area Network) index to NULL. The dereferencing of this NULL pointer causes the crash.
PR NumberSynopsisCategory: Device Configuration Daemon
1848768
Major		MTU configuration is not applied from the configuration group after commit and "warning" is seen
Product-Group=evo
Severity=Major		When configuring MTU on interfaces through a configuration-group and commit the changes, those are not saved on the configuration file.
PR NumberSynopsisCategory: ACX BFD specific issues
1879925
Major		Traffic disruption is observed when successive switchover is performed having single-hop BFD configured in the dual RE scenario
Product-Group=evo
Severity=Major		On Junos OS Evolved ACX7509, ACX7332, ACX7348 platforms with dual RE, protocol flap is observed when BFD (Bidirectional Forwarding Detection) liveness detection fails, leading to traffic disruption. This issue occurs because the Backup Routing Engine (RE), which takes over as the Master after successive RE switchover, has an incomplete or missing BFD session state. As a result, upon becoming the Master, it is unable to maintain established BFD sessions, triggering routing protocol reconvergence and causing temporary traffic interruption.
PR NumberSynopsisCategory: Host path software for ACX platform
1821807
Major		Excessive logging in various log files is observed on EVO ACX platforms
Product-Group=evo
Severity=Major		On all Junos OS Evolved ACX platforms, the log message 'packetio[10514]: [t:17681] [Info] JUNIPER:: DevDb params are not needed for other platform productId:257' appears in the messages file and the JournalCtl. This message has no functional impact, but it should be logged only once during PFE initialization following a reboot and not continuously.
1851810
Major		The Devdb messages will be seen continuously on ACX EVO platforms
Product-Group=evo
Severity=Major		On ACX EVO platforms, due to the Discard filter programmed and the traffic hitting continuously on the same discard filter, the Devdb messages continuously keeps flooded.
PR NumberSynopsisCategory: VPWS, L2 CKT, EVPN-VPWS
1787689
Major		, After system reboot or RE switch over, syslog messages with "ddsType = "RouteCcc" tpName = "BrcmRtCcc"" are seen.
Product-Group=evo
Severity=Major		On ACX7348, after system reboot or RE switch over, syslog messages with "ddsType = "RouteCcc" tpName = "BrcmRtCcc"" are seen. These messages won't cause any service or traffic impact.
PR NumberSynopsisCategory: Layer 3 forwarding, both v4+v6
1854763
Minor		The post-convergence-lfa configuration causes a suboptimal-routing
Product-Group=evo
Severity=Minor		A suboptimal routing of traffic can be seen post configuring the post-convergence-lfa due to failover ID miss programming in the PFE.
PR NumberSynopsisCategory: BGP MPLS VPN specific issues
1865858
Major		The FEC leak will be seen on all ACX EVO platforms
Product-Group=evo
Severity=Major		On all Junos OS Evolved ACX platforms, the hardware FEC (Forwarding Equivalence Class) resource leak will be seen when the programming of the MPLS (Multi-Protocol Label Switching) labels associated with the unilist nexthops fails due to any reason, which will lead to FEC resource exhaustion over time. As a result, further unilist NHIDs (Next-Hop IDs) can't be installed in the PFE (packet Forwarding Engine), resulting in traffic loss.
PR NumberSynopsisCategory: sflow issues on ACX platforms
1814306
Minor		Memory leak due to sFlow resource not releasing the allocated memory on Junos OS Evolved ACX platforms
Product-Group=evo
Severity=Minor		On Junos OS Evolved ACX platforms with sFlow (Sampled Flow) configured, memory exhaustion resulting in device reboot for sFlow resource not releasing the allocated memory, leading to memory leak over the course of time.
PR NumberSynopsisCategory: DNX VPLS
1807349
Critical		Traffic drop is observed when evo-pfemand is restarted in VPLS scenario
Product-Group=evo
Severity=Critical		On Junos Evolved ACX platforms, when Virtual Private LAN Service (VPLS) is configured, on restarting evo-pfemand deamon, the VPLS next-hop lookup fails, impacting traffic.
PR NumberSynopsisCategory: EVO Netstack FIB Service Daemon
1860358
Major		File Descriptor leak in fibd process leads to core files of different processes such as Jade, SSHd and Stunnel.
Product-Group=evo
Severity=Major		On Junos OS Evolved platforms, when fibd reaches the process limit on the maximum number of allowed open file descriptors, fibd is unable to open new file descriptors and track new reader processes. Given this, processes such as Jade, SSHd and Stunnel are not found by fibd, triggering the core files for these processes affecting device management and Tx/Rx packet process. The Soft Limit value within the "cat /proc//limits" output command will show the maximum number of file descriptors that fibd can have opened.
PR NumberSynopsisCategory: Firewall related development
1804699
Major		Firewall filters behaves unexpectedly after kfirewall-agent restart
Product-Group=evo
Severity=Major		Due to inconsistency between programmed firewall rules when there are large prefix lists in kernel, when or if kfirewall-agent is restarted, firewall programming post restart may not work as expected.
PR NumberSynopsisCategory: EVO Netstack icmpd
1795667
Major		evo, traceroute's final hop to lo0 addr responds with intf addr rather than lo0 addr
Product-Group=evo
Severity=Major		Synopsis: Incorrect local address selection when traceroute command issued. Symptom: The selected local address may not match the intended interface address. The traceroute output shows an unexpected or incorrect source address. Problem: In some deployments, this may lead to misleading diagnostics or incorrect path analysis due to improper local address selection by the Routing Engine.
1822994
Minor		DNS (Domain Name System) resolution fails when nameserver is reachable via a routing instance bound to a line card port on releases prior to 24.1R1-Junos OS Evolved
Product-Group=evo
Severity=Minor		On Junos OS Evolved based platforms, while using ping, traceroute, or other utility that requires host name resolution, an error is raised indicating hostname resolution has failed.
PR NumberSynopsisCategory: Issues related to EVO dependency layer including object graphs, incompletes, anomalies and nkdb
1857091
Major		evo-aftmand-bt crash on Junos OS Evolved platforms triggered by rapid interface or route changes
Product-Group=evo
Severity=Major		On Junos OS Evolved platforms, the evo-aftmand-bt process crashes in a rare scenario involving rapid interface changes, such as interface flaps, configuration modifications, or reboots occurring within a short time interval. This crash results in a Packet Forwarding Engine (PFE) restart and traffic loss.
PR NumberSynopsisCategory: Issues related to debug utilties - objmon, objshell/Dashboard
1827914
Minor		NETCONF output for unsuccessful ping is empty
Product-Group=evo
Severity=Minor		On all Junos Evolved platforms, when a ping is initiated using NETCONF RPC to a destination which is unreachable, the expected output corresponding to an unsuccessful ping is seen to be empty in the NETCONF RPC response. This is a cosmetic issue.
1835388
Major		The Netconf output for xml format shows tag under ping failure situation
Product-Group=evo
Severity=Major		On all Junos OS Evolved platforms, the Netconf output for xml format shows tag under ping failure situation. It is only an XML display output issue and has no impact to network traffic.
1838074
Minor		Serial Console Stops Working After Cable Reconnection
Product-Group=evo
Severity=Minor		On Junos OS Evolved platforms, the serial console may stop functioning, displaying a blank output, after one or more physical disconnections and reconnections of the console cable. The use of intermediate cable adapters or unreliable cables can exacerbate this issue.
PR NumberSynopsisCategory: Interface PRs defect & enhancement requests
1824753
Minor		The Junos-Evolved OS does not encode special/multi-byte characters properly in CLI/RPC XML output
Product-Group=evo
Severity=Minor		In all Junos-Evolved Operating Systems (OS), special characters entered in the description field of the set interfaces command in the Command Line Interface (CLI) may not be correctly encoded in XML outputs. This is a cosmetic issue.
1859501
Minor		Interfaces with the same outer VLAN ID but different inner vlans or inner-lists/ranges are reporting a commit error
Product-Group=evo
Severity=Minor		On all Junos OS Evolved platforms, When an interface configured with the same outer VLAN ID but with different inner vlans or inner-lists/ranges, reports a commit error.
1867231
Major		Transit multicast traffic is getting blackhole due to peer interface flap
Product-Group=evo
Severity=Major		On Junos OS Evolved platforms, when peer interface flaps which connected to AE (Aggregated Ethernet) interface leading to synchronization of the interface up events with PFE (Packet Forwarding Engine) gets delayed. This issue results in the transit multicast traffic getting blackhole.
1867603
Major		Coredump during LAG disable
Product-Group=evo
Severity=Major		Pre-conditions are: 1. Aggregate Ethernet interface is configured with/without lacp 2. Aggregate Ethernet interface is configured with BFD configs. Trigger is: 3. With the specified configuration, if any config change is issued on AE IFL then it results in aggd core. 4. One such example is [edit interfaces ae2301 unit 0] + disable; There is no work-around, so none is mentined.
PR NumberSynopsisCategory: jdhcpd daemon refactored for evo
1817061
Major		EVO(EVPN Fabric): DHCP packets are getting relayed even after deleting the dhcp relay configuration from the leaf
Product-Group=evo
Severity=Major		DHCP packets will get relayed even after deleting the DHCP realy configuration for the irb.
PR NumberSynopsisCategory: EVO L2 Control Plane PRs
1844623
Major		Stale MAC-IP entries are not cleared in an EVPN-VXLAN scenario when encapsulate-inner-vlan or decapsulate-accept-inner-vlan or both knobs are present
Product-Group=evo
Severity=Major		On all Junos and Junos OS Evolved platforms, when decapsulate-accept-inner-vlan or encapsulate-inner-vlan or both knobs are configured for a VXLAN (Virtual Extensible Local Area Network) and when any action corresponding to MAC-IP entries cleanup takes place, the MAC-IP entries will not be cleaned up from kernel. This will result in anomalies in device and could also lead to a core crash.
1852152
Major		The l2ald-agent process crashes when the scale of IFBDs within a single VLAN exceeds the capacity of the Rx rtsock buffer, causing an overflow
Product-Group=evo
Severity=Major		On all Junos OS Evolved platforms, scaling of IFBDs (Interface Family Bridge Domain) within a single VLAN(Virtual Local Area Network) will result in the formation of rtsock messages that exceed the Rx size of the rtsock buffer (8192 bytes). This will cause the l2ald-agent (Layer 2 Address Learning Daemon) process to crash. There will be no traffic impact.
PR NumberSynopsisCategory: Lacp related problems and issues.
1859633
Minor		LACP session destroy time is not getting updated in PFE
Product-Group=evo
Severity=Minor		On all Junos Evolved platforms, the LACP session destroys time is not being updated in the PFE due to the session history limit being exceeded (50 sessions). This issue does not cause a functional impact but generates unnecessary log messages, which can be misleading to users.
PR NumberSynopsisCategory: Express ptx-evo PFE L3 Features
1819887
Major		If the notify for a client fails, it should not affect the other clients
Product-Group=evo
Severity=Major		In EVO based systems, If the notify for a client was failing, the code falls through and remaining clients were not getting the notification. Now the other clients willl still get updated.
PR NumberSynopsisCategory: Express PFE MPLS for EVO platforms
1847169
Major		Traffic going over LDP or LDPoRSVP route matching the CBF is getting impacted when PTX EVO platform working as PHP router with CBF configuration
Product-Group=evo
Severity=Major		Traffic hitting Penultimate Hop Popping router and matching the class based forwarding (CBF) is affected when Junos OS Evolved PTX platform acting as PHP router with CBF configuration. This will impact traffic going over affected LDP or LDPoRSVP route. Also, it will cause ping and trace route failure.
1861803
Minor		Control plane is not properly managing the label 1048575 for MPLS traffic, leading to service impact
Product-Group=evo
Severity=Minor		On PTX Evolved platforms, the control plane is incorrectly using label 1048575 for MPLS (Multiprotocol Label Switching) traffic, this label is being changed to the NULL label 3, as if it corresponds to a non-MPLS packet, resulting in the label being popped, leading to all traffic associated to these MPLS threads to be dropped.
PR NumberSynopsisCategory: event/op/commit scripts, SLAX, netconf issues
1836806
Major		Rest API service will not launch on EVO devices when the server address is configured as any interface IP (excluding management interface IP).
Product-Group=evo
Severity=Major		Rest API service will not launch on EVO devices when the server address is configured as any interface IP (excluding management interface IP).
1847814
Major		Unable to run event scripts for events: system_abnormal_shutdown/system_shutdown/system_reboot_event
Product-Group=evo
Severity=Major		* system_abnormal_shutdown * system_shutdown Above events are not supported in EVO. These events cannot be used in scripts. Hence the event tags have been removed for EVO.
PR NumberSynopsisCategory: eventd, syslog infra issues
1815238
Minor		PTX10004 - Host-name is not updated in picd logs
Product-Group=evo
Severity=Minor		On Junos OS Evolved platforms, host-name was not appended to PICD logs.
PR NumberSynopsisCategory: SNMP, mib2d issues
1792360
Major		The SNMPv3 Authentication error is observed
Product-Group=evo
Severity=Major		On All Junos Evolved platforms, the Simple Network Management Protocol version 3 (SNMPv3) Authentication error is observed at Network Management System (NMS) side as routing engine switch over causes change in engine-id and SNMPv3 requests sent to the server will fail.
1836012
Minor		The mib2d memory increase observed during 24 hours testing
Product-Group=evo
Severity=Minor		On all Junos OS Evolved platforms, mib2d memory leak may be observed when querying ip, tcp, udp, jnxIpv6GlobalStats and jnxIcmpv6GlobalStats scalar mib objects.
PR NumberSynopsisCategory: EVPN control plane issues
1830295
Major		An enhancement to improve BGP performance
Product-Group=evo
Severity=Major		On all platforms, Border Gateway Protocol (BGP) will have a performance degradation causing high CPU utilization.
1839959
Critical		The MAC+IP table and mac-table are not in sync in the EVPN-MPLS active-active multihomed scenario leading to traffic loss
Product-Group=evo
Severity=Critical		On all Junos and Junos OS Evolved platforms that supports ESI lag interface and in an EVPN-MPLS (Ethernet Virtual Private Network - Multi Protocol Label Switching) active-active multihomed scenario, when the multihomed access interfaces are flapped in quick succession, it results in an unresolved destination route for the specific IP host. This is occurred due to race condition within l2ald (Layer 2 Address learning daemon) followed by an interface flap which causes the locally learned MAC to go missing from the mac-table on the other PE router.
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1833660
Major		Stale MAC entries may remain in the MAC table of EVPN routing instances after rapid MAC-IP move scenarios
Product-Group=evo
Severity=Major		On all Junos OS and Junos OS Evolved platforms with EVPN-MPLS (Ethernet Virtual Private Network - Multiprotocol Label Switching) setup , stale MAC entries may remain in the MAC table of the EVPN (Ethernet Virtual Private Network) routing instances during rapid MAC-IP move scenarios. This can cause MAC tables to reach their limits preventing new MAC addresses learning and user registration.
PR NumberSynopsisCategory: Express AFT Common FW issues
1811761
Critical		The evo-cda-bt crash is observed on Junos Evolved platforms
Product-Group=evo
Severity=Critical		In the PLCT page read on failure of read instead od returning 0 cda API return EFAIL as return value, which causes un wanted memory writes in upper layer casuing the crash. Fix Details: Fix the API to reutrn 0 in case failure instead of EFAIL, changed other places also where issue was seen.
PR NumberSynopsisCategory: Express PFE FW Features
1790275
Major		Incorrect peak utilization shown in show npu memory info due to touched bucket method
Product-Group=evo
Severity=Major		On Junos OS Evolved platforms, peak utilization for Key Hash Table (KHT) resources is computed using the "touched bucket" method, where a bucket is marked as used if any of its three cells are occupied. This calculation inflates the actual resource usage. The logic has been updated to use the "scaled bucket" method, which accounts for unutilized cells within a bucket and provides a more accurate and consistent peak utilization value aligned with instant usage metrics.
1853326
Major		FLT alpha algorithm gracefully rollback support.
Product-Group=evo
Severity=Major		When scaled prefixes are used as part of filter match conditions, there's a risk of encountering resource issues that can cause allocation failures leading to improper rollback of recently configured prefixes in the alpha/hash table. Specifically, when hash entries are rolled back due to these failures, their state remains unchanged, leading to potential prefix programming issues and causing Alpha/Hash entry corruption and an Evo-aftmand crash. Solution: The fix now addresses this issue by tracking the state of hash table entries. In case of resource-related allocation failures, the rollback method will reset both the hash entry states and prefixes, ensuring a stable system for any future prefix programming operations.
1862048
Major		NPU's (Network Processing Unit) KHT (Kernal Hash Table) utilization shows 100% utilization post config commit
Product-Group=evo
Severity=Major		On Junos Evolved platforms, NPU's KHT utilization shows 100% utilization post config commit
PR NumberSynopsisCategory: ACX7332 ACX7348 Interfaces software
1870528
Major		Interface down is observed while configuring 1G speed on ACX7332/ACX7348/ACX7509 platforms
Product-Group=evo
Severity=Major		On Junos OS Evolved ACX7332/ACX7348/ACX7509 platforms, physical interface goes down on configuring 1G speed after the first boot with or without auto-negotiation.
PR NumberSynopsisCategory: ACX7509 platform, FEB, RCB and linecaard resi
1863708
Major		The picd process crashes on Junos OS Evolved ACX7509 platforms during RE switchover
Product-Group=evo
Severity=Major		On Junos OS Evolved ACX7509 platforms with GRES (Graceful Routing Engine Switchover) and NSR (Nonstop Active Routing) enabled, picd process crash is seen with protocol flaps during Route Engine (RE) switchover which results in interface going down and further results in protocols going down.
PR NumberSynopsisCategory: ACX7509 Linecard (FPC) related issues
1791632
Major		"BrcmPlusPfe: Phy Time Clear Config Set Failed. Invalid configuration" error seen with evo-pfemand restart
Product-Group=evo
Severity=Major		On Junos Evolved platforms, "[Error] BrcmPlusPfe: Phy Time Clear Config Set Failed. Invalid configuration" error is seen with evo-pfemand restart.
1840790
Minor		ACX7509 : LACP interfaces stuck in Attached state.
Product-Group=evo
Severity=Minor		On Junos OS Evolved ACX7509 platforms, due to multiple RE(Routing Engine) Switchover traffic drop will be observed.
PR NumberSynopsisCategory: Libjtask for RPD tasks, scheduler, timers, memory, and slip
1846294
Major		Memory Leak: Memory leak is detected with rpd task blocks "rpd-trace"
Product-Group=evo
Severity=Major		Memory Leak: Memory leak is detected with rpd task blocks "rpd-trace"
PR NumberSynopsisCategory: ISIS routing protocol
1777702
Minor		The rpd process crashes after multiple iterations of disable/enable ISIS protocol
Product-Group=evo
Severity=Minor		On all Junos and Junos Evolved platforms, the rpd process crashes after disabling/enabling the ISIS (Intermediate System-to-Intermediate System) protocol using the set command. The issue is seen after 2-3 hours of continuous disabling, and enabling the ISIS process with a 90-sec interval.
PR NumberSynopsisCategory: Layer 2 Control Module
1855088
Major		In Junos EX and QFX platforms, when ERPS protocol is enabled on a ISL trunk, the commit command fails
Product-Group=evo
Severity=Major		In Junos EX and QFX platforms, when a port is configured with Inter-switch-link (ISL) trunk and the Ethernet ring protection switching (ERPS) protocol is enabled on the port, the commit command fails, causing the commit-check daemon process to crash and preventing the new configuration from being applied. This doesn't impact the devices traffic, performance, or management.
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1838335
Critical		High FPC CPU utilisation and local MAC learning failure in EVPN-MPLS scenario due to rapid MAC moves
Product-Group=evo
Severity=Critical		On all Junos platforms (except MX platforms with MPC10, MPC11, LC9600) with Ethernet Virtual Private Network (VPN) - Multiprotocol Label Switching (EVPN-MPLS) configured, Media Access Control (MAC) learning failure and high CPU utilisation in FPC is seen due to rapid MAC moves and incorrect interface state in Packet Forwarding Engine (PFE).
PR NumberSynopsisCategory: lacp protocol
1874126
Major		AE member not able to discover lost LACP peer connection leading to traffic black-holing
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms, when a loop occurs in the transmission switch, the device starts receiving looped LACP (Link Aggregation Control Protocol) PDU's from itself, instead of messages from the actual peer device. This causes the system to mistakenly believe that a valid LACP connection exists, even though the peer device is not actually connected.As a result, it continues to forward traffic as if the peer were active. Since no valid peer connection is present, this can lead to traffic blackholing .
PR NumberSynopsisCategory: Issues related to Junos licensing infrastructure
1808956
Major		The syslog "LICENSE_EXPIRED" are not seen when license gets expired"
Product-Group=evo
Severity=Major
PR NumberSynopsisCategory: Port-based link layer security services and protocols that a
1847418
Major		MACSec fails after applying MACSec configuration on IFL and removing it
Product-Group=evo
Severity=Major		On MX devices with MPC10 linecard when applying Media Access Control Security (MACSec) configuration on IFL and removing it, MACSec negotiation fails and complete traffic blackholing.
PR NumberSynopsisCategory: Multiprotocol Label Switching
1773796
Minor		The LSP name and bandwidth values are displayed continuously in "show mpls lsp autobandwidth name X" command
Product-Group=evo
Severity=Minor		In "show mpls lsp autobandwidth name X" command when the name of the Link State Packet (LSP) is greater than 21 characters, the first column with LSP name and the second column with the Last bandwidth are merged.
1802244
Minor		Traffic loss is seen during the LSP re-optimisation MBB process
Product-Group=evo
Severity=Minor		On Junos and Junos Evolved platforms with link/Node protection configured, when the tunnel local repair patherr or link down event arrives at the ingress for the new instance i.e. PSB2 (Path State Block) while a path in MBB (Make Before Break) is waiting for the old instance (PSB1) teardown results in traffic loss if P2B2 is carrying traffic at that time.
PR NumberSynopsisCategory: Multicast Routing
1863470
Major		The rpd crash due to memory corruption in PIM/MSDP network
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms, enabling PIM (Protocol Independent Multicast) or MSDP (Multicast Source Discovery Protocol) may cause a rare memory corruption during the update of the MSDP Source Active route. This issue primarily affects highly scaled environments, leading to rpd (routing protocol daemon) coredumps and potential traffic loss.
PR NumberSynopsisCategory: RPD infrastructure issues related to NSR, GRES, switchover, 
1848313
Major		OSPF neighbours go down due to link flapping after NSR switchover on Junos OS Evolved platforms with IPSEC configuration
Product-Group=evo
Severity=Major		OSPF neighborship goes down after NSR (Nonstop routing) switchover due to link flapping on Junos OS Evolved platforms with Dual RE and IPSEC configuration.
PR NumberSynopsisCategory: RPD Interfaces related issues
1850620
Minor		When BGP RIB Sharding is enabled, new BGP group/peer added gets stuck at Flags: 
Product-Group=evo
Severity=Minor		On Junos OS and Junos Evolved platforms, when BGP RIB Sharding is enabled, new BGP group/peer added gets stuck at Flags: . Route is established but freezes by sending 0 size window and the peer stops sending routes then, after some time the remote side tears the session down.
PR NumberSynopsisCategory: KRT Queue issues within RPD
1801382
Minor		Memory Leak in the rpd Process During Protocol Deactivation/Activation
Product-Group=evo
Severity=Minor		On all Junos and Junos Evolved platforms, A memory leak occurs during protocol, routing instance, or interface deactivation/activation, linked to improper IPv6 Interface Address (IFA) reference handling in the " ifx_dist_msg " process. This can lead to rpd crashes and service disruptions.
1834859
Major		The RPD crashes after executing "show krt error-statistics errorno X"
Product-Group=evo
Severity=Major		Please do not issue the "show krt error-statistics errorno ..." stanza. This command causes RPD to restart unexpectedly.
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1793196
Major		Multicast traffic black-holing upon MoFRR primary link went down
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms, when MoFRR (Multicast-only fast reroute) is configured with NSR (Non-stop routing) while interface flapping or RE switchover, there is a next-hop leak and the next-hop in RIB (Routing Information Base) is different from the next-hop in FIB (Forwarding information base) due to that multicast traffic will be impacted.
1848971
Major		Configuring BGP rib-sharding and generate route will cause rpd process to crash
Product-Group=evo
Severity=Major		On Junos and Junos OS Evolved platforms, configuring BGP (Border Gateway Protocol) rib-sharding and generate routes will cause the rpd process to crash.
1863248
Major		On all Junos OS Evolved platforms, traffic loss will be seen after switching the LSP from SRTE to L-ISIS
Product-Group=evo
Severity=Major		On all Junos OS Evolved platforms with Segment Routing Traffic-Engineering (SRTE) and Labeled- Intermediate System- Intermediate System (L-ISIS) configuration, when a service route is resolved over SRTE route in inet6color.0 and if the SRTE path in inet6color.0 is deactivated/goes down, the SRTE route is deleted and service route starts resolving over L-ISIS. However traffic loss for 20 minutes or more is seen after switching the Label Switched path (LSP) from SRTE to L-ISIS path.
PR NumberSynopsisCategory: Shard routing infrastructure within RPD
1845425
Major		Traffic blackhole is observed for IPv4 /32 LDP prefixes advertised over BGP-LU when BGP sharding is configured
Product-Group=evo
Severity=Major		On Junos OS MX and Junos OS Evolved PTX platforms with MPLS (Multiprotocol Label Switching) and BGP (Border Gateway Protocol) sharding configured, the route is not resolved as the resolver does not request PNH (Protocol Next Hop) information from RaaS (Routing as a Service) server although BGP added the route resolution in the inet.3 table. This issue leads to IPv4 /32 LDP (Label Distribution Protocol) prefixes advertised over BGP-LU (BGP Label Unicast) not being installed in the mpls.0 table i.e. corresponding labels being marked as hidden in the MPLS routing table (mpls.0), preventing proper traffic forwarding, leading to a traffic blackhole.
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1813582
Minor		Static route refreshes age when commit full is performed
Product-Group=evo
Severity=Minor		On all Junos and Junos OS Evolved platforms, with import policy defined in the rib-group and commit full is performed, static route refreshes age. There is no service impact due to this issue. This issue is not seen with normal commit.
1832366
Major		performance optimizations for route resolution
Product-Group=evo
Severity=Major		Performance optimizations have been implemented in the managing resolution of bgp indirect nexthop. Improving the efficiency of these operations helps reduce latency during route updates and enhances overall convergence performance.
1849202
Major		BGP route still seen in routing table when route not available
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms , the router learns routes through the BGP (Border Gateway Protocol) and has the feature: "BGP RIB Sharding" enabled for IPv4. These routes are stored in the Inet.0 routing table. Later, if the neighbor that announced this route or the protocols associated with the routing table of the used VRF (Virtual Routing and Forwarding) are removed, the route remains in the routing table, and hence traffic is forwarded to the stale routes.
PR NumberSynopsisCategory: show route table commands, tracing, and syslog facilities
1804363
Critical		The rpd process crash can be seen in restoration to baseline configuration in scaled scenario
Product-Group=evo
Severity=Critical		On all Junos and Junos OS Evolved platforms with dual RE, restoring from a scaled configuration (with BGP and Auto route-distinguisher instances) to baseline configuration (without BGP and Auto-RD), and then back to scaled configuration, leads to rpd process crash on the master RE.
1808481
Minor		The error message "sysctl kern.corefile not supported" is seen for multiple daemons during daemon initialisation
Product-Group=evo
Severity=Minor		On all Junos Evolved platforms, while executing "show log messages", error message "sysctl kern.corefile not supported" is seen which is introduced during daemon initialisation.
PR NumberSynopsisCategory: Resource Reservation Protocol
1792192
Major		Missing HELLO object in RSVP Hello messages after RE failovers in the NSR mode
Product-Group=evo
Severity=Major		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.
1819948
Minor		LSP re-optimization issue has been observed
Product-Group=evo
Severity=Minor		On all Junos and Junos Evolved platforms, the LSP (Label Switched Path) re-optimization issue has been observed. LSP bandwidth change is unsuccessful due to bandwidth unavailable RSVP (Resource Reservation Protocol) PathErr.
1823215
Minor		Bypass re-optimisation not taking SRLG or fate-sharing into account when protected link is down
Product-Group=evo
Severity=Minor		On all MX and PTX platforms, In RSVP-TE (Resource Reservation Protocol-Traffic Engineering) scenario, when interface protected by bypass LSP (Label Switched Path) goes down, re-optimization of bypass can leads to unexpected path selection due to non consideration of SRLG (Shared Risk Link Group) or fate-sharing information with respect to protected interface during CSPF (Constrained Shortest Path First) path computation, could result in traffic impact due to this unexpected path selection.
1837770
Major		mgd timeout communicating with routing daemon rpd for 30 minutes during RSVP MBB event
Product-Group=evo
Severity=Major		On all Junos OS platforms, Management Daemon (MGD) on a Junos device was unable to communicate with the Routing Protocol Daemon (RPD) for an extended period during a Make Before Break (MBB) event for RSVP signaling. This issue is seen mostly under high scale mpls label switch paths.
1864949
Major		User traffic dropped after ISIS went down on one side with trapcode observed
Product-Group=evo
Severity=Major		On all JUNOS and JUNOS evolved Operating Systems, if a link along the path of a Label Switched Path (LSP) flaps briefly such that the router at upstream end of the flapping link does not detect the link down but only the router at the downstream end does, then the upstream router does not undertake necessary actions, like generating ResvTear message, that should be taken after next-hop link down. This will result in unexpected traffic blackholing on the router at the downstream end of the flapping link.
PR NumberSynopsisCategory: PTX10K Line Card specific interface PRs
1814606
Major		Extra Link Flap During Xcvr Rx LOS
Product-Group=evo
Severity=Major		During a short loss of link due to a Xcvr loss of signal, there was a rare occurrence where the interface would report an extra link flap. This was a result of the interface link coming up at the same time the interface was retuned to the new signal. This is a momentary issue and the interface will self recover within a few seconds. No special actions need to be taken.
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
Severity=Major		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.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1751025
Major		User key mismatch will be observed when ssh key has more than 1024 characters
Product-Group=evo
Severity=Major		On all Junos and Junos OS Evolved platforms, ssh host key configured under system services is limited to taking only up to 1024 characters. So any key with more than 1024 characters won't be getting the full content of the certificate file. Only partial content will be stored in the attribute and user key mismatch will be observed.
1854070
Minor		cli coredump genarated when the size of buffer area (user input) increased to 1GB
Product-Group=evo
Severity=Minor		Cli coredump genarated when the size of buffer area (user input) increased to 1GB.
PR NumberSynopsisCategory: Issues related to Logging/Tracing, errmsg, eventd infrastruc
1814980
Major		The eventd crash is observed on Junos and Junos Evolved platforms
Product-Group=evo
Severity=Major		On Junos and Junos OS Evolved platform, when syslog over TLS is configured, empty hostnames are generated in logs. The logging will be briefly affected since eventd is cored.
PR NumberSynopsisCategory: Virtual Private LAN Services
1797423
Major		Memory leak is observed for the VPLS CE facing interface on all Junos and Junos Evolved platforms
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms memory leak in task_timer block is observed for Virtual Private LAN Service (VPLS) CE facing interface. These leaks are configuration driven and can happen when VPLS instance configuration is deleted or probably when CE interface moves across VPLS instances or deleted from the VPLS instance.
PR NumberSynopsisCategory: Express ZX PFE L3 Features
1867003
Major		IS-IS adjacency between CE devices is not established over L2 circuit
Product-Group=evo
Severity=Major		On Junos OS Evolved PTX10003 platform, In scenario where IS-IS (Intermediate System to Intermediate System) adjacency forming between CE (Customer Edge) devices over Layer2 circuit ("encapsulation vlan-ccc") through PTX10003 as a PE (Provider Edge) in this connectivity, IS-IS hello (IIH) packets from host CE incorrectly direct to connected PE instead of forwarding it to the remote CE over this Layer2 circuit. This is causing failure to establish the IS-IS adjacency between the CE devices. In certain upgrade scenarios where a PE device is upgraded to an affected release, the IS-IS adjacency between the CE devices may fail to establish causing service imapct.

 

 

23.2R2-S4-EVO - List of Known issues 

PR NumberSynopsisCategory: Issues with pluggable optics
1849814
Minor		Extend the interfaces optics-options configuration of dp init max duration for 400G ZR-M-HP optical transceiver
Product-Group=evo		A 400G ZR-M-HP optical transceiver may go into fault state when initialized, configured, or upgrade. This caused by the module's FW advertising a "MaxDurationDPInit" value that is shorter than the time required to initialize the data path of the module. On a 400G-ZR-M-HP module, the max DP init completion time has been extended to 5 minutes.

Resolved In: evo:23.4R2-S4-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:23.4R2-S4 junos:24.4R2 junos:25.2R1
PR NumberSynopsisCategory: Border Gateway Protocol
1853025
Major		Updating a source-file to load ROAs should be done by changing the name of the source file
Product-Group=evo		Loading ROAs from a source-file was a feature introduced as a convenience feature and as such this only affects that feature. This feature is not in widespread use and was created to have a fallback ROA when all sessions go down. This problem scenario requires multiple reloads with the being modified back and forth to add and then delete and re-add the database configured in the import policy.

Resolved In: evo:22.4R3-S7-EVO evo:23.4R2-S5-EVO evo:24.2R2-S2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:22.4R3-S7 junos:23.2R2-S5 junos:23.4R2-S2-J13 junos:23.4R2-S5 junos:24.2R2-S2 junos:24.4R2 junos:25.2R1 junos:25.3R1
1875144
Minor		Longer convergence is seen for a BGP neighbor having validation configured in its import policy
Product-Group=evo		On all Junos and Junos Evolved platform, when any BGP peer has validation policy configured for import, it is observed that there is an extra walk to re-evaluate the routes in the loc-rib for validation even though the policy/unrelated configuration is changed for an unrelated peer.

Resolved In: evo:23.4R2-S5-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:22.4R3-S7 junos:23.4R2-S5 junos:24.4R2 junos:25.2R1 junos:25.3R1
1875834
Major		On switchover on ACX7509, L3VPN some of the prefixes traffic hit is around 1-5secs
Product-Group=evo		On switchover on ACX7509, L3VPN some of the prefixes traffic hit is around 1-5secs. Some of the prefixes seen traffic drop in terms of seconds after NSR switchover and issue is not consistent. It is not a continuous traffic drop and it recovers.

Resolved In:
PR NumberSynopsisCategory: PTX10003 Interface related issues
1851078
Major		Configuration of ZR optics(400G) is not available on PTX platforms
Product-Group=evo		On PTX10003 systems, it is not allowed to configure ZR optics (400G) through CLI.

Resolved In: evo:23.2R2-S3-EVO junos:23.2R2-S4
PR NumberSynopsisCategory: PTX10003 Platform related issues
1805380
Minor		The correct number of FPCs are not being listed
Product-Group=evo		On PTX10003 platforms, the correct number of Flexible PIC Concentrators (FPCs) are not being listed when requesting the output from Packet Forwarding Engine (PFE).

Resolved In: evo:23.2R2-S3-EVO evo:23.4R2-S4-EVO evo:24.3R1-EVO junos:23.4R2-S4 junos:24.3R1
PR NumberSynopsisCategory: Express BT PFE L3 Features
1784498
Minor		Higher AE traffic convergence observed in ALB configured AE interface
Product-Group=evo		On PTX10001-36MR/PTX10004/PTX10008 and PTX10016 platforms, if Adaptive load balancing (ALB) is configured on AE (Aggregated Ethernet) interface and link up/down, the AE interfaces will take higher traffic convergence during FRR (Fast Reroute) compared to regular AE.

Resolved In: evo:22.2R3-S5-EVO evo:22.4R3-S5-EVO evo:23.4R2-EVO evo:23.4R2-S1-EVO evo:24.2R2-EVO evo:24.3R1-EVO junos:24.2R2 junos:24.3R1
1859044
Major		The IPv6 firewall filter applied on loopback 0 Is not processing NS and NA packets.
Product-Group=evo		On PTX platforms running the Junos Evolved Operating System (OS), an Internet Protocol Version 6 (IPv6) filter applied to the Loopback 0 interface does not process incoming Neighbor Solicitation (NS) and Neighbor Advertisement (NA) packets in the Neighbor Discovery Protocol (NDP), though it does not impact traffic.

Resolved In: evo:23.4R2-S5-EVO evo:24.2R2-S1-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO
PR NumberSynopsisCategory: MX304 timing software
1869538
Minor		PTP FPGA ethernet interface down and cause PTP stuck in initializing state
Product-Group=evo		On Junos OS Evolved platforms and MX304 device with PTP (Precision Time Protocol) enabled, on bootup or FPC reboot, device will encounter issues with time synchronization, including devices going out of phase, disconnecting, or remaining in freerun state, potentially impacting applications that rely on precise timing. PTP will be stuck in initializing state.

Resolved In: evo:23.4R2-S5-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:23.4R2-S5 junos:24.4R2 junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: ACX BFD specific issues
1866553
Major		On ACX7K platforms, BFD sessions with may flap while updating prefix list of firewall filter. It depends on the BFD timers and firewall filter terms scale
Product-Group=evo		On ACX7K platforms, BFD sessions with may flap while updating prefix list of loopback/RE firewall filter. It depends on the BFD timers and firewall filter terms scale.

Resolved In:
PR NumberSynopsisCategory: CoS support on DNX
1793256
Major		Error messages are populating "getQosRewriteHwMapIdFromIflIndex" and interface ifd queue stats traffic is going to the wrong queue
Product-Group=evo		ACX7509 :: Observing Error messages are populating "getQosRewriteHwMapIdFromIflIndex" and verify interface ifd queue stats traffic is going to wrong queue"

Resolved In: evo:23.4R2-EVO evo:24.2R1-EVO evo:24.2R1-S2-EVO evo:24.2R2-EVO evo:24.3R1-EVO
1839055
Major		Junos Evolved ACX7k platforms may experience packet drops due to a delay in route update
Product-Group=evo		Junos Evolved ACX7k platforms may experience delays in route programming on handling AE (Aggregated Ethernet) interface down events causing convergence issues.

Resolved In: evo:24.2R1-S2-EVO evo:24.2R2-EVO evo:24.4R1-EVO evo:25.1R1-EVO
PR NumberSynopsisCategory: Alias for DHCP issue on DNX based platform.
1771121
Major		jdhcpd.re.re0 cored at trace_file_close_internal (traceptr=0x7efc443b2bb0) at ../../src/junos_trace.c:188
Product-Group=evo		When DHCP trace options are enabled, there is a possibility that jdhcpd could core. In general, traceoptions should be enabled only for debugging. They should be disabled once debuffing is done.

Resolved In: evo:25.3R1-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
1845015
Minor		Traffic will be flooded for a prolonged time when mac-table-size is reduced
Product-Group=evo		On Junos Evolved ACX platforms, when "mac-table-size" is reduced(to make the size less than the usable MAC), traffic will be flooded for a prolonged time(around 5 mins). Based on remote MAC installation behavior traffic will be impacted.

Resolved In: evo:23.4R2-S4-EVO evo:24.2R2-EVO evo:24.4R1-EVO evo:25.1R1-EVO
PR NumberSynopsisCategory: Issues related to EVO dependency layer including object graphs, incompletes, anomalies and nkdb
1874151
Critical		Rare assert with an Junos Evolved process
Product-Group=evo		This is a rare chance of a process panic. This can be seen in Evo apps. If seen in forwarding apps it can result in system reboot and resulting traffic loss.

Resolved In: evo:23.4X100-D31-EVO evo:24.2R2-S1-EVO evo:24.2R2-S2-EVO evo:24.4R1-S3-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: management ethernet related issues - mgmt-ethd daemon
1800373
Critical		CPU hike will be observed when scaled BGP converge through management interface
Product-Group=evo		In large scale scenario when BGP routes resolved over WAN interface goes down, all the BGP routes will get re-converged through management interface which results into CPU hike on Junos OS Evolved platforms.

Resolved In: evo:22.3X80-D43-EVO evo:22.3X80-D44-EVO evo:22.3X80-D45-EVO evo:24.2R1-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO
PR NumberSynopsisCategory: jdhcpd daemon refactored for evo
1816246
Major		[ACX7000 Series] DHCPv4/v6 packets may be dropped because DHCP packets are not routed to kernel after initial jdhcpd starts
Product-Group=evo		Under certain conditions, the DHCP session database becomes unstable or JDHCPD not getting IFL/IFD events which cause DHCP packets to fail to route to the kernel and then leads to DHCP packet drop.

Resolved In: evo:23.4R2-S4-EVO evo:24.2R1-S2-EVO evo:24.2R2-EVO evo:24.4R1-EVO evo:24.4R2-EVO evo:25.1R1-EVO evo:25.2R1-EVO junos:23.2R2-S5 junos:23.4R2-S4 junos:24.2R1-S2 junos:24.2R2 junos:24.4R1 junos:24.4R2 junos:25.1R1 junos:25.2R1
PR NumberSynopsisCategory: Category to track runtime issues during package install
1822040
Major		ACX7024 SSH connection unresponsive multiple times after filesystem errors resulting from "uswitchd" crash.
Product-Group=evo		SSH connection unresponsive multiple times after filesystem errors resulting from "uswitchd" crash.

Resolved In: evo:23.2R2-S3-EVO evo:23.4R2-S5-EVO evo:24.2R1-S2-EVO evo:24.2R2-EVO evo:24.4R1-EVO evo:25.1R1-EVO
PR NumberSynopsisCategory: mgd, ddl, odl infra issues
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
1827751
Major		ACX7100 sees an RPD core when adding a sampling flow-server
Product-Group=evo		ACX7100 sees an RPD core when adding a sampling flow-server

Resolved In: evo:23.4R2-S2-EVO evo:24.2R2-EVO
1839955
Major		On Junos OS Evolved platforms, HTTPS download fails when HTTPS URL is present in the configuration
Product-Group=evo		On Junos OS Evolved platforms, when HTTPS URL is present as a part of file or mentioned explicitly in the configuration, and when there is a download attempted through this file the download fails. However, this is will not impact the forwarding traffic only the download through HTTPS will fail.

Resolved In: evo:23.4X100-D30-EVO evo:24.4R1-S2-EVO evo:24.4R2-EVO evo:25.2R1-EVO junos:23.4R2-S4 junos:23.4X30-D20 junos:24.2R2-S1 junos:24.4R1-S2 junos:24.4R2 junos:25.2R1
PR NumberSynopsisCategory: Category for software tracing Infra issues
1869479
Major		On Junos-EVO platforms, configuration under to "set system trace application " gets lost during rollback with sequence of steps
Product-Group=evo		On Junos-EVO platforms, configuration under to "set system trace application " gets lost during rollback with sequence of steps. Steps: 1. Seen if commit delta-export configured ("set system commit delta-export"). 2. Configure trace under "set system trace application " and commit. 3. Do rollback 1 but without committing again do rollback, commit. Configuration changes under trace will be lost on commit

Resolved In:
PR NumberSynopsisCategory: Express PFE FW Features
1872657
Major		PTX10003 EVO parity error recovery from shadow copy
Product-Group=evo		Parity error recovery mechanism has been missing for the FLT block in ZX ASIC. With this PR, it will be fixed.

Resolved In: evo:25.3R1-EVO evo:25.4R1-EVO junos:25.3R1
PR NumberSynopsisCategory: ACX7509 platform, FEB, RCB and linecaard resi
1846199
Major		Possible SSD 'read disturbance' due to platform_monitor script accessing the drive every 5 sec
Product-Group=evo		On an ACX7509 system, the system may access the backup SSD (/dev/sdb) frequently -- reducing the useful life of the SSD.

Resolved In: evo:23.2R2-S5-EVO evo:24.2R2-S1-EVO evo:24.4R2-EVO evo:25.1R1-EVO evo:25.2R1-EVO junos:24.4R2
PR NumberSynopsisCategory: ISIS routing protocol
1840681
Major		Traffic is blackholed when segment routing is disabled
Product-Group=evo		In all Junos and Junos Evolved devices supporting Intermediate System to Intermediate System (IS-IS) segment routing with L1 and L2 levels configured, and segment routing enabled in only one level. When there is a configured policy controlling which prefixes are advertised with a Prefix Segment Identifier (prefix-sid policy), and a command is added to disable segment routing, it causes IS-IS fragments to time out, resulting in network traffic being blackholed at the level.

Resolved In: evo:22.4R3-S5-EVO evo:23.4R2-S4-EVO evo:24.2R2-EVO evo:24.4R1-EVO evo:25.1R1-EVO junos:22.4R3-S5 junos:23.4R2-S4 junos:24.2R2 junos:24.4R1 junos:25.1R1
1841108
Major		Traffic drop is seen after GRES on ISIS peer
Product-Group=evo		On all Junos and Junos OS Evolved platforms, in an ISIS(Intermediate System-Intermediate System) graceful restart scenario, helper node sends and programs its locally configured hold-time (180 secs) instead of the "Restart-duration" received as hold-time from DUT (210 secs), due to this incorrect update, the hold timer expires at the helper node before the GR (Graceful Restart) is complete on DUT and it causes a flap of ISIS adjacency on peer/helper Node.

Resolved In: evo:21.4R3-S10-EVO evo:22.3X80-D47-EVO evo:22.4R3-S6-EVO evo:23.2R2-S3-EVO evo:23.4R2-S4-EVO evo:24.2R2-EVO evo:24.4R1-EVO evo:25.1R1-EVO junos:22.4R3-S6 junos:23.2R2-S4 junos:24.2R2 junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: Multiprotocol Label Switching
1854623
Major		The rpd process crashes due to memory exhaustion
Product-Group=evo		On all Junos and Junos Evolved platforms, an out-of-memory condition in the rpd process caused by uncontrolled memory allocation leads to the rpd process crashing.

Resolved In: evo:25.2R1-EVO junos:23.4R2-S4-J9 junos:23.4R2-S5 junos:24.4R2 junos:25.1R1 junos:25.2R1
PR NumberSynopsisCategory: FreeBSD Kernel Infrastructure
1802447
Major		failed to copy file '//var/etc/if_alias_map+' to 're1' error when user authenticated via tacacs comitting netconf configuration change
Product-Group=evo		Commit error issue via netconf session

Resolved In: evo:22.2R3-S7-EVO evo:22.3X50-EVO evo:22.3X80-D47-EVO evo:22.3X80-D49-EVO evo:23.2R2-S3-EVO evo:23.4R2-S4-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:20.3X75-D52 junos:21.2R3-S9 junos:22.2R3-S7 junos:22.4R3-S6 junos:23.2R2-S3 junos:23.4R2-S1 junos:24.2R1-S1 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: OSPF routing protocol
1865621
Minor		IPSEC OSPF3 realm sessions do not stay UP
Product-Group=evo		IPSEC OSPF3 realm sessions do not stay UP when you have the same interface configured in both ospf3 realm and non-realm. When the aggregate interface goes down for any reason (physical link issue or something else) when it recovers the realm session will not come back online.

Resolved In:
PR NumberSynopsisCategory: QFX5K EVO Platform Timing related
1829734
Major		QFX5130-48CM: High correction field errors in PTP packets during link flaps
Product-Group=evo		On Junos Evolved TD4 platform (QFX5130-48CM), intermittent link flaps cause the hardware link scan to malfunction, resulting in incorrect high values in the Correction Field (CF) of Precision Time Protocol (PTP) packets, causing improper timestamping. This impacts system time inaccuracies across the network and the overall timing synchronization of the network until remediated.

Resolved In:
PR NumberSynopsisCategory: Resource Reservation Protocol
1866944
Major		Traffic blackholing in LSPs due to link failure before protection signalling is processed
Product-Group=evo		On all Junos and Junos Evolved platforms, traffic blackholing occurs on MPLS (Multi-Protocol Label Switching) Label Switched Paths (LSPs) when link protection is enabled, under specific conditions during link failure events that occur just after the LSP is established.

Resolved In: evo:23.4R2-S5-EVO evo:24.4R2-EVO evo:25.3R1-EVO junos:20.3X75-D441 junos:23.4R2-S5 junos:24.4R2 junos:25.3R1
PR NumberSynopsisCategory: RPD API infrastructure
1715599
Critical		Inconsistent RPD crash found in rt_walk, task_job_run_job_bg, task_scheduler
Product-Group=evo		PRPD installed flowspec routes were not deleted on routing-instance delete, leading to RPD crash.

Resolved In: evo:22.3X80-D40-EVO evo:22.3X80-D41-EVO evo:23.4R1-EVO evo:23.4R2-EVO evo:24.1R1-EVO junos:23.4R1 junos:23.4R2 junos:24.1R1
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1704406
Major		VMX :: JDI-REG-VIRTUAL: Observed xml validation failure seen for "show host | display xml validate" and The emitted XML is INVALID.
Product-Group=evo		"show host" is not properly XMLized. So from a netconf channel the XML output is encapsulated in an tag. If any automation tool plans to use the XML output of this CLI command, it may have to do some logic on its side (as the response is not 100% XMLized)

Resolved In:
1799215
Major		The commit fails error can be seen when configuration is modified after commit prepare
Product-Group=evo		On all Junos and Junos Evolved platforms, when the user attempts to issue the commit command after modifying the configuration post 'commit prepare', the commit discards the prepared commit cache as it is no longer valid and throws " commit fails" error and proceeds with the regular commit process from scratch.

Resolved In: evo:22.2R3-S6-EVO evo:22.3X80-D45-EVO evo:22.3X80-D46-EVO evo:23.2R2-S3-EVO evo:23.4R2-S4-EVO evo:23.4X100-D30-EVO evo:24.2R1-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:21.4R3-S10 junos:22.2R3-S6 junos:23.2R2-S3 junos:23.4R2-S4 junos:23.4X30-D20 junos:24.2R1 junos:24.2R2 junos:24.3R1 junos:24.4R1 junos:25.1R1
1821824
Major		The mgd process crashes when load override and rollback is done simultaneously
Product-Group=evo		On all Junos and Junos Evolved platforms, when load override and rollback is done simultaneously, the mgd process crashes. It's a very rare issue observed in race condition. This doesn't have any traffic impact only CLI session will be closed , which can be accessed again with re-login.

Resolved In: evo:22.3X50-EVO evo:22.3X80-D47-EVO evo:22.3X80-D49-EVO evo:22.4R3-S5-EVO evo:23.2R2-S3-EVO evo:23.4R2-S4-EVO evo:23.4X100-D30-EVO evo:24.2R2-EVO evo:25.1R1-EVO junos:22.2R3-S7 junos:22.4R3-S5 junos:23.2R2-S3 junos:23.4R2-S4 junos:23.4X30-D20 junos:24.2R1-S2 junos:24.2R2 junos:24.4R1 junos:25.1R1
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:22.4R3-S7-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:21.4R3-S11 junos:21.4X12-X1 junos:22.2R3-S6 junos:22.4R3-S7 junos:23.2R2-S3 junos:23.4R2-S4 junos:23.4X30-D20 junos:24.2R1 junos:24.2R2 junos:24.3R1 junos:25.1R1
1820048
Minor		An error "RPC error: error operation-failed: parse error in identifier attributes" is seen if route-filter configuration push is applied via NETCONF
Product-Group=evo		On all Junos and Junos OS Evolved platforms when configuration push is done via NETCONF, involving re-ordering of the existing configured route-filter entries, will fail with an error "RPC error: error operation-failed: parse error in identifier attributes". This scenario is most likely applicable when Yang based controllers or clients are used to manage the Juniper devices and choice-ident and choice-value must be present in edit-config RPC while re-ordering. There is no service impact due to this issue.

Resolved In: evo:21.4R3-S10-EVO evo:22.3R3-S4-EVO evo:22.3X50-EVO evo:22.4R3-S7-EVO evo:23.2R2-S3-EVO evo:23.4R2-S4-EVO evo:23.4X100-D30-EVO evo:24.2R1-S1-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:21.2R3-S9 junos:21.2X32-D30 junos:21.4R3-S10 junos:22.2R3-S6 junos:22.3R3-S4 junos:22.4R3-S7 junos:23.2R2-S3 junos:23.4R2-S4 junos:23.4X30-D20 junos:24.2R1-S1 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: PRs related to PICd and associated lib WAN side PI code.
1802376
Critical		The picd crash is observed on Junos OS Evolved ACX /PTX platforms
Product-Group=evo		When SysMan application is terminated twice due to picd stop signal results in picd.re crash leading to traffic impact.

Resolved In: evo:22.3X80-D46-EVO evo:23.4R2-S3-EVO evo:24.4R1-EVO
PR NumberSynopsisCategory: VMHOST platforms software
1795506
Minor		A non service impacting warning message 'Failed to set 'memory.limit' will be observed
Product-Group=evo		On all Junos OS Evolved platforms a warning message "Failed to set 'memory.limit_in_bytes' attribute on '/user.slice' to '-1': Invalid argument" would be observed.

Resolved In: evo:22.3R3-S4-EVO evo:22.3X50-EVO evo:22.3X80-D43-EVO evo:22.3X80-D44-EVO evo:24.2R1-EVO evo:24.2R1-S1-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:24.4R1
PR NumberSynopsisCategory: Virtual Private LAN Services