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 22.4R3-S7-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

Please review the SRN for software deployment planning.

Solution

Junos Software service Release version 22.4R3-S7-EVO is now available.

22.4R3-S7-EVO - List of Fixed issues 

PR NumberSynopsisCategory: Border Gateway Protocol
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.
PR NumberSynopsisCategory: EVO L3 routing for BCM XGS Platforms
1828017
Minor		The pfemand crash will be observed when "clear bgp neighbor all" command is executed
Product-Group=evo
Severity=Minor		On all Junos and Evolved platforms, in a scaled setup when the "clear bgp neighbor all" command is executed or "restart l2-learning immediately" is executed, the pfemand crash will be seen which leads to the restarting of the Flexible Packet Forwarding Card (FPC).
PR NumberSynopsisCategory: PFE L2 forwarding features on BT based platforms
1777003
Major		PTX10001-36MR: epp_epc_intr_shmem_err seen in logs
Product-Group=evo
Severity=Major		On a BT-base PTX platform, you may see the "epp_epc_intr_shmem_err" in its Syslog when a vlan id is missing from an interface.
PR NumberSynopsisCategory: Express BT PFE L3 Features
1856732
Minor		Post configuration changes on an AE interface MPLS traffic is discarded for other interfaces/AE interface on a different FPC
Product-Group=evo
Severity=Minor		On Junos Evolved PTX10008, PTX10016, PTX10004 platforms having JNP10K-LC1201/LC1202 and multiple FPCs (Flexible PIC (Physical Interface Cards) Concentrators), it is observed that when any of the following configuration changes are performed on a given AE (Aggregate Ethernet) interface, this may cause MPLS (Multiprotocol Label Switching) traffic to be dropped on other interfaces or AE interfaces hosted on other FPCs having the same PIC and port number as the intended AE interface members where no such configuration change is made.* When family MPLS is removed from an AE interface, or* When an AE interface with family MPLS configured is deactivated, or* When the IFD (Interface Device) MTU (Maximum Transmission Unit) is modified on the AE interface that has family MPLS configured, or* When "vlan-tagging" is added or removed on an AE interface that has family MPLS configured, or* When "encapsulation" is added or removed on an AE interface that has family MPLS configured PTX10003, PTX10001-36, PTX10002-36QDD are not exposed.MPLS Traffic drops are recorded as 'normal discard' under "show pfe statistics traffic"
PR NumberSynopsisCategory: MX304 fabric issues (ULC side)
1863674
Major		Link error reported on one PFE(Packet Forwarding Engine) will also report error on other PFE
Product-Group=evo
Severity=Major		On all Junos MX304 platforms, when a link error or training failure occurs, the "show chassis fabric fpcs extended" and "show chassis fabric plane extended" commands display incorrect PFE-to-plane mappings for plane numbers greater than 9. As a result, an incorrect PFE is shown as affected. Due to this incorrect mapping, a training failure, it shows both PFEs getting impacted.
PR NumberSynopsisCategory: QFX Access Control related
1872280
Major		The l2ald process crash is observed on non L2NG Junos platforms configured with "native-vlan-id" and "bridge-domains" on an IFL
Product-Group=evo
Severity=Major		On non L2NG (Layer2 Next Generation) Junos EX, MX and SRX platforms, the l2ald (Layer 2 Address Learning Daemon) process crash is observed when an IFL (Logical Interface) configured with "native-vlan-id" and "bridge-domains" and when certain config change takes place in an IFL which maps VLAN (Virtual Local Area Network) index to NULL. The dereferencing of this NULL pointer causes the crash.
PR NumberSynopsisCategory: Firewall Filter
1872347
Critical		System crash is observed due to frequent filter changes in a scale scenario having mib2d process in use
Product-Group=evo
Severity=Critical		On Junos OS platforms, the system runs out of memory due to mbuf (Memory Buffer) leak, leading to the system crash (VMcore is generated) resulting in service impact and error logs is observed. This issue happens when a firewall filter is applied to around 1k ifls (logical interface), each filter having > 250 terms and the filter is updated every 2-3 minutes which triggers an update for all filter attachments.
PR NumberSynopsisCategory: Layer 3 forwarding, both v4+v6
1841071
Major		Incorrect routing seen for VRF traffic after changing packet-forwarding options from hw-db-profile to balanced-exem
Product-Group=evo
Severity=Major		On all ACX Evolved platforms the packet-forwarding options hw-db-profiles "balanced-exem" and "l3-xl" causes routing issues for traffic coming in a VRF (Virtual routing and forwarding) and forwarded using the default route leading to traffic impact.
PR NumberSynopsisCategory: EVO Netstack icmpd
1822994
Minor		DNS (Domain Name System) resolution fails when nameserver is reachable via a routing instance bound to a line card port on releases prior to 24.1R1-Junos OS Evolved
Product-Group=evo
Severity=Minor		On Junos OS Evolved based platforms, while using ping, traceroute, or other utility that requires host name resolution, an error is raised indicating hostname resolution has failed.
PR NumberSynopsisCategory: Issues related to EVO dependency layer including object graphs, incompletes, anomalies and nkdb
1857091
Major		Extremely rare core in applications
Product-Group=evo
Severity=Major		We may see a extremely rare core in applications when there are several interface flaps or interface configuration changes or reboots in a short interval of a few seconds. The issue is hard to hit and is seen only been twice even though its a day 1 issue.
PR NumberSynopsisCategory: Interface PRs defect & enhancement requests
1859501
Minor		Interfaces with the same outer VLAN ID but different inner-lists/ranges are reporting a commit error
Product-Group=evo
Severity=Minor		On all Junos OS Evolved platforms, When an interface configured with the same outer VLAN ID but with different inner-lists/ranges, reports a commit error.
1867231
Major		Multicast traffic impact on EVO platforms after laser OFF/ON on AE member peer interface
Product-Group=evo
Severity=Major		On all Evo platforms, configured with the Aggregated Ethernet (AE) due to laser OFF and ON on the peer interface of the DUT's AE member, multicast traffic will be dropped.
1867603
Major		Coredump during LAG disable
Product-Group=evo
Severity=Major		Pre-conditions are: 1. Aggregate Ethernet interface is configured with/without lacp 2. Aggregate Ethernet interface is configured with BFD configs. Trigger is: 3. With the specified configuration, if any config change is issued on AE IFL then it results in aggd core. 4. One such example is [edit interfaces ae2301 unit 0] + disable; There is no work-around, so none is mentined.
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: EVPN control plane issues
1839959
Critical		The MAC+IP table and mac-table are not in sync in the EVPN-MPLS active-active multihomed scenario leading to traffic loss
Product-Group=evo
Severity=Critical		On all Junos and Junos OS Evolved platforms that supports ESI lag interface and in an EVPN-MPLS (Ethernet Virtual Private Network - Multi Protocol Label Switching) active-active multihomed scenario, when the multihomed access interfaces are flapped in quick succession, it results in an unresolved destination route for the specific IP host. This is occurred due to race condition within l2ald (Layer 2 Address learning daemon) followed by an interface flap which causes the locally learned MAC to go missing from the mac-table on the other PE router.
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1833660
Major		Stale MAC entries may remain in the MAC table of EVPN routing instances after rapid MAC-IP move scenarios
Product-Group=evo
Severity=Major		On all Junos OS and Junos OS Evolved platforms with EVPN-MPLS (Ethernet Virtual Private Network - Multiprotocol Label Switching) setup , stale MAC entries may remain in the MAC table of the EVPN (Ethernet Virtual Private Network) routing instances during rapid MAC-IP move scenarios. This can cause MAC tables to reach their limits preventing new MAC addresses learning and user registration.
PR NumberSynopsisCategory: Layer 2 Control Module
1855088
Major		In Junos EX and QFX platforms, when ERPS protocol is enabled on a ISL trunk, the commit command fails
Product-Group=evo
Severity=Major		In Junos EX and QFX platforms, when a port is configured with Inter-switch-link (ISL) trunk and the Ethernet ring protection switching (ERPS) protocol is enabled on the port, the commit command fails, causing the commit-check daemon process to crash and preventing the new configuration from being applied. This doesn't impact the devices traffic, performance, or management.
PR NumberSynopsisCategory: Label Distribution Protocol
1772904
Major		The rpd process crashes when LDP telemetry streaming xpath is enabled
Product-Group=evo
Severity=Major		On all Junos OS and Junos OS Evolved platforms, the rpd process crash when LDP telemetry for xpath "/network-instances/network-instance/mpls/signaling-protocols/ldp/neighbors/neighbor/hello-adjacencies/hello-adjacency/hello-holdtime/state/hello-expiration" is enabled.
PR NumberSynopsisCategory: Protocol Independant Multicast
1740811
Critical		Drop in multicast traffic observed when multiple Reverse Path Forwarding (RPF) interfaces are available towards the upstream router
Product-Group=evo
Severity=Critical		This issue is linked to the PIM Join-load-balance feature. When downstream router has multiple ECMP paths towards the upstream router to reach the multicast source and is configured for PIM Join-load-balance, load balancing of joins creates an active upstream path and a standby upstream path. In scenarios with multiple links available towards the upstream router, the standby path for a given (S, G) pair needs to be reselected multiple times due to ongoing rebalancing. Consequently, the old standby path must be pruned, and periodic joins must be canceled. But, in this case, PIM prematurely removes the old standby path without sending a prune on that path and consequently does not remove the periodic joins. This mismanagement leads to the upstream router inadvertently adding an unintended interface to its OFIL (Outgoing Interface List). This causes replication issue at upstream router and traffic loss is observed.
PR NumberSynopsisCategory: KRT Queue issues within RPD
1831421
Critical		Multiple flaps on BGP routes causing traffic blackholing
Product-Group=evo
Severity=Critical		On all Junos and Junos Evolved platforms, BGP (Border Gateway Protocol) route with PNH1 (Preserve Nexthop Hierarchy) may not be resolved correctly during rapid route fluctuations (e.g., link flaps). Specifically, when the preferred route (Rt1) experiences rapid deletions and re-additions, the system might incorrectly associate the PNH with an outdated route (Rt2).
PR NumberSynopsisCategory: Issues related route resolution routing infrastructure
1737594
Critical		Traffic drop can be seen in the MPLS traffic Engineering scenario
Product-Group=evo
Severity=Critical		On all Junos and Junos Evolved platforms, traffic drop can be seen in MPLS (Multi-Protocol Label Switching) traffic engineering with IGP-FRR (Interior Gateway Protocol Fast Reroute) and preserve next-hop hierarchy. This issue happens when the BGP (Border Gateway Protocol) routes are resolving over BGP and there is a change in the active route. The session ID for the IGP-FRR is assigned to the new active route and the old active route is withdrawn, while the above processing is done the session ID is associated with both the old and new active route, and the old active route, the route gets deleted which triggers the IGP-FRR session ID to be down and the unilist (ECMP)path get stuck causing traffic impact.
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1849202
Major		BGP route still seen in routing table when route not available
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms , the router learns routes through the BGP (Border Gateway Protocol) and has the feature: "BGP RIB Sharding" enabled for IPv4. These routes are stored in the Inet.0 routing table. Later, if the neighbor that announced this route or the protocols associated with the routing table of the used VRF (Virtual Routing and Forwarding) are removed, the route remains in the routing table, and hence traffic is forwarded to the stale routes.
PR NumberSynopsisCategory: Resource Reservation Protocol
1792192
Major		Missing HELLO object in RSVP Hello messages after RE failovers in the NSR mode
Product-Group=evo
Severity=Major		In rare unknown condition after RE switchover, rsvp hello can have local instance to be zero due to wrong information synced from master RE by mirroring process. When rsvp neighbor is created and never received hello exchange with neighbor, the replication entry which is synced to standby RE will have most of the information as zero, including the local instance, which is used to generate hello object. After RE switchover, rsvp hello will have local instance to be zero due to the wrong information synced from master RE by mirroring process. This is addressed by update the replication entry once all the parameters of the rsvp neighbor is filled, so standby RE will receive the right info, also for future protection, backup RE will avoid creating neighbor until after switchover and setting a new local instance if it is zero.
1864949
Major		User traffic dropped after ISIS went down on one side with trapcode observed
Product-Group=evo
Severity=Major		On all JUNOS and JUNOS evolved Operating Systems, if a link along the path of a Label Switched Path (LSP) flaps briefly such that the router at upstream end of the flapping link does not detect the link down but only the router at the downstream end does, then the upstream router does not undertake necessary actions, like generating ResvTear message, that should be taken after next-hop link down. This will result in unexpected traffic blackholing on the router at the downstream end of the flapping link.
PR NumberSynopsisCategory: Issues related to NETCONF
1796297
Major		Error message not prompted on commit confirmed RPC sent in private mode on all Junos and Junos Evolved platforms
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms, commit confirmed command executed with remote procedure call (RPC) in private configuration mode is being allowed where ideally it should not be.

 

 

22.4R3-S7-EVO - List of Known issues 

PR NumberSynopsisCategory: DNX L2 related features
1841573
Minor		High CPU utilization observed on all Junos Evolved ACK7k platforms
Product-Group=evo		On all Junos Evolved ACX7k platforms, high CPU utilization is observed when multiple IFLs (logical interface) are configured over the same IFD (physical interface device). The Broadcom (Brcm) MACs become out of sync with Routing Engine (RE) MACs, performance is affected, and then there is potential traffic disruption.

Resolved In: evo:24.2R2-EVO evo:24.4R1-EVO evo:24.4R2-EVO evo:25.1R1-EVO evo:25.2R1-EVO
PR NumberSynopsisCategory: Issues related to EVO Health Monitoring System
1737180
Minor		EVO: Support new sensors under opnconfig /components/components/state hierarchy via EHMD for RE:CPU
Product-Group=evo		New sensor leaf are supported thru this PR for openconfig-platform model -- components/component/state: at the components/component[name=RE0:CPU0] level

Resolved In: evo:22.3X80-D36-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:23.1R2 junos:23.2R2 junos:23.3R1 junos:23.4R1
PR NumberSynopsisCategory: System Management daemon and related issues
1808788
Major		sysapp-mib.re core generated for EVO devices.
Product-Group=evo		On all JUNOS-EVO platforms, a sys-app mib core might be generated when running program with large parameters.

Resolved In: evo:23.2R2-S3-EVO evo:23.4R2-S3-J15-EVO evo:23.4R2-S4-EVO evo:23.4X100-D30-EVO evo:24.2R2-EVO evo:24.4R1-EVO evo:25.3R1-EVO
PR NumberSynopsisCategory: Integrated Routing & Bridging (IRB) module
1827648
Minor		ARP not learned on Switch Leading to Traffic Drop in EVPN-VXLAN Setup
Product-Group=evo		On all Junos QFX series platforms in an EVPN (Ethernet Virtual Private Network) VXLAN (Virtual Extensible Local Area Network) setup with CRB (Centralized Routing Bridge) architecture, ARP packets are not being learned, leading to traffic forwarding issues. This problem arises when ARP packets are sent from the firewall to the spine switches. The issue is linked to IRB (Integrated Routing and Bridging) handling and bridge domain re-incarnation, which triggers ARP request failures and impacts L3 forwarding.

Resolved In: junos:21.4R3-S10 junos:22.2R3-S5 junos:23.2R2-S4 junos:23.4R2-S4 junos:24.2R2 junos:24.3R1 junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: Platform infra to support jvision
1880876
Major		Regression: Junos Evolved GNMI for the x-path ../ethernet/state/auto-negotiate is returning true even though auto-negotiation: is Disabled
Product-Group=evo		On a PTX10008 running Junos Evolved software, the GNMI result for the x-path /interfaces/interface[name=et-1/0/1]/ethernet/state/auto-negotiate is returning true even though auto-negotiation: is Disabled

Resolved In:
PR NumberSynopsisCategory: OSPF routing protocol
1865621
Minor		IPSEC OSPF3 realm sessions do not stay UP
Product-Group=evo		IPSEC OSPF3 realm sessions do not stay UP when you have the same interface configured in both ospf3 realm and non-realm. When the aggregate interface goes down for any reason (physical link issue or something else) when it recovers the realm session will not come back online.

Resolved In:
PR NumberSynopsisCategory: Issues related to broadband edge apps (PPP, DHCP) on ZT/YT
1827261
Major		Junos OS: MX Series with AFT line card: Subscriber login/logout activity will lead to a memory leak (CVE-2025-30647)
Product-Group=evo		A Missing Release of Memory after Effective Lifetime vulnerability in the packet forwarding engine (PFE) of Juniper Networks Junos OS on MX Series with AFT line card allows an unauthenticated adjacent attacker to cause a Denial-of-Service (DoS). Please refer to https://supportportal.juniper.net/JSA96457 [juniper.net] for more information.

Resolved In: evo:23.2R2-S4-EVO evo:24.2R2-EVO evo:24.4R1-EVO evo:25.1R1-EVO junos:21.2R3-S9 junos:21.4R3-S10 junos:22.2R3-S6 junos:22.4R2-S1-J8 junos:22.4R3-S5 junos:23.2R2-S3 junos:23.4R2-S3 junos:24.2R2 junos:24.4R1 junos:25.1R1

 

Modification History

First publication 2025-05-09