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 25.2R1-S2-EVO is now available for download from the Junos software download site

Download Junos Software Service Release:

  1. Go to Junos Platforms - Download Software page
  2. Input your product in the "Find a Product" search box
  3. From the Type/OS drop-down menu, select Junos SR
  4. From the Version drop-down menu, select your version
  5. Click the Software tab
  6. Select the Install Package as need and follow the prompts

NOTE: Starting on August 30th, 2024, we include PR's severity with each entry. See KB86335 [juniper.net] for the definition of PR's Severity

 

Junos Selective Update (JSU) feasible

Not applicable

Call to Action

For your review.

Solution

Junos Software service Release version 25.2R1-S2-EVO is now available.

25.2R1-S2-EVO - List of Fixed issues

PR NumberSynopsisCategory: EVO interface software
1818352
Major		The picd process crash will be seen on PTX10001-36MR
Product-Group=evo
Severity=Major		On Junos OS Evolved PTX10001-36MR platforms with Coherent Optics (400G-QDD-ZR, 400G-QDD-ZR-M , 400G-QDD-ZR-M-HP and 100G-ZR), the picd (port interface concentrator daemon) leaks memory during normal operation, which will lead to its crash resulting in traffic loss.
PR NumberSynopsisCategory: Border Gateway Protocol
1864676
Major		The rpd process will crash due to memory leak
Product-Group=evo
Severity=Major		The rpd process will crash due to a memory leak when configuration using apply-groups or ephemeral database for "routing-options autonomous-system independent-domain".
1898734
Major		The rpd process crashes in an Inter-AS Option-AB L3VPN with BGP multipath list-nexthop enabled
Product-Group=evo
Severity=Major		On all Junos and Junos OS Evolved platforms, in an Inter-AS (Autonomous System) Option-AB L3VPN (Layer3 Virtual Private Network) scenario, if 'bgp multipath list-nexthop' is configured and a VRF (Virtual Routing and Forwarding) generates a route with list-nexthop that is advertised to an Option-AB peer, the rpd process crashes and generates a core-dump.
1907391
Major		Routes are hidden when accept-own feature is enabled with rib-sharding
Product-Group=evo
Severity=Major		On MX480 and MX960 platforms, routes become hidden when the "accept-own" feature is enabled in environments configured with rib-sharding. This issue arises when the "vrf-table-label" is configured within a routing instance and route sharding is enabled, potentially leading to routing failures.
1909599
Major		BGP prefixes get stuck in output queue forever, with BGP delay-route-advertisements and route-ack-converge feature enabled
Product-Group=evo
Severity=Major		BGP(Border Gateway Protocol) prefixes doesn't get advertise and stuck forever in the output queue, with BGP delay-route-advertisements and route-ack-converge feature enabled.
PR NumberSynopsisCategory: PFE L2 forwarding features on BT based platforms
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: MX304 Chassis specific platform
1905954
Critical		memory leak caused by using the "show ccl statistic summary ... " command
Product-Group=evo
Severity=Critical		On Junos OS and Junos OS Evolved platforms, running the command "show ccl statistic summary ... " cause memory leaks in the Packet Forwarding Engine (PFE).
PR NumberSynopsisCategory: Alias for DHCP issue on DNX based platform.
1889637
Major		DHCP clients do not come up when VRF leak and "dhcp-relay" with "no-snoop" are configured under a routing-instance
Product-Group=evo
Severity=Major		On all Junos OS Evolved ACX7K Series platforms, when DHCP (Dynamic Host Configuration Protocol) relay mode is used within a routing-instance scenario, DHCP clients fail to come up because DHCP offer packets are being dropped.
PR NumberSynopsisCategory: Segment Routing PFE part for v4 + SR-TE
1920723
Minor		MPLS traffic loss is observed due to the incorrect label pushing on PHP pop operation on Junos OS Evolved ACX7K platforms
Product-Group=evo
Severity=Minor		On all Junos OS Evolved ACX7K platforms, in an MPLS (Multi-Protocol Label Switching) scenario, due to the incorrect label pushing on PHP (Penultimate Hop Popping) pop operation, the MPLS traffic on the egress node is impacted.
PR NumberSynopsisCategory: Issues related to EVO Health Monitoring System
1892348
Major		Incorrect shared memory unit interpretation causes memory leak log errors
Product-Group=evo
Severity=Major		On all Junos OS Evolved platforms, the shared memory value in the CPU memory log is stored in bytes, but the memory leak detection logic interprets is as kilobytes. This unit mismatch leads to incorrect per-application memory usage calculations, resulting in memory leak error messages for various applications.
PR NumberSynopsisCategory: EVO L2 Control Plane PRs
1899530
Major		MAC learning failure when moving the AE interface from one VLAN to another VLAN in a single commit
Product-Group=evo
Severity=Major		On Junos OS Evolved platforms, when an Aggregated Ethernet (AE) logical interface (IFL) is moved from one Virtual LAN (VLAN) to another VLAN in a single commit, Layer 2 forwarding tables fail to update correctly. This causes Media Access Control (MAC) learning failure and traffic disruption.
1914423
Major		On-change telemetry events dropped when l2ald telemetry queue memory limit is not configured
Product-Group=evo
Severity=Major		On all Junos and Junos OS Evolved platforms, when l2-learning telemetry is enabled without explicitly configuring a memory limit for the l2ald (Layer 2 Address Learning Daemon) telemetry queue, the default memory limit is not applied. As a result, all on-change telemetry events are dropped.
PR NumberSynopsisCategory: EVO-AFT Infrastructure PFE related issues
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: SNMP, mib2d issues
1890712
Minor		The snmpwalk for OID ifJnxInputErrors is not working on Junos Evolved platforms
Product-Group=evo
Severity=Minor		On all Junos Evolved platforms, the snmpwalk for OID ifJnxInputErrors (1.3.6.1.4.1.2636.3.3.1.1.36) is not working. This issue has no impact on traffic.
PR NumberSynopsisCategory: EVPN control plane issues
1894803
Major		Inconsistency is observed between the ARP table learned on PE devices in EVPN-MPLS or EVPN-VXLAN Multihoming scenario
Product-Group=evo
Severity=Major		On all Junos OS and Junos OS Evolved platforms, during EVPN-MPLS (Ethernet VPN over MPLS) or EVPN-VXLAN (Ethernet VPN over VXLAN) multi-homing scenarios (active-active or active-standby) the ARP (Address Resolution Protocol) tables from Customer Edge (CE's) device may not update simultaneously on Provider Edge (PE) devices when an IP address moves between two different Ethernet Segments (ESIs) during a switchover, leading to temporary traffic disruption until the tables are refreshed.
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: ACX7509 Linecard (FPC) related issues
1898908
Major		The other port in a port group goes down after an RE switchover if one of the port in the port group is already down on an ACX7509
Product-Group=evo
Severity=Major		On Junos OS Evolved ACX7509 platforms, when one port in a channelized group (like ports 0 in a port group consisting of port 0 and port 1) is already in 'down' state in a ACX7509-FPC-16C with 16x100G-QSFP, performing a Routing Engine (RE) switchover or restarting the picd process can cause the other port in the port group to go down. This will lead to disruption of services running on the port.
PR NumberSynopsisCategory: ACX7509 Platform related issues
1848468
Minor		ACX7509 and QFX5700 may report SSD DMA error on secondary disk.
Product-Group=evo
Severity=Minor		ACX7509 and QFX5700 may report below SSD DMA error on secondary disk. In most cases there is no operational impact observed. New firmware being packaged into software via this PR fix will resolve this issue.
1907310
Major		After RE switchover on the device, the capacity of DC PSM is observed to be zero after toggling the input power
Product-Group=evo
Severity=Major		On all Junos OS Evolved platforms, whenever a Routing Engine (RE) switchover occurs and the DC input supply to one of the Power Supply Modules (PSMs) is toggled or flapped, the output capacity of that PSM becomes zero. If the remaining PSMs are unable to provide sufficient power to the chassis, all Flexible PIC Concentrators (FPCs) go offline, resulting in traffic impact.
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1867811
Major		L2ald memory usage increased up to100MB
Product-Group=evo
Severity=Major		On all Junos, the memory usage of the Layer 2 Address Learning Daemon (L2ALD) can increase rapidly due to the context history maintained by the Layer 2 Address Learning Manager (L2ALM), which can grow up to 100MB.
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
Severity=Major		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.
PR NumberSynopsisCategory: Multicast for L3VPNs
1902405
Major		The rpd process crash is observed with MVPN and RIB sharding enabled
Product-Group=evo
Severity=Major		On Junos MX and Junos Evolved PTX platforms , with RIB sharding enabled and if either IPv4 or IPv6 address family is disabled in MVPN (multicast virtual private network), the unicast route flow from shard tries to access MVPN data structures without validation leading to rpd (Routing Protocol Daemon) process crash.
PR NumberSynopsisCategory: JUNOS Network App Infrastructure (for ping, traceroute, etc)
1872704
Major		NTS for NTP not working even after the Ceritficate is validated with External servers like Chrony and NTPSec
Product-Group=evo
Severity=Major		NTS for NTP not working even after the Ceritficate is validated with External servers like Chrony and NTPSec
PR NumberSynopsisCategory: Periodic Packet Management Daemon
1909719
Critical		Junos and Junos OS Evolved platforms experience high CPU after FPC reboot causing unpredictable issues with protocols (OSPF/ISIS/BGP, etc.) managed by PPMD
Product-Group=evo
Severity=Critical		After upgrading or rebooting Junos/Junos OS Evolved platforms, a CPU spike may be observed in the PPMD (Periodic Packet Management Daemon) process due to repeated internal message failures. This can lead to BFD (Bidirectional Forwarding Detection) authentication failures. Additionally, other protocols that rely on authentication and PPMD for packet distribution may also be affected, potentially resulting in traffic loss.
PR NumberSynopsisCategory: Resource Reservation Protocol
1866944
Major		Traffic blackholing in LSPs due to link failure before protection signalling is processed
Product-Group=evo
Severity=Major		On all Junos and Junos OS 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.
1893822
Major		Record Route Object displayed in show mpls lsp output is trucated if number of hops is sixteen or more
Product-Group=evo
Severity=Major		If the number of RSVP LSP hops is sixteen or higher, the RRO displayed in show mpls lsp extensive output may get truncated
1896022
Major		More bandwidth admitted onto a TE link when Label Switched Paths (LSPs) undergoing make-before-break re-route over the same link carrying the bypass LSP during local repair
Product-Group=evo
Severity=Major		On all Junos and Junos evolved platforms with Point of Local Repair Router, in a Multiprotocol Label Switching(MPLS) Label Switched Paths (LSPs) set-up if the ingress router is configured with link-protection , if Label Switched Paths (LSPs) undergo local repair and subsequently undergo global repair in make-before-break fashion such that the LSPs are re-routed over the same TE link that carries the bypass LSP that protect the LSPs during local repair, then more re-routed LSPs may be admitted on the TE link carrying the bypass LSP than that should be admitted. This may result in some re-routed LSPs remaining on the TE link causing additional traffic sent on the TE link than the capacity of the TE link.
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
1863354
Minor		Command line freezes when Ctrl+Z is used
Product-Group=evo
Severity=Minor		In Junos OS Releases 24.2 and later(BSD 15), pressing Ctrl+Z in the Command Line Interface CLI suspends the process and causes it to become unresponsive. This behaviour is observed on systems using the and Berkeley Software Distribution BSD15 platform.

 

 

25.2R1-S2-EVO - List of Known issues

PR NumberSynopsisCategory: Issues related to EVO Health Monitoring System
1864882
Major		Ehmd fails to cleanup old directories past 25.2R1-EVO
Product-Group=evo		Due to the introduction of ancillary files to ehmd's log directory, it caused a regression in ehmd's cleanup script. Prior, it relied on certain directories becoming empty after cleaning up a further nested directory. This never comes true due to the newer files that were introduced. Which leads to /var/log/ehmd slowly growing over time.

Resolved In: evo:25.1R1-EVO evo:25.2R1-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO evo:25.4R2-EVO junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: Paragon Active Assurance
1886928
Major		PAA installation failure on reboot due to "Not found default vrf" error
Product-Group=evo		When a device is rebooted with PAA installed in 25.2R1 , PAA installation on reboot may fail due to "Not found default vrf" error. This can be resolved by deactivating and activating or freshly installing the PAA configuration

Resolved In: evo:25.2R2-EVO evo:25.4R1-EVO junos:25.4R1
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:23.4R2-S7-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 evo:25.4R1-S1-EVO
PR NumberSynopsisCategory: Configuration mgmt, ffp, load-action, commit processing
1751574
Major		Netconf RPC commit fails due to commit warning received for unprotect operation, CLI commit completes with warning
Product-Group=evo		In Netconf private edit configuration session, commit RPC fails when unprotect operation is performed.

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

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

 

Modification History

First publication 2026-01-13