Alert Type

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

Product Affected

ACX PTX QFX platforms running Junos Evolved Software

Alert Description

Junos Software Service Release version 24.4R2-S4-EVO is now available for download from the Junos software download site

Download Junos Software Service Release:

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

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

 

PTX-Specific Platform Notification:

We have re-issued 24.4R2-S4-EVO to include additional PRs for PTX platforms. This is especially important for PTX10008 with LC1301 and SF5.

The new version is posted on the software download site. The new image can be identified with the ".15" respin number. The full package name is junos-evo-install-ptx-x86-64-24.4R2-S4.15-EVO.iso

The direct download link is: https://webdownload.juniper.net/swdl/dl/secure/site/1/record/196029.html?pf=PTX10008 

The following PRs have been included in the 24.4R2-S4.15-EVO image; release notes have been added in the table.

  • 1964102 1915594 1932267 1936725 1945978

 

Junos Selective Update (JSU) feasible

Not applicable

Call to Action

For your review.

Solution

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

24.4R2-S4-EVO - List of Fixed issues

PR NumberSynopsisCategory: Fabric for LC1300 and SIB3
1964102
Major		A system with LC1301 and SF5 raises a fabric capacity alarm rather than major link fault alarms when minor fabric degradation occurs.
Product-Group=evo
Severity=Major		LC1301 with SF5 platforms: isolated fabric link faults could trigger major alarms despite minimal impact to overall fabric operation. The system now raises a "less than acceptable fabric capacity" alarm when fabric capacity falls below platform-defined thresholds.
PR NumberSynopsisCategory: Tracking interface specific issues for Aegon Line card
1945978
Major		Interfaces remain down on PTX10008/PTX10004 with LC1301 line cards when 2X100G speed is configured before QSFP optics insertion
Product-Group=evo
Severity=Major		On PTX10008 and PTX10004 platforms running Junos Evolved affected releases with LC1301 line cards, Ethernet interfaces remain down when the 2x100G interface speed is configured before Quad Small Formfactor Pluggable (QSFP) transceivers are inserted and the optical signal is up. This condition affects dataplane connectivity and can result in loss of traffic on the impacted interfaces.
PR NumberSynopsisCategory: N/A:sw-aegon-resiliency:
1936725
Major		Junos EVO platform fails to recognize a SIB card after it experiences a power failure
Product-Group=evo
Severity=Major		On PTX10004, PTX10008 and PTX10016 platforms running Junos OS Evolved, when a Switch Interface Board (SIB) experiences a power failure and is later replaced with a healthy SIB, the device fails to recognize the installed SIB. The affected SIB slot remains in an Empty state, resulting in reduced switch fabric capacity, loss of fabric redundancy, and potential traffic impact under load.
PR NumberSynopsisCategory: "agentd" software daemon
1779722
Minor		The interface fails to come up after FPC reboot if the streaming server and export profile are not configured correctly
Product-Group=evo
Severity=Minor		On all Junos and Junos evolved platforms with telemetry enabled, if the streaming server and export profile for reporting-rate are not properly configured in the analytics settings, rebooting the FPC would prevent any of the interfaces from coming up.
1923848
Major		Junos Evolved platfrom, when gNMI collecting data from "optics/lanediags/lane/lane_laser_receiver_power_dbm" and "optics/lanediags/lane/lane_laser_output_power_dbm" are unreadable
Product-Group=evo
Severity=Major		The JavaScript Object Notation (JSON) encoding of leafs of type "ieeefloat32"(https://github.com/openconfig/public/blob/master/release/models/types/openconfig-types.yang#L127) is not correct, causing gRPC Network Management Interface (gNMI) data outputs unreadable.
1929823
Major		The sysd process crashes with error logs upon exceeding its memory limit
Product-Group=evo
Severity=Major		On Junos OS Evolved platforms with telemetry streaming configured, the sysd (System Daemon) process crashes on the backup RE (Routing Engine), and error logs are observed when sysd memory usage continues to grow over time, and the memory limit is exceeded. This issue is observed when the 64-bit sysd consumes more memory than the configured system limit when the device has been running for a long time (typically more than 100 days) in the dual RE scenario.
1930303
Major		NA-GRPCD process crashes when the collector terminates where the dial-out telemetry sensor is added through CLI configuration
Product-Group=evo
Severity=Major		On Junos OS Evolved platforms, the na-grpcd process crashes where dail-out telemetry is enabled and sensor is added through CLI configuration and the collector is terminated. This does not impact any service.
PR NumberSynopsisCategory: PTX1000s Interfaces software
1896329
Minor		Interfaces take 30 seconds to come up for a short LOS event
Product-Group=evo
Severity=Minor		On PTX10002-36QDD, interfaces take 30 seconds to come up for a short LOS (Loss of Signal) event.
PR NumberSynopsisCategory: Border Gateway Protocol
1889749
Critical		BGP Prefix-SID Label collision causing RPD crash
Product-Group=evo
Severity=Critical		On all Junos and Junos OS Evolved platforms, In Segment Routing the RPD ( Routing Protocol Daemon ) crash was observed due to different prefixes were trying to use same label, when Bgp prefix SID ( Segment Identifier ) feature was configured and labels were derived using the SID index.
1935730
Major		BGP session teardown due to incorrect 'prefix-limit maximum exceeded' error when RIB sharding is enabled
Product-Group=evo
Severity=Major		On all Junos and Junos OS Evolved platforms, when prefix-limit or accepted-prefix-limit is configured under family route-target with rib-sharding, prefix-limit will be incorrectly reported as 'prefix-limit maximum is exceeded'. This causes the BGP session to go down immediately. This occurs because the system incorrectly counts each received route multiple times (once for the main thread and once for each shard)
PR NumberSynopsisCategory: BGP BMP Software
1908215
Minor		BMP traces continues to fill the trace file even after removing BMP traceoptions configuration
Product-Group=evo
Severity=Minor		On all Junos OS and Junos OS Evolved platforms, enabling BMP(BGP Monitoring Protocol) tracing with local-rib monitoring continues to fill the trace file even after removing BMP trace option Configuration it is still running this on a cRPD instance, this creates a risk of the space exhaustion on a host that contains other production cRPDs.
PR NumberSynopsisCategory: Track PRs in BGP Flow Spec area & is part of BGP inside RPD.
1945627
Minor		BGP IPv6 Flow Specification Session Flapping When inet6-flow Is Enabled
Product-Group=evo
Severity=Minor		In certain Junos OS releases, BGP sessions may repeatedly reset when IPv6 Flow Specification (inet6-flow) is enabled. This behavior occurs when the router receives specific IPv6 Flow Specification updates that include a default (wildcard) match. Earlier releases do not exhibit this behavior, leading to a difference in observed stability when upgrading.
PR NumberSynopsisCategory: PTX10003 Platform related issues
1915594
Major		PICD process core observed on device
Product-Group=evo
Severity=Major		On all Junos OS Evolved platforms, due to software segmentation fault, optics firmware reports a max_lane_count greater than 8. This causes the picd process to core resulting in traffic loss. This is a rare issue.
PR NumberSynopsisCategory: QOS issues in EVO for BCM XGS Platforms
1829998
Major		Intermittent evo-pfemand crash when SNMP query is performed immediately after PFE restart
Product-Group=evo
Severity=Major		On all Junos Evolved platforms, the evo-pfemand crashes intermittently when interface statistics is fetched through SNMP (Simple Network Management Protocol) query immediately after PFE (Packet Forwarding Engine) restart. This issue is seen after multiple PFE restarts and recovers after the evo-pfemand restart.
PR NumberSynopsisCategory: PFE COS features on BT based platforms
1918366
Minor		10G channelized interface fails to reach full line rate due to low-rate queue overscheduling
Product-Group=evo
Severity=Minor		On Junos OS Evolved PTX10004, PTX10008 and PTX10016 platforms using LC1201 or LC1202 line cards, a 10G channelized interface created from a 100G or 400G port may fail to reach full line rate. This issue occurs because the interface cannot fully utilize the link due to scheduler behavior when the interface has more than 4 channels and one or more output queues are set to a 5% or lower rate limit and receive a very high offered load compared to other queues.
PR NumberSynopsisCategory: 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: BX PFE firewall issues
1949690
Major		ASIC error triggers PFE disable state on PTX10002-36QDD platform and LC1301 line card with active counter processing
Product-Group=evo
Severity=Major		On PTX10002-36QDD platform and LC1301 line card, under high-traffic conditions with active counter processing on a loopback interface, an ASIC error may be triggered, causing the Packet Forwarding Engine (PFE) to enter a disabled state. This results in all interfaces going down and leads to complete traffic loss.
PR NumberSynopsisCategory: Express PFE MPLS BX platforms
1940918
Major		Traffic drops in 6VPE deployments without IPv6 enabled core interfaces
Product-Group=evo
Severity=Major		On Junos OS Evolved PTX platforms, the traffic will be dropped when IPv6 traffic is over IPv4 MPLS (Multiprotocol Label Switching.) tunnel under BGP (Border Gateway Protocol) 6VPE (IPv6 VPN Provider Edge) environment.
PR NumberSynopsisCategory: QFX Access Control related
1905612
Major		Correct values of ACCTG-Terminate-cause are not getting populated in ACCTG-STOP message.
Product-Group=evo
Severity=Major		Correct values of ACCTG-Terminate-cause are not getting populated in ACCTG-STOP message for few scenarios as mentioned below: Ageout of client mac clear ethernet-switching-table clear dot1x interface
PR NumberSynopsisCategory: QFX Control Plane VXLAN
1921796
Minor		Traffic dropped after priority change in VRRP with EVPN-VxLAN scenario
Product-Group=evo
Severity=Minor		On all Junos and Junos Evolved platforms, in Virtual Router Redundancy Protocol (VRRP) with Ethernet Virtual Private Network - Virtual Extensible Local Area Network (EVPN-VXLAN) scenario, when VRRP priority is changed, the VRRP virtual Media Access Control (MAC) address can remain pinned as a static entry on the remote device. As a result, MAC movement does not occur correctly, and VRRP packets are dropped on the leaf device. This impacts VRRP operation after priority changes.
PR NumberSynopsisCategory: CoS support on DNX
1833976
Major		Commit error when deleting interface with hierarchical scheduler enabled
Product-Group=evo
Severity=Major		On ACX7100 and ACX7348 platforms running Junos EVO 24.4R1, a commit error may occur when attempting to delete an interface (IFD) that has the hierarchical scheduler enabled and configured. The hierarchical scheduler is a required dependency for the output traffic control profile applied on interface sets (IFLSET). During commit validation, this dependency is enforced, preventing interface deletion until associated hierarchical scheduler configurations are deactivated.
PR NumberSynopsisCategory: Host path software for ACX 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.
1922793
Major		Error messages are seen on Junos OS Evolved ACX and QFX platforms
Product-Group=evo
Severity=Major		On Junos OS Evolved ACX and QFX platforms, when "set system ddos-protection protocol " is configured or ddos-protection configuration is deleted or when "show ddos-protection protocol" is executed then below logs will be seen.DDOS:POLICE: DdosPolicer does not exist DDOS:POLICE: Ddos group does not exist.
PR NumberSynopsisCategory: Layer 3 forwarding, both v4+v6
1924450
Major		L3VPN traffic drop due to incorrect destination MAC after MAC move in core
Product-Group=evo
Severity=Major		On all Junos OS Evolved ACK7K platforms, When a Media Access Control (MAC) address change or move occurs on the core side of the ingress Provider Edge (PE) node in a Layer 3 Virtual Private Network (L3VPN) topology, the ingress PE correctly updates the unicast Internet Protocol version 4 (IPv4) next-hop via Address Resolution Protocol (ARP); however, the dependent IPv4 to Multiprotocol Label Switching (MPLS) (indirect) L3VPN next-hop fails to update its destination MAC address. As a result, L3VPN MPLS traffic is forwarded with a stale destination MAC address, leading to incorrect packet forwarding and service impact.
PR NumberSynopsisCategory: DNX Multicast
1931648
Major		VPLS Layer 2 multicast traffic might be duplicated after output traffic control profile or HCOS interface configuration changes
Product-Group=evo
Severity=Major		On Junos OS Evolved ACX platforms, when HCOS (Hierarchical Class of Service) and class of service are enabled for VPLS (Virtual Private LAN Service), deactivating and reactivating the output-traffic-control-profile or making HCOS interface configuration changes might cause L2 (Layer 2) multicast traffic to be duplicated toward the access interface.
PR NumberSynopsisCategory: JUNOS Dynamic Profile Configuration Infrastructure
1930036
Major		High memory usage is showing, when we configure unsupported licensing feature
Product-Group=evo
Severity=Major		On all Junos EX and QFX platforms operating in an EVPN (Ethernet Virtual Private Network) environment, this issue occurs when the CLI command 'licensing hourly update' is executed on a device that does not support the licensing feature.
PR NumberSynopsisCategory: EVO ARP related PRs
1934771
Minor		PyEZ Issue, failing on RPC request "show arp interface <>" to EVO platforms
Product-Group=evo
Severity=Minor		On all Junos Evolved platforms, on invalid interface fetching, display error is seen on "show arp interface <>" command.
PR NumberSynopsisCategory: Firewall related development
1935328
Minor		Prolonged commit time with largescale lo0 filter binds cause configuration load failure
Product-Group=evo
Severity=Minor		On Junos OS Evolved platforms, commit operations with ~38005000 lo0 filter binds take ~4m42s (vs <1m expected). If commit exceeds 5 minutes, mgd times out, which cause configuration load failure and service impact.
PR NumberSynopsisCategory: Issues related to debug utilties - objmon, objshell/Dashboard
1932148
Minor		[EVO] snmp get-next on hrStorage mib fails every 10 seconds
Product-Group=evo
Severity=Minor
PR NumberSynopsisCategory: EVO Netstack Juniper Tunnel Driver Module
1919313
Major		The LDP session does not come up when an IPsec SA is configured under OSPFv3
Product-Group=evo
Severity=Major		On Junos Evolved platforms, when Open Shortest Path First version 3 (OSPFv3) Internet Protocol Security (IPsec) SA is applied at the interface (IFD/IFL) level, Label Distribution Protocol (LDP) is able to discover the neighbor via User Datagram Protocol (UDP) Hellos, but fails to bring up the Transmission Control Protocol (TCP) session, preventing the LDP session from becoming operational. Disabling the OSPFv3 IPsec SA immediately restores normal LDP operation. During the service impact, the session will be down and traffic will not be send. Once the LDP session comes up, traffic can be routed through it.
PR NumberSynopsisCategory: EVO linux defects & enhancement requests
1939674
Major		RTC time sync delay after reboot on Junos OS Evolved platforms
Product-Group=evo
Severity=Major		On all Junos OS Evolved platforms, due to linux kernel issue, periodical sync from system time to RTC (Real-Time Communication) every 11min stops working when system time moves to backwards.
PR NumberSynopsisCategory: Issues related to NTP issues on evo
1909908
Critical		Junos OS Evolved: A port which has been inadvertently exposed can be reached by an attacker (CVE-2026-33803)
Product-Group=evo
Severity=Critical		An Improper Restriction of Communication Channel to Intended Endpoints vulnerability in Juniper Networks Junos OS Evolved allows an unauthenticated, network-based attacker to cause a limited information disclosure and availability impact to the device. Please refer to https://supportportal.juniper.net/JSA110078 [juniper.net] for more details.
PR NumberSynopsisCategory: Express PFE Tunnels on ptx-evo platforms
1921577
Major		UDP Source Port cannot hash when using FTI tunnel interface for MPLS traffic
Product-Group=evo
Severity=Major		On Junos OS Evolved PTX Series platforms with incoming MPLS packets and outgoing MPLS over UDP configured over a Flexible Tunnel Interface (FTI), MPLS over UDP traffic for the same label would have the same source port. This would affect load balancing mechanism and can lead to inefficient utilization of links.
PR NumberSynopsisCategory: EVO TCP AO module
1924030
Major		BGP/LDP sessions flap due to TCP sequence number wraparound when TCP-AO is enabled
Product-Group=evo
Severity=Major		On all Junos OS Evolved platforms, Border Gateway Protocol (BGP) or Label Distribution Protocol (LDP) sessions will intermittently flap when Transmission Control Protocol-Authentication Option (TCP-AO) is enabled under high traffic or long-lived connections due to TCP sequence number rollover, leading to TCP authentication failures. The issue is primarily observed in interoperability scenarios and does not cause system crashes.
PR NumberSynopsisCategory: eventd, syslog infra issues
1919638
Major		Certain Junos EVO applications may become unresponsive during trace file rotation
Product-Group=evo
Severity=Major		On Junos EVO platforms, frequent trace file rotation may cause certain EVO applications to become unresponsive.
PR NumberSynopsisCategory: mgd, ddl, odl infra issues
1954021
Minor		CLI session timeout clears terminal scroll back
Product-Group=evo
Severity=Minor		On all Junos OS Evolved platforms, when a CLI(Command Line Interface) session times out, it triggers a terminal reset which clears the visible screen and scrollback buffer. As a result, users are unable to view previous command outputs.
PR NumberSynopsisCategory: SNMP, mib2d issues
1932267
Major		SNMP traps related to optics/optic's media lane alarms will not be raised
Product-Group=evo
Severity=Major		On Junos OS Evolved platforms, SNMP(Simple Network Management Protocol) management systems do not receive related to optics or transceiver lane and module alarm traps.
PR NumberSynopsisCategory: EVPN control plane issues
1910546
Minor		IM NH table synchronization failures during Routing Engine switchover
Product-Group=evo
Severity=Minor		On all Junos and Junos Evolved platforms configured with Multiple Protocol Label Switch (MPLS) Virtual Private Network (VPN) services profiles, repeated backtoback routing engine (RE) switchovers can cause an RE0toRE1 switchover to fail to populate Internal Memory Next-Hop (IM NH) table entries, resulting in lookup related errors and impacting the forwarding of Broadcast, Unknownunicast, and Multicast (BUM) traffic and routing engine switchovers which are critical for network stability.
1912156
Minor		Enhancement to retain route-target community after auto-import VRF routes
Product-Group=evo
Severity=Minor		On all Junos OS and Junos OS Evolved platforms, an enhancement added to retain the route-target community after auto-importing Virtual Routing and Forwarding (VRF) routes from an Ethernet Virtual Private Network (EVPN) route to an IP Virtual Private Network (IPVPN) route.
PR NumberSynopsisCategory: Express AFT Common FW issues
1934506
Major		The FPC crashes when VLANs on an AE interface are updated or deleted
Product-Group=evo
Severity=Major		On all Junos OS Evolved PTX Series platforms with multiple VLANs on an Aggregate Ethernet (AE) interface and an Firewall filter with family ethernet switching and bandwidth policer attached to both the AE interface and its associated VLAN interfaces, a modification or deletion of the VLANs will lead to a FPC crash. All the traffic over the affected FPC will be dropped.
PR NumberSynopsisCategory: Express PFE FW Features
1911372
Minor		The evo-aftmand process crashes when the prefix list is modified in scaled scenario
Product-Group=evo
Severity=Minor		On all Junos OS Evolved PTX platforms, a filter installation failure under high prefix utilization leaves the system in an inconsistent internal state, and subsequent modification of prefix lists or prefixes in the in the same scaled filter can further result in evo-aftmand process to crash and traffic loss seen until process auto recover.
PR NumberSynopsisCategory: Enhanced Broadband Edge support for firewall
1928462
Major		FPC crash occurs after configuration changes are made to a service-filter on specific MX platforms
Product-Group=evo
Severity=Major		FPC crash and aftd-trio core-dump will be observed on MX platforms supporting MPC10E, MPC11E, LC9600 line cards, and MX304 after configuration changes were made to a service-filter which was in use by BBE subscribers.
PR NumberSynopsisCategory: ACX7348 PTP
1793926
Major		[Clocking Solution]:ACX7348: PTP performance is not working as expected for asymmetry config
Product-Group=evo
Severity=Major		This is day-1 issue of jnpr servo. It exist's on all ACX platforms where JNPR servo runs. Once the asymmetry configured at slave port, The error propagated to the down stream eventually cause this this perf issue of spike .
1892686
Major		PTP delay message sent from different LAG after RE switchover
Product-Group=evo
Severity=Major		On Junos OS Evolved ACX7332 and ACX7348 platforms, after Routing Engines( RE) switchover the Precision Time Protocol (PTP) delay message is sent from different REs when Link Aggregation Group (LAG) members are configured on different Flexible PIC Concentrators (FPCs) leading to PTP timing discrepancy.
PR NumberSynopsisCategory: ACX7509 Linecard (FPC) related issues
1894512
Minor		Interfaces Fail to Come Up After Repeated Activation and Deactivation of Ports with 1G SFP-T Optics on Junos OS Evolved Platforms
Product-Group=evo
Severity=Minor		On all Junos OS Evolved platforms supporting 1G SFP-T optics , repeated deactivation and reactivation (~12+ cycles) of such interfaces can cause the interface to go down permanently. All the services and traffic running on that interface will be affected.
1931077
Major		CRC errors and packet loss are being observed at the peer device when using 1G fibre optic connections
Product-Group=evo
Severity=Major		On Junos OS Evolved ACX7509, ACX7348, ACX7332, and ACX7100-32C platforms with 1G fibre Optics, when the Inter-Packet Gap (IPG) setting intermittently falls below the IEEE minimum requirement of 8 bytes, and traffic passes through the PHY, certain receiving devices are sensitive to this reduced IPG, which leads to CRC (Cyclic Redundancy Check) errors and packet loss on the peer device connected to 1G fibre optics connection.
PR NumberSynopsisCategory: jdhcpd daemon
1911001
Major		On Junos devices supporting subscriber services acting as DHCPv6 relay randomly deletes IA_NA or IA_PD binding/route
Product-Group=evo
Severity=Major		On all Junos devices supporting subscriber services, in case of dual stack DHCP (Dynamic Host Configuration Protocol) subscribers with IA_NA (Identity Association for Non-temporary Address) and IA_PD (Identity Association for Prefix Delegation) bindings with lease times (For the assignment of IPv6 address to a client device), when a client initiates separate renew exchanges for the IA_NA and IA_PD, and once client and DHCP server are in sync with these timers, there can be a race condition at Junos device which is DHCPv6 relay, has not refreshed lease timer and can go out of sync. This can result in deleting IA_NA/IA_PD binding and route to get deleted for that subscriber only. This causes one of the leg for IA_PD or IA_NA to go down for that subscriber, which can result in traffic impact for that leg.
1916981
Minor		Core and context for jdhcpd saved in /var/tmp/jdhcpd.core-tarball.0.tgz
Product-Group=evo
Severity=Minor		When the jdhcpd process encounters an internal exception, the process may generate a core file and save the relevant diagnostic context in /var/tmp/jdhcpd.core-tarball.0.tgz. This data is intended to assist Juniper support in root-cause analysis. The impact is limited to the affected jdhcpd process instance and recovery follows the standard process restart behavior.
1927449
Major		Jdhcpd cores generated after upgrade
Product-Group=evo
Severity=Major		jdhcpd cores seen after upgrade with dhcpv6 for IANA/PD
PR NumberSynopsisCategory: Layer 2 Control Module
1930380
Major		The hash collision for storm control profile indices will result in an l2ald process crash
Product-Group=evo
Severity=Major		On all Junos OS platforms and Junos OS Evolved platforms which supports storm control, when a different storm-control profile is applied for interface where these profile have same profile index allocated then the storm control profile configuration and system state will not be in sync and a different profile will be applied for interface binding due to profile index collision which results into l2ald process crash.
PR NumberSynopsisCategory: Layer2 forwarding on EX/NFX/PTX/QFX
1928530
Critical		A buffer overflow during IPv6 NDP operations in an EVPN environment caused segmentation faults leading to FPC crash files and repeated reboots
Product-Group=evo
Severity=Critical		On JunOS MX240/MX480/MX960/MX2008/MX2010/MX2020 platforms with MPC10E/MPC11E line cards as well as the MX304 platform, an issue in IPv6 EVPN (Ethernet Virtual Private Network) during NDP (Neighbor Discovery Protocol) resolicitation of a link local target address causes the system to use the IRB link local address in outgoing packets. Stack corruption happens when handling the IRB link local address and resulting in continuous FPC (Flexible PIC Concentrator) reboots (around 3 or 4 times) and crash files generation.
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.
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.
1923867
Minor		The rpd process crash is observed after a graceful restart in the RSVP-TE scenario
Product-Group=evo
Severity=Minor		On Junos OS and Junos OS Evolved platforms with Graceful Restart and RSVP-TE (Resource Reservation Protocol - Traffic Engineering) configured, an rpd crash is observed, leading to traffic impact after a Graceful Restart if a PVC (Permanent Virtual Circuit) fails to allocate correctly during this recovery process, leaving it in an incomplete or unallocated state, and the system attempts to clean up or remove this unallocated PVC.
PR NumberSynopsisCategory: N/A:sw-octomore-qsfp-intf:
1946222
Major		Excessive transceiver configuration mismatch debug messages could be generated during periodic monitoring
Product-Group=evo
Severity=Major		When a transceiver configuration mismatch was detected, periodic monitoring generated repetitive debug messages that could flood picd logs. This issue has been fixed by suppressing redundant log generation while preserving mismatch detection and reporting.
PR NumberSynopsisCategory: Protocol Independant Multicast
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: Issues related to PKI daemon
1901098
Major		PFE Crash observed platforms where PKI and SSL-Proxy services are configured
Product-Group=evo
Severity=Major		In stressful conditions, FPC crash observed and core file generated when PKI (Public key infrastructure) and SSL-Proxy (Secure Sockets Layer) services are configured, on all Junos platforms supporting PKI and SSL-Proxy services (MX, PTX, SRX).
PR NumberSynopsisCategory: Periodic Packet Management Daemon
1931633
Major		PFE crash due to memory corruption when STP is enabled
Product-Group=evo
Severity=Major		On all Junos Platforms, a rare memory corruption condition may occur in the Packet Forwarding Engine (PFE) when Spanning Tree Protocol (STP) is enabled and operating in default (distributed) mode. When the issue is triggered, the PFE crashes and a dc-pfe core file is generated. The exact trigger for the memory corruption is currently unknown.
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1907558
Major		The rpd process crashes in a vrf having EVPN-VXLAN routes with specific configuration.
Product-Group=evo
Severity=Major		In all Junos and Junos OS Evolved platforms, when EVPN-VXLAN (Ethernet Virtual Private Network-Virtual Extensible LAN) routes are present in a VRF (Virtual Routing and Forwarding), configuring a generate route in same vrf can cause rpd (Routing Protocol Daemon) to crash and restart. Generate route configuration has to be removed to recover from this behaviour.
PR NumberSynopsisCategory: SNMP Infrastructure (snmpd, mib2d)
1906718
Critical		Junos OS and Junos OS Evolved: CVE-2022-24805 resolved in net-SNMP
Product-Group=evo
Severity=Critical		CVE-2022-24805 has been resolved in net-SNMP software included with Juniper Networks Junos OS and Junos OS Evolved. Please refer to https://supportportal.juniper.net/JSA107822 [juniper.net] for more information.
PR NumberSynopsisCategory: Trio pfe stateless firewall software
1919115
Major		MPC restart during commit when modifying the prefix-list in firewall filters
Product-Group=evo
Severity=Major		On MX platforms with MPC7E-MRATE line cards, committing firewall filter changes that include prefix-list match conditions can cause an MPC (Modular Port Concentrator) restart.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1902358
Minor		RPC crash when non-ASCII character is included in XML data result
Product-Group=evo
Severity=Minor
PR NumberSynopsisCategory: Issues related to NETCONF
1894296
Major		GNMI Get on openconfig returns not-found when only root-level openconfig metadata is configured
Product-Group=evo
Severity=Major		On Junos Evolved platforms, a gNMI Get request for the OpenConfig root (origin: openconfig, type CONFIG) returns a NOT_FOUND error when only root-level OpenConfig metadata is configured and no OpenConfig configuration data nodes are present. In this scenario, the configured OpenConfig metadata is not returned unless at least one OpenConfig configuration subtree exists.
PR NumberSynopsisCategory: ACX724 platform issues
1895749
Critical		BIOS version 22.01 - for ACX7024 - System crashes due to a CPU glitch
Product-Group=evo
Severity=Critical		On Junos Evolved ACX7024 and ACX7024X platforms, the system crashes, and a kernel crash is generated due to a random CPU error.
PR NumberSynopsisCategory: Virtual Private LAN Services
1885690
Major		rpd crash on backup RE during switchover due to VPLS Auto-Site mismatch
Product-Group=evo
Severity=Major		An rpd core triggered on the backup Routing Engine after a switchover due to an assertion failure in within the context of L2VPN VPLS auto-site processing, caused by a mismatch between the auto-site claim-id/site-id and the local site-id associated with interfaces in the VPLS IFL repository for a given instance, leading to stale interface entries being referenced during auto-site processing.
PR NumberSynopsisCategory: ACX7000 platform software related issues.
1935793
Major		I2C alarm and traffic drop is seen with a type of QSFP on certain ACX platforms
Product-Group=evo
Severity=Major		On Junos OS Evolved ACX7100-32C, ACX7100-48L, ACX7100-32C-K and ACX7100-48L-K platforms when QSFP-100G-FR optics which has serial number starting with 2J4 is plugged in, it is observed that the port goes down with I2C(Inter-Integrated Circuit) access failure alarm and traffic is dropped.
PR NumberSynopsisCategory: Express ZX PFE L3 Features
1923943
Major		Routing approachs/protocols sees forwarding issue on Junos OS Evolved PTX10003 platforms
Product-Group=evo
Severity=Major		Routing protocols sees forwarding impact on Junos Evolved PTX10003 platforms when a nexthop transitions between forwardable and hold/reject states, causing the nexthop token to fail reacquisition and leading to unresolved forwarding plane dependencies.

24.4R2-S4-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:24.2R2-S5-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:25.2R2 junos:25.3R1
PR NumberSynopsisCategory: "agentd" software daemon
1855002
Major		gRPC connections fail when the gRPC server is configured in a VRF
Product-Group=evo		On Junos and Junos OS Evolved platforms, when the gRPC (Google Remote Procedure Call) server is configured in a VRF (Virtual Routing and Forwarding) instance, , the connections through that VRF fail and the gRPC service does not work as expected.

Resolved In: evo:22.3X80-D47-EVO evo:22.3X80-D49-EVO evo:25.3R1-EVO junos:25.3R1
1933395
Major		System connections are not established while Subscribing for OC path using ssl local-certificates after upgrading to 24.4R2-S3-EVO
Product-Group=evo		System connections are not established while Subscribing for OC path using ssl local-certificates after upgrading to 24.4R2-S3-EVO. This issue is only applicable on 24.4R2-S3-EVO and 24.4R2-S4-EVO

Resolved In: evo:24.4R2-S3-J1-EVO evo:24.4R2-S3-J11-EVO evo:24.4R2-S3-J14-EVO evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:24.2X1 junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: Border Gateway Protocol
1915893
Major		The rpd process crash triggered by LLGR stale timer expiry and late reconnection of unconfigured BGP peer on helper node
Product-Group=evo		On all Junos OS and Junos OS Evolved, when Long-Lived Graceful Restart (LLGR) is configured and a Border Gateway Protocol (BGP) neighbor goes down and reconnects after the LLGR stale timer expires, the Routing Protocol Daemon (rpd) process crashes leading to service disruption.

Resolved In: evo:23.2R2-S7-EVO evo:23.4R2-S8-EVO evo:24.2R2-S4-EVO evo:25.2R2-EVO evo:25.4R1-S1-EVO evo:25.4R2-EVO evo:26.1R1-EVO evo:26.2R1-EVO junos:21.2R3-S11 junos:21.4R3-S13 junos:22.4R3-S10 junos:23.2R2-S7 junos:23.4R2-S8 junos:24.2R2-S4 junos:24.4R2-S4 junos:25.2R2 junos:25.2R2-S1 junos:25.4R1-S1 junos:25.4R2 junos:26.1R1 junos:26.2R1
PR NumberSynopsisCategory: BGP Segment Routing
PR NumberSynopsisCategory: PTX10003 Platform related issues
1944331
Critical		On the JunosEvolved PTX10003 platform, post-upgrade or reboot, alarms were raised before interface initialization causing false alarms
Product-Group=evo		On the JunosEvolved PTX10003 platform, following an upgrade or reboot, alarms were triggered before ethernet interfaces became operational, resulting in false alarms on the device. There is no operational or functional impact.

Resolved In: evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:25.4R2 junos:26.2R1 junos:26.3R1
PR NumberSynopsisCategory: EVO Layer-2 switching for BCM XGS Platforms
1938821
Major		Traffic from certain VLANs are not forwarded through the EVPN/VXLAN enabled spine switches
Product-Group=evo		On Junos OS Evolved QFX QFX 5130, 5700, 5230, 5240 platforms, traffic from certain VLANs (Virtual Local Area Network) mapped to VNIs (VXLAN Network Identifier) on EVPN/VXLAN (Ethernet Virtual Private Network/Virtual Extensible Local Area Network) enabled spine switches are not L3 (Layer 3) routed, resulting in traffic drop.

Resolved In: evo:23.4X100-D45-EVO evo:25.2R2-S1-EVO evo:25.2X100-EVO evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO
PR NumberSynopsisCategory: PFE L2 forwarding features on BT based platforms
1928605
Minor		IRB routed traffic is dropped when both hosts are learned on the same SP-style Layer 2 interface on EVO-PTX platforms
Product-Group=evo		On all Junos OS Evolved PTX platforms, IRB (Integrated Routing and Bridging) routed traffic is dropped when both source and destination hosts are reachable through the same Service Provider (SP)-style Layer 2 IFL (Logical Interface) and associated IRB interface.

Resolved In: evo:23.2R2-S8-EVO evo:24.2R2-S5-EVO evo:25.2R2-S2-EVO evo:25.4R1-S3-EVO evo:25.4R2-EVO evo:26.2R1-EVO
PR NumberSynopsisCategory: MX304 interface specific
1878873
Major		Interface remains operationally down on MX platforms after transient flap during boot
Product-Group=evo		On all platforms with MPC10, MPC11, LC4800, LC4802, LC9600 linecards and MX304, interfaces configured with hold timers remain in the operationally down state following an interface flap during system boot. When this issue occurs, Layer 2 and Layer 3 protocols on the affected interface remain down, routing adjacencies fail, and traffic forwarding through the affected link stops.

Resolved In: evo:23.2R2-S8-EVO evo:25.2R2-S2-EVO evo:25.3R1-EVO junos:25.3R1
PR NumberSynopsisCategory: DHCP 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 evo:25.4R2-EVO evo:26.2R1-EVO
PR NumberSynopsisCategory: EVPN ELAN/E-TREE
1944234
Major		Traffic blackholing (drop) is observed when output-traffic-control-profile is deactivated/activated on an ESI LAG interface in EVPN scenarios.
Product-Group=evo		IRB (Integrated Routing and Bridging) next-hop is not updated with the latest QoS (Quality-of-service) attributes after output-traffic-control-profile is deactivated/activated on ESI (Ethernet Segment Identifier) LAG. This results in traffic blackholing after deactivating/activating the output-traffic-control-profile on an ESI LAG interface in EVPN scenarios.

Resolved In: evo:24.2R2-S6-EVO evo:25.2R2-S2-EVO evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:25.4R2 junos:26.2R1 junos:26.3R1
PR NumberSynopsisCategory: Layer 3 forwarding, both v4+v6
1927637
Major		IPv6 frames are incorrectly padded
Product-Group=evo		On all EVO ACX platforms ACX7100-32C/ACX7100-48L/ACX7024/ACX7509/ACX7348/ACX7908, IPv6 frames are incorrectly padded with 0's ethernet/vlan padding (trailer) while sending to the peer device. In our incidence, GTP transit frames with these added paddings are dropped by the sGW (Serving Gateway) which causes service disruption. 5G mobility signaling will be impacted due to this issue.

Resolved In: evo:23.4R2-S8-EVO
PR NumberSynopsisCategory: DNX platform MPLS FRR features
1942200
Major		FEC table reaches the limit with the error "Failed to program the hardware with an error - table is full" on ACX7K platforms
Product-Group=evo		Due to FEC resource exhaustion, MPLS tunnel service programming fails on evo-pfemand on ACX7K platforms. New MPLS tunnels and some forwarding entries cannot be programmed into the ASIC. This may impact traffic and cause instability in MPLS forwarding, even if the reported route scale is low.

Resolved In: evo:24.2R2-S6-EVO evo:24.4R2-J12-EVO evo:24.4R2-S3-J13-EVO evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO
PR NumberSynopsisCategory: EVO Class of Services
1858634
Critical		Telemetry subscription to path /qos/interfaces/interface/output/queues/queue/state/transmit-pkts showing incorrect result
Product-Group=evo		Telemetry subscription to path /qos/interfaces/interface/output/queues/queue/state/transmit-pkts showing incorrect result

Resolved In: evo:22.3X80-D47-EVO evo:22.3X80-D49-EVO evo:25.2R2-EVO evo:25.4R1-S2-EVO evo:25.4R2-EVO evo:26.1R1-EVO junos:24.4R2-S4 junos:25.2R2 junos:25.4R1-S2 junos:25.4R2 junos:26.1R1
PR NumberSynopsisCategory: Index management related issues; idmd* daemons
1879392
Major		The rpdagent crashes due to the forward slash character being used in routing-instance name
Product-Group=evo		On all Junos Evolved platforms, configuring a routing-instance name with special characters such as forward slash can trigger a 'rpdagent' crash causing traffic disruption.

Resolved In: evo:22.3X80-D49-EVO evo:24.2R2-S4-EVO evo:25.2R2-EVO evo:25.4R1-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: Issues related to evo operations - libevo infra, typeinfo ..
1874238
Major		Objmon Memory Leak from Unreleased IndexReleaseConfirm Objects leads to distributord Out of memory and Router Reboot
Product-Group=evo		On all Junos Evolved PTX platforms, long-term use of PFEtoken features triggers an objmon memory leak, where net:: juniper:: evlruntime:: indexrelease:: IndexReleaseConfirm objects are not properly released, causing distributord to be OOM (Out of Memory) and killed due to memory exhaustion.

Resolved In: evo:23.2R2-S7-EVO evo:24.2R2-S5-EVO evo:24.4R2-S2-J20-EVO evo:24.4R2-S2-J25-EVO evo:24.4R2-S2-J27-EVO evo:24.4R2-S3-J1-EVO evo:24.4R2-S4-J10-EVO evo:24.4R2-S4-J9-EVO evo:25.2X100-EVO evo:25.3R1-EVO evo:25.4R2-EVO evo:25.4R2-S1-EVO evo:26.3R1-EVO junos:25.3R1
PR NumberSynopsisCategory: software upgrade infra issues
1927502
Major		JDI-REG:VIRTUAL:EVO-Suite fails due to SSH reconnection timeout as textchannel creation to RE device fails after reboot
Product-Group=evo		EVO-Suite fails due to SSH reconnection timeout as textchannel creation to RE device fails after reboot

Resolved In:
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: AAA, auditd issues
1909811
Minor		Management access via telnet disconnects under certain conditions
Product-Group=evo		On All Junos Evolved platform, management access via telnet disconnects under certain conditions.

Resolved In: evo:25.2R2-S1-EVO evo:25.4R2-EVO evo:26.1R1-EVO evo:26.2R1-EVO junos:25.4R2 junos:26.1R1 junos:26.2R1
PR NumberSynopsisCategory: Configd, ffp issues
1849300
Minor		.ssh/authorized_keys not synchronized when replacing a Routing Engine that contains pre-existing same-named local users
Product-Group=evo		On Junos Evolved dual-RE platforms, when a replacement Routing Engine (RMA) or previously used RE is inserted and the new RE already contains local user accounts with the same usernames as users configured on the current master RE, the SSH files (.ssh/authorized_keys, .ssh/id_rsa, .ssh/id_rsa.pub) are not synchronized or merged. As a result, passwordless SSH login between Routing Engines fails, and commands such as 'request routing-engine login re1' prompt for a password, even though the system login user configuration is identical and fully synchronized on both REs.

Resolved In: evo:25.4R2-EVO evo:26.1R1-EVO junos:25.4R2 junos:26.1R1
1907238
Minor		Rescue Configuration Check Fails
Product-Group=evo		On all Junos OS Evolved ACX Series platforms, which do not verify the syntax and integrity of the saved rescue configuration file when performing a configuration check, rescue configuration check fails.

Resolved In: evo:25.2R2-S1-EVO evo:25.4R2-EVO evo:25.4X300-EVO evo:25.4X50-EVO evo:26.1R1-EVO evo:26.2R1-EVO
PR NumberSynopsisCategory: Port Mirroring feature on express PFE
1916382
Minor		Network packets on the self-mirrored file shows the same timestamp on every packet with self-mirroring function enabled
Product-Group=evo		On all Junos Evolved platforms, with On-device packet capture or self-mirroring function enabled, the copied packets into the PCAP (Packet Capture) file shows the same timestamps for every packet. This issue has no service impact.

Resolved In: evo:24.2R2-S5-EVO evo:25.2R2-EVO evo:25.4R2-EVO evo:26.1R1-EVO junos:25.4R2 junos:26.1R1
PR NumberSynopsisCategory: ACX7332 & ACX7348 Platform Software
1896521
Minor		Intermittent "broadsync_lock_failure" alarms are seen on Junos OS Evolved ACX platforms
Product-Group=evo		On Junos OS Evolved ACX platforms, "broadsync_lock_failure" alarms are seen intermittently without any external trigger. These alarms are seen as a result of internal firmware misconfiguration and affects PTP (Precision Time Protocol) functionality. The alarms are cleared after few seconds (~10 secs) once the broadsync lock is restored.

Resolved In: evo:24.2R2-S6-EVO evo:25.2R2-S2-EVO evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:24.2R2-S6 junos:25.2R2-S2 junos:25.4R2 junos:26.2R1 junos:26.3R1
PR NumberSynopsisCategory: ACX7509 Platform related issues
1907117
Major		PDT:After kill of evo-pfemand, RE got rebooted with Last reason "catastrophic error/hw misc"
Product-Group=evo		For 24.2R2-S4, If evo-pfemand crashed (using kill -6) when device same traffic scale configured similar this PR reporter configured. This will lead restart of RE new backup RE with "catastrophic error/hw misc" as reboot reason. For more details please check AT

Resolved In:
PR NumberSynopsisCategory: Interface Information Display
1840142
Minor		The ODL execution failure observed for cli 'get-interface-information'
Product-Group=evo		On Junos and Junos OS Evolved platforms, the command 'get-interface-information' returns an error when called via RPC (Remote Procedure Call) and the XML (Extended Markup Language) response is validated against the YANG( (Yet Another Next Generation) model by the OpenDaylight (ODL) controller. There is no traffic impact because of this issue.

Resolved In: evo:24.2R2-S3-EVO evo:25.1R1-EVO evo:25.2R1-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:24.2R2-S3 junos:25.1R1 junos:25.2R1 junos:25.2R2 junos:25.3R1 junos:25.4R2
PR NumberSynopsisCategory: Internet Group Management Protocol
1888392
Major		CTG-REG: GARNET: After configuring igmp snooping group_count is not as expected since groups are showing in irb's
Product-Group=evo		GARNET: After configuring igmp snooping group_count is not as expected since groups are showing in irb's

Resolved In:
PR NumberSynopsisCategory: Label Distribution Protocol
1852934
Major		The rpd process crash is seen during RE switchover
Product-Group=evo		On Junos and Junos OS Evolved dual RE (Routing-Engine) platforms with LDP (Label Distribution Protocol) configuration, an rpd process crash in the new master RE is observed during a RE switchover.

Resolved In: evo:25.3R1-EVO junos:25.3R1
1906611
Major		Crash in the rpd process after LDP P2MP LSP Identifier reaches its maximum value and rolls over, due to duplicate identifier allocation
Product-Group=evo		On all Junos OS and Junos OS Evolved versions that support Label Distribution Protocol Point-to-Multipoint Label Switched Paths (LDP P2MP LSPs), the rpd process (routing protocol daemon) crashes when an LSP Identifier reaches its 24-bit maximum value (224 1 = 16, 777, 215) and rolls over to the starting value because a duplicate identifier is incorrectly allocated. This condition occurs only after prolonged tunnel flapping (typically more than 16 million flaps). When the rpd process crashes, routing convergence is briefly disrupted, and services relying on label-switched traffic are impacted until the process automatically restarts.

Resolved In: evo:26.1R1-EVO junos:26.1R1
PR NumberSynopsisCategory: Issues related to Junos licensing infrastructure
1926569
Major		License process crashes when AE interface configuration changes on Junos OS Evolved platforms
Product-Group=evo		A license process crash is observed on Junos OS Evolved platforms when Aggregated Ethernet (AE) interface configuration is deactivated and activated or modified.

Resolved In: evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO
PR NumberSynopsisCategory: Resource Reservation Protocol
1881609
Minor		RSVP hello messages uses secondary address when primary/preferred address are present for same interface
Product-Group=evo		On all Junos and Junos OS Evolved platforms where RSVP (Resource Reservation Protocol) configuration is present and a RSVP enabled interface has 2 IP address of which one is configured as primary/preferred in that case the RSVP Hello message uses the secondary IP address to form neighborship.

Resolved In: evo:25.3R1-EVO junos:25.3R1
PR NumberSynopsisCategory: PTX10K Line Card specific interface PRs
1869856
Major		PTX10008 : Error messages "CDA :btchip_lcpu_mtip_setup(202): LCPU1-0: MAC SOFT INIT failed for MAC:MTIP_10GE_LCPU" observed after FPC power-off / power-on
Product-Group=evo		PTX10008 : Error messages "CDA :btchip_lcpu_mtip_setup(202): LCPU1-0: MAC SOFT INIT failed for MAC:MTIP_10GE_LCPU" observed after FPC power-off / power-on

Resolved In: evo:24.4R2-S3-J12-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:25.3R1 junos:25.4R1
1937870
Major		Incorrect module temperature readings trigger unintended optics shutdown
Product-Group=evo		On MX platforms with MPC11, LC9600, LC4800 Linecards, MX304 and all Junos OS Evolved platforms, optics modules intermittently reports extremely high false temperature values in "show interfaces diagnostics optics" command. This can trigger false high-temperature alarms, leading to unnecessary optics shutdown.

Resolved In: evo:23.4R2-S6-J22-EVO evo:23.4R2-S8-EVO evo:24.2R2-S6-EVO evo:24.4R2-S3-J14-EVO evo:24.4R2-S3-J7-EVO evo:24.4R2-S5-EVO evo:25.2R2-S2-EVO evo:25.2X100-D20-EVO evo:25.2X100-EVO evo:25.4R1-S2-J4-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:23.2R2-S5-J6 junos:23.4R2-S8-J9 junos:24.2R2-S3-J10 junos:25.4R1-S2-J6 junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: PTX10K specific platform PRs
1771483
Major		EVO: RPC "get-power-usage-information" for cli "show chassis power" shows error wtih ODL response
Product-Group=evo		RPC "get-power-usage-information" for cli "show chassis power" shows error wtih ODL response

Resolved In:
1953725
Minor		Incorrect allocated power values are returned via telemetry
Product-Group=evo		Due to missing capdb change, telemetry incorrectly reports the allocated power values for RCB and fan tray.

Resolved In: evo:25.4R2-EVO evo:26.3R1-EVO junos:26.3R1
PR NumberSynopsisCategory: Segment routing traffic Engineering
1881989
Major		Tactical Traffic Engineering does not work on aggregated-ethernet interfaces
Product-Group=evo		On all Junos and Junos Evolved platforms, Segment Routing Tactical Traffic Engineering (TTE) does not work as expected for aggregated-ethernet interfaces. As a result, congestion is not alleviated or sent over TI-LFA paths.

Resolved In: evo:25.2R1-EVO evo:25.3R1-EVO junos:23.4R2-S7 junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: ZT/YTpfe bridging, learning, stp, oam, irb software
1800466
Major		Hamilton :: LC4800 :: Initial Sync values not streaming
Product-Group=evo		Hamilton :: LC4800 :: Initial Sync values not streaming

Resolved In:
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: UI Infrastructure - mgd, DAX API, DDL/ODL
1861779
Critical		Junos OS and Junos OS Evolved: EX Series, QFX Series, MX Series: A specific 'show l2-learning/ethernet-switching' command causes l2ald crash (CVE-2026-57025)
Product-Group=evo		A Return of Pointer Value Outside of Expected Range vulnerability in the fileio library of Juniper Networks Junos OS and Junos OS Evolved allows a local, low-privilged attacker to cause a Denial-of-Service (DoS). Please refer to https://supportportal.juniper.net/JSA110085 [juniper.net] for more information.

Resolved In: evo:22.4R3-S9-EVO evo:23.2R2-S7-EVO evo:23.4R2-S8-EVO evo:24.2R2-EVO evo:24.4R1-S3-EVO evo:24.4R2-EVO evo:24.4R2-S3-J1-EVO evo:25.2R1-EVO evo:25.4R2-EVO junos:20.2X42 junos:20.3X75-D443 junos:21.2R3-S11 junos:22.4R3-S10 junos:22.4R3-S7-J1 junos:22.4R3-S9 junos:23.2R2-S7 junos:23.4R2-S7 junos:23.4R2-S8 junos:23.4X12 junos:23.4X13 junos:23.4X14 junos:23.4X15 junos:23.4X30 junos:24.2R2 junos:24.2X1 junos:24.4R1-S2 junos:24.4R1-S3 junos:24.4R2 junos:25.2R1 junos:26.3R1
1899597
Major		Getting validation error for get-interface-information rpc execution through ODL controller
Product-Group=evo		Getting validation error for get-interface-information rpc execution through ODL controller

Resolved In: evo:26.2R1-EVO
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:
1865547
Major		Command timeouts were observed while establishing NETCONF sessions over outbound https after configuring management-instance
Product-Group=evo		On all Junos OS Evolved platforms, command timeouts are seen on the device while establishing NETCONF over outbound-https sessions. This issue is specific to the use case of NETCONF over outbound-https operations when the "system management-instance" configuration is enabled, the regular NETCONF over outbound-https operations (without "system management-instance" configuration) and regular NETCONF over SSH operations works fine. There is no control plane/data plane traffic impact due to this issue.

Resolved In: evo:25.2R2-EVO evo:25.4R1-EVO evo:25.4R2-EVO evo:26.1R1-EVO junos:25.2R2 junos:25.4R1 junos:25.4R2 junos:26.1R1
1906621
Major		RPC reply delayed for commit during NETCONF over SSH session on Junos TVP-based VMhost platforms
Product-Group=evo		On JUNOS VM Host-based platforms, when performing NetConf "", an internal script caused its PID to be displayed in the NETCONF session during commit.

Resolved In: evo:24.4R2-S3-J1-EVO evo:25.4R2-EVO evo:26.1R1-EVO junos:22.4R3-S7-J1 junos:22.4R3-S8 junos:22.4R3-S9 junos:22.4X50 junos:22.4X8 junos:23.2R2-S7 junos:23.4R2-S7 junos:23.4X12 junos:23.4X13 junos:23.4X14 junos:23.4X15 junos:23.4X30 junos:23.4X30-D30 junos:24.2R2-S5 junos:24.2X1 junos:24.4R2-S1-C1 junos:24.4R2-S4 junos:24.4X3 junos:24.4X32 junos:24.4X42 junos:25.2R1-S2 junos:25.2R2 junos:25.4B1 junos:25.4R1 junos:25.4R2 junos:26.1R1
PR NumberSynopsisCategory: Issues related to XML, JSON handling
1843789
Critical		Management Daemon (MGD) when executing certain configuration display commands with the display json option in the CLI
Product-Group=evo		A core-dump issue has been identified in the Management Daemon (MGD) when executing certain configuration display commands with the display json option in the CLI. This may lead to an abrupt session termination and CLI disruption.

Resolved In: evo:22.3X80-D49-EVO evo:23.4R2-S6-EVO evo:24.2R2-S4-EVO evo:25.2R2-EVO evo:25.4R1-EVO junos:22.4R3-S7-J1 junos:22.4R3-S9 junos:23.4R2-S4-J26 junos:23.4R2-S5-J17 junos:23.4R2-S6 junos:23.4X12 junos:23.4X13 junos:23.4X15 junos:23.4X30-D30 junos:23.4X9 junos:24.2R2-S4 junos:24.2X1 junos:24.2X4 junos:24.4R2-S1-C1 junos:24.4R2-S3 junos:24.4X3 junos:24.4X42 junos:25.2R1-S1 junos:25.2R1-S2 junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: Issues related to YANG Data Models
1781023
Minor		Few yang package are occuring multiple place On Box
Product-Group=evo		Few yang package are occuring multiple place On Box

Resolved In:
1815644
Minor		Few of the yang package are unvailable in GNMI capability response
Product-Group=evo		Few of the yang package are unvailable in GNMI capability response

Resolved In:
PR NumberSynopsisCategory: PRs related to PICd and associated lib WAN side PI code.
1914708
Minor		PICD fails to reuse or clean SNMP trap objects, causing memory leak
Product-Group=evo		On all Junos OS Evolved platforms, PICD repeatedly created new SNMP trap objects without removing old ones, causing distributord memory leaks over time. This is tracked under TSB107540 [juniper.net]

Resolved In: evo:24.4R2-S2-J20-EVO evo:24.4R2-S2-J22-EVO evo:24.4R2-S2-J23-EVO evo:24.4R2-S2-J25-EVO evo:24.4R2-S2-J27-EVO evo:24.4R2-S3-EVO evo:24.4R2-S3-J1-EVO evo:25.2R2-EVO evo:25.2X100-D20-EVO evo:25.2X100-EVO evo:25.4R1-EVO evo:25.4R2-EVO evo:26.1R1-EVO evo:26.2R1-EVO junos:25.4R2 junos:26.1R1
PR NumberSynopsisCategory: Express ZX PFE L3 Features
1937796
Major		The FPC major errors seen after FPC restart on Junos Evolved PTX platforms and PFEs fail to come back online in scaled setup
Product-Group=evo		On Junos Evolved PTX platforms, FPC (Flexible PIC Concentrator) major errors can be seen after FPC restart/offline or multiple concurrent PFE (Packet Forwarding Engine) restart/offline in a highly-scaled scenario that can result in the PFEs failing to come back online. This is due to offline timeout, FPC go into fault state causing services to impact. This is a rare case scenario.

Resolved In: evo:22.3X80-D49-EVO evo:24.4R2-S3-J1-EVO evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:25.4R2 junos:26.2R1 junos:26.3R1