Alert Type

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

Product Affected

EX4300 only

Alert Description

Junos Software Service Release version 21.4R3-S10 is now available for download from the Junos software download site.

This SRN is for the EX4300 series/platforms only

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

 

Solution

Junos Software service Release version 21.4R3-S10 is now available.

21.4R3-S10 - List of Fixed issues 

PR NumberSynopsisCategory: EX4300 PFE
1849492
Major		VSTP BPDU are not properly processed by EX4300 when the interface is configured in SP style
Product-Group=junos
Severity=Major		VSTP BPDU are not properly processed by EX4300 when the interface is configured in SP style causing VSTP not to converge
PR NumberSynopsisCategory: SRX Gen-3 RE, leveraged from Point Success Mt.Rainier
1730298
Minor		Image validation option not supported on Junos SRX5K platforms
Product-Group=junos
Severity=Minor		On Junos SRX5K platforms with RE3 (Routing Engine), there is no support for image compatibility validation in the pre-check script. Hence the image compatibility discrepancies may get bypassed.
PR NumberSynopsisCategory: Border Gateway Protocol
1817834
Major		The rpd crashes when stale label entry keeps increasing when knob stale-labels-holddown-period is configured
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms configured with the "stale-labels-holddown-period" setting and extensive label configurations (such as Multiprotocol Label Switching labels), the Routing Protocol Daemon (RPD) may crash if stale labels are not cleared periodically and keep accumulating. Due this, temporary traffic impact will be seen until the rpd process restarts.
PR NumberSynopsisCategory: Track PRs in BGP BMP area & is part of BGP inside RPD.
1767785
Minor		The EOR message is missed for one peer in a scaled BMP scenario
Product-Group=junos
Severity=Minor		On all Junos and Junos OS Evolved platforms with BGP Monitoring Protocol (BMP) enabled in scaled scenario (4K BGP peers, 6 BMP stations), after disabling/enabling BMP, due to timing issues, one out of six BMP stations will not receive End-of-RIB (EOR) message for one peer. This will not impact routing or data forwarding, however will have impact on data collection.
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=junos
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: MX304 Chassis specific platform 
1655827
Major		MX304: Chassis : RSI command execution getting aborted due to error message - "[: JUNIPER: unexpected operator"
Product-Group=junos
Severity=Major		"request support information" command show "[: JUNIPER: unexpected operator" error message at end of the command output. This error messages in not harmful.
PR NumberSynopsisCategory: Class of Service
1836528
Minor		FC id goes out of sync between the RE and PFE impacting all CoS features using FC id
Product-Group=junos
Severity=Minor		On all Junos and Junos Evolved Platform, forwarding-class (FC) identifier (id) goes out of sync between the Routing Engine (RE) and Packet Forwarding Engine (PFE) when software upgrade is performed. When In Service Software Upgrade (ISSU) is performed, FC id goes out of sync between the RE and PFE impacting all class-of-service (CoS) features using FC id. When manual software upgrade is performed (without using ISSU) , this issue will be seen as a cosmetic display issue where the order in which the FC configurations are displayed will differ.
PR NumberSynopsisCategory: QFX Access Control related
1840988
Major		PFE process crash is observed when web-management is not configured in a CWA setup
Product-Group=junos
Severity=Major		On Junos EX2300, EX3400, EX4100, EX4300, EX4400 platforms, a misconfiguration in CWA (Centralised Web Authentication) occurs when authentication web-management is not configured, leaving alias entries stale until the session clears, the interface flaps or the MAC ages out. If memory is exhausted due to these stale entries, a PFE (Packet Forwarding Engine) process crash will occur, impacting traffic on all ports.
PR NumberSynopsisCategory: 1G/10G LC Timing software
1583496
Major		Error message seen in clksyncd logs with SyncE/PTP configs "ESYNC-Error:ferrari_zl30362_reg_write: Error, EEC(0) not yet initialized"
Product-Group=junos
Severity=Major		Error message seen on MX10K8 chassis with SyncE/PTP configurations, This does not affect any functionality, The error seen here because the API called is specific to ferrari platform which needs to be vecterized.
PR NumberSynopsisCategory: DNS software support.
1826129
Major		Traffic outages due to memory shortage and core files
Product-Group=junos
Severity=Major		On all Junos SRX and vSRX series platforms Juniper networks Deep Packet Inspection (JDPI) gives events per packet. Domain Name System Firewall (DNSF) plugin is leaking memory while processing those events.
PR NumberSynopsisCategory: EVO L2 Control Plane PRs
1844623
Major		Stale MAC-IP entries are not cleared in an EVPN-VXLAN scenario when encapsulate-inner-vlan or decapsulate-accept-inner-vlan or both knobs are present
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms, when decapsulate-accept-inner-vlan or encapsulate-inner-vlan or both knobs are configured for a VXLAN (Virtual Extensible Local Area Network) and when any action corresponding to MAC-IP entries cleanup takes place, the MAC-IP entries will not be cleaned up from kernel. This will result in anomalies in device and could also lead to a core crash.
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=junos
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
1715343
Major		Ping overlay vxlan replies Overlay-segment present even the bridge-domain has been deactivated
Product-Group=junos
Severity=Major		The vxlan ping overlay request is recevied for a certain VNI on MX and the bridge-domain associcated with the VNI has been deactivated. However the MX still responses with "Overlay-segment present" sub-code in the reply message.
PR NumberSynopsisCategory: N/A:sw-ex-edradour-pfe
1847159
Major		Reachability issues are seen on interfaces that are aggregated without address-family
Product-Group=junos
Severity=Major		On Junos platforms, specifically on EX and QFX series aggregated interfaces configured without address-family results in reachability issues.
PR NumberSynopsisCategory: EX4100 PFE
1802455
Major		The default port behaviour is not working as expected after deleting VOIP (Voice over IP) configuration on an access interface
Product-Group=junos
Severity=Major		On EX4400/EX4100 Platforms for VXLAN (Virtual extensible Local Area Network) configuration the interface is expected to accept untagged and member vlan tagged packet on deleting VOIP (Voice over IP) configuration on an access interface. But the access interface is not allowing member vlan tagged packets and only untagged packets are allowed.
PR NumberSynopsisCategory: EX interfaces issues
1745855
Major		[EX4300-VC]Link state for ge-x/0/1 are not reflecting correctly when a VC member gets split and merge.
Product-Group=junos
Severity=Major		The interface of ge-x/0/1 port might go down after virtual-chassis split and merge on EX4300-VC
1805100
Major		Establishing virtual-chassis connection between EX4300-MP platforms, the traffic sent via the VCP port is lost minimally
Product-Group=junos
Severity=Major		On EX4300-MP platforms in non-mixed VC mode, when the VC connection is established between the platforms, the ports don't pass traffic, which leads to minimum traffic loss.
PR NumberSynopsisCategory: EX Timing software
1800949
Major		The clksyncd process crash on Junos EX platforms
Product-Group=junos
Severity=Major		On Junos and EX4400-VC platforms, the clksyncd process will crash occasionally when FPC(Flexible PIC Concentrators) restarts due to segmentation fault. There is no traffic impact due to this issue and also this issue is seen in a very corner case.
PR NumberSynopsisCategory: EX Entry Level Access VC platform
1648310
Major		For EX4100 and EX3400 Virtual Chassis switches, Ping is not working for some irbs after Master reboot and traffic loss is observed
Product-Group=junos
Severity=Major		The message was not sent to the member from the master . mac-peristence-timer does not work correctly in releases 21.4R3-S5, 21.4R3-S8. The fix is available from 22.2 release onwards.
PR NumberSynopsisCategory: Express PFE FW Features
1830706
Major		FPC crash will occur when modifying or deleting a filter instance on Junos platforms
Product-Group=junos
Severity=Major		On all Junos platforms, when a filter instance is modified or deleted, there should not be any old Packet Forwarding Engine (PFE) instances. However, during these operations, old PFE instances are being incorrectly assigned, resulting in incorrect memory address allocation. This leads to an Flexible PIC Concentrator (FPC) crash after committing the configuration, causing traffic loss.
PR NumberSynopsisCategory: SRX1500 platform software
1845407
Major		SRX1500 will not show jnxOperatingTemp and jnxFruTemp temperature reading for PSU temperature
Product-Group=junos
Severity=Major		On SRX1500, "show snmp mib walk jnxOperatingTemp" and "show snmp mib walk jnxFruTemp" will not show up temperature reading for PSU temperature.
PR NumberSynopsisCategory: idp flow creation, deletion, notification, session mgr intfce
1825279
Major		The srxpfe process crash seen during heavy traffic processing by IDP
Product-Group=junos
Severity=Major		On all SRX platforms, srxpfe (SRX Packet Forwarding Engine) process may produce coredumps and traffic drops may be observed under heavy traffic processing by IDP (Intrusion Detection and Prevention).
PR NumberSynopsisCategory: Libjtask for RPD tasks, scheduler, timers, memory, and slip
1826194
Major		The rpd crash is observed during upgrade or restart
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms, rpd crash is observed during upgrade or restart since kernel takes more time to update ifstate information.
PR NumberSynopsisCategory: MX Inline Jflow
1813925
Major		FPC reboots after sensor configuration is removed and readded over a long period on MX and EX9200-15C platforms
Product-Group=junos
Severity=Major		On all MX platforms with MPC10/MPC11/LC9600, MX304 and EX9200-15C platforms, when any sensor configuration on protocols, for example, MPLS LSP, is configured and removed over a long period, the aftd-trio process starts a memory leak and eventually causes FPC to reboot.
PR NumberSynopsisCategory: Kernel software for AE/AS/Container
1845370
Major		Interface not added back to AE bundle with multiple changes in single commit
Product-Group=junos
Severity=Major		On all Junos platforms when speed is changed on an interface which is part of AE bundle, interface will be removed and added with the updated speed. When some other operation such as interface disable is configured along with speed change on the interface in the same commit, then the interface is not removed and added to the bundle, it can cause other AE interfaces flap and traffic drop.
PR NumberSynopsisCategory: Integrated Routing & Bridging (IRB) module
1827648
Major		ARP not learned on Switch Leading to Traffic Drop in EVPN-VXLAN Setup
Product-Group=junos
Severity=Major		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.
PR NumberSynopsisCategory: ISIS routing protocol
1841108
Major		Traffic drop is seen after GRES on ISIS peer
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms, in an ISIS(Intermediate System-Intermediate System) graceful restart scenario, helper node sends and programs its locally configured hold-time (180 secs) instead of the "Restart-duration" received as hold-time from DUT (210 secs), due to this incorrect update, the hold timer expires at the helper node before the GR (Graceful Restart) is complete on DUT and it causes a flap of ISIS adjacency on peer/helper Node.
PR NumberSynopsisCategory: jdhcpd daemon
1808289
Major		Switch provisioned via ZTP going unreachable due to DHCP misbehaviour on upgrading to 21.4R3-S6
Product-Group=junos
Severity=Major		All IRB (Integrated Bridging and Routing) interfaces of EX3400-48P switches which pull initial configuration from Dynamic Host Configuration Protocol (DHCP) server via zero touch provisioning (ZTP) process, upon upgrade to 21.4R3-S6 do not send DHCPdiscover packet to obtain a new IP address after sending DHCPrelease packet resulting in interface not able to obtain IP address until rebooted.
1833148
Major		DHCP relay option "allow-server-change" does not work as expected in trusted server group when roaming between access points
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms when roaming between Wireless Access Points (WAP) and binding server is down, server failover does not happen in an active-server group even when "allow-server-change" is configured on Dynamic Host Configuration Protocol (DHCP) relay agent.
PR NumberSynopsisCategory: RPM, TWAMP feature related to SRX specific design
1830290
Major		Log messages related to 'gencfg no msg handlers' will be seen on SRX4600 platforms
Product-Group=junos
Severity=Major		On SRX4600 platforms when Real-time Performance Monitoring (RPM) related configuration is committed, 'gencfg no msg handlers for gencfg msg' log messages will be generated. This will not have any functional impact.
PR NumberSynopsisCategory: IPSEC/IKE VPN
1762463
Major		The system boots into amnesiac mode or rescue mode if HSM is disabled/enabled during vSRX reboot
Product-Group=junos
Severity=Major		On Junos OS vSRX platforms with HSM (Hardware Security Module) integrated, in a race condition, if HSM is disabled/enabled and taking more time (more than 60 Secs) to return failure (retry mechanism before declaring HSM connectivity failure) during vSRX reboot window, the system boots into amnesiac mode or rescue mode (if rescue configuration has been configured by administrator).
PR NumberSynopsisCategory: Security platform jweb support
1766378
Major		J-Web UI cannot be launched
Product-Group=junos
Severity=Major		On all SRX platforms, while displaying the configured login message from Command Line Interface (CLI), the newline characters will be added which results in parsing error. Hence J-Web UI cannot be launched.
1837925
Major		Junos image upload via J-Web fails on select SRX platforms
Product-Group=junos
Severity=Major		On Junos SRX (SRX1500, SRX4600, SRX4100 and SRX5K's) platforms, image upload via J-Web fails with an error "Access Error: 502 -- Bad Gateway".
1851362
Major		Unable to load J-Web after upgrading SRX when time zone is set to GMT+x or GMT-x.
Product-Group=junos
Severity=Major		Due to GMT+x or GMT-x time zone is not supported, J-Web will fail to load after upgrading SRX.
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1820882
Major		Traffic drop is seen in an EVPN multihoming scenario when mac-pinning is enabled
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms, in Ethernet VPN (EVPN) multihoming scenario with mac-pinning enabled, traffic drop will be seen when the Designated Forwarder role (DF) is changed.
PR NumberSynopsisCategory: Label Distribution Protocol
1817712
Major		MPLS LDP sessions are not established when container-lsp is configured with an already existing lsp-template
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms Label Distribution Protocol (LDP) sessions are not formed due to the configuration of "container-lsp" with an already existing configured lsp-template which has "ldp-tunneling" knob enabled.
PR NumberSynopsisCategory: Port-based link layer security services and protocols that a
1656415
Minor		Device could go into amnesiac when commit check fails with macsec config. Coredump could be observed for dot1xd process due to file descriptor leaks.
Product-Group=junos
Severity=Minor		Following issues have been fixed by this PR, 1) Device could go into amnesiac when commit check fails with macsec config. 2) Coredump could be observed for dot1xd process due to file descriptor leaks.
PR NumberSynopsisCategory: MPC10E timing and synchronization
1746541
Major		MPC10E line card crashes when it reboots after FPC firmware upgrade
Product-Group=junos
Severity=Major		On MX240/MX480/MX960 platforms, if Precision time protocol (PTP) is configured, MPC10E line card crashes continuously after FPC firmware upgrade and when MPC10E line card is rebooted. Due to this issue, the clksyncd module also crashes.
1750316
Critical		SyncE stuck in holdover upon PTP slot switchover without change in PTP phase align state
Product-Group=junos
Severity=Critical		SyncE stuck in holdover upon PTP slot switchover without change in PTP phase align state.
1756317
Major		The clksyncd process crashes on backup RE when PTP is deactivated and activated back
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms configured with PTP in Hybrid mode of operation, when PTP is deactivated and activated back, the change of mode from SyncE to Hybrid causes SyncE clock sources in backup RE to reset and FSM timer is restarted. Before expiry of this timer, the SyncE clock sources are qualified in active RE and same is propagated to backup-RE through gencfg and at the expiry of this timer, the configs are checked which is a mismatch and causes clksyncd core. This issue is a rare issue and it is does not cause any functional impact.
1765772
Major		FPC crash will be observed when issuing PIC offline/online commands
Product-Group=junos
Severity=Major		On MX240/MX480/MX960/MX2010/MX2020 platforms with MPC7, 8, 9, 10E, when issuing Physical Interface Cards (PICs) offline/online commands, Flexible PIC Concentrators (FPC) cores will be observed that causes FPCs to be restarted.
PR NumberSynopsisCategory: Track Mt Rainier RE platform software issues
1776854
Major		VM Core with the reason "panic: deadlres_td_sleep_q: possible deadlock detected" might be seen on all JUNOS vmhost platforms
Product-Group=junos
Severity=Major		PR1735843 has fixed a VM core on ACX5448 platform with the reason "panic: deadlres_td_sleep_q: possible deadlock detected". The same issue might also be seen on all other JUNOS vmhost platforms but with a different root cause.
PR NumberSynopsisCategory: OS IPv4/ARP/ICMPv4
1616775
Major		The SNMP packet (traps or polls) will be dropped if it crosses multiple routing-instances on SRX Series devices
Product-Group=junos
Severity=Major		On SRX Series devices, if the SNMP packet (traps or polls) has to cross multiple routing-instances, it will cause the packet to be dropped due to incorrect routing-instance ID added by SRX.
PR NumberSynopsisCategory: FreeBSD Kernel Infrastructure
1592495
Major		Recovery snapshot creation fails due to a lack of storage on the OAM partition
Product-Group=junos
Severity=Major		On EX2300/EX3400/EX2300-48MP platforms, the recovery snapshot creation fails due to a lack of storage on the Operations, Administration, and Management (OAM) partition.
PR NumberSynopsisCategory: JUNOS Network App Infrastructure (for ping, traceroute, etc)
1717843
Critical		JUNOS - FILE COPY - Secure file copy using VRF succeeds even on disabling VRF
Product-Group=junos
Severity=Critical		JUNOS - FILE COPY - Secure file copy using VRF succeeds even on disabling VRF
PR NumberSynopsisCategory: Express Chip L3 software
1826626
Major		Unpoliced sampling traffic causes host congestion and forwarding failure
Product-Group=junos
Severity=Major		On Junos PTX and QFX platforms, unpoliced sampling traffic can cause host path congestion, leading to a failure in forwarding operations. This issue occurs when specific conditions, such as higher rates of sampling classes or smaller packet sizes, are met.
PR NumberSynopsisCategory: QFX L2 PFE
1822251
Major		QFX5100, EX4600, QFX5110, QFX5200, QFX5210 : Traffic is black-holed due to MAC addresses being stuck in hardware
Product-Group=junosvae
Severity=Major		On QFX5100, EX4600, QFX5110, QFX5200, QFX5210 platforms (VC and standalone), MAC address may get into stuck in hardware. As a result, traffic is black-holed.
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1823601
Critical		Protocol traffic drops were seen in the network for any configuration change in the protocol
Product-Group=junos
Severity=Critical		On all Junos QFX5K platforms, with ECMP (Equal Cost Multi Path) configured, when there is any routing protocol change (like ISIS cost metric change), the protocol traffic on the network is dropped.
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1842475
Major		Traffic drops are observed in the EVPN-VxLAN scenario due to VPLAG flaps
Product-Group=junos
Severity=Major		On Junos OS QFX5k and EX4k platforms having EVPN-VxLAN (Ethernet VPN - Virtual Extensible Local Area Network) configured, traffic drops are observed due to missing hardware programming caused by stale hardware entries leading to VTEP (Virtual Tunnel Endpoint) Destination IP-address is not updated properly. The issue is observed due to VPLAG (Virtual Chassis Port Link Aggregation) flaps (any incident, such as a reboot of the gateway device / remote device) causes VPLAG to uninstall and install.
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platform optics related issues
1823771
Major		The SFP 10GBASE-T part No. 740-083295 on platforms running Junos/Junos EVO is unable to detect a linkdown
Product-Group=junos
Severity=Major		On Junos/Junos EVO platforms with the SFP 10GBASE-T part No. 740-083295 Link up/Link down is randomly not detected.
PR NumberSynopsisCategory: Routing Information Protocol
1726028
Major		Neighbor state is down while checking RIPng neighbor information
Product-Group=junos
Severity=Major		When a virtual IP is configured over an IRB interface, IFA having the virtual IP is considered by RIPng and hence an IFA having a non-virtual ip is discarded with the error (errno : Address already in use), which is causing RIPng neighbor state to be down.
PR NumberSynopsisCategory: N/A:sw-riptide-timing
1704633
Major		Interface flaps are seen after PTP GM changes to a different FPC slot
Product-Group=junos
Severity=Major		On MX platforms, when PTP (Precision Time Protocol) is configured, the interfaces will flap after the PTP GM (Grand Master) is changed to a different FPC (Flexible PIC Concentrators) slot. The flaps can last for several seconds. Chassis-SyncE clock is also influenced by PTP phase change.
1755479
Major		CLI output is not correct during SyncE down PTP intact scenario
Product-Group=junos
Severity=Major		On MX240/MX480/MX960 platforms, the CLI output is incorrect when SyncE is down and PTP is intact.
PR NumberSynopsisCategory: KRT Queue issues within RPD
1761667
Major		The rpd process and chassisd process crash is seen
Product-Group=junos
Severity=Major		On Junos and Junos Evolved platforms configuring BGP causes the rpd to crash abnormally and later chassisd crashes too.
1801382
Minor		Memory Leak in the rpd Process During Protocol Deactivation/Activation
Product-Group=junos
Severity=Minor		On all Junos and Junos Evolved platforms, A memory leak occurs during protocol, routing instance, or interface deactivation/activation, linked to improper IPv6 Interface Address (IFA) reference handling in the " ifx_dist_msg " process. This can lead to rpd crashes and service disruptions.
1817807
Major		Routes for secure tunnel interface interface not installed on forwarding-table on SRX platforms
Product-Group=junos
Severity=Major		On all SRX platforms, after the In-Band Cluster (ICU) upgrade if the system has routes pointing to the secure tunnel interface (st0) interface, or on clearing security IPsec sa on peer router a few routes might have trouble getting installed in forwarding, impacting traffic on the routes that are not installed after the upgrade.
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1808463
Major		CPU utilization of the rpd process stays high on all Junos and Junos OS Evolved platforms
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms in a corner case, the Routing Protocol Daemon (rpd) CPU utilization will be seen high in scenarios where recursive route resolution is involved. The rpd process will be continuously spinning in the re-resolution job which could impact scheduling of other jobs and re-resolution of other routes impacting traffic.
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1806694
Major		Junos OS and Junos OS Evolved: On SRv6 enabled devices, an attacker sending a malformed BGP update can cause the rpd to crash (CVE-2025-21593)
Product-Group=junos
Severity=Major		An Improper Control of a Resource Through its Lifetime vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated network-based attacker to cause a Denial-of-Service (DoS). Please refer to https://supportportal.juniper.net/JSA92861 [juniper.net] for more information.
PR NumberSynopsisCategory: Resource Reservation Protocol
1819948
Major		LSP re-optimization issue has been observed
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms, the LSP (Label Switched Path) re-optimization issue has been observed. LSP bandwidth change is unsuccessful due to bandwidth unavailable RSVP (Resource Reservation Protocol) PathErr.
PR NumberSynopsisCategory: N/A:sw-scbe3-timing
1742266
Major		Implement an alarm to notify the system in the "PLL Core Frozen" event
Product-Group=junos
Severity=Major		In a rare occation, an MPC, or an SCB3's hardware clock synchronization PLL module may locked up and not be able to lock on to the clocking signal during holdover, resulting in PTP or SyncE failure. The change in this PR raises a "PLL Core Frozen" major alarm so the system can react to this by raising an alarm, and rebooting the affected MPC, or the SCBE3.
PR NumberSynopsisCategory: Scuba fabric software
1803832
Critical		Traffic blackholing observed due to PFE remaining active despite CM_CMERROR_FABRIC_SELFPING errors
Product-Group=junos
Severity=Critical		On MX2008, MX2010, MX2020 and MX10K platforms with MPC1-9 line cards, the PFE (Packet Forwarding Engine) remains active despite CM_CMERROR_FABRIC_SELFPING errors which leads to a traffic blackholing to that PFE.
PR NumberSynopsisCategory: IPSEC functionality on M/MX/T ser
1801201
Major		IKE is not coming up with dhgroup19 and dhgroup20
Product-Group=junos
Severity=Major		IKE is not coming up with dhgroup19 and dhgroup20. The below Junos releases are impacted. junos:21.2R3-S7 junos:21.4R3-S6 junos:22.1R3-S5 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3-S1 junos:24.1R1. So previous to these releases dhgroup19 and dhgroup20 should be working.
PR NumberSynopsisCategory: SRX branch platforms
1747849
Major		The CLI command "set system processes watchdog '" results in kernel panic
Product-Group=junos
Severity=Major		On SRX-branch series platforms, configuring the "set system processes watchdog " command causes a commit kernel panic i.e. device will get stuck, and traffic loss will be observed. Watchdog related commands are unsupported.
1811858
Major		Monitored-Status keeps Up after CTL link down in branch model SRX HA
Product-Group=junos
Severity=Major		After CTL link down, Monitored-Status in "show chassis cluster interfaces" keeps showing "Up" state.
1836235
Major		SRX default named.conf file is created with non dns-proxy related configuration changes
Product-Group=junos
Severity=Major		On SRX platforms with dns-proxy configured, default named.conf file is created with non dns-proxy related configuration changes. This leads to halting of dns-proxy operation.
1841080
Major		Xe interfaces link down when IP address is assigned
Product-Group=junos
Severity=Major		On SRX380 platforms configured for packet-mode operation and an IP address is assigned to xe (10 Gigabit ethernet) interfaces, the interface link status will go to down state.
PR NumberSynopsisCategory: MPC7E, MPC8E and MPC9E timing and synchronization
1652275
Major		PTP Playback Engine reset error is reported sporadically with PTP FPGA Firmware version A4 7
Product-Group=junos
Severity=Major		On Junos MX platforms, the PTP Playback Engine reset error is reported sporadically with PTP FPGA Firmware version A4 7. It has No functionality impact.
1772138
Major		DUT is sending same source-port-id for two PTP master links connected to downstream node with multiline card scenarios
Product-Group=junos
Severity=Major		On Junos MX240/480/960/2010/2020/2008 Distributed Precision Time Protocol (PTP) platforms, When PTP master/slave/stateful is configured across multiple linecards and allocated with same port-number in the line cards, then the packets generated from both the ports, shall contain the same source-port-id. It shall create Baseboard Management Controller (BMC) issues in G.8275.1 deployment and passive port monitoring deployments.
1806526
Major		Chassis not recovering clock from GM, but still advertisement of GM provided clock-class to downstream node
Product-Group=junos
Severity=Major		On Junos MX platforms, PLL gets frozen because of the Hardware failure but still advertises the GM provided clock-class leading to synchronization failure and potential service impact. This affects clock signals distributed to all devices on the line-card, resulting in service degradation. The issue affects line-cards from MPC3E to MPC10E, chassis with SCBE3, and platforms such as MX10003 and MX204.
1830281
Major		Sourceport-ID comparison resulting in higher value for MPC7E compared to MPC5E for distributed PTP architecture
Product-Group=junos
Severity=Major		SourcePort-ID comparison across line cards between MPC7E and MPC5E/6E/3E-NG/2E-NG shall result in selecting MPC5E/6E/3E-NG/2E-NG compared to MPC7E/8E/9E/10E.
PR NumberSynopsisCategory: SRX-1RU infrastructure SW defects
1839346
Major		After performing ISSU on SRX4600, the SPM is no longer operational
Product-Group=junos
Severity=Major		On SRX4600 platform with chassis cluster, after performing an ISSU (In-service Software Upgrade) upgrade, the SPM (Secure Port Module) (fpc 0) against the node that is upgraded first will experience issue states where it can either cycle through 'Present' or 'Offline', or it will not report any errors but will be unable to perform any PFE (Packet Forwarding Engine) functions such as session management i.e. wont be able to process traffic resulting in traffic impact.
PR NumberSynopsisCategory: SRX-1RU platfom related protocol, QoS, filtering features et
1823577
Major		On SRX4600, in rare cases with heavy traffic, the FPGA may drop packets.
Product-Group=junosvae
Severity=Major		On SRX4600, in rare cases with heavy traffic, the FPGA may drop packets.
PR NumberSynopsisCategory: N/A:sw-taz-timing
1800134
Major		Clksyncd core dump observed when performing snmp mib walk
Product-Group=junos
Severity=Major		On Junos MX80 platform, post upgrade to 21.2R3-S6.11 from 21.2R3-S4.8, when snmp mib walk is done clksyncd core dump can be seen, however there is no service impact due to this issue.
PR NumberSynopsisCategory: ZT/YT pfe qos software issues
1793375
Critical		CMErrors are observed on MX platforms running MPC10/MPC11 causing the PFE to be disabled
Product-Group=junos
Severity=Critical		On all MX platforms having MPC10 or MPC11 having class-of-service configured, it is observed that in a scaled scenario (1500 IFLs (Interface Logical)), when queues are oversubscribed and the output interface starts to get congested, "CMERROR 0x230063 " or "XQSS_CMERROR_SCHED_QL4_INT_REG_DQU_QSUM_UDR" error message is seen. These cm errors would result in PFE (Packet Forwarding Engine) disable or the action configured in the device.
PR NumberSynopsisCategory: ZT/YT pfe firewall software
1795940
Major		The ARP resolution will fail on the interface when the default ARP policer fails to program.
Product-Group=junos
Severity=Major		On AFT(Advanced Forwarding Toolkit) based MX platforms, default ARP(Address Resolution Protocol) policer fails because of which ARP resolution fails on the interface and hence the traffic gets impacted.
PR NumberSynopsisCategory: ZT/YT pfe l3 forwarding issues
1803578
Major		MPLSoUDP route issue preventing LSP establishment
Product-Group=junos
Severity=Major		On all MX platforms, the discrepancy is seen when attempting to establish LSP (Label Switched Paths) using MPLSoUDP (MPLS over UPD) routes due to the mishandling of IP options during tunnel processing.
PR NumberSynopsisCategory: Trio pfe l3 forwarding issues
1816378
Major		XQSS_CMERROR errors will be seen which might disable PFE
Product-Group=junos
Severity=Major		On MX204, MX10003 and MX platforms with MPC7, MPC8, MPC9, LC480, LC2101, LC2103, MPC10 and MPC11 line cards or EX92xx platforms with EX9200-40XS, EX9200-12QS, EX9253-6Q12C, EX9253-6Q12C-M line cards, SRX5400, SRX5600, SRX5800 platforms with SRX5K-IOC4-10G, SRX5K-IOC4-MRAT line cards, in a scenario where there could be fabric drops because of over-subscription or CRC errors, there could be case when the same tail entry get re-used across packets leading to packet corruption and CM error. This is a corner case and might lead to PFE(Packet Forwarding Engine) disable resulting in traffic loss.
PR NumberSynopsisCategory: Authentication, Authorization, Accounting, PAM (RADIUS/tacplus)
1802329
Major		Multiple Products: RADIUS protocol susceptible to forgery attacks (Blast-RADIUS) (CVE-2024-3596)
Product-Group=junos
Severity=Major		An Authentication Bypass by Spoofing vulnerability in the RADIUS protocol of Juniper Networks Junos OS and Junos OS Evolved platforms allows an on-path attacker between a RADIUS server and a RADIUS client to bypass authentication when RADIUS authentication is in use. Please refer to https://supportportal.juniper.net/JSA88210 [juniper.net] for more information.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1636085
Major		MTU configuration on an interface is not set as expected
Product-Group=junos
Severity=Major		On all Junos with persist-groups disabled ( on Junos persist-groups feature is enabled by default 19.4 onwards) and on EVO platforms where persist groups can be disabled (21.4R1 onwards persist-groups cannot be disabled on EVO) this issue can be seen. This issue occurs when grafting happens during configuration expansion (when persist-groups is disabled) and a configuration such as a customer configuration is applied( for example, a configuration in which MTU is inherited from a groups configuration).
1645119
Critical		Junos OS and Junos OS Evolved: Confidential information in logs can be accessed by another user (CVE-2024-39532)
Product-Group=junos
Severity=Critical		An Insertion of Sensitive Information into Log File vulnerability in Juniper Networks Junos OS and Junos OS Evolved allows a local, authenticated attacker with high privileges to access sensitive information. Please refer to https://supportportal.juniper.net/JSA82992 [juniper.net] for more information.
1799215
Major		The commit fails error can be seen when configuration is modified after commit prepare
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms, when the user attempts to issue the commit command after modifying the configuration post 'commit prepare', the commit discards the prepared commit cache as it is no longer valid and throws " commit fails" error and proceeds with the regular commit process from scratch.
PR NumberSynopsisCategory: MX10K linecard
1809511
Major		Ethernet interfaces configured with loopback option remains down after multiple iteration of line card boot is performed
Product-Group=junos
Severity=Major		On MX platforms with LC2101 line cards and 10-gigabit ethernet interfaces configured in loopback mode, when Line card is booted multiple times, the ethernet interfaces on line card remains down and traffic on those interfaces will be impacted.
PR NumberSynopsisCategory: usf flow and datapath issue on SPC3
1841859
Major		Due to high bursty traffic, PIC on MX-SPC3 might go down.
Product-Group=junos
Severity=Major		On all MX Junos devices with SPC3, on receiving bursty traffic PIC may go down and cause network disruption.

 

 

21.4R3-S10 - List of Known issues 

PR NumberSynopsisCategory: EX4300 PFE
1849492
Major		VSTP BPDU are not properly processed by EX4300 when the interface is configured in SP style
Product-Group=junos		VSTP BPDU are not properly processed by EX4300 when the interface is configured in SP style causing VSTP not to converge

Resolved In: junos:21.4R3-S10
PR NumberSynopsisCategory: MPC10/11/LC9600 Chassis Category
1752654
Major		Voltage Threshold Crossed message observed on all Junos OS Evolved platforms
Product-Group=junos		On all Junos OS Evolved platforms and device with MX10K-LC2301/ MX10K-LC9600, MX304, LC480, LC2101, LC1201 the voltage threshold cross is reported by MX20796 sensor.

Resolved In: evo:21.4R3-S10-EVO junos:22.4R3
PR NumberSynopsisCategory: PFE issue for flowd on australia SPU
1726888
Major		SNMP MIB walk for ipSystemStatsTable takes a long time to dump the output
Product-Group=junos		When polling ip SystemStatsTable, the responses have noticable delay

Resolved In: junos:20.4R3-S10 junos:21.2R3-S8 junos:21.4R3-S6 junos:22.1R3-S5 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:23.2R2 junos:23.4R1 junos:24.1R1
PR NumberSynopsisCategory: the replication daemon (repd) for Shared Memory-base
1797189
Major		We may observe repd core (in the "from" release) during ISSU. There are no functional impact due to this repd core
Product-Group=junos		On all Junos and Junos Evolved platforms, repd core observed (in the "from" release) during ISSU.

Resolved In: evo:23.4R2-S4-EVO evo:24.2R2-EVO evo:24.3R1-EVO junos:22.4R3-S6 junos:23.4R2 junos:24.2R1 junos:24.2R2 junos:24.3R1
PR NumberSynopsisCategory: Border Gateway Protocol
1699633
Major		The BGP graceful-shutdown community is not advertised on Junos/Junos Evolved platforms
Product-Group=junos		On Junos and Junos Evolved platforms configured with graceful-shutdown sender under the BGP(Border Gateway Protocol) dynamic neighborship, the peer device does not receive routes with communities "graceful-shutdown", as it is not advertised by the sender causing the traffic drop for the affected routes.

Resolved In: evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
1719498
Major		In MPLS L3VPN-BGP multipath scenario route calculation or recalculation causes the rpd process to crash
Product-Group=junos		On all Junos and Junos Evolved platforms, memory leak is observed in Multi-protocol Label Switching (MPLS) Layer3 and labelled routes scenario when Border Gateway Protocol (BGP) with multipath is configured. Multiple route changes and deletion overtime that triggers this memory leak can lead the rpd to run out of memory causing the rpd process to crash.

Resolved In: evo:21.4R3-S4-EVO evo:22.1R3-S3-EVO evo:22.2R3-S1-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.3X80-D38-EVO evo:22.3X80-D39-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:21.4R3-S2-J16 junos:21.4R3-S2-J22 junos:21.4R3-S4 junos:21.4R3-S5 junos:21.4R3-S6 junos:22.1R3-S3 junos:22.2R3-J7 junos:22.2R3-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:22.4R3-S1 junos:23.1R2 junos:23.2R1 junos:23.3R1 junos:24.2R2
1737679
Major		The rpd crash files are seen due to a use-after free of objects
Product-Group=junos		On all Junos and Junos Evolved platforms, due to a use-after free of objects that are being shared across threads for tracing that happened when some assumptions were broken in a recent fix. The crash files generated in rare conditions when the object is freed prior to when the trace is cut.

Resolved In: evo:22.2R3-S3-EVO evo:22.3X50-EVO evo:22.3X80-D43-EVO evo:22.3X80-D44-EVO evo:22.4R3-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:20.3X75-D441 junos:21.2R3-S9 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:23.2R1-S1-J7 junos:23.2R2 junos:23.2R2-J14 junos:23.3R1 junos:23.4R1
1788543
Major		BGP OutQ counter of one of the BGP peers gets stuck after system reboot/restart routing/clear bgp neighbor
Product-Group=junos		On all Junos and Junos Evolved platforms, when there is a high route churn and the system reboot/restart routing/clear bgp neighbor is done, there are some values stuck in the OutQ counter of one of the peers in a group. Due to this, the route updates are not sent which might result in traffic/service impact.

Resolved In: evo:22.3X50-EVO evo:23.4R2-S3-EVO evo:23.4R2-S4-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:21.2R3-S9 junos:23.4R2-S3 junos:23.4R2-S4 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: Issues related to Common BIOS on x86 based designs
1608045
Major		The TSC_DEADLINE disabled error logs are observed on Junos vmhost platforms after upgrade
Product-Group=junos

Resolved In: junos:22.2R3-S3 junos:23.4R2 junos:24.2R1 junos:24.2R2 junos:24.3R1
PR NumberSynopsisCategory: MX Platform SW - FRU Management
1816912
Major		IIC access error during commit operation cause false positive alarms in devices
Product-Group=junos		On Junos platforms, RE detects IIC read or write failures and triggers a minor alarm " RE1 IIC access alarm" during commit operations

Resolved In: junos:21.2R3-S9 junos:22.4R3-S6 junos:23.2R2-S3 junos:23.4R2-S4 junos:24.2R2 junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: Device Configuration Daemon
1725168
Major		Traffic impact will be seen with mismatched speeds on the LAG interface and member interface
Product-Group=junos		On all Junos platforms, if a speed mismatch happens in the LAG (Link Aggregation) & member interface then a traffic drop will be seen.

Resolved In: junos:22.2R3-S4 junos:22.4R3-S1 junos:23.2R2 junos:23.4R1
PR NumberSynopsisCategory: All issues related to PFE Resiliency for ACX7K products
1823195
Major		Network Protocol Outage on ACX Junos platforms due to SER of Memory ECC Parity Errors
Product-Group=junos		On Junos ACX710/ACX5448 platforms, the protocols like BGP/ISIS/OSPF/LACP/BFD etc. will go down due to Soft Error Recovery (SER) of memory ECC parity error. The impact will be malfunction on critical memory.

Resolved In: junos:24.2R2 junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: Distributor related issues
1836997
Major		The rpdagent process is getting restarted after switchover
Product-Group=junos		On Junos OS Evolved platforms, a rare race condition can cause a previously added state on master before switchover to arrive late on the new master and after switchover rpdagent restarts which results into traffic loss.

Resolved In: evo:23.4R2-S4-EVO evo:24.2R2-EVO evo:24.4R1-EVO evo:25.1R1-EVO junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: EVPN control plane issues
1796532
Major		EVPN mac-ip entry flag "Duplicate-Not-Best" not updated after deleting duplicated IRB IP in EVPN_VXLAN MAC-VRF
Product-Group=junos		On all Junos and Junos Evolved platforms, duplicate mac-ip detection for IRB IP is not working since the IP move is not triggered after adding an IP address to the IRB interface.

Resolved In: evo:23.4R2-S4-EVO evo:23.4X100-D30-EVO evo:24.2R1-EVO evo:24.3R1-EVO junos:23.4R2-S4 junos:24.2R1 junos:24.3R1
PR NumberSynopsisCategory: EX4100 PFE
1846286
Major		The error message will be seen on EX4100 platforms when deactivating/activating IRB interfaces
Product-Group=junos		On EX4100 platforms, When deactivating/activating IRB interfaces on vlans with vni enabled, error message will be observed.

Resolved In: junos:22.2R3-S6 junos:22.4R3-S6 junos:24.2R2 junos:24.4R1 junos:24.4R2 junos:25.1R1
PR NumberSynopsisCategory: EX interfaces issues
1580560
Major		On EX2300, EX3400, :EX4300-48MP and EX4300 , Pause frames counters does not get incremented when pause frames are sent.
Product-Group=junos		On EX2300, EX3400, :EX4300-48MP and EX4300 , Pause frames counters does not get incremented when pause frames are sent.

Resolved In:
1789999
Major		[interfaces]:Ex-Hardening:Local/Remote fault insertion from TG is failing
Product-Group=junos		Ex-Hardening:Local/Remote fault insertion from TG is failing

Resolved In:
1823688
Major		EX4400: In some instances, after a dc-pfe process restart in a VC environment, one or more interfaces do not get created
Product-Group=junos		On a working VC system, if there happens a dc-pfe process restart for any reasons, then there is a possibility of some interfaces not getting created after the dc-pfe restart.

Resolved In:
PR NumberSynopsisCategory: EX4400 PFE software
1854253
Major		Devices fail to obtain an IP address when DHCP Security Option 82 is enabled
Product-Group=junos		On Junos EX and QFX platforms when DHCP (Dynamic Host Configuration Protocol) option 82 settings are enabled under dhcp-security, hosts fail to get an IP address from the DHCP server.

Resolved In: junos:22.2R3-S6 junos:22.4R3-S6 junos:23.4R2-S4 junos:24.2R2 junos:24.4R1-S2 junos:24.4R2 junos:25.1R1
PR NumberSynopsisCategory: Express PFE Services including JTI, TOE, HostPath, Jflow
1830575
Major		The dcpfe crashes when ukern_trace handle buffer size is set to 10000
Product-Group=junos		On all Junos platforms, the dcpfe crash is seen with a core-dcpfe dump when the ukern_trace handle buffer size is set to 10000. It is a rare issue.

Resolved In: junos:21.2R3-S9 junos:22.2R3-S6 junos:22.4R3-S5 junos:23.2R2-S3 junos:23.4R2-S4 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: MX10K LC2101 Timing
1664569
Major		Switch Fabric Board information for supporting PTP on MX10k8 with MX10K-LC2101 LC(s)
Product-Group=junos		MX10k8 with MX10K-LC2101 Linecard(s) supports *PTP* only with JNP10008-SF Switch Fabric Board(s), *PTP* currently doesn't work with JNP10008-SF2 Switch Fabric Board(s).

Resolved In: evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:20.4R3-S8 junos:21.2R3-S6 junos:22.1R3-S5 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: BSDX Software installation issues
1713187
Major		JSU: request system software delete reboot does not trigger a reboot
Product-Group=junos		On all Junos platforms, request system software delete reboot does not trigger a reboot. The JSU functionality is working and JSU package is getting deleted as excepted. Manual reboot is required.

Resolved In: junos:23.2R2 junos:23.3R1 junos:23.4R1
PR NumberSynopsisCategory: ISIS routing protocol
1841108
Major		Traffic drop is seen after GRES on ISIS peer
Product-Group=junos		On all Junos and Junos OS Evolved platforms, in an ISIS(Intermediate System-Intermediate System) graceful restart scenario, helper node sends and programs its locally configured hold-time (180 secs) instead of the "Restart-duration" received as hold-time from DUT (210 secs), due to this incorrect update, the hold timer expires at the helper node before the GR (Graceful Restart) is complete on DUT and it causes a flap of ISIS adjacency on peer/helper Node.

Resolved In: evo:21.4R3-S10-EVO evo:22.3X80-D47-EVO evo:22.4R3-S6-EVO evo:23.2R2-S3-EVO evo:23.4R2-S4-EVO evo:24.2R2-EVO evo:24.4R1-EVO evo:25.1R1-EVO junos:22.4R3-S6 junos:24.2R2 junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: jdhcpd daemon
1776451
Major		DHCP clients not receiving IP address
Product-Group=junos		On all Junos platforms, When client is configured on IRB(Integrated Routing and Bridging) and relay is in RI(Routing Instance), then DHCP(Dynamic Host Configuration Protocol.) clients will not receive the IP address because of which traffic drop will be seen.

Resolved In: junos:23.4R2 junos:24.2R1 junos:24.3R1
PR NumberSynopsisCategory: Flow Module
1839910
Major		On SRX5800, SRX4700 and SRX4600 flowd crash is detected during PIM register packet processing
Product-Group=junos		The SRX5800, SRX4700 and SRX4600 platforms encounters a flowd crash issue when processing PIM (Protocol Independent Multicast) register packets under specific multicast topologies. The issue disrupts data plane traffic temporarily but recovers after a flowd reboot.

Resolved In: junos:21.2R3-S9 junos:22.4R3-S6 junos:23.4R2-S4 junos:24.2R2 junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: Firewall Policy
1838698
Major		Security flow sessions are impacted during ISSU on SRX platforms
Product-Group=junos		On Junos SRX platforms configured as chassis clusters, while performing ISSU (In-Service Software Upgrade), when the secondary node is being upgraded, synchronization between primary and secondary nodes is concluded without completion. Due to this, the security session flows are impacted when the secondary node takes over primary role and polices are realised and pushed to PFE (Packet Forwarding Engine).

Resolved In: junos:24.2R2 junos:24.4R2 junos:25.1R1
PR NumberSynopsisCategory: IPSEC/IKE VPN
1665506
Major		Master-encryption-password is not accessible when system is in FIPS mode
Product-Group=junos		On all SRX 345 and SRX380 that have TPM1.2 support enabled in FIPS mode master-encryption-password is will not be accessible.

Resolved In: junos:22.2R2 junos:22.2R3 junos:22.3R1 junos:22.3R2 junos:22.4R1
1818197
Major		The srxpfe process will crash due to memory buffer corruption if the outgoing interface of the IPsec VPN peer goes down and the default route points to st0
Product-Group=junos		On SRX platforms, if the outgoing interface of the Internet Protocol Security (IPsec) Virtual Private Network (VPN) peer goes down when the peer device operates in the Network Address Translation-Traversal (NAT-T) environment and the default route points to the secure tunnel interface (st0), there are chances of an internal routing loop which will lead a srxpfe process crash caused by the Memory Buffer (mbuf) corruption.

Resolved In: junos:22.4R3-S5 junos:23.2R2-S3 junos:23.4R2-S4 junos:24.2R2 junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: Label Distribution Protocol
1817712
Major		MPLS LDP sessions are not established when container-lsp is configured with an already existing lsp-template
Product-Group=junos		On all Junos and Junos Evolved platforms Label Distribution Protocol (LDP) sessions are not formed due to the configuration of "container-lsp" with an already existing configured lsp-template which has "ldp-tunneling" knob enabled.

Resolved In: evo:21.4R3-S10-EVO evo:22.4R3-S5-EVO evo:23.4R2-S4-EVO evo:24.2R2-EVO evo:24.4R1-EVO junos:22.4R3-S5 junos:22.4R3-S7 junos:23.4R2-S4 junos:24.2R2 junos:24.4R1
PR NumberSynopsisCategory: Issues related to Junos licensing infrastructure
1545175
Critical		Intermittent license-check.core observed
Product-Group=junos		Intermittent license-check.core observed during the device initialization. License daemon will restart and start providing the required support. There is no service impact.

Resolved In:
PR NumberSynopsisCategory: lldp sw on MX platform
1811545
Major		The LLDP neighborship does not recover on AE interfaces
Product-Group=junos		When LLDP is configured on interface all and there are AE interfaces configured, to disable LLDP on one of the AE "set protocols lldp interface is done". To enable it back when rollback is done for reverting disable config, AE is not participating in LLDP neighborship and this happening because PFE stopped sending packets to control plane because on rollback L2CPD did not sent LLDP ENABLE for its child interface to PFE and LLDP on child interface was still set to disabled for PFE.

Resolved In: evo:22.3X50-EVO evo:22.4R3-S6-EVO evo:23.2R2-S3-EVO evo:23.4R2-EVO evo:24.2R1-S2-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:21.2R3-S7-J17 junos:21.2R3-S8-J2 junos:22.4R3-S6 junos:23.2R2-S3 junos:23.4R2-S4 junos:24.2R1-S2 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: MPC10E timing and synchronization
1750885
Major		MPC10E: Support of G.8275.1 PTP Hybrid mode with speed 25G and 400G
Product-Group=junos		In 21.2R3S6 release, MPC10E line-card does not support of G.8275.1 PTP Hybrid mode with speed 25G and 400G

Resolved In: evo:23.4R1-EVO evo:24.1R1-EVO junos:21.2R3-S7 junos:22.2R3-S3 junos:22.4R3-S2 junos:23.2R2 junos:23.4R1 junos:24.1R1
PR NumberSynopsisCategory: MPC11 ULC fabric software related issues.
1827058
Major		The PFE gets disabled due to large number of fabric self ping errors
Product-Group=junos		On MX platforms with MPC11E and LC9600 and MX304, when multiple fabric self ping errors and timeouts are seen, device attempts to recover by performing port bounces at fabric end. But when there are large number of self ping errors and timeouts are seen which require more than 256 port bounces, the affected PFE(Packet Forwarding Engine) will get disabled resulting in traffic loss.

Resolved In: evo:24.2R2-EVO evo:24.4R1-EVO junos:23.4R2-S4 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: MPC11 ULC fabric software related issues.
1798780
Critical		The system goes into a bad state when an SFB ungraceful offline happens due to a fatal Interrupt
Product-Group=junos		On MX platforms with SFB, in case of a fatal error encountered during SFB reboot ( due to hardware issue or ungrateful power restart ), SPMB will try to offline this SFB during bootup. At the same time, the system is busy training the fabric links to begin it online. This may cause a system-wide traffic impact due to the fabric not being consistent.

Resolved In: junos:21.2R3-S9 junos:23.2R2-S2 junos:23.4R2-S3 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: Multiprotocol Label Switching
1694648
Major		The rpd process crashes during the MPLS label block allocation
Product-Group=junos		On all Junos and Junos Evolved platforms in the MPLS scenario, the rpd process crashes in rare conditions during MPLS label block allocation.

Resolved In: evo:20.4R3-S6-EVO evo:21.2R3-S4-EVO evo:21.4R3-S3-EVO evo:22.1R3-S1-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:20.2R3-S7 junos:20.3X75-D36 junos:20.3X75-D44 junos:20.3X75-D46 junos:20.3X75-D52 junos:20.4R3-S6 junos:21.1R3-S5 junos:21.2R3-S4 junos:21.4R3-S3 junos:22.1R3-S1 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R2 junos:23.1R1
1738774
Critical		Traffic blackhole due to an additional label when CCNH is toggled
Product-Group=junos		On all Junos and Junos Evolved platforms, with scaled Border Gateway Protocol (BGP) routes, when Chained Composite Next Hops (CCNH) is toggled, a few next-hops end up creating additional labels causing a traffic blackhole.

Resolved In: evo:21.4R3-S5-EVO evo:22.3X50-EVO evo:22.3X80-D36-EVO evo:22.3X80-D38-EVO evo:22.3X80-D42-EVO evo:22.3X80-D43-EVO evo:22.3X80-D45-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:21.2R3-S4-J27 junos:21.2R3-S6 junos:21.4R3-S5 junos:22.2R3-S3 junos:22.4R2-S2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1 junos:23.4R1 junos:24.2R2
PR NumberSynopsisCategory: MX10K platform
1674322
Major		SNMP traps "Power Supply failed" and "Power Supply OK" are not generated
Product-Group=junos		On all Junos MX10k and PTX10k platforms, when a PSU with no feeds connected, but the DIP switch at the back of the PSU is set in a position where it expects the feeds to be connected, then POWER FAILED TRAPs might not get generated as expected.

Resolved In: evo:22.1R3-EVO evo:22.2R2-EVO evo:22.3R2-EVO evo:22.4R1-EVO junos:20.3X75-D36 junos:20.4R3-S5 junos:21.2R3-S6 junos:22.1R3 junos:22.2R2 junos:22.3R2 junos:22.4R1 junos:23.1R1
PR NumberSynopsisCategory: Protocol Independant Multicast
1767314
Major		RPD may restart unexpectedly when MSDP peers were reset or closed
Product-Group=junos		When an MSDP peer is terminated, the peer's information may not be cleaned up properly. Causing the RPD process to restart unexpectedly.

Resolved In: evo:22.4R3-S6-EVO evo:23.2R2-S1-EVO evo:23.4R2-EVO evo:24.1R1-EVO junos:21.2R3-S9 junos:22.4R3-S1 junos:22.4R3-S6 junos:23.2R2-S1 junos:23.4R2 junos:24.1R1 junos:24.2R1
PR NumberSynopsisCategory: Issues related to PKI daemon
1845573
Major		Auto-re-enrollment for local certificate once fail, not trigger again on SRX platforms
Product-Group=junos		Added missing syslog messages for SCEP and CMPv2 certificate enrolment failure.

Resolved In: junos:23.4R2-S4 junos:24.2R2 junos:24.4R1-S2 junos:24.4R2 junos:25.1R1
PR NumberSynopsisCategory: vMX Platform Infrastructure related issue tracking
1729152
Major		The FPC crash or flap in protocols will be seen as soon as port-mirroring or firewall filters with syslog action is enabled
Product-Group=junos		On MX150 platform, when port-mirroring or firewall with syslog configuration is enabled, there will be a memory leak which will cause depletion of buffer memory which will lead to flap in the protocols or the (Flexible PIC Concentrators) FPC crash. This will impact the traffic.

Resolved In: junos:19.1R3-S12 junos:19.2R3-S9 junos:19.3R3-S11 junos:19.4R3-S14 junos:20.2R3-S9 junos:20.3X75-D36 junos:20.3X75-D440 junos:20.3X75-D46 junos:20.3X75-D52 junos:21.2R3-S9 junos:21.2X32-D30 junos:21.4R3-S7 junos:22.2R3-S4 junos:22.3R3-S3 junos:22.4R3-S2 junos:22.4R3-S3 junos:23.2R2-S1 junos:23.4R1-S2 junos:23.4R2 junos:24.2R1 junos:24.3R1
PR NumberSynopsisCategory: PTX10K Routing Engine
1770585
Major		Junos vmhost upgrade will continue to reboot the box even if the upgrade has failed due to tar errors when the reboot option is used
Product-Group=junos		Issue identified when upgrading vmhost, but applies to all Junos platforms that support vmhost. When there are tar errors during the upgrade, and the reboot option is used in the upgrade command, the machine will still reboot the RE despite that the upgrade was not completed correctly. This will break the routing engine. It is necessary to stop the reboot, if error or tar problems occurred during the upgrade.

Resolved In: junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: QFX L2 PFE
1820830
Major		Complete packet loss will be observed for the inter-VLAN traffic in EVPN-VXLAN CRB scenario
Product-Group=junosvae		On Junos QFX and EX platforms in an EVPN-VXLAN (Extended Virtual Private Network- Virtual Extensible LAN) CRB (Centrally-Routed Bridging) scenario where the ingress leaf switch is configured with ESI (Ethernet Segment Identifier) lags (i.e. the server is multihomed), if there is an overlap between ESI lag(s) trunk ID with physical port number(s) and overlap of DMAC (destination MAC) between VGA (Virtual Gateway Address) MAC address 00:00:5e:00:01:01 (CRB setup with VGA / GW is on spine) with VRRP (Virtual Router Redundancy Protocol) MAC (specifically for the VRRP group 1 MAC address 00:00:5e:00:01:01) on the physical ports of the Leaf switches, then traffic loss will be observed for the inter-VLAN traffic.

Resolved In: junos:23.4R2-S4 junos:24.4R2 junos:25.1R1
PR NumberSynopsisCategory: QFX10008/16 QFX10002 Ultimat/Elit platform related issues -
1833154
Major		FPC crashed with "Last Reboot Reason: CPU Watchdog Reset"
Product-Group=junosvae		On all Junos QFX10008, QFX10016 platforms, the FPC (Flexible PIC Concentrator) crashed with the reboot reason CPU Watchdog Reset due to the system placing the PCI (Peripheral Component Interconnect) bridge port into a low-power state.

Resolved In: junos:22.4R3-S6 junos:24.2R2 junos:24.4R1 junos:24.4R2 junos:25.1R1
PR NumberSynopsisCategory: QFX5K Timing software
1848071
Major		The PTP BC is not working and stays in 'FREERUN' state.
Product-Group=junos		The PTP BC is not working and stays in 'FREERUN' state. PTP slave is not locking to upstream master.

Resolved In: junos:24.2R2
PR NumberSynopsisCategory: KRT Queue issues within RPD
1805427
Minor		The rpd process crashes during rpd restart on Junos and Junos Evolved platforms
Product-Group=junos		On all Junos platforms, due to timing issue during the restart of the rpd process may cause it to crash. This can temporarily impacts traffic until the process recovers.

Resolved In: evo:22.4R3-S5-EVO evo:23.2R2-S3-EVO evo:23.4R2-S4-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:21.4R3-S9 junos:22.4R3-S5 junos:23.2R2-S3 junos:23.4R2-S4 junos:24.2R1 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1771344
Major		Leaked routes via BGP rib-group remains in hidden state even though "loops" is configured with any value greater than one
Product-Group=junos		On all Junos and Junos Evolved platforms having BGP (Border Gateway protocol) configured, when route is leaked via rib-group from one routing instance to another having the same AS (Autonomous System) number and one of the routing-instances has BGP configured with local-as, it is observed that even after configuring "loops" with any value greater than one as the number of loops option, the route still remains hidden instead of being active which results in traffic drop.

Resolved In: evo:23.4R2-S4-EVO evo:24.2R2-EVO evo:24.4R1-EVO evo:25.2R1-EVO junos:23.4R2-S4 junos:24.2R2 junos:24.3R1 junos:24.4R1
1842654
Major		RPD process crash observed with dynamic tunnel configuration with overlap in destination networks under APP based and NHB mode and rollback
Product-Group=junos		On all Junos and Junos OS Evolved platforms the rpd (Routing Protocol Daemon) process will crash when dynamic tunnels are configured with overlap in destination networks under APP (Application-based tunnels) based and NHB (Next Hop Based) mode and rollback after some time.

Resolved In: evo:23.4R2-S4-EVO evo:24.2R2-EVO evo:24.4R2-EVO evo:25.1R1-EVO junos:21.4R3-S3-J16 junos:22.4R2-S2-J9 junos:23.4R2-S4 junos:24.2R2 junos:24.4R2 junos:25.1R1
PR NumberSynopsisCategory: PTX10K specific platform PRs
1766097
Major		PTX10008: When NSR Enabled and FMBB Knobs are configured and if SIB is Offline/Online casue resiliencyd core
Product-Group=junos		PTX10008: When NSR Enabled and FMBB Knobs are configured and if SIB is Offline/Online casue resiliencyd core

Resolved In: evo:21.4R3-S7-EVO evo:22.2R3-S4-EVO evo:22.4R3-S2-EVO evo:23.4R2-EVO evo:24.1R1-EVO evo:24.2R1-EVO junos:22.1R3-S6 junos:22.2R3-S4 junos:22.3R3-S3 junos:22.4R3-S2 junos:23.4R2 junos:24.1R1 junos:24.2R1
PR NumberSynopsisCategory: SNMP Infrastructure (snmpd, mib2d)
1734549
Major		Syslog messages modification for SNMPv3 authentication failure
Product-Group=junos		On all Junos and Junos Evolved platforms, a cosmetic change was made to an existing syslog message to print more information. The syslog error message that is logged when a user with wrong auth/privacy password sends a SNMP v3 request to router has been changed to add more information. From: LIBJSNMP_NS_LOG_WARNING: WARNING: Authentication failed for To: LIBJSNMP_NS_LOG_WARNING: WARNING: Authentication failed for , SNMPv3 query from to 

Resolved In: evo:22.3X50-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:21.2R3-S9 junos:22.1R3-S6 junos:22.4R2-S1 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1 junos:23.4R1
PR NumberSynopsisCategory: MPC7E, MPC8E and MPC9E timing and synchronization
1803105
Major		PTP attribute changes on upstream device causes best clock master slot switchover
Product-Group=junos		On all MX platforms(except MX80) with multi line card chassis, when PTP slave or stateful streams are configured across multiple linecards with clock from same PTP time provider and the announce msg parameters changes from the upstream device, the best master clock (BMC) slot switchover is observed and is restored back within few seconds. Although the slot time interval is very less, it can still lead to major impact as the active PTP slot and clock path is switched over and results in re-routing of the clocks.

Resolved In: evo:24.4R1-EVO evo:25.1R1-EVO junos:24.4R1 junos:24.4R2 junos:25.1R1
PR NumberSynopsisCategory: ZT/YT LUSS SW driver
1765394
Major		Fatal(MQSS and XQSS errors) error on FPC leads to PIC card offline and traffic impact
Product-Group=junos		On Junos MX304 and MX platforms with LC9600 linecards, With the current error handling mechanism upon receiving fatal error on Flexible pic concentrators(FPC), leads to disable both the Packet Forwarding Engine(PFE) on a Physical Interface Cards(PIC) card and seen traffic impact.

Resolved In: evo:24.1R1-EVO junos:23.4R2-S4 junos:24.1R1
PR NumberSynopsisCategory: Trio pfe l3 forwarding issues
1813253
Major		Memory issue seen with syslog/log in firewall terms
Product-Group=junos		On all Junos MX150 platforms, firewall terms with syslog or logging may cause an mbuf (memory buffer) memory leak, resulting in an FPC crash.

Resolved In: evo:25.1R1-EVO junos:22.2R3-S6 junos:24.2R1-S2 junos:24.2R2 junos:25.1R1
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=junos		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
1708321
Critical		Device goes to amnesiac state on configuring dynamic-profiles followed by reboot
Product-Group=junos		On Junos platforms, when a toggle attribute is defined in dynamic-profiles with variable, the system goes to amnesiac mode upon reboot and thus causes traffic loss.

Resolved In: evo:21.4R3-S3-EVO evo:22.2R2-J4-EVO evo:22.2R2-J6-EVO evo:22.2R2-S2-J1-EVO evo:22.2R2-S2-J2-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R1-S2-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:20.4R3-S7 junos:21.4R3-S3 junos:22.1R3-S2 junos:22.2R2-S2 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R1-S2 junos:22.4R2 junos:23.1R1 junos:23.1R2 junos:23.2R1
1821845
Major		The system scripts refresh will fail when using load CLI option
Product-Group=junos		On all Junos and Junos OS Evolved platforms when the 'edit system scripts' hierarchy configuration is changed using loading a configuration from a file or the terminal using 'load' option, the scripts refresh will fail.

Resolved In: evo:22.4R0-J0-EVO evo:23.2R2-S2-EVO evo:23.4R2-S1-EVO evo:23.4R2-S2-EVO evo:23.4X31-EVO evo:24.2R1-S1-EVO evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:22.4R3-S4 junos:23.2R2-S2 junos:23.4R2-S1 junos:24.2R1-S1 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: Issues related to NETCONF
1585855
Critical		< ok/> response is getting generated along with < rpc-error>
Product-Group=junos		When maximum-password-length is configured and the user tries to configure password whose length exceeds configured maximum-password-length, there is an error and the '' tag is emitted. (Ideally '' tag should not be emitted in an error scenario.) The configuration does not get committed.

Resolved In: evo:22.2R3-S1-EVO evo:22.3R2-S2-EVO evo:22.3X50-EVO evo:22.3X80-D43-EVO evo:22.3X80-D44-EVO evo:22.4R3-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:20.3X75-D36 junos:22.1R3-S6 junos:22.2R3-S1 junos:22.3R2-S2 junos:22.3R3-S1 junos:22.4R2-S2 junos:22.4R3 junos:23.1R1 junos:23.2R1 junos:23.4R2
1709056
Major		Unable to upgrade Junos using NetConf or Junos script
Product-Group=junos		On all Junos and Junos OS Evolved platforms, if RPC get-configuration is invoked before RPC request-package-add in the same session of the NETCONF or Junos script, RPC request-package-add will not work.

Resolved In: evo:22.1R3-S3-EVO evo:22.2R2-S2-J2-EVO evo:22.2R2-S2-J3-EVO evo:22.2R3-S1-EVO evo:22.3R2-J1-EVO evo:22.3R2-J2-EVO evo:22.3R2-S1-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.3X80-D43-EVO evo:22.4R1-S2-J3-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:21.4R3-S4 junos:22.1R3-S3 junos:22.2R3-S1 junos:22.3R2-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1-S1 junos:23.1R2 junos:23.2R1 junos:23.3R1
1796297
Major		Error message not prompted on commit confirmed RPC sent in private mode on all Junos and Junos Evolved platforms
Product-Group=junos		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.

Resolved In: evo:22.3X80-D45-EVO evo:22.3X80-D46-EVO evo:23.2R2-S3-EVO evo:24.2R1-EVO evo:24.2R2-EVO evo:24.3R1-EVO junos:21.2R3-S9 junos:23.2R2-S3 junos:23.4R2-S4 junos:24.2R1 junos:24.2R2 junos:24.3R1 junos:25.1R1
PR NumberSynopsisCategory: Antivirus UTM issue
1841398
Critical		PFE process crash is observed after enabling Sophos Antivirus
Product-Group=junos		On all SRX platforms, the PFE (Packet Forwarding Engine) process core is observed after enabling Sophos anti-virus.

Resolved In: junos:23.4R2-S4 junos:24.2R2 junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: PTX/QFX100002/8/16 interface software
1817562
Major		DFE tuning stuck due to configuration error preventing interface from coming up
Product-Group=junos		On Junos PTX10008, PTX10016 and PTX platforms with FPC3-PTX, after a router reboot or FPC (Flexible PIC Concentrator) restart, DFE (Decision Feedback Equalisation) tuning is initiated on all active interfaces. If a tuning failure occurs due to a FEC (Forward Error Correction) mismatch, the process gets stuck. Even after correcting the error, the interface remains down as the system cannot initiate a new DFE tuning until the previous attempt completes.

Resolved In: junos:22.4R3-S4 junos:22.4R3-S5 junos:23.2R2-S3 junos:24.4R1
PR NumberSynopsisCategory: usf service set related issues
1814935
Minor		jnxSpSvcSetIfMemoryZone SNMP mib always returns 0 for service-set memory usage zone
Product-Group=junos		All the statistics are 0 for the SNMP OID jnxSpSvcSetIfMemoryZone. Other statistics regarding memory utilization are normal.

Resolved In: evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:24.2R2 junos:24.3R1 junos:24.4R1



Modification History

First publication 2025-01-23