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 24.4R2-S5-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 24.4R2-S5-EVO is now available.

24.4R2-S5-EVO - List of Fixed issues

PR NumberSynopsisCategory: Fabric for LC1300 and SIB3
1964102
Major		Major alarms for fabric link faults that result in reduced fabric capacity are introduced on PTX10004 and PTX10008 platforms
Product-Group=evo
Severity=Major		On Junos OS Evolved PTX10004 and PTX10008 platforms with LC1301 line cards and SF5 fabric, fabric link faults need to be reported as major alarms. Link faults can occur during system operation and result in reduced fabric capacity with partial impact. This enhancement introduces the new alarm "One or more PFE pairs operating with less than acceptable fabric capacity" to indicate reduced fabric capacity conditions.
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: 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: 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: BX PFE firewall issues
1877486
Minor		Ethernet-switching flood filter stops working when policer action is added
Product-Group=evo
Severity=Minor		On BX-based Junos OS Evolved PTX platforms, when a flood filter with a policer is applied together with VLAN interface configuration in a single commit, the filter may not be properly installed, even though the commit is successful. As a result, the flood filter does not function as intended, leading to degraded traffic handling and performance issues.
1922583
Critical		JDI-RCT:EVO: PTX10008-JNP10K-RE1-E128 - ERROR : evo-aftmand-bx core is seen and not able to backtrace the core during baseline validation
Product-Group=evo
Severity=Critical		Filter rollback under high-scale conditions may trigger an unexpected evo-aftmand restart
PR NumberSynopsisCategory: Express BX PFE L3 Features
1878647
Minor		Physical interface creation failure was ignored resulting in system crash or traffic blackhole
Product-Group=evo
Severity=Minor		On Junos OS Evolved PTX Series routers, during physical interface deactivate/activate operations, failure to recreate a physical Interface Device (IFD) resulted in an inconsistent interface state. This issue caused a system crash leading to service disruption or traffic blackhole.
1964489
Major		Traffic impact is observed due to rapid interface flapping on PTX12008 routers or devices equipped with JNP10K-LC1301 FPC or JNP10008-SF5 SIB modules
Product-Group=evo
Severity=Major		On Junos OS Evolved PTX12008 platform or devices equipped with JNP10K-LC1301 FPC (Flexible PIC Concentrator) or JNP10008-SF5 SIB (Switch Interface Board) cards, a rapid (sub-second) interface flap triggers a timing issue that causes the evo-cda-bx process to hog CPU resources. These periods of high CPU utilization affect other processes and protocols, ultimately impacting traffic on the device.
PR NumberSynopsisCategory: Junos Evolved Netstack Socket Intercept and NetIO libraries
1954037
Critical		Locally originated TCP traffic egresses drained interface despite RIB/FIB pointing to right next-hop
Product-Group=evo
Severity=Critical		On a Junos Evolved Routing Engine, TCP host traffic may use stale route state for egress.This fault may be seen for a TCP socket whose remote peer transitions from being reachable over an ECMP route to being reachable over a non-ECMP route.These conditions are necessary but not sufficient to produce the fault in which some TCP flows continue to use stale route state. The fault is not fully deterministic, as it is affected by the timing of events and by the results of ECMP load-balancing logic. The impact of the fault depends on the release. On releases from 24.4R2 and 25.2R1 onward, an established TCP flow may migrate from one ECMP link to another after a socket option is changed, but traffic will not be lost. If any route state changes (even for an unrelated route or interface), the next send or receive operation on a TCP socket will update the state for that flow to use the egress interface expected for the current route state. On older releases, the stale state may linger after the route state changes to no longer use ECMP, which can lead to packet drops and TCP retransmission.
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: ACX7332 ACX7348 Interfaces software
1965887
Critical		ACX7020/ACX7024/ACX7024X/ ACX71xx/ACX73xx/ACX7509/Ufispace is not able to configure "no-temperature-monitoring" for ports higher than 23
Product-Group=evo
Severity=Critical		ACX7020/ACX7024/ACX7024X/ ACX73xx/ACX7509/Ufispace is not able to configure "no-temperature-monitoring" for ports higher than 23
PR NumberSynopsisCategory: N/A:sw-octomore-qsfp-intf:
1946222
Major		Excessive xcvr config_mismatch DEBUG messages were generated in picd during periodic monitoring
Product-Group=evo
Severity=Major		On Junos EVO PTX Series platforms (PTX12008, PTX10001-36MR, and PTX10003-160C), when a transceiver (xcvr) configuration mismatch alarm was present, the picd periodic transceiver monitoring process generated repetitive DEBUG log messages. The issue was observed in environments containing transceivers reporting configuration mismatch alarms. During periodic monitoring, the same mismatch and alarm conditions were repeatedly logged, resulting in excessive growth of picd logs.
PR NumberSynopsisCategory: PTX10K Line Card specific interface PRs
1937870
Major		Incorrect module temperature readings trigger unintended optics shutdown
Product-Group=evo
Severity=Major		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.
PR NumberSynopsisCategory: ACX724 hwd issues
1945505
Major		jnxOperatingState not reporting the correct value for FanTray after the FanTray Recovered from an error
Product-Group=evo
Severity=Major		Field Replaceable Unit (FRU) fault state was missing in the SNMP MIBs. This causes jnxOperatingState to return 1, which means 'unknown' instead of 2, which means 'running'

 

 

24.4R2-S5-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: 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		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.

Resolved In: evo:24.4R2-S3-C1-EVO evo:24.4R2-S3-J1-EVO evo:24.4R2-S3-J15-EVO evo:24.4R2-S4-EVO evo:24.4R2-S5-EVO evo:25.2R2-S2-EVO evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO
PR NumberSynopsisCategory: BX PFE firewall issues
1972768
Major		PTX10002-36QDD: evo-aftmand-bx "Out-of-order deletion of AftNode AftTunnelDecap" errors when changing route-distinguisher value on routing-instance
Product-Group=evo		If you change an RD that you configured and committed previously, or change the routing instance type from virtual-router to vrf, make either of those changes during a maintenance window, as follows: Deactivate the routing instance. Change the RD. Activate the routing instance. If there is a filter installed with decap-action configured and the associated NH is part of the routing instance for which the route-distinguisher is changed without following the above steps, the filter could get into error state.

Resolved In:
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
1953985
Major		The BUM traffic is looped back towards customer edge in EVPN-MPLS all-active multihoming environment due to missing ESI label encapsulation
Product-Group=evo		On Junos OS Evolved ACX Series platforms configured in an EVPN-MPLS (Ethernet Virtual Private Network - Multiprotocol Label Switching) all-active multihoming environment using ESI-LAG (Ethernet Segment Identifier - Link Aggregation Group), when a BGP (Border Gateway Protocol) / BFD (Bidirectional Forwarding Detection) flap occurs between EVPN peers, BUM (Broadcast, Unknown-unicast, Multicast) traffic is sent back towards the same CE (Customer Edge) from which it was received due to missing ESI label encapsulation. As a result, BUM traffic is impacted and is not forwarded correctly.

Resolved In: evo:24.2R2-S6-EVO evo:25.4R2-EVO evo:26.2R1-EVO evo:26.2R1-S1-EVO evo:26.2R2-EVO evo:26.3R1-EVO
PR NumberSynopsisCategory: DNX Multicast
1965010
Minor		Multicast route programming fails on Junos OS Evolved ACX platforms with EVO_PFEMAND_ASIC_ PROGRAM_FAILED error
Product-Group=evo		On Junos OS Evolved ACX platforms that configures IGMP (Internet Group Management Protocol) with IRB (Integrated Routing and Bridging) interfaces and IGMP snooping is enabled, during heavy IGMP join/leave churn, multicast route programming fails and the EVO_PFEMAND_ASIC_PROGRAM_FAILED error is observed. When this issue occurs, multicast hardware resource that is not correctly released, resulting in traffic disruption for all traffics associated with multicast routes.

Resolved In: evo:24.2X2-EVO evo:25.4R2-EVO evo:26.2R2-EVO evo:26.4R1-EVO junos:25.4R2 junos:26.2R2 junos:26.4R1
PR NumberSynopsisCategory: sflow issues on ACX platforms
1957160
Minor		Multiple link flaps observed on all ACX7K platforms
Product-Group=evo		On all ACX7K platforms, an internal ASIC interrupt was triggered in two different scenarios, in some cases the issue is seen without any change in the configuration and in some other cases the issue is seen when an egress sflow (sampled Flow) and egress mirror was enabled/attached to the same interface and committed. The triggered interrupt causes multiple interface flaps and temporary suspension of the ASIC programming resulting in transient disruption of forwarding operations and packet loss.

Resolved In: evo:25.4R2-EVO evo:26.2R2-EVO evo:26.4R1-EVO
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-J26-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: EVO L2 Control Plane PRs
1905116
Minor		In an EVPN Flex Algorithm environment, if multiple routing instances share the same color and the same VLAN, traffic may not be handled correctly
Product-Group=evo		In an EVPN Flex algorithm environment, if multiple routing instances share the same color and VLAN, there is a possibility that traffic may not be processed correctly. Under such circumstances, the bridged domains within the routing instances may end up sharing the same VSI, which can result in traffic being directed to unintended routing instances.

Resolved In: evo:25.2R2-EVO evo:25.4R1-EVO evo:26.1R1-EVO junos:25.4R1 junos:26.1R1
PR NumberSynopsisCategory: Issues related to NTP issues on evo
1923757
Major		Nagios server not able to connect to ACX7024X
Product-Group=evo		On EVO ACX platforms with VRF/loopback/vrrp when ntpd replies to client requests the NTP server responses uses incorrect source addresses instead of the destination address of the received packet, causing NTP client queries to fail or receive responses from unexpected source addresses.

Resolved In: evo:23.2R2-S8-EVO evo:26.2R1-S2-EVO evo:26.2R2-EVO evo:26.3R1-EVO junos:26.2R2 junos:26.3R1 junos:26.4R1
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: SNMP, mib2d issues
1932267
Major		SNMP traps related to optics/optic's media lane alarms will not be raised
Product-Group=evo		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.

Resolved In: evo:24.4R2-S3-J1-EVO evo:24.4R2-S4-EVO evo:24.4R2-S5-EVO evo:25.2R2-S1-EVO evo:25.2X100-EVO evo:25.4R1-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: 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:24.2X2-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: ACX7348 PTP
1892686
Major		PTP delay message sent from different LAG after RE switchover
Product-Group=evo		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.

Resolved In: evo:24.2R2-S5-EVO evo:24.4R2-S4-EVO evo:25.2R2-S2-EVO evo:25.4R1-S2-EVO evo:25.4R2-EVO evo:26.1R1-EVO evo:26.2R1-EVO
PR NumberSynopsisCategory: Category for JET(JUNOS Extension Toolkit) related issues
1894461
Major		Removal of the suffix when the hostname is used as the target ID in the gRPC-tunnel configuration
Product-Group=evo		On all Junos Evolved platforms, when hostname is used as the target ID in the gRPC-tunnel configuration, it includes the routing engine information as a suffix ("-re0" or "-re1"), the suffix part is now removed. is now removed. This issue has no impact on traffic.

Resolved In: evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:25.2R2 junos:25.3R1 junos:25.4R1
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:24.4R2-S4-J9-EVO evo:24.4R2-S5-C1-EVO evo:25.2R1-S2-J3-EVO evo:25.4R2-EVO evo:26.2R1-EVO evo:26.3R1-EVO junos:24.2X1 junos:25.4R2 junos:26.2R1
PR NumberSynopsisCategory: Multiprotocol Label Switching
1917033
Major		MPLS auto-policing fails to drop excess IPv6 traffic on P2MP RSVP-TE LSPs
Product-Group=evo		On Junos and Junos EVO platforms the MPLS auto-policing function fails to drop excess IPv6 traffic on Resource Reservation Protocol P2MP LSP (Label Switched Paths). Although the policer is correctly applied for IPv4 P2MP (Point to Multipoint) LSP the IPv6 equivalent fails because the flood-nexthop (floodNH) does not contain the auto-policer information. This issue leads to oversubscription and unpredictable QoS behavior.

Resolved In: evo:25.4R2-EVO evo:26.1R1-EVO evo:26.2R1-EVO junos:25.4R2 junos:26.1R1 junos:26.2R1
PR NumberSynopsisCategory: Transport daemon for Packet Optical applications
1979263
Minor		Optical performance monitoring becomes unavailable on PTX platforms with high scale of coherent-ZR interfaces
Product-Group=evo		On Junos Evolved PTX platforms, systems with approximately 240 or more interfaces configured on ports using coherent-ZR optics (such as 100ZR and 400ZR transceivers) experience a loss of optical performance monitoring functionality. As a result, optical performance monitoring data, alarms, and statistics are no longer available through management interfaces.

Resolved In: evo:24.4R2-S5-C1-EVO evo:25.4R2-EVO evo:26.2R2-EVO evo:26.2X200-D20-EVO evo:26.2X200-EVO evo:26.4R1-EVO evo:27.1R1-EVO
PR NumberSynopsisCategory: OSPF routing protocol
1958559
Minor		The rdp process crash after executing "clear ospf database" when OSPF Remote Loop-Free Alternate RLFA is configured
Product-Group=evo		The software issue occurs during Open Shortest Path First (OSPF) Remote Loop-Free Alternate (RLFA) route calculation. One way to trigger the issue is by executing the "clear ospf database" CLI command.

Resolved In: evo:24.4R2-J15-EVO evo:25.4R2-EVO evo:26.2R2-EVO evo:26.3R1-EVO junos:25.4R2 junos:26.2R2 junos:26.3R1
PR NumberSynopsisCategory: Shard routing infrastructure within RPD
1757915
Major		The rpd process crashes when processing multipath routes with mixed indirect and composite next-hops under rib-sharding
Product-Group=evo		On all Junos and Junos OS Evolved platforms, when rib-sharding is enabled and RT (Route Target) multipath routes containing both indirect and composite next-hop types are processed, the rpd (Routing Protocol Daemon) process will crash due to incorrect handling during the next-hop copy operation from RIB (Routing Information Base) shards to the main RIB thread. An rpd crash results in all routing protocols going down and causes a brief traffic disruption until the rpd process restarts.

Resolved In: evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO evo:26.3R1-EVO evo:26.4R1-EVO evo:27.1R1-EVO junos:23.2R2-S2-J9 junos:23.4R2-S5 junos:24.4R2-S2-J8 junos:24.4R2-S3 junos:25.2R2 junos:25.2R2-S1 junos:25.3R1 junos:25.4R1 junos:25.4R2 junos:26.1DCB
PR NumberSynopsisCategory: Resource Reservation Protocol
1967461
Major		RSVP detour LSP does not follow configured FRR admin-group exclusion constraints
Product-Group=evo		On Junos OS and Junos OS Evolved platforms, when MPLS (Multiprotocol Label Switching), RSVP (Resource Reservation Protocol), dynamic tunnels, and an LSP (Label-Switched Path) template with FRR (Fast Reroute) admin-group exclusion constraints are configured, the detour LSP does not follow the configured exclusions after the primary LSP becomes unavailable. The detour LSP uses an unintended path, while traffic and services remain unaffected.

Resolved In: evo:25.4R2-EVO evo:26.2R2-EVO evo:26.3R1-EVO evo:26.4R1-EVO junos:25.4R2 junos:26.2R2 junos:26.3R1 junos:26.4R1
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: 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: 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

 

Modification History

First publication 2026-10-14