Alert Type

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

Product Affected

ACX PTX running Junos Evolved Software

Alert Description

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

Solution

Junos Software service Release version 24.2R2-S2-EVO is now available.

24.2R2-S2-EVO - List of Fixed issues 

PR NumberSynopsisCategory: Issues on PTX10002-36QDD Hardware
1870153
Major		PTX10k2-36QDD showing incorrect Power Status
Product-Group=evo
Severity=Major		On a PTX10k2-36QDD system, the output of "show chassis environment" may incorrectly shows a disconnected PEM's status as "OK" instead of "Check".
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.
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: the replication daemon (repd) for Shared Memory-base
1870183
Major		RPD might crash when upgrading using no-validate.
Product-Group=evo
Severity=Major		RPD might crash when upgrading and NOT using no-validate. Use no-validate to avoid the crash.
PR NumberSynopsisCategory: Border Gateway Protocol
1758786
Minor		Configuring max color value 2^32-1(4294967295) in transport-class does not create the corresponding transport-class color table
Product-Group=evo
Severity=Minor		On device configured with LSP with transport-class, when configuring max color value (2^32-1=4294967295), transport-class color table is not created and rpd may core. This issue only happens with configuring the max color value.
1853025
Major		Updating a source-file to load ROAs should be done by changing the name of the source file
Product-Group=evo
Severity=Major		Loading ROAs from a source-file was a feature introduced as a convenience feature and as such this only affects that feature. This feature is not in widespread use and was created to have a fallback ROA when all sessions go down. This problem scenario requires multiple reloads with the being modified back and forth to add and then delete and re-add the database configured in the import policy.
1857801
Major		Memory leak is observed when "graceful-shutdown" is configured
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms with Border Gateway Protocol (BGP) "graceful-shutdown" configured, memory leak is observed. This issue does not cause traffic impact.
1865114
Major		Valid BGP routes in RIB are displayed with verification state as Invalid
Product-Group=evo
Severity=Major		On Junos and Junos Evolved platforms, with resource public key infrastructure(RPKI ) enabled for the BGP, the valid routes are installed in the routing table with validation state invalid.However, the route is parsed by policy as a valid route.
1877261
Major		BGP updates missing graceful-shutdown community after quick sender knob flaps
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms, when the graceful-shutdown sender knob is repeatedly deleted and subsequently re-added in quick intervals under a BGP-LU (Border Gateway Protocol-Labeled Unicast) session, the router CLI (command line interface) incorrectly indicates that the graceful-shutdown community is being advertised. However, the actual BGP update messages sent over the session do not include the graceful-shutdown community. This results in the graceful-shutdown community not being propagated to BGP peers during graceful shutdown events, which will potentially cause traffic forwarding issues.
1877288
Major		rpd crash when changes are applied to as-path with dynamic-db in use
Product-Group=evo
Severity=Major		On Junos OS platforms using as-path-groups (Autonomous System Path Group) with dynamic-db (dynamic Data base) feature enabled, rpd (Routing Protocol Daemon) may crash after as-path configuration changes.
1877332
Major		EBGP MULTIPATH is not set on ACTIVE route
Product-Group=evo
Severity=Major		On all Junos/EVO platforms, in BGP multipath scenario, it is observed that due to a software issue, the Active route does not have all the ECMP legs. Hence only one leg is installed to forwarding.
PR NumberSynopsisCategory: PFE COS features on BT based platforms
1879439
Minor		Rare evo-cda-bt crash in PTX10008 Junos OS Evolved with multiple FPCs when one FPC fails
Product-Group=evo
Severity=Minor		On all Junos Evolved PTX10008 platforms, the failure of one FPC (Flexible PIC Concentrator) can cause a rare evo-cda-bt crash on another FPC, resulting in a reboot.
PR NumberSynopsisCategory: Firewall Filter
1856854
Major		MIB2D will see 100% CPU utilization due to MIB2D walk fail
Product-Group=evo
Severity=Major		On PTX3000/PTX5000/PTX10008 /PTX10016/QFX10008 /PTX1000/PTX10002/ QFX10002 platforms, MIB2D will see 100% CPU utilization due to MIB2D walk failure.
1872347
Major		System becomes unresponsive or crash due to frequent filter changes in a scale scenario having mib2d process in use
Product-Group=evo
Severity=Major		On Junos OS platforms, The system experiences memory exhaustion due to an mbuf (Memory Buffer) leak, system logs error message. This condition can cause the system to become unresponsive (hang state) or potentially crash, resulting in a VMcore file and service disruption. The issue arises when a firewall filter is applied to approximately 1k (1000) logical interfaces (IFLs), each filter containing over 250 terms and these filters are updated every 2-3 minutes, triggering updates for all filter attachments.
PR NumberSynopsisCategory: ACX BFD specific issues
1879925
Major		Traffic disruption is observed when successive switchover is performed having single-hop BFD configured in the dual RE scenario
Product-Group=evo
Severity=Major		On Junos OS Evolved ACX7509, ACX7332, ACX7348 platforms with dual RE, protocol flap is observed when BFD (Bidirectional Forwarding Detection) liveness detection fails, leading to traffic disruption. This issue occurs because the Backup Routing Engine (RE), which takes over as the Master after successive RE switchover, has an incomplete or missing BFD session state. As a result, upon becoming the Master, it is unable to maintain established BFD sessions, triggering routing protocol reconvergence and causing temporary traffic interruption.
PR NumberSynopsisCategory: Firewall support for DNX
1888201
Major		Commit can fail if apply-path contains pattern-matching tokens other than the wildcard <*>
Product-Group=evo
Severity=Major		When the apply-path contains pattern-matching tokens other than the wildcard <*>, prefix list validation may fail, causing the commit to fail.
1891684
Major		Matching TOS IP precedence values in the same term by firewall family inet on ACX 7100 and all ACX evo
Product-Group=evo
Severity=Major		Firewall filter IP precedence match incorrect when a range of values is configured. With matching only one precedence value, either (6 or 7) as an example, packets match the correct term and the action is achieved. Or when configuring a firewall family filter to match the precedence value, for example, of internet-control (6) and net-control (7) in the same term, packets do not match the correct term, and the action is not achieved.
PR NumberSynopsisCategory: Host path software for ACX platform
1851810
Major		The Devdb messages will be seen continuously on ACX EVO platforms
Product-Group=evo
Severity=Major		On ACX EVO platforms, due to the Discard filter programmed and the traffic hitting continuously on the same discard filter, the Devdb messages continuously keeps flooded.
PR NumberSynopsisCategory: EA chip ( MQSS SW issues )
1872743
Major		Packet loss or retransmissions observed on MX platforms using SFP-T transceivers
Product-Group=evo
Severity=Major		On MX10004, MX10008 and MX10016 platforms with LC480 line cards, the use of Small Form-factor Pluggable Twisted-pair (SFP-T) transceiver will lead to packet loss or retransmissions on neighboring devices due to incorrect Inter-Packet Gap (IPG) handling.
PR NumberSynopsisCategory: Binding Queue
1859621
Minor		SNMP walk failure due to missing OID after FCO/TPA delete compression
Product-Group=evo
Severity=Minor		On all PTX Junos and Junos evolved platforms, an issue occurs when performing SNMP walks, resulting in the error No Such Instance currently exists at this OID. This is caused by a lifecycle management problem involving FCO (Factory Configuration Object) and TPA (Third-Party Attachment) objects. Specifically, when both FCO (IFDO) and TPA (IfSnmpInfo) are deleted in quick succession, only the FCO delete notification is sent, skipping the FCO modification callback that the TPA would typically trigger a delete event. As a result, the SNMP index mapping associated with the TPA is not properly updated, leading to missing entries during SNMP walks.
PR NumberSynopsisCategory: Issues related to EVO dependency layer including object graphs, incompletes, anomalies and nkdb
1874151
Critical		Rare assert with an Junos Evolved process
Product-Group=evo
Severity=Critical		This is a rare chance of a process panic. This can be seen in Evo apps. If seen in forwarding apps it can result in system reboot and resulting traffic loss.
PR NumberSynopsisCategory: System Management daemon and related issues
1866988
Critical		System stops responding to "show system applications app ndp detail" command or prevents applications from start/stop/restart
Product-Group=evo
Severity=Critical		On all Junos OS Evolved platforms, a failure in internal process communication will cause the system to stop responding to the "show system applications app ndp detail" CLI command or prevent applications from start/stop/restart. This issue occurs when systemd becomes unresponsive to requests initiated by sysman. There is no impact to traffic forwarding.
PR NumberSynopsisCategory: Interface PRs defect & enhancement requests
1875917
Major		Disabling a single AE IFL in a MAC-VRF can bring the entire AE interface down
Product-Group=evo
Severity=Major		On all Junos Evolved platforms, under MAC-VRF routing configurations, when any Layer 3 IFL is deactivated, it causes the associated AE interface to go administratively down, leading to complete traffic disruption across the AE bundle.
1880635
Major		Interface remains administratively down state, fails to recover after execution of CLI command "request interface bounce"
Product-Group=evo
Severity=Major		On Junos OS Evolved PTX platforms, executing the CLI command "request interface bounce" causes the member Ethernet interface (et-x/x/x), which is part of the Aggregated Ethernet (AE) bundle, to remain in an administratively down state and not recover after the defined interval. As a result, this condition can cause a traffic impact.
1882754
Major		AE interface speed mismatch causes link down and missing command outputs on Junos OS Evolved platforms
Product-Group=evo
Severity=Major		On all Junos OS Evolved platforms, when the AE (Aggregated Ethernet) interface is configured with a link-speed different from its member interfaces, it results in a misconfiguration. Due to this, the link between devices goes down, causing disruption in traffic forwarding.
PR NumberSynopsisCategory: EVO Netstack Juniper Tunnel Driver Module
1854932
Major		TCP connection stalls with BGP Explicit Null and MPLS forwarding on certain Junos Evolved PTX platforms when sending packets exceeding MTU limit
Product-Group=evo
Severity=Major		On Junos Evolved PTX10001, PTX10004 and PTX10008 platforms, if LDP(Label Distribution Protocol) is initially established over IP protocol, and later transitions to MPLS(Multiprotocol Label Switching) encapsulation (mpls-forwarding), the outgoing TCP(Transmission Control Protocol) packet size is not adjusted to account for added MPLS label. As a result, packets exceeding the configured interface MTU(Maximum Transmission Unit) are dropped before transmission. Since the receiving side does not receive these packets, the LDP session eventually times out due to "hold time expiry".
PR NumberSynopsisCategory: EVO L2 Control Plane PRs
1874476
Major		Transient traffic loss for CE in an EVPN MPLS setup with Multi-Homing
Product-Group=evo
Severity=Major		On Junos and Junos Evolved platforms with EVPN MPLS, Multi-Homing scenarios, when there is a Multi-Homing peer node reboot, the destination route entries that were learned locally on IRB(Integrated Routing and Bridging) interface of rebooted node get deleted on other multi-homing peers without RE-ARP (Routing Engine-Address Resolution Protocol) causing transient traffic loss for CE (Customer Edge) traffic.
PR NumberSynopsisCategory: EVO-AFT Infrastructure PFE related issues
1889042
Major		PTX10001-36MR reboot after ppman-aft-bt hot patch.
Product-Group=evo
Severity=Major		Hot patch and restart of ppman-aft-bt will cause a reboot of the system. This is specific to PTX10001-36MR and 23.4.
PR NumberSynopsisCategory: Express PFE MPLS for EVO platforms
1861803
Minor		Control plane is not properly managing the label 1048575 for MPLS traffic, leading to service impact
Product-Group=evo
Severity=Minor		On PTX Evolved platforms, the control plane is incorrectly using label 1048575 for MPLS (Multiprotocol Label Switching) traffic, this label is being changed to the NULL label 3, as if it corresponds to a non-MPLS packet, resulting in the label being popped, leading to all traffic associated to these MPLS threads to be dropped.
PR NumberSynopsisCategory: Configd, ffp issues
1877439
Minor		Traffic drop occurs on Junos Evolved platforms when prefix is moved between dynamic prefix-lists used in firewall filter
Product-Group=evo
Severity=Minor		On all Junos Evolved platforms, when a firewall filter is configured with a dynamic prefix-list that is referenced using an apply-path statement, moving a prefix from one such prefix-list to another where both prefix-lists match the apply-path pattern results in the prefix not being programmed in the PFE. This causes traffic loss for that prefix. The issue is triggered when the configuration includes apply-path pointing to both the source and destination prefix-lists, and a prefix is deleted from one and added to the other through a commit operation.
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1848993
Major		The data plane will be out of sync when migrating to EVPN A/A stitching with Vanila VXLAN (PIM Multicast)
Product-Group=evo
Severity=Major		On MX platforms, to improve the convergence of node failures in EVPN MH interconnects with Data Plane VXLAN, migrating to an Active-Active setup may cause the data plane to become out of sync for ARP entries. The gateway learns the MAC address and advertises it to the peer gateway. However, on the peer gateway, some MAC-IP entries may remain stuck in the 'Unresolved' (Ur) state.
PR NumberSynopsisCategory: Express PFE FW Features
1862048
Major		NPU's (Network Processing Unit) KHT (Kernal Hash Table) utilization shows 100% utilization post config commit
Product-Group=evo
Severity=Major		On Junos Evolved platforms, NPU's KHT utilization shows 100% utilization post config commit
PR NumberSynopsisCategory: ACX7332 ACX7348 Interfaces software
1818810
Major		On ACX7348 and ACX7332 , Jack Out Jack In of FPC blocks MACSEC traffic
Product-Group=evo
Severity=Major		On ACX7348 and ACX7332 Junos Evolved Platforms during Jack out of FPC, MACSEC resources are not properly cleaned up, this results in initialisation failure and MACSEC traffic getting blocked after FPC is Jacked In.
1870528
Major		Interface down is observed while configuring 1G speed on ACX7332/ACX7348/ACX7509 platforms
Product-Group=evo
Severity=Major		On Junos OS Evolved ACX7332/ACX7348/ACX7509 platforms, physical interface goes down on configuring 1G speed after the first boot with or without auto-negotiation.
PR NumberSynopsisCategory: ACX7332 & ACX7348 Platform Software
1809091
Minor		ACX7024 sees a vmcore and restarts or potentially hangs on reboot
Product-Group=evo
Severity=Minor		ACX7024 sees a vmcore and restarts or potentially hangs on reboot
1842389
Major		Evo-pfemand process crashes on ACX7348/ACX7332/ACX7024/ACX7509 platforms
Product-Group=evo
Severity=Major		On ACX7348/ACX7332/ACX7024/ACX7509 platforms, evo-pfemand process crashes after evo-pfemand application restarts or after a RE(Routing Engine) switchover resulting in impact on forwarding traffic.
PR NumberSynopsisCategory: ISIS routing protocol
1847557
Critical		Link State of IS-IS IPv6 adjacency is not updated after interface flap (Due to any reason)
Product-Group=evo
Severity=Critical		On all Junos and Junos Evolved platforms with Intermediate System-to-Intermediate System (IS-IS) protocol configured with IPv6 Multitopology, in rare scenarios the IS-IS adjacency is not updated and IPv6 traffic drop is seen after restarting the FPC.
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1817705
Critical		The l2ald crash is observed when adding scaled EVPN-VXLAN configuration on Junos platforms
Product-Group=evo
Severity=Critical		On Junos platforms, if disk is full, when scaling configuration is moved to baseline configuration and move back to scaling configuration, l2ald try to create a source VTEP, but old VTEP is still in the middle of deletion, so kernel return EBUSY and l2ald will retry. If retry too many times, l2ald insist and core.
1838335
Critical		High FPC CPU utilisation and local MAC learning failure in EVPN-MPLS scenario due to rapid MAC moves
Product-Group=evo
Severity=Critical		On all Junos platforms (except MX platforms with MPC10, MPC11, LC9600) with Ethernet Virtual Private Network (VPN) - Multiprotocol Label Switching (EVPN-MPLS) configured, Media Access Control (MAC) learning failure and high CPU utilisation in FPC is seen due to rapid MAC moves and incorrect interface state in Packet Forwarding Engine (PFE).
PR NumberSynopsisCategory: lacp protocol
1874126
Major		AE member not able to discover lost LACP peer connection leading to traffic black-holing
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms, when a loop occurs in the transmission switch, the device starts receiving looped LACP (Link Aggregation Control Protocol) PDU's from itself, instead of messages from the actual peer device. This causes the system to mistakenly believe that a valid LACP connection exists, even though the peer device is not actually connected.As a result, it continues to forward traffic as if the peer were active. Since no valid peer connection is present, this can lead to traffic blackholing .
PR NumberSynopsisCategory: authd (AAA) library code
1860913
Major		The authd process crashes when /etc/resolv.conf file is empty
Product-Group=evo
Severity=Major		On Junos OS Evolved ACX platforms, when DHCP (Dynamic Host Control Protocol) local server is configured without domain-name specified, the authd process crash may be observed. There will be no forwarding traffic impact due this issue, however, new DHCP client requests will not be answered.
PR NumberSynopsisCategory: MPC11 ULC platform software related issues.
1881499
Major		MX2010: MPC11E - FPC 1 temp sensor DDR4 A failed
Product-Group=evo
Severity=Major		DDR temp sensor is designed to be used periodically to get temps to send to chassisd. The temp sensors reside may have an intermittent contention that can cause these read failures resulting in DDR4 Temp Sensor Fail" logs on MPC11E linecards.
PR NumberSynopsisCategory: Multiprotocol Label Switching
1854623
Major		The rpd process crashes due to memory exhaustion
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms, an out-of-memory condition in the rpd process caused by uncontrolled memory allocation leads to the rpd process crashing.
1859219
Major		RSVP-TE LSP path is not re-optimised to the path with best IGP metric
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms, when RSVP-TE (Resource Reservation Protocol - Traffic Engineering) is configured with MBB (make-before-break) setup, if the protected link of the primary LSP (Label Switched Path) goes down and if "clear mpls lsp" or "clear rsvp session" commands are executed, then LSP switches to new instance from the old which will be on higher IGP (Interior Gateway Protocol) metric. However, after re-optimization, LSP will not get switched to better IGP metric path and remain in old instance. Traffic drop can be seen due to this double fault events.
PR NumberSynopsisCategory: Multicast Routing
1876458
Major		MX960 mcsnoopd core dump during rt_mcnh_nh_release
Product-Group=evo
Severity=Major		The root cause is, when the system comes up after reboot, in MCSNOOPD (/usr/sbin/mcsnoopd used for L2 multicast), the lsi interfaces are learned. In MCSNOOPD, when there are 4 lsi interfaces learned, we create a nexthop(assume VE NH1) with all these 4 lsi as members and we use it in the routes for forwarding the traffic. When MCSNOOPD learns 5th lsi interface, as per internal NH(nexthop) allocation logic, we allocate a new nh(assume VE NH2) containing all these 5 lsi interfaces and free the old NH(VE NH1). The old freed NH(VE NH1) is accessed and tried to be freed again in another part of the code flow which is causing MCSNOOPD core(/usr/sbin/mcsnoopd). The fix is to free the old NH(VE NH1) in a common place instead of freeing in multiple places.
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
1876497
Minor		Wrong digest algorithm is used for ECDSA key based certificate requests using PKI
Product-Group=evo
Severity=Minor		On all Junos and Junos Evolved platforms, when generating Elliptic Curve Digital Signature Algorithm (ECDSA) based Certificate Signing Request (CSR) using Public Key Infrastructure (PKI), SHA-384 digest is used even when other digest algorithm is specified in Command Line Interface (CLI). This issue will impact services that are based on these certificates when the services are configured for specific digest algorithm.
PR NumberSynopsisCategory: QFX5K EVO Platform Optic
1723814
Critical		QFX5700: SFP+-10G-ACU1M : DAC Cable port down on after performing jack out and jack in.
Product-Group=evo
Severity=Critical		QFX5700: SFP+-10G-ACU1M : DAC Cable port down on after performing jack out and jack in. This issue will not be seen if the recommended procedure for cable jack-out and jack-in is followed: 1. Disable the interface from EVO configuration 2. Jack-out the cable 3. Jack-in the cable (or another cable) 4. Re-enable the interface from the EVO configuration If the recommended procedure is not followed, and a jack-out/jack-in is performed, this issue will be hit. To come out of this situation, the workaround is to disable and re-enable the affected interface from EVO configuration.
PR NumberSynopsisCategory: KRT Queue issues within RPD
1868085
Major		The rpd process crashes and asserts are seen due to memory leak
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms, rpd process crashes and asserts are seen due to a memory leak when BGP sharding is enabled and 'show route' is performed continuously.
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1858750
Critical		Route change is not synced after rpd restart due to rib-fib inconsistency
Product-Group=evo
Severity=Critical		On all Junos OS Evolved platforms, after rpd (Routing Protocol Daemon) restart, the route change is not sent from routing daemon RIB(Routing Information Base) to forwarding plane FIB (Forwarding Information Base). This results in traffic drop.
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1860786
Major		BGP queue deadlock on Junos/Junos OS Evolved/cRPD platforms leading to route advertisement failure and traffic loss
Product-Group=evo
Severity=Major		On all Junos, Junos OS Evolved, and cRPD platforms, due to deadlock in internal processes, BGP (Border Gateway Protocol) route advertisement fails leading to traffic disruption.
PR NumberSynopsisCategory: Bug and Review Tracking for Segment routing traffic eng
1860334
Major		A momentary drop in traffic is observed when changes are applied on multipath SR-TE LSPs
Product-Group=evo
Severity=Major		On all Junos and Junos OS EVO (Evolved) platforms, when using SR-TE (Segment Routing-Traffic Engineering) LSP (Label-Switched Path) within a multipath container, a configuration or state change (Eg: modifying the maximum-ecmp value) or a change to the segment-list on one SR-TE LSP, may impact other LSP traffic which are pointing to the same BGP Protocol next-hop. During such event, SR-TE routes are temporarily moved to a hidden state, leading to brief traffic disruption. This occurs because SR-TE is populating route parameters with an unusable next-hop.
PR NumberSynopsisCategory: Configuration mgmt, ffp, load-action, commit processing
1839362
Minor		The commit error is seen in backup RE on MX platforms
Product-Group=evo
Severity=Minor		On all MX platforms, the commit fails in Backup RE during configuration commit where "fast-synchronise" and "graceful-switchover" are being committed together.
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.
1872820
Major		The dcd process crashes when deactivating only 'swap' under ' interfaces <> unit <> output-vlan-map' with no other attributes present
Product-Group=evo
Severity=Major		On all Junos and Junos OS Evolved platforms, this issue affects configurations where Virtual Local Area Network (VLAN) mapping is used, particularly in scenarios where only the swap attribute is applied under 'interfaces <> unit <> output-vlan-map'. Sequence of 'Deactivate -> Activate -> Commit' of the config hieararchy leads to crash of the device control daemon (dcd) process, potentially causing service disruption.
PR NumberSynopsisCategory: Issues related to Logging/Tracing, errmsg, eventd infrastruc
1843602
Major		TCP session between syslog server and device remains in closed state
Product-Group=evo
Severity=Major		On all Junos platforms, a TCP (Transmission Control Protocol) connection issue occurs between the device and syslog server after an idle period exceeding 2 hours. The session gets terminated and remains in a closed state without initiating any new session until the syslog server configuration is deleted and added again. This impacts disruption in log forwarding to the remote syslog server.
PR NumberSynopsisCategory: ACX724 timing issues
1868449
Major		Performance measurement will be impacted on deactivating both chassis and PTP configuration and power off USB
Product-Group=evo
Severity=Major		On ACX7024 Junos OS Evolved platform, performance measurement impact will be seen (measurement will be incorrect since compensation removed) on deactivating both chassis and PTP configuration and power off USB. It is very unlikely sequence to be happened.
PR NumberSynopsisCategory: Virtual Private LAN Services
1850803
Minor		A traffic outage is seen when disabling and enabling the LACP configuration
Product-Group=evo
Severity=Minor		On all Junos and Junos OS Evolved platforms that support EVPN Egress Link Protection, the AE(Aggregated Ethernet) member-link "Device flags" keeps "Present Running PFE-Gone" even after the LACP(Link Aggregation Control Protocol) configuration is re-enabled.
PR NumberSynopsisCategory: ACX7000 PTP timing related issues.
1848586
Major		PTP packets which are incoming with with padded bytes are dropped on certain Junos Evolved ACX platforms
Product-Group=evo
Severity=Major		In a rare scenario, on Junos Evolved ACX7024, ACX7100-32C and ACX7100-48L platforms configured with PTP (Precision Time Protocol) it is observed that the PTP FPGA (Field Programmable Gate Array) drops the incoming PTP packets with trailing padded bytes. But there is no impact to the active traffic due to this issue, apart from the PTP traffic (PTP is impacted since Delay-Request/Response packets are getting dropped).



Extended Solution

24.2R2-S2-EVO - List of Known issues 

PR NumberSynopsisCategory: ACX7020 Platform Software
1890751
Major		ACX7024 see's a "\" character in show chassis hardware output
Product-Group=evo		Whenever the USB device brand Rally2 is connected to USB port A, a stale /dev/sda entry is being created, which results in junk characters being printed in the show chassis hardware output. To address this issue a fix has been added to verify whether the opened device is a valid block device. If it's not, the code now skips to the next iteration without processing it. Added logic to sanitize the device string by replacing junk characters with spaces. Introduced additional checks to validate block count and size, preventing further processing of dummy or invalid devices.

Resolved In: evo:24.4R2-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO
PR NumberSynopsisCategory: Device Configuration Daemon
1848768
Major		MTU configuration is not applied from the configuration group after commit and "warning" is seen
Product-Group=evo		When configuring MTU on interfaces through a configuration-group and commit the changes, those are not saved on the configuration file.

Resolved In: evo:22.3X50-EVO evo:22.3X80-D49-EVO evo:22.4R3-S6-EVO evo:23.2R2-S4-EVO evo:23.4R2-S5-EVO evo:23.4X100-D40-EVO evo:24.2R2-S1-EVO evo:24.4R1-S3-EVO evo:25.2R1-EVO junos:21.2R3-S9 junos:21.2X32-D30 junos:21.2X33 junos:21.2X40 junos:21.2X9 junos:22.3X60 junos:22.4R3-S6 junos:22.4X50 junos:23.2R2-S4 junos:23.4R2-S5 junos:24.2R2-S1 junos:24.2R2-S2 junos:24.2X1 junos:24.4R1-S2 junos:24.4R1-S3 junos:24.4R2 junos:25.2R1
PR NumberSynopsisCategory: ACX BFD specific issues
1885776
Minor		ACX EVO - FTP "file copy" causing BFD flaps
Product-Group=evo		Multihop sessions in ACX are distributed sessions(software-based) and not inlined (hardware-offloaded). Distributed sessions are hosted by the ppman application, that shares the same CPU with rest of the JunosE applications. During the time of copy, packetio is used considerably which would have delayed in processing other control packets. Since the BFD sessions were running at a detection-time of 300ms, a delay in packetio path to ppman could influence the timer expiry, if ppman does not receive enough packet within the detection-time. For improved failure detection, BFD is configured on all BGP sessions using a 300ms detection timer (100x3). BGP BFD can be singlehop or multihop sessions, while singlehop bfd sessions support this interval, multihop bfd does not. Multihop sessions on ACX7348, ACX7024, ACX7100, do not support BFD 3x100ms, use 3x1000ms

Resolved In:
PR NumberSynopsisCategory: Firewall support for DNX
1869363
Minor		The router incorrectly assume the VRRP Master role on Junos Evolved ACX platforms
Product-Group=evo		On Junos Evolved ACX platforms, dual VRRP mastership may be seen with VRRP configuration and having filter configuration with log/syslog action. Due to the issue, the VRRP advertisements were not processed correctly, it was receiving the advertisements but getting discarded when log action is configured on the filter, so it assumed the master role. The issue may affect traffic using VRRP protocol.

Resolved In: evo:23.4R2-S6-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO
PR NumberSynopsisCategory: DNX L2 related features
1886421
Minor		VSTP convergence failure on Junos OS Evolved ACX7K when IRB shares bridge domain with VSTP enabled IFL
Product-Group=evo		On all Junos Evolved ACX7K platforms, when a VLAN Spanning Tree Protocol (VSTP) enabled Layer 2 logical interface (IFL) shares a bridge domain with an Integrated Routing and Bridging (IRB) interface, VSTP fails to converge due to Spanning Tree Protocol (STP) packets are misrouted to the IRB interface, preventing them from reaching the VSTP process. This causes potential traffic loops due to lack of VSTP convergence.

Resolved In: evo:23.4R2-S6-EVO evo:24.4R2-EVO evo:24.4R2-S1-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO
PR NumberSynopsisCategory: Firewall related development
1875725
Minor		The firewalld process crashes post specific set of filter related modifications performed in single commit
Product-Group=evo		On Junos EVO platforms, When Firewall Filter change involved both delete and change to new filter on an interface in a single commit resulted in Firewalld coredump

Resolved In: evo:23.4R2-S6-EVO evo:24.4R2-EVO evo:24.4X200-D10-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: Interface PRs defect & enhancement requests
1859501
Minor		Interfaces with the same outer VLAN ID but different inner vlans or inner-lists/ranges are reporting a commit error
Product-Group=evo		On all Junos OS Evolved platforms, When an interface configured with the same outer VLAN ID but with different inner vlans or inner-lists/ranges, reports a commit error.

Resolved In: evo:22.2R3-S7-EVO evo:22.4R3-S7-EVO evo:23.2R2-S4-EVO evo:23.4R2-S5-EVO evo:24.2R2-S1-EVO evo:24.4R1-S3-EVO evo:24.4R2-EVO evo:25.2R1-EVO
PR NumberSynopsisCategory: EVO Netstack Juniper Tunnel Driver Module
1865403
Major		Memory leak is observed when Telemetry is configured
Product-Group=evo		On all Junos and Junos Evolved platforms having Telemetry configured, the memory allocations in 512 bytes slab that are seen to be growing in problem state, are related to write on a unix domain socket (internal to application). Since the data is not read, the send buffer keeps growing and the associated memory does not gets released. Every telemetry response from the producer does a 1 byte write on this socket and over a period of time the send buffer gets full. The default size of the unix socket send buffer is set to 512MB. But there is no functional impact.

Resolved In: evo:22.3X50-EVO evo:22.3X50-J3-EVO evo:22.3X80-D47-EVO evo:22.3X80-D49-EVO evo:23.4R2-S5-EVO evo:24.4R2-EVO evo:24.4X200-D10-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:23.4R2-S5 junos:24.2R2-S2 junos:24.4R2 junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: EVO L2 Control Plane PRs
1859302
Major		EVPN next-hop installation for ESI over VTEP fails after remote device restart on PTX and QFX platforms.
Product-Group=evo		On all Junos Evolved PTX and QFX series platforms, running EVPN (Ethernet Virtual Private Network) and ESI LAG (Ethernet Segment Identifier Link Aggregation Group) is causing issues with the next-hop installation after restarting of remote or peer devices, which affects the overall network stability and performance.

Resolved In: evo:23.4R2-S5-EVO evo:24.2R2-S1-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO
PR NumberSynopsisCategory: SNMP, mib2d issues
1890712
Minor		The snmpwalk for OID ifJnxInputErrors is not working on Junos Evolved platforms
Product-Group=evo		On 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.

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

Resolved In:
PR NumberSynopsisCategory: ACX7509 timing related issues
1877949
Major		ACX7509 : Evopfemand core triggered RE switchover. Major service impact
Product-Group=evo		A crash in Broadcom code is leading to evo-pfemand core. RE switchover is triggered due this crash/core.

Resolved In:
PR NumberSynopsisCategory: Libjtask for RPD tasks, scheduler, timers, memory, and slip
1843627
Critical		Memory leak when deactivating/reactivating routing instances with vrf-table-label
Product-Group=evo		On all Junos Evolved platforms, a memory leak occurs when a routing instance configured with "vrf-table-label" is deactivated and then reactivated, followed by a Routing Engine (RE) switchover on dual RE systems. This issue causes a slow memory leak in the system.

Resolved In: evo:23.4R2-S4-EVO evo:23.4R2-S5-EVO evo:24.4R1-S3-EVO evo:24.4R2-EVO evo:24.4X200-D10-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:23.4R2-S4 junos:23.4R2-S5 junos:24.4R1-S3 junos:24.4R2 junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: Packet Based Link Qualification Analysis (PBLQ) on EVO platforms
1845996
Major		Interface failure when removing and adding the ports to ae bundle
Product-Group=evo		On all Junos Evolved PTX10001-36MR/PTX10001-36MR-K/PTX10008/PTX10016 platforms, removing a port from an Aggregated Ethernet (AE) bundle and then re-adding it causes the interface (IF) to go down and not come back up.

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

Resolved In: evo:23.2R2-S5-EVO evo:25.3R1-EVO junos:25.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.
1802376
Critical		The picd crash is observed on Junos OS Evolved ACX /PTX platforms
Product-Group=evo		When SysMan application is terminated twice due to picd stop signal results in picd.re crash leading to traffic impact.

Resolved In: evo:22.3X80-D46-EVO evo:23.4R2-S3-EVO evo:24.4R1-EVO
PR NumberSynopsisCategory: VMHOST platforms software
1787608
Critical		The chassisd crashes at first boot up after reboot
Product-Group=evo		Additional logging has been added to the primry Routing Engine. This is to help narrow down the issue which chassisd process restarted unexpectedly at snmp_init_oids( ) function on the primary Routing Engine while booting up.

Resolved In:
PR NumberSynopsisCategory: Track Windriver Linux issues
1631579
Critical		A few line cards will be stuck in the 'Present' state and later go 'Offline'
Product-Group=evo		A system equipped with specific line cards, the line cards will be stuck in the 'Present' state and later go 'Offline' after the line card or router is rebooted. Ideally, the Line Card should go 'Online' instead it goes 'Offline'.

Resolved In: junos:19.1R3-S10 junos:19.4R3-S11 junos:21.1R3 junos:21.1R3-S1 junos:21.1R3-S2 junos:21.1R3-S4 junos:21.1R3-S5 junos:21.2R3 junos:21.2R3-S4 junos:21.3R3-S2 junos:21.4R3 junos:21.4R3-S1 junos:22.2R3-S1 junos:22.4R3-S2 junos:22.4X3 junos:22.4X4 junos:23.2R2-S1 junos:23.2R2-S3 junos:23.4R2-S4 junos:23.4R2-S5 junos:23.4X30 junos:23.4X30-D20 junos:24.2R1-S1 junos:24.2R1-S2 junos:24.2R2-S2 junos:24.2X1 junos:24.4R1



Modification History

First publication 2025-07-30