Alert Type

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

Product Affected

ACX PTX QFX platforms running Junos Evolved software

Alert Description

Junos Software Service Release version 23.4R2-S6-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-S6-EVO is now available.

23.4R2-S6-EVO - List of Fixed issues

PR NumberSynopsisCategory: EVO Debug collector
1868326
Major
FPC commands repeatedly prompt for a password and fail when debug-collector is run by non-root users
Product-Group=evo
Severity=Major
On all Junos EVO platforms, when debug-collectors are run by non-root users the flexible physical interface card concentrators (FPC) commands repeated prompt for passwords. The commands will fail to run though the password is provided.
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
Severity=Major
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.
1888506
Major
Support for new CMIS 4.0-compliant 2x100G-LR4 optics on Junos Evolved/ULC Platforms
Product-Group=evo
Severity=Major
Junos Evolved and ULC platforms now support CMIS 4.0+ compliant 2x100G-LR4 optics using updated host electrical interface codes (e.g., 100GAUI-4) as defined in SFF-8024. This enhancement enables proper optic detection and initialization for newer modules.
1890558
Major
Mismatch between configured and reported wavelength for some optics
Product-Group=evo
Severity=Major
On all Junos OS Evolved platforms and MX paltforms with MPC11E / LC9600 line cards , the issue is seen with optics that doesn't support 6.25GHz spacing. There is a mismatch seen between the configured and the reported wavelength. The wavelength mismatch will lead to the loss of signal and thus result in impact on the traffic.
PR NumberSynopsisCategory: "agentd" software daemon
1873990
Major
EX9208: Syslog message 'JINSIGHTD_SENSOR_RESUBSCRIPTION' every 5 sec
Product-Group=evo
Severity=Major
On EX9200 series switch, syslog message 'JINSIGHTD_SENSOR_RESUBSCRIPTION' is seen every 5 sec
1889924
Major
Data still seems to be streaming somewhere when the DialOut (Established) connection on the port is already closed
Product-Group=evo
Severity=Major
On all Junos and Junos OS Evolved platforms, the existing gRPC-DialOut connection does not disconnect completely on the DUT, causing any other DialOut connections to fail.
PR NumberSynopsisCategory: EVO interface software
1878198
Major
Link flapping occurs on stable subinterfaces when using QDD400GZR optics if any one subinterface in the channelized group is down
Product-Group=evo
Severity=Major
On all Junos OS Evolved platforms that support the QDD-400G-ZR coherent optical transceiver modules (400G-ZR and 400G OpenZR+), when an interface is equipped with any of these optics and configured in breakout mode, if anyone of the sub-interfaces in the group is administratively up and operationally down, the remaining stable sub-interfaces in the same group experience the link flaps at a regular interval.
PR NumberSynopsisCategory: EVO RCB software
1799443
Minor
USB Media installation shows up minor alarm "Host 0 Voltage Threshold Crossed"
Product-Group=evo
Severity=Minor
On Junos Evolved PTX10001-36MR platform, upon software installation with USB Media, the system might report a minor Alarm "Host 0 Voltage Threshold Crossed ". The root cause is a missing symbolic link for the voltage sensor configuration. During the installation reboot process, the assembly_id readout did not return a value. This is only applicable during media USB installation and not during regular system reboots. There is no operational impact.
PR NumberSynopsisCategory: Border Gateway Protocol
1857801
Major
Memory leak is observed when "graceful-shutdown" is configured
Product-Group=evo
Severity=Major
On all Junos and Junos Evolved platforms with Border Gateway Protocol (BGP) "graceful-shutdown" configured, memory leak is observed. This issue does not cause traffic impact.
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''.
1887911
Major
The rpd process crashes after BGP configuration commits involving group-split-size and RIB-sharding
Product-Group=evo
Severity=Major
On Junos and Junos OS Evolved platforms, configuring "group-split-size" with BGP RIB-sharding(Border Gateway Protocol Routing Information Base Sharding) can lead to a crash in the routing protocol daemon (rpd) when a route update for a non-negotiated NLRI(Network Layer Reachability Information) is received in the update thread. This occurs if the NLRI is targeted at other BGP peers within the group that have negotiated it.
PR NumberSynopsisCategory: EVO L3 routing for BCM XGS Platforms
1896239
Major
Host-bound packet drops when using decapsulate filter action in non-default routing-instances
Product-Group=evo
Severity=Major
On all Junos OS Evolved QFX5K platforms, host-bound packets on L3 interfaces associated with non-default routing-instances are consistently dropped when a filter with the decapsulate action is applied sequentially on one interface and then on its counterpart.
PR NumberSynopsisCategory: PFE L2 forwarding features on BT based platforms
1885670
Minor
IGMP or MLD packets associated with CCC services will be dropped instead of being forwarded
Product-Group=evo
Severity=Minor
On Junos Evolved PTX10008, PTX10016, and PTX10002-36QDD platforms, Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) packets associated with Circuit Cross-Connect (CCC) services such as EVPN-VPWS (Ethernet VPN-Virtual Private Wire Service (VPWS) or L2Circuit ingressing into the Provider-Edge (PE) device will be dropped instead of being forwarded.
1890878
Major
On PTX EVO platforms in EVPN-VXLAN scenario traffic will not egress out of the irb next-hop when the bridge-domain doesn't have VXLAN VNI configured
Product-Group=evo
Severity=Major
On all PTX Evolved platforms that support EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN), when the PTX router acts as a MAC-VRF (Media Access Control - Virtual Routing and Forwarding) EVPN gateway, it will fail to forward traffic routed through the 'irb' interface due to packets being discarded at PFE (packet forwarding Engine), causing packet loss.
PR NumberSynopsisCategory: Express BT PFE L3 Features
1907660
Minor
Interface telemetry statistic /interfaces is not streamed correctly on Junos OS Evolved PTX platforms
Product-Group=evo
Severity=Minor
Interface telemetry statistic /interfaces may be streamed incorrectly on Junos OS Evolved PTX platforms. The counter may not be updated, or not update at regular intervals. There is no service impact except monitoring capability using telemetry.
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: Firewall support for DNX
1869363
Minor
The router incorrectly assume the VRRP Master role on Junos Evolved ACX platforms
Product-Group=evo
Severity=Minor
On Junos Evolved ACX platforms, dual VRRP mastership may be seen with VRRP configuration and having filter configuration with log/syslog action. Due to the issue, the VRRP advertisements were not processed correctly, it was receiving the advertisements but getting discarded when log action is configured on the filter, so it assumed the master role. The issue may affect traffic using VRRP protocol.
PR NumberSynopsisCategory: DNX L2 related features
1855369
Major
Storm Control stops working on all LAG members after deactivating one or more interfaces on Junos OS Evolved ACX7K platforms
Product-Group=evo
Severity=Major
On Junos OS Evolved ACX7K platforms, when storm control is configured on a LAG (Link Aggregation Group) interface and one or more LAG member interfaces are deactivated, storm control stops working on all remaining active members. This results in an immediate increase in BUM (Broadcast, Unknown Unicast, and Multicast) traffic on the egress interface.
1886421
Minor
VSTP convergence failure on Junos OS Evolved ACX7K when IRB shares bridge domain with VSTP enabled IFL
Product-Group=evo
Severity=Minor
On all Junos Evolved ACX7K platforms, when a VLAN Spanning Tree Protocol (VSTP) enabled Layer 2 logical interface (IFL) shares a bridge domain with an Integrated Routing and Bridging (IRB) interface, VSTP fails to converge due to Spanning Tree Protocol (STP) packets are misrouted to the IRB interface, preventing them from reaching the VSTP process. This causes potential traffic loops due to lack of VSTP convergence.
PR NumberSynopsisCategory: Layer 3 forwarding, both v4+v6
1798925
Minor
Junos OS Evolved ACX Series platform does not respond to ICMP/SSH destined to VRF interface without vrf-table-label
Product-Group=evo
Severity=Minor
On Junos OS Evolved ACX Series platforms running 22.3R1-EVO and later releases, when 'vrf-table-label' is not configured for the routing instance of type VRF (Virtual Routing and Forwarding), the router does not respond to ICMP/SSH destined to the VRF interfaces.
PR NumberSynopsisCategory: ACX VxLAN Issue
1824748
Minor
BUM traffic not forwarded to the access interface on Junos Evolved OS ACX platforms
Product-Group=evo
Severity=Minor
On Junos Evolved OS ACX platforms with EVPN-VXLAN (Ethernet VPN - Virtual Extensible Local Area Network) configuration, access interfaces are not correctly added to the VXLAN BD (Bridge Domain) flood list in the PFE (Packet Forwarding Engine). As a result, BUM (broadcast, unknown unicast and multicast) traffic will not be forwarded properly, potentially leading to service disruption.
1854710
Critical
ACX platform configured as a data center gateway with EVPN-VXLAN failed to forward IP prefix routes for inter-data center communication
Product-Group=evo
Severity=Critical
On Junos evolved ACX platforms with Evolved Routing Engine, an issue was identified where Ethernet VPN (EVPN) Type-5 IP prefix routes are dropped at the Data Center Gateway (DC-GW).Due to timing-related conditions in the Packet Forwarding Engine (PFE), the expected next-hop published by the Routing Protocol Daemon (rpd) is not properly updated. Instead, the next-hop associated with the same prefix from the Layer 2 Address Learning Daemon (l2ald) is incorrectly selected. Since the l2ald next-hop is not valid for Type-5 IP traffic, this results in traffic drops for EVPN Type-5 routes received from the remote Data Center Gateway.
PR NumberSynopsisCategory: Firewall related development
1875725
Minor
The firewalld process crashes post specific set of filter related modifications performed in single commit
Product-Group=evo
Severity=Minor
On Junos EVO platforms, When Firewall Filter change involved both delete and change to new filter on an interface in a single commit resulted in Firewalld coredump.
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
Severity=Critical
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.
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
Severity=Critical
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.
PR NumberSynopsisCategory: Issues related to evo operations - libevo infra, typeinfo ..
1808552
Minor
Usage alerts about re0:tempfs, mounted on /run/user/#### being marked as full
Product-Group=evo
Severity=Minor
Usage alerts about re0:tempfs, mounted on /run/user/#### being marked as full
PR NumberSynopsisCategory: System Management daemon and related issues
1866988
Critical
System stops responding to "show system applications app ndp detail" command or prevents applications from start/stop/restart
Product-Group=evo
Severity=Critical
On all Junos OS Evolved platforms, 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.
PR NumberSynopsisCategory: Issues related to debug utilties - objmon, objshell/Dashboard
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.
PR NumberSynopsisCategory: Interface PRs defect & enhancement requests
1856651
Major
Mixing EP and SP style configurations on AE bundle causes traffic loss and protocol session failure on Junos OS Evolved PTX Series platforms
Product-Group=evo
Severity=Major
On all Junos OS Evolved PTX Series platforms, configuring an Enterprise (EP) style logical interface (family ethernet switching) on an Aggregated Ethernet (AE) bundle that is already configured with service provider (SP) style encapsulation (flexible-ethernet-services or extended-vlan-bridge) is not supported. If the unsupported configuration is committed, traffic on the interface is dropped and protocol sessions go down.
1875917
Major
Disabling a single AE IFL in a MAC-VRF can bring the entire AE interface down
Product-Group=evo
Severity=Major
On all Junos Evolved platforms, under MAC-VRF routing configurations, when any Layer 3 IFL is deactivated, it causes the associated AE interface to go administratively down, leading to complete traffic disruption across the AE bundle.
1882754
Major
AE interface speed mismatch causes link down and missing command outputs on Junos OS Evolved platforms
Product-Group=evo
Severity=Major
On all Junos OS Evolved platforms, when the AE (Aggregated Ethernet) interface is configured with a link-speed different from its member interfaces, it results in a misconfiguration. Due to this, the link between devices goes down, causing disruption in traffic forwarding.
1898055
Minor
Unexpected commit failure will be observed when deactivating of unit or changing any configuration and performing a commit operation
Product-Group=evo
Severity=Minor
On Junos OS Evolved platforms, if input-vlan-map and output-vlan-map are configured, an unexpected commit failure may occur when deactivating a unit (e.g., unit ) or making any configuration changes followed by a commit operation. This issue results in commit failure errors and prevents further configuration changes.
PR NumberSynopsisCategory: EVO L2 Control Plane PRs
1889335
Minor
Traffic drop is observed in an EVPN multihoming as the MAC route points to the ESI interface when the CE (ESI) IFD flaps
Product-Group=evo
Severity=Minor
On all Junos and Junos Evolved platforms, in an Ethernet Virtual Private Network (EVPN) MultiHoming setup with Ethernet Segment Identifier (ESI) configured under logical Interface (IFL) (CE-facing), when the corresponding IFD (Physical Interface) flaps, the MAC route will point to the ESI interface, while it should point to the Multihoming CE (Customer Edge) interface. This results in traffic loss.
PR NumberSynopsisCategory: EVO-AFT Infrastructure PFE related issues
1889042
Major
On PTX10001-36MR devices, after applying a Junos Selective Update JSU, the entire system is rebooted
Product-Group=evo
Severity=Major
On PTX10001-36MR platforms running Junos Evolved, after applying Junos Selective Update (JSU) for ppman-aft process will cause a reboot of the system. The reboot is caused by the service binding between ppman-aft and evo-cda, present only in the PTX10001-36MR series running affected versions
1899071
Major
Host loopback wedge error is seen when committing firewall filter leading to major FPC errors
Product-Group=evo
Severity=Major
On PTX routers except ptx10003-80c and ptx10003-160c, when firewall IFD filter is committed, the PFE(Packet Forwarding Engine) encounters a host path wedge, resulting in host loopback timeout errors and major functional alarms in the system.
PR NumberSynopsisCategory: EVO Socket replication
1895827
Major
Adding a new key to authentication-key-chain causes kernel crash
Product-Group=evo
Severity=Major
On all Junos Evolved platforms, when setting/changing the tolerance value of key-chain to max value of 4294967295 and committing and then adding a new key to a key-chain and performing a commit action will result in kernel crash. Device self-recovers after the crash. "show system core-dumps" can be used to check the core. Core name starts with vmcore*
PR NumberSynopsisCategory: Configd, ffp issues
1877439
Minor
Traffic drop occurs on Junos Evolved platforms when prefix is moved between dynamic prefix-lists used in firewall filter
Product-Group=evo
Severity=Minor
On all Junos Evolved platforms, when a firewall filter is configured with a dynamic prefix-list that is referenced using an apply-path statement, moving a prefix from one such prefix-list to another where both prefix-lists match the apply-path pattern results in the prefix not being programmed in the PFE. This causes traffic loss for that prefix. The issue is triggered when the configuration includes apply-path pointing to both the source and destination prefix-lists, and a prefix is deleted from one and added to the other through a commit operation.
PR NumberSynopsisCategory: mgd, ddl, odl infra issues
1882996
Major
xnm-ssl feature fails without loopback interface configuration on Junos Evolved platforms.
Product-Group=evo
Severity=Major
On Junos Evolved platforms, the xnm-ssl feature does not function unless a loopback address (lo0.0) is explicitly configured. The feature is not applicable to Junos (non-EVO) platforms. To ensure proper operation, configure 127.0.0.1/32 on lo0.0.
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1848993
Major
The data plane will be out of sync when migrating to EVPN A/A stitching with Vanila VXLAN (PIM Multicast)
Product-Group=evo
Severity=Major
On MX platforms, to improve the convergence of node failures in EVPN MH interconnects with Data Plane VXLAN, migrating to an Active-Active setup may cause the data plane to become out of sync for ARP entries. The gateway learns the MAC address and advertises it to the peer gateway. However, on the peer gateway, some MAC-IP entries may remain stuck in the 'Unresolved' (Ur) state.
PR NumberSynopsisCategory: Common PR category for all EVO AFT based L2 features related issues on Express platforms
1890125
Major
In scale EVPN scenario with IRB, host traffic via IRB will be impacted ICMP, OSPF, BGP and L3 protocols on Junos Evolved OS PTX series platform
Product-Group=evo
Severity=Major
On Junos OS Evolved PTX series platforms, in a scale EVPN (Ethernet Virtual Private Network) scenario with IRB (Integrated Routing and Bridging), the traffic via IRB will be impacted ICMP, OSPF, BGP and L3 protocols.
PR NumberSynopsisCategory: Express PFE CFM
1810549
Major
Non-Impactful CFMMAN Parse Error on First CFM CCM PDU During FPC/PFE Online Transition
Product-Group=evo
Severity=Major
On Junos Evolved PTX platforms, the log message "CFMMAN: Parse Error: CFM CCM pkt TLV parsing error" may appear when an FPC or PFE is restarted and comes online. This message indicates that a CFM Continuity Check Message (CCM) was truncated, leading to an error while parsing the TLV (Type-Length-Value) fields in the packet. The error is transient and typically affects only a small number (usually 1 or 2) of CCM packets received immediately after the FPC or PFE becomes operational. It has no functional impact on CFM sessions or overall network operations. CFM continues to function normally, and no persistent degradation is observed. This issue does not consistently affect any specific CFM session and occurs only during the brief initialisation period of the hardware component.
1891363
Major
hardware-assisted-keepalives CFM transmit packets are queued into Q4 instead of Q3/Network-control
Product-Group=evo
Severity=Major
On EVO-based PTX platform, hardware-assisted-keepalives (aka inline) CFM transmit packets running on INET and CCC downmep topology are queued into Q4, instead of Q3/network-control. If no COS scheduler is configured on interface Q4, the CFM packets will be dropped in an interface burst scenario which will end up with protocol flap.
PR NumberSynopsisCategory: Express PFE FW Features
1876672
Major
SCU/DCU match is not working when configured along with the forwarding-class
Product-Group=evo
Severity=Major
On PTX Junos OS Evolved platforms, the SCU/DCU (Source class usage/ Destination class usage) match is not working when it is configured along with the forwarding-class.
PR NumberSynopsisCategory: Enhanced Broadband Edge support for firewall
1883530
Critical
FPC crash is seen on certain Junos platforms when firewall filter is configured for subscribers
Product-Group=evo
Severity=Critical
On MX platforms with MPC10E, MPC11E, LC9600 line-cards and MX304 with subscriber-management enabled, Flexible PIC Concentrator (FPC) crashes in a rare scenario and crash files are generated when filters are configured for subscribers . This will lead to traffic impact since the line-card reboots and subscribers are re-logged.
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: ACX7332 & ACX7348 Platform Software
1900115
Major
PCIe fatal error resulting in an unexpected device reboot and evo-pfemand crash on Junos OS Evolved ACX7322 platform
Product-Group=evo
Severity=Major
On the Junos OS Evolved ACX7332 platform, an unexpected device reboot and evo-pfemand (Evolved Packet Forwarding Engine management process) process crash will be observed, due to PCIe (Peripheral Component Interconnect Express) fatal error "DPC: ERR_FATAL PCI error". This error results in a PCIe link-down event, causing a loss of signal to the external TCAM (Ternary Content Addressable Memory). When the TCAM becomes unavailable, any software attempt to access the TCAM can trigger a PCIe link failure, leading to a complete traffic impact. These events are logged in the system's journal logs.
PR NumberSynopsisCategory: ACX7509 Platform related issues
PR NumberSynopsisCategory: MX Inline Jflow
1861100
Minor
System journal logs are flooded without enabling debugging when inline monitoring is configured
Product-Group=evo
Severity=Minor
On MX304 platform and all MX platforms having MPC10E/MPC11E/LC9600 line cards, when inline monitoring is configured, system journal is being flooded with IPFIX headers by default, without enabling any debugging.
PR NumberSynopsisCategory: ISIS routing protocol
1847557
Critical
Link State of IS-IS IPv6 adjacency is not updated after interface flap (Due to any reason)
Product-Group=evo
Severity=Critical
On all Junos and Junos Evolved platforms with Intermediate System-to-Intermediate System (IS-IS) protocol configured with IPv6 Multitopology, in rare scenarios the IS-IS adjacency is not updated and IPv6 traffic drop is seen after restarting the FPC.
1859099
Minor
Memory leak is observed for certain topologies when TI-LFA is configured
Product-Group=evo
Severity=Minor
On all Junos and Junos OS Evolved platforms , where IS-IS/OSPF is enabled and TI-LFA (post-convergence-lfa) is configured in a SR (Segment Routing) environment. In a scenario where the computed backup paths to reach a destination is fetched from the more than one originator, duplicate paths gets computed for certain topology combinations and the clean-up of infosid list doesn't happen this leads to memory leak that might eventually lead to high memory usage and result in rpd crash and thus impacting traffic.
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).
1909786
Critical
Selection of VGA-IP as source IP for RE-ARP packet causes incorrect ARP updation of VGA-IP getting bound with IRB-MAC at end-hosts
Product-Group=evo
Severity=Critical
Selection of VGA-IP as source IP for RE-ARP packet causes incorrect ARP updation of VGA-IP getting bound with IRB-MAC at end-hosts
PR NumberSynopsisCategory: Interface PR for LC1202 LC
1846379
Minor
Retimer/gearbox ports on LC1202 line card might take long duration to bring an interface back up
Product-Group=evo
Severity=Minor
On PTX10004/8/16 platforms with LC1202 line card, retimer/gearbox ports on LC1202 line card take longer duration(~1500 msec) to bring an interface back up after short LOS insertion from peer device. This breaks sub-second hold-time down feature. The code fix enabled 'fast linkup' feature of retimer/gearbox ports. It helped the link to come up faster. Ideally retimer/gearbox ports take 1.5 sec to come up, but with this feature, links come up in 1 sec.
1857490
Minor
Extra link flap will be seen when the link fails for a short time on PTX10K with LC1202
Product-Group=evo
Severity=Minor
On Junos OS Evolved PTX10K platform with LC1202, if hold-time down is configured on any port, an extra link flap will be seen when the link fails for a short time.
PR NumberSynopsisCategory: Label Distribution Protocol
1789663
Major
Unexpected rpd crash when huge amount of telemetry data is being streamed
Product-Group=evo
Severity=Major
On Junos and Junos Evolved platforms with telemetry enabled, in escenarios where huge amount of data is being streamed, when streaming data crosses the limit (i.e size based defer limit is at 15kb and time-based defer limit 100 ms) there will be a defer and continue. If configuration changes occur during this deffering state that affected the last streamed XPath (the specific data path being monitored), it will cause rpd (routing protocol deamon) to crash causing traffic drop and core file will be generated. No workaroung is provided, rpd will restart automatically.
PR NumberSynopsisCategory: Port-based link layer security services and protocols that a
1883473
Major
Packet drops are observed when MACsec with bounded-delay is configured due to key rollover
Product-Group=evo
Severity=Major
On Junos OS MX304, MX platforms with line cards LC4800 and LC4802, and Junos OS Evolved ACX platforms with MACsec (Media Access Control security) with bounded-delay is configured, packet drops will be observed as valid packets will be incorrectly identified as replays and dropped because they fall outside the allowed replay protection window. The issue happens when the expected PN (Packet Number) on the receiver becomes unsynchronized with the sender during a key rollover event.
PR NumberSynopsisCategory: Multiprotocol Label Switching
1859219
Major
RSVP-TE LSP path is not re-optimised to the path with best IGP metric
Product-Group=evo
Severity=Major
On all Junos and Junos Evolved platforms, when RSVP-TE (Resource Reservation Protocol - Traffic Engineering) is configured with MBB (make-before-break) setup, if the protected link of the primary LSP (Label Switched Path) goes down and if "clear mpls lsp" or "clear rsvp session" commands are executed, then LSP switches to new instance from the old which will be on higher IGP (Interior Gateway Protocol) metric. However, after re-optimization, LSP will not get switched to better IGP metric path and remain in old instance. Traffic drop can be seen due to this double fault events.
1878360
Minor
memory leak in lsp_regex_cache_entry block (lsp_regex_cache_entry_add)
Product-Group=evo
Severity=Minor
On all Junos and Junos OS Evolved platforms, when configured with RSVP (Resource Reservation Protocol) LSPs (label-switched path) and when MPLS (Multi-Protocol Label Switching) protocol activate/deactivate is performed, the rpd memory leak is observed. There is no service impact due to this issue.
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.
1876458
Major
MX960 mcsnoopd core dump during rt_mcnh_nh_release
Product-Group=evo
Severity=Major
When the mcsnoopd process (use for L2 multicast) creating a new NH , our system takes a reference to it. However, if this reference is released too quickly, the old NH might be deleted before its references are fully cleared. This may cause the mcsnoopd process to restart.
PR NumberSynopsisCategory: Protocol Independant Multicast
1857699
Major
Native_Multicast:: : Protocol PIM Interface disable command not working
Product-Group=evo
Severity=Major
Disabling the PIM interface underneath the [edit protocols pim interfaces ] hierarchy may still show PIM as still being UP instead of DOWN.
1880262
Major
PIM neighbors timeout on backup RE due to inconsistent state with master
Product-Group=evo
Severity=Major
On all Junos and Junos Evolved platforms with dual Routing Engines (REs), Protocol Independent Multicast (PIM) neighborship is not be maintained on the backup Routing Engine after a ppmd-agent restart. This can lead to loss of PIM neighbor state on the backup RE.
PR NumberSynopsisCategory: RPD Interfaces related issues
1842546
Major
Memory leak is detected when interfaces are configured
Product-Group=evo
Severity=Major
On all Junos and Junos Evolved platforms, 72-byte size memory leak is seen when interface configuration is added. But there is no traffic impact due to this issue.
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1815837
Minor
Configure low file size in traceoptions while logging volume is high will lead to high CPU and RPD scheduler slips causing operational impact
Product-Group=evo
Severity=Minor
If the file size is too small and the amount of traceoptions volume is too high it can cause scheduler slips and operational impact.
PR NumberSynopsisCategory: SNMP Infrastructure (snmpd, mib2d)
1817865
Minor
The "snmp packet-size " command not working for SNMPv3
Product-Group=evo
Severity=Minor
If the "snmp packet-size " is configured on Junos and Junos Evolved platforms. , the responded SNMPv3 packet could be of larger size causing more fragmentation and packet overhead for SNMP traffic.
PR NumberSynopsisCategory: Junos Automation, Commit/Op/Event and SLAX
1872284
Major
master-eventd will fail after multiple RE switchover
Product-Group=evo
Severity=Major
On Junos and Junos OS Evolved platforms with dual RE(Routing Engine) , master-eventd will fail to start after multiple RE switchovers when event-options policies are configured. This happens only if a process is still waiting for an action (like file transfer or SSH) to complete.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1878430
Major
The mgd process crash is seen on all Junos and Junos Evolved platforms when FQDN is configured along with ephemeral database
Product-Group=evo
Severity=Major
On all Junos and Junos OS Evolved platforms, Fully Qualified Domain Name(FQDN) configured in static database in presence of ephemeral database instances results in the mgd process crash. As a result, mgd session gets terminated and commit fails. There is no traffic impact due to this issue. The issue is seen with FQDNs that resolve to multiple IP addresses.
PR NumberSynopsisCategory: ACX724 platform issues
1884419
Major
Host 0 Active Disk Usage Exceeded is not getting cleared even if the usage is less
Product-Group=evo
Severity=Major
On Junos Evolved ACX7024 and ACX7024X, the "Active Disk Usage Exceeded" alarm is raised and not cleared even if the usage is less than 50%. This issue has no impact on traffic.
PR NumberSynopsisCategory: ACX7000 interface software related issues.
1885817
Major
ACX7k DWDM optics wavelength not applied after reboot
Product-Group=evo
Severity=Major
On Junos OS Evolved ACX7K platforms, the DWDM (Dense Wavelength Division Multiplexing) optics wavelength is not applied after reboot. Hence, the system defaulted to the standard wavelength mode rather than the explicitly configured wavelength. When the wavelength is defaulted to the standard wavelength mode, the link will be up and with no data traffic impact, and it's a corner case, and is specific to DWDM optics only.
PR NumberSynopsisCategory: Express ZX PFE L3 Features
1842666
Minor
IPv6 Neighbor Discovery Packets Punted to RE Instead of Transiting via Core Interface
Product-Group=evo
Severity=Minor
In a cross-connect (L2Circuit) scenario, IPv6 Neighbor Advertisement (NA) and Neighbor Solicitation (NS) packets originating from the CE side are being punted to the Routing Engine (RE) instead of passing through the L2Circuit over the core interface.
1914060
Major
On PTX10003 platform, MPLS packets with an explicit NULL label and IPv4/IPv6 payload do not hit IPv4 or IPv6 filters, potentially skipping filter actions.
Product-Group=evo
Severity=Major
On PTX10003 devices, when MPLS packets with an explicit NULL label and IPv4/IPv6 payload enter the router, any IPv4/IPv6 filters configured on the interface are not executed. This happens because MPLS NULL label termination is skipped, causing the filter block to treat the packet as MPLS rather than IP.

 


 

Extended Solution

23.4R2-S6-EVO - List of Known issues

PR NumberSynopsisCategory: Software build tools (packaging, makefiles, et. al.)
1663426
Major
NETCONF: RPC get & get-configuration display invalid json format response for an OpenConfig when adds a routing-options configuration
Product-Group=evo
After adding a "routing-options" configuration via OpenConfig operation, subsequent "get" and "get-configuration" may display an invalid JSON format.

Resolved In: evo:25.2R2-EVO evo:25.3R1-EVO junos:25.2R2 junos:25.3R1
PR NumberSynopsisCategory: "agentd" software daemon
1839478
Major
/junos/system/linecard/interface/traffic/ sensor is seeing packet drops but there is no actual drops
Product-Group=evo
On all MX devices with ULC line cards (MPC10/11 and LC4800/9600), when subscribing to the /junos/system/linecard/interface/traffic/ native telemetry subscription path, the exported data includes the following containers: /interfaces/interface//interfaces/interface/state//interfaces/interfaces/state/counters. The picd and evo-aftmand-bt daemons are responsible for exporting data for these paths. When running the CLI command "show network-agent statistics detail, " it shows packet and byte statistics for each sensor per daemon. The picd daemon reports some drops due to an error in the CLI's data reporting. However, no actual packet drops occur. The issue arises from a bug in the bookkeeping code that tracks packet statistics, causing the CLI to incorrectly show drops even when no packets have been lost. This issue only affects the CLI display and does not impact actual packet transmission.

Resolved In: evo:24.2R2-S1-EVO evo:24.2R2-S2-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:24.2R2 junos:24.2R2-S2 junos:24.4R2 junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: EVO interface software
1851051
Major
On Tx side the MAC does not enforce/truncate any oversize frames and are reported in "CRC/ Align error Transmit" and "Total errors Transmit" counters
Product-Group=evo
On Tx side, the MAC does not enforce or truncate any oversize frames, it will send out the frames and append a correct CRC. If the MTU is set to say 2000, then any frame sent to the MAC > 1996 bytes will have a 4byte CRC appended. As that frame will be "too large" it will NOT be reported in aFramesTransmittedOK, but instead will be reported in ifOutErrors. There is no direct hardware counter in the ASIC that reports Frames transmitted with a bad crc, the ifOutErrors may be an aggregate count of bad frames due to multiple reasons. Since the hardware does not have a counter to count the frames that are transmitted with bad crc it cannot be included in Total packets transmit.

Resolved In: evo:25.2R1-EVO
PR NumberSynopsisCategory: Border Gateway Protocol
1696328
Major
The rpd process will crash on all Junos and Junos OS Evolved platforms when BGP multipath is enabled
Product-Group=evo
The rpd process crash is observed on all Junos and Junos OS Evolved platforms with BGP multipath configuration.

Resolved In: evo:21.4R3-S5-EVO evo:22.1R3-S4-EVO evo:22.2R3-S2-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.3X80-D43-EVO evo:22.3X80-D44-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:21.2R3-S7-J13 junos:21.2R3-S8 junos:22.1R3-S4 junos:22.2R3-S2 junos:22.3R2-S2 junos:22.3R3 junos:22.3X60 junos:22.4R2 junos:23.1R1 junos:24.2R2
PR NumberSynopsisCategory: Express BT PFE L3 Features
1911859
Major
PDT: In EVO, DOWN IFL returned as UP by na-grpc and DONW by PFE, duplicate leaf data received - interfaces/interface/subinterfaces/subinterface]/state/oper-status
Product-Group=evo
To avoid duplicate data for interfaces/interface[name=et-0/0/11:0]/subinterfaces/subinterface[index=100]/state/oper-status: UP use the command set forwarding-options suppress-interface-leaf-nodes

Resolved In:
PR NumberSynopsisCategory: MX304 interface specific
1818120
Critical
100G AOC cable with serial numbers starting with 1A will not get detected on all Junos OS Evolved based FPC
Product-Group=evo
On all Junos OS Evolved platforms, MX platforms with MPC10 and above, MX304 and EX9K with EX9200-15C, 100G AOC cable with serial numbers starting with 1A will not get detected. When this issue occurs, interface will go down which causes traffic loss.

Resolved In: evo:24.2R1-S2-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:24.2R2 junos:24.2X1 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: Firewall Filter
PR NumberSynopsisCategory: ACX BFD specific issues
1885776
Minor
ACX EVO - FTP "file copy" causing BFD flaps
Product-Group=evo
In Junos EVO, multihop sessions in ACX platforms may experience delays due to packet I/O congestion. This happens when copying packets to the ppman application, which hosts distributed sessions. This congestion can affect "Bidirectional Forwarding Detection" (BFD) sessions, causing timer expiries due to delay of packet transmission. Specifically, multihop BFD sessions on certain ACX models (ACX7348, ACX7024, ACX7100) have a detection time of 3x1000ms, whereas single-hop BFD sessions use a 300ms interval, which can lead to inconsistencies and potential issues in failure detection.

Resolved In:
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: Firewall support for DNX
1789481
Critical
L3 vlan tagged packets dropped and tagged as Egress Marking error in the Egress L3VPN interface over tunnels (IP, SRv6, Dynamic etc).
Product-Group=evo
On all Junos Evolved ACX7K platforms, L3VPN traffic over tunnels (including IP, SRv6, Dynamic, etc.) could drop due to an Egress Marking Error when these tunnels are configured. This issue can be identified by examining the output of the "show pfe statistics error" command.

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: 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
Continuous increase in framing errors observed on AE interface after doing RE switchover on Junos OS Evolved ACX7509 platform.

Resolved In: evo:23.2R2-S4-J6-EVO evo:23.2R2-S5-EVO evo:23.2X2-EVO evo:24.2R2-S3-EVO evo:24.4R2-EVO evo:24.4R2-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO
PR NumberSynopsisCategory: DNX VPLS
1896785
Major
Stale ARP details after RE switchover leading to traffic loss observed on ACX7K
Product-Group=evo
On all Junos OS Evolved ACX7K Platforms, Layer 3 traffic loss can occur after an RE reboot due to a race condition between ARP and VPLS programming.

Resolved In: evo:23.2R2-S4-J6-EVO evo:23.2R2-S5-EVO evo:23.2X2-EVO evo:24.2R2-S3-EVO evo:24.4R2-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO evo:26.1R1-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: software upgrade infra issues
1867902
Major
Software upgrade aborts or FPC does not come online on specific Junos Evolved PTX platforms while upgrading with an option validate-restart or add restart
Product-Group=evo
1. Software upgrade failure is observed on specific to Junos OS Evolved PTX platforms (PTX10004/PTX10008/PTX10016/PTX12K) when 'request system software validate-restart' or 'request system software add restart' is used to perform software upgrade and the base and target image have different IMA (Integrity Measurement Architecture) keys or successful 'request system software add restart', followed by a second 'request system software add restart' will fail and there is a low disk space issues on FPC. 2. FPC is not coming online on specific to Junos OS Evolved PTX platforms (PTX10004/PTX10008/PTX10016/PTX12K) when reboot is performed post installing an image with 'request system software add restart' and the base and target image have different IMA keys.

Resolved In: evo:22.2R3-S7-EVO evo:22.3X80-D49-EVO evo:22.4R3-S8-EVO evo:23.2R2-S5-EVO evo:23.4X100-D40-EVO evo:24.2R2-S2-EVO evo:24.4R2-EVO evo:24.4X200-D10-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
1859095
Minor
On Junos OS Evolved based platforms "Sysman.re" crash file might be observed in particular conditions
Product-Group=evo
On all Junos OS Evolved based platforms, when the RE (Routing Engine) node experiences switchover, offline/online transitions, or rebooting, a 'Sysman.re' crash file might appear in rare cases and could cause traffic impact.

Resolved In: evo:23.4X100-D40-EVO evo:24.2R2-S3-EVO evo:24.2X2-EVO evo:24.4R2-EVO evo:24.4X200-D10-EVO evo:24.4X200-D20-EVO evo:25.3R1-EVO junos:25.2R1
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
PR NumberSynopsisCategory: EVO Netstack Juniper Tunnel Driver Module
PR NumberSynopsisCategory: EVO MACSEC Platform Independent Implementation
1839514
Major
EVO PTX platform BGP keeps flapping with hold timer expiration after software upgrade due to MACsec MTU mismatch
Product-Group=evo
EVO releases with 23.1 and higher have increased the BGP TCP Socket Buffer size from 16k to 32k for performance improvements. If two EVO peers are at 23.1 or higher and MACsec interface MTU is not accommodated for the 32Byte overhead, BGP session might start flapping with hold timer expatriation.

Resolved In:
PR NumberSynopsisCategory: PRs related to software Agentd daemon on EVO
PR NumberSynopsisCategory: EVO-AFT interface and LAG PFE issues
1863060
Minor
Traffic drops will be observed when multiple interfaces are part of the same ASIC and configured with the same MAC address
Product-Group=evo
On Junos OS Evolved PTX platforms, when multiple interfaces are part of the same ASIC (Application-Specific Integrated Circuit) and configured with the same MAC (Media Access Control) address, traffic drops are observed. The issue happens as only one interface will function correctly, as it will be properly programmed with the MAC address. For the other interfaces, the MAC address entry gets overwritten.

Resolved In: evo:25.2R1-EVO evo:25.3R1-EVO
PR NumberSynopsisCategory: EVO RPD agent PRs
1820482
Minor
ECMP Route modifications can cause temporary traffic disruptions
Product-Group=evo
On all Junos Evolved ACX platforms, modifying an ECMP route triggers the deletion of the old Next Hop route, which can temporarily disrupt traffic flow until the new route is fully established.

Resolved In: evo:25.4R1-EVO evo:26.1R1-EVO
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1871034
Major
on QFX5130, duplicate-mac-detect action discard does not work . The action shutdown port should be used instead.
Product-Group=evo
When duplicate-mac-detect feature is configured, if the mac moves from leaf to network in a VXLAN enviroment, the action discard does not take effect. The mac move is prevented. As an alternate, use the action shutdown port instead which is also one of the supported options.

Resolved In:
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
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.

Resolved In: evo:23.2R2-S4-J6-EVO evo:23.2R2-S5-EVO evo:23.2X2-EVO evo:24.2R2-S3-EVO evo:24.2X2-EVO evo:24.4R2-S1-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO
PR NumberSynopsisCategory: ACX7509 platform, FEB, RCB and linecaard resi
1846199
Major
Device will not boot from secondary disk
Product-Group=evo
On Junos OS Evolved platforms, the system may access the backup SSD (/dev/sdb) frequently which will reduce the useful life of the SSD.

Resolved In: evo:22.3X50-EVO evo:22.3X50-J5-EVO evo:22.3X80-D49-EVO evo:23.2R2-S4-J6-EVO evo:23.2R2-S5-EVO evo:23.2X2-EVO evo:24.2R2-S1-EVO evo:24.4R2-EVO evo:25.1R1-EVO evo:25.2R1-EVO junos:24.4R2
PR NumberSynopsisCategory: N/A:sw-hamilton-timing:
1874475
Minor
PTP LAG interface GRES issue
Product-Group=evo
PTP on one particular LAG interface stops working on the ULC - MX10004, MX10008 Line Card - in the below scenarios: - Load override existing LAG+PTP config with some baseline config - Replace baseline config with the previous LAG+PTP config - Perform GRES and then on the new master we see that one of the slave LAG interfaces do not receive PTP packets. Issue is only seen in above scenarios. Other GRES scenarios work correctly wrt PTP

Resolved In: evo:25.2R1-EVO evo:25.3R1-EVO junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: Libjtask for RPD tasks, scheduler, timers, memory, and slip
1861810
Major
The process rpd is cored while adding or removing dynamic-tunnels
Product-Group=evo
On all Junos Evolved platforms, the indexing of next hop while adding or deleting dynamic tunnels causes the rpd process to core and restart. This is a timing issue.

Resolved In: evo:22.3X80-D49-EVO evo:24.2R2-S1-J8-EVO evo:24.2R2-S3-EVO evo:24.2X2-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:22.4R3-S9 junos:23.2R2-S5 junos:24.2R2-S2 junos:24.2R2-S4 junos:24.4R2 junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: Integrated Routing & Bridging (IRB) module
PR NumberSynopsisCategory: Platform infra to support jvision
PR NumberSynopsisCategory: Multiprotocol Label Switching
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
PR NumberSynopsisCategory: "ifstate" infrastructure
1882329
Minor
em0 mgmt port is unreachable after RE switchover
Product-Group=evo
On MX10008 with em0 disabled, the em0 port remains unreachable after performing RE switchover and re-enabling em0.

Resolved In: junos:25.4R1
PR NumberSynopsisCategory: Issues related to krt-async routing infrastructure
1866522
Major
VPLS session stays down after interface flaps
Product-Group=evo
An LSI IFL remains in RPD even after being deleted by the interface manager daemon. It is visible in show interface routing but not in show interfaces, indicating that RPD still holds the IFL despite its removal elsewhere. rpd-agent does not send a delete message to RPD due to a reference count issue. Another daemon?likely l2ald?still holds a reference to the IFL. rpd-agent only sends the delete once all references are cleared, which doesn't happen in this case. The fix is to send a "delete pending" message from rpd-agent to RPD. RPD will treat this as a delete and remove the IFL, ensuring consistency across the system.

Resolved In: evo:23.2R2-S5-EVO evo:23.2X2-EVO evo:24.2R2-S4-EVO evo:24.4R2-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:25.2R2 junos:25.3R1
PR NumberSynopsisCategory: RPD policy options
1887006
Minor
Deleting duplicate entries in a route-filter-list or source-filter-list can disrupt policy evaluation, leading to route withdrawal and traffic disruption for services using the filter-list
Product-Group=evo
On all Junos and Junos OS Evolved platforms, deleting one of multiple duplicate entries in a route-filter-list or source-filter-list can cause the remaining entry to be ignored. This leads to incorrect policy application for any service using that filter-list, resulting in route withdrawal, traffic loss, or other service disruptions.

Resolved In: evo:22.3X80-D49-EVO evo:25.4R1-EVO junos:25.4R1 junos:25.4R2
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
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:24.2R2-S3 junos:24.4R2 junos:25.2R1-S2 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: PTX10K platform specific fabric PRs
1870684
Major
Junos OS Evolved: OS command injection vulnerabilities fixed (CVE-2025-60006)
Product-Group=evo
Multiple instances of an Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in the CLI of Juniper Networks Junos OS Evolved could be used to elevate privileges and/or execute unauthorized commands. Please refer to https://supportportal.juniper.net/JSA103163 [juniper.net] for more information.

Resolved In: evo:22.3X80-D47-EVO evo:22.3X80-D49-EVO evo:24.2R2-S2-EVO evo:24.4R2-EVO evo:24.4R2-S1-EVO evo:24.4R2-S1-J1-EVO evo:25.2R1-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:24.2R2-S2 junos:25.2R1 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: PTX10K specific platform PRs
1711595
Major
Ungraceful FPC offline events cause egress PFE traffic disruptions on Junos Evolved PTX10008 and PTX10016 platforms
Product-Group=evo
On PTX10008 and PTX10016 platforms equipped with LC1201 or LC1202 line cards and running the Junos Evolved Operating System (OS), an ungraceful restart of a Flexible Port Concentrator (FPC) causes all egress traffic on the Packet Forwarding Engine (PFE) associated with that FPC to enter a fault state triggering the "disable-pfe" action resulting in traffic loss.

Resolved In: evo:22.3R2-S1-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.3X80-D40-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R1-S1-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
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: UI Infrastructure - mgd, DAX API, DDL/ODL
1704406
Major
XML validation failure may be seen with the "show host | display xml validate" command
Product-Group=evo
The XML output of "show host| display xml validate" command results in the "WARNING: Received the tag , the output may not have been properly xmlized." error.

Resolved In:
1769911
Major
File copy with password less authentication is failing with rpc request
Product-Group=evo
On all Junos and Junos OS Evolved platforms , file copy with password less authetication for a non-root user over Netconf is failing with rpc (Remote Procedure Call) request.

Resolved In: evo:22.3X50-EVO evo:22.3X80-D47-EVO evo:22.3X80-D49-EVO evo:24.4R1-EVO evo:25.1R1-EVO junos:22.3X60 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:
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: ACX724 platform issues
1895749
Critical
System crashes due to a CPU glitch
Product-Group=evo
On Junos Evolved ACX7024 and ACX7024X platforms, the system crashes and kernel core is generated due to a random CPU error.

Resolved In: evo:24.2R2-S3-EVO evo:24.2X2-EVO evo:24.4R2-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO
PR NumberSynopsisCategory: MX10K platform
1819263
Minor
The SNMP jnxFruRemoval/insertion trap OID is not being sent correctly when the FTC module or the fan tray module is inserted or removed
Product-Group=evo
On the MX10008 and PTX10008 platforms, when the Fan Tray Controller (FTC) or the fan tray is either removed or inserted, the device sends out SNMP traps with incorrect values (34 and 35) for the jnxFruRemoval and jnxFruInsertion OIDs. These values are not listed in Juniper's Management Information Base (MIB). This is a minor cosmetic issue.

Resolved In: evo:24.2R2-EVO evo:24.4R1-EVO junos:22.2R3-J11 junos:23.2R2-S2-J2 junos:23.2R2-S3-J5 junos:24.2R2 junos:24.4R1
PR NumberSynopsisCategory: ACX7000 platform software related issues.
1889258
Minor
SSD firmware for both primary & secondary SSD is not displayed
Product-Group=evo
SSD firmware for both primary & secondary SSD is not displayed

Resolved In: evo:23.2R2-S6-EVO evo:23.4R2-S7-EVO evo:24.2R2-S4-EVO evo:24.2X2-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO
PR NumberSynopsisCategory: Express ZX PFE L3 Features
1881324
Major
PTX10003-160C FPC may not restart properly on a high scale system
Product-Group=evo
A PTX10003-160C with high protocols scaling number, its FPC may not restart properly. An example of a high scaling number is a L2VPN gateway with more than 9000 outbound labels.

Resolved In: