Alert Type

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

Product Affected

ACX EX MX NFX QFX SRX vSRX

Alert Description

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

Solution

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

24.2R2-S1 - List of Fixed issues 

PR NumberSynopsisCategory: NSD process
1857379
Critical		The nsd process crashes on SRX platforms during cluster reboot, failover, or policy addition causes traffic outage
Product-Group=junos
Severity=Critical		On all Junos OS SRX series platforms configured with the logical systems (LSYS), the network security daemon (nsd) process crashes due to cluster failover or reboot of node in a standalone firewall setup or while adding security policies. This crash generates a core dump and prevents the system from configuring security policies. As a result, all policy configurations are removed, leading to a traffic outage.
PR NumberSynopsisCategory: NFX Layer 3 Features Software
1861770
Minor		Virtual Port Peer on vmhost interface behavior with 24.2R1
Product-Group=junosvae
Severity=Minor		On the NFX platforms, the user can map front panel L2 interfaces to a single L3 interface by using the "peer-interface" command which is not as per the design which states that the mapping requires the knob "fail-on-any-peer".
PR NumberSynopsisCategory: SRX1600 MACsec
1863576
Minor		Packet drops can occur when packets are received with a size equal to the default MRU
Product-Group=junos
Severity=Minor		On SRX1600, SRX2300 and SRX4300 platforms, when packets are received with a size matching the default MRU (Maximum Receive Unit) value of 1522 bytes, packets are dropped, leading to an impact on traffic.
PR NumberSynopsisCategory: SRX Fleming L2NG platform support
1868103
Minor		CoS shaping is not functional on IRB interfaces when the SRX1600 is in switching mode
Product-Group=junos
Severity=Minor		On SRX1600 platform, Class of Service (CoS) shaping does not work on IRB (Integrated Routing and Bridging) interfaces.
PR NumberSynopsisCategory: Border Gateway Protocol
1849568
Minor		L3VPN routes are not advertised to peer when BGP sessions with route-target filter flaps
Product-Group=junos
Severity=Minor		On all Junos and Junos OS Evolved platforms, after Border Gateway Protocol (BGP) sessions configured with 'family route-target' flaps, delayed route deletion causes the loss of the Route Target Filter (RTF), preventing the node from advertising L3VPN (Layer 3 Virtual Private Network) and direct routes (e.g., loopbacks and interface routes) to the BGP peer, leading to VPN route loss and service disruption.
1859020
Minor		Incorrect subcode NOTIFICATION is sent when local interface is disabled for which multihop is configured for directly connected peer
Product-Group=junos
Severity=Minor		On all Junos and Junos OS Evolved platforms, when 'multihop' is configured on a directly connected interface towards a peer and the session goes in IDLE state due to no local interface (interface is disabled or down), the log messages shows 'subcode 6 'Other Configuration Change'' instead of 'subcode 9 'Hard Reset''.
1863551
Major		BGP route advertisement failure with as-override and peer-as configured at group level
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms, BGP ( Border Gateway Protocol ) fails to advertise routes to external peers in an L3VPN ( Layer 3 Virtual Private Network ) environment when as-override is configured for a neighbor on the local device, and peer-as is applied at the group level. Since the routes are not advertised to peers, traffic matching those routes are dropped, causing service disruption.
PR NumberSynopsisCategory: MX304 Routing Engine issues
1854658
Major		Slow commits and chassisd cores on backup RE
Product-Group=junos
Severity=Major		On Junos VMHOST platforms, the delay in SSH session execution results in a delay in configuration commits and commit checks, which in turn causes a chassisd core dump.
1857833
Major		The chassisd process crash is seen after the device reboot when chassisd stalls after configuration commit
Product-Group=junos
Severity=Major		On all VMHost platforms, the chassisd crash can be seen, which can also lead to mastership switchover. This is mainly caused by a configuration commit (no specific configuration required) followed by a reboot.
PR NumberSynopsisCategory: QFX Access Control related
1851299
Minor		EX3400 Dot1x Radius accounting send incorrect value to the server for Acct-Input-Gigawords/ Acct-Output-Gigawords
Product-Group=junos
Severity=Minor		With Dot1x Radius Authentication and Accounting, when the Stop Accounting (due to disconnect) is sent to the Radius server the Acct-Input-Gigawords and the Acct-Output-Gigawords contains unexpectedly large value.
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=junos
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: EVO MACSEC Platform Independent Implementation
1808773
Minor		On ACX7348/ACX7332 all traffic is blocked on FPC after RE Switchover
Product-Group=junos
Severity=Minor		On ACX7348/ACX7332 with MACsec enabled in channelized interfaces, after performing a double RE switchover (primary RE swap to backup and then back to active), traffic in FPC1 stops in being forwarded.
PR NumberSynopsisCategory: AAA, auditd issues
1862203
Minor		Radius authentication is failing when Challenge Token is entered
Product-Group=junos
Severity=Minor		On all Junos and Evo platforms, the Radius Multi-Factor Authentication (MFA) failing for user login if the password and token were provided in two separate steps.
PR NumberSynopsisCategory: mgd, ddl, odl infra issues
1839955
Major		On Junos OS Evolved platforms, HTTPS download fails when HTTPS URL is present in the configuration
Product-Group=junos
Severity=Major		On Junos OS Evolved platforms, when HTTPS URL is present as a part of file or mentioned explicitly in the configuration, and when there is a download attempted through this file the download fails. However, this is will not impact the forwarding traffic only the download through HTTPS will fail.
PR NumberSynopsisCategory: EVPN control plane issues
1870365
Major		'TLV type 00000052 not supported on IFL gr' seen repeatedly in syslog for EVPN routing-instance configured with gr- ifls
Product-Group=junos
Severity=Major		JUNOS/EVO platforms running 23.4R2 and later software, if they have EVPN routing-instances with gr- ifls as members, continuous 'TLV not supported' messages could be seen in syslog.
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=junos
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: EX interfaces issues
1757034
Major		EX3400: "Error:tvp_optics_eeprom_read: Failed to read eeprom for link" syslog error message
Product-Group=junos
Severity=Major		"Error:tvp_optics_eeprom_read: Failed to read eeprom for link" logs might be seen for some time during system reboot or pfe restart in EX3400. There is no functional impact due to these logs.
1812891
Major		Packet drops when jumbo frames forwarded through ge interfaces configured for 10/100Mbps speed
Product-Group=junosvae
Severity=Major		On EX4300-MP platforms, ge (Gigabit ethernet) interfaces configured for 10 or 100Mbps (Mega bits per second), jumbo frame packets will be dropped.
1823688
Major		Interface goes down after a dc-pfe (Data Centre Packet Forwarding Engine) process restart in a Virtual Chassis environment on EX4400 platform
Product-Group=junos
Severity=Major		On a EX4400 virtual chassis environment, if the dc-pfe process restart for any reasons or restarted manually, then there is a possibility of some interfaces going down.
1841117
Major		TDR test can cause a CPU hog and result in BFD flaps
Product-Group=junos
Severity=Major		On the EX4100-F-12P, EX4100-F-12T, EX4100-24MP, EX4400-24MP, and EX4400-48MP platforms, running a TDR (Time-Domain Reflectometry) test specifically on mge interface, can cause a CPU (Central Processing Unit) hog and result in BFD (Bidirectional Forwarding Detection) flaps.
PR NumberSynopsisCategory: EX4400 PFE software
1817034
Major		For Junos OS platforms, the OSPF neighborship gets stuck in EXSTART state after performing NSSU
Product-Group=junos
Severity=Major		For Junos OS platforms, in a specific configuration change after NSSU (Nonstop Software Upgrade), i.e. delete and add sequence of LAG (Link Aggregation Group) bundles performed via load baseline configuration and re-apply original configuration, OSPF (Open Shortest Path First) session might get stuck in EXSTART state. This issue will impact the traffic.
1864371
Minor		STP/MSTP/RSTP/VSTP convergence issue due to BPDU drop by l2cpd
Product-Group=junos
Severity=Minor		On Junos EX4K and QFX5K platforms, STP (Spanning Tree Protocol)/MSTP (Multiple Spanning Tree Protocol) /RSTP (Rapid Multiple Spanning Tree Protocol) /VSTP (Vlan Spanning Tree Protocol) convergence issues were observed due to BPDUs (Bridge Protocol Data Units) being dropped by the l2cpd (Layer 2 Control Protocol Daemon) process. This behavior prevents STP/MSTP/RSTP/VSTP from converging successfully, impacting network stability.
1867562
Major		Default Route configured with Discard Next Hop on PFE instead of ECMP Next Hop after reboot
Product-Group=junos
Severity=Major		On all Junos EX4K (except EX4300) in a VC (Virtual Chassis) environment using LPM (Longest Prefix Match) routing, after a reboot the default route on the PFE (Packet Forwarding Engine) is incorrectly set to a "discard next-hop (NH)" instead of an ECMP (Equal-Cost Multi-Path) next-hop resulting in connectivity issues.
PR NumberSynopsisCategory: SRX1500 platform software
1831955
Major		The SRX1500 drops the packet if MTU matches the MRU of the receiving device
Product-Group=junosvae
Severity=Major		On SRX1500 platforms, if the Maximum Transmission Unit (MTU) is configured to match the Maximum Receive Unit (MRU) of the receiving device, packet drops occur. This occurs because additional processing overhead increases the packet size beyond the MRU limit, causing the receiving device to drop the packets.
PR NumberSynopsisCategory: Interface Information Display
1741282
Major		JUNOS MX | iflset stats not getting cleared after issuing clear interfaces stats all and clear interfaces interface-set statistics all CLI command
Product-Group=junos
Severity=Major		JUNOS MX | iflset stats not getting cleared after issuing clear interfaces stats all and clear interfaces interface-set statistics all CLI command
PR NumberSynopsisCategory: Libjtask for RPD tasks, scheduler, timers, memory, and slip
1846294
Major		Memory Leak: Memory leak is detected with rpd task blocks "rpd-trace"
Product-Group=junos
Severity=Major		Memory Leak: Memory leak is detected with rpd task blocks "rpd-trace"
PR NumberSynopsisCategory: JFlow bug tracker for SRX platforms
1843679
Minor		Application crash is observed due to insufficient memory when a large number of JFlow entries are created
Product-Group=junos
Severity=Minor		On Junos OS SRX platforms with JFlow configured with sampling interval set to 1, traffic impact is observed due to insufficient memory for the Layer 7 applications leading to application failure. The issue happens when a large number of JFlow entries are created exhausting memory potentially leading to crash.
PR NumberSynopsisCategory: Adresses ALG issues found in JSF
1852968
Major		The SRX platform may experience a flowd process crash and generate core dump files when the ALG feature is enabled
Product-Group=junos
Severity=Major		On SRX platforms running the Junos Operating System (OS) with Application Layer Gateway (ALG) enabled, in rare scenarios, flowd process can crash and crash files are generated. While the platform eventually recovers, traffic loss will occur during this process.
PR NumberSynopsisCategory: SRX PFE side multicast
1854130
Major		PIM IP ESP packet fragments dropped in SRX platform
Product-Group=junos
Severity=Major		Protocol Independent Multicast (PIM) fragmented packets using IP Protocol 50 (Encapsulating Security Payload - ESP) are dropped when traversing SRX devices operating in flow mode.
PR NumberSynopsisCategory: Flow Module
1859163
Minor		Security forwarding process crash may occur when multicast traffic triggers a route resolution request that needs to be processed for a pending session
Product-Group=junos
Severity=Minor		When multicast traffic triggers a route resolution request for a pending session, and the route is subsequently resolved, a race condition may occur if that pending session is terminated by a different thread before processing can continue. This can result in a crash of the flowd (security forwarding process). However, the control plane remains online and unaffected.
1872613
Major		PFE crash is observed when PFE processes the traffic passing through the dedicated fabric link
Product-Group=junos
Severity=Major		On the Junos OS SRX4600 platform, when PFE (Packet Forwarding Engine) processes the IPv4/IPv6 traffic passes through the dedicated fabric link, PFE crash is observed. This issue happens when PMI (PowerMode IPsec) is enabled (by default) and flow session accessing stale values.
PR NumberSynopsisCategory: High Availability/NSRP/VRRP
1850967
Major		L3MNHA with SRG1 IPSEC : MNHA ICL ipsec encryption link went down permanently after rebooting connected router through which ICL was established before. During this state IKE process got stuck at ~70% on MNHA Active node.
Product-Group=junos
Severity=Major		Generic MNHA issue not specific to CSDS
PR NumberSynopsisCategory: all logging related bugs on srx platforms
1860597
Major		Security log report messages w.r.t logical system is not generated
Product-Group=junos
Severity=Major		show security log report cli command for logical systems is not working for 24.2R2, 24.4R1-S2, if log report is disabled under root system. Work around is available for this issue.
PR NumberSynopsisCategory: Firewall Policy
1809563
Major		The "show security match-policies" command results in a timeout error
Product-Group=junos
Severity=Major		On all SRX platforms, when a scaled DNS (Domain Name System) configuration with approximately 500 entries is applied along with a policy configuration, issuing the "show security match-policies" command results in a timeout error. This issue has no functional impact.
1823591
Minor		Failed inter-process communication results in higher heap and buffer usage which impacts the functionality of processes
Product-Group=junos
Severity=Minor		On all Junos SRX platforms, when there is a broken Inter-Process Communication (IPC) link between the Routing Engine (RE) and Packet Forwarding Engine (PFE), heap and buffer utilization gradually increase to 99%, causing some software modules to start failing.
1859554
Minor		Wrong service-name display in SRX RT_FLOW traffic log.
Product-Group=junos
Severity=Minor		On SRX platforms, wrong service-name might display in SRX RT_FLOW traffic log.
PR NumberSynopsisCategory: User Firewall related issues
1810310
Minor		NSD file handles incrementing consistently in database file causing a rare condition of ssh access failure
Product-Group=junos
Severity=Minor		On all Junos SRX branch platforms, Network Security Daemon(NSD) file handles increments consistently. Triggering a rare condition of ssh access failure of the device.
1845506
Major		SRX PFE crash is observed with source-identity enabled
Product-Group=junos
Severity=Major		On all SRX platforms with source-identify and logging enabled, the PFE (Packet Forwarding Engine) crashes if the source identity username and group-names exceeds certain count and length. The system self-recovers after the issue is hit.
PR NumberSynopsisCategory: Layer 2 VPN related issues
1867040
Minor		Type 5 EVPN traffic is dropped on SRX when PMI is disabled or not supported
Product-Group=junos
Severity=Minor		On all SRX platforms, in an EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) environment, when PMI (Power Mode IPSec) is disabled or not supported, type 5 EVPN traffic gets dropped. The issue occurs due to flow context being cleared incorrectly, causing the overlay JEXEC nexthop to be pushed after the underlay one. This leads to the packet being treated as multicast and subsequently dropped.
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1864295
Major		L2ald process crash is observed upon executing hidden command "show ethernet-switching debug-statistics fast-mac-update" in case the command doesn't have any output
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms, the l2ald process crash is observed upon executing the hidden command "show ethernet-switching debug-statistics fast-mac-update" in case the command doesn't have any output.
PR NumberSynopsisCategory: Issues related to Junos licensing infrastructure
1844934
Major		Subscribers unable to connect in GNF setup
Product-Group=junos
Severity=Major		On Junos MX platforms with Node Slicing, i.e., GNF (Guest Network Function), and Subscriber Management services enabled, Subscriber bring-up failure can occur when an upgrade is performed from a non-Agile License infra release to a release running Agile-based Licensing. This issue impacts subscriber services and is encountered due to the enforced Hard Licensing feature for node slicing.
1873587
Minor		[MX] "smid ../../../../../../src/junos/lib/libsdb/licsubs/bsd12/liblicense_subs_os.c liblic_subs_total_active_licenses_in_use XXX" logs flood in license_flex_subs_trace.log.
Product-Group=junos
Severity=Minor		"smid ../../../../../../src/junos/lib/libsdb/licsubs/bsd12/liblicense_subs_os.c liblic_subs_total_active_licenses_in_use XXX" messages can be seen so frequent interval in license_flex_subs_trace.log.
PR NumberSynopsisCategory: JNP10K-RE3 CB Centralized MX timing
1817097
Critical		On MX10K4, MX10K8, MX10K16 systems, in some cases, a SPMB PFE (spmbpfe)core might be seen when system is going down.
Product-Group=junos
Severity=Critical		On MX10K4, MX10K8, MX10K16 systems , a SPMB PFE (spmbpfe) may occationally create a core file when the system is being shutdown. This event adds 10 seconds to the time to shut the system down. The delay dues to the PTP FPGA reset sequence during the shutdown process.
PR NumberSynopsisCategory: SW PRs for MPC10E Interfaces
1870156
Minor		Link instability is seen on 4x10GSR and 40G-SR4 SFP modules from Finisar having high Rx output value
Product-Group=junos
Severity=Minor		On MX platforms with MPC10E line cards, having SFPs from Finisar like 4x10GSR and 40G-SR4 plugged into the chassis results in high Rx (Receive) output values, causing link instability.
PR NumberSynopsisCategory: Multicast Routing
1863470
Major		The rpd crash due to memory corruption in PIM/MSDP network
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms, enabling PIM (Protocol Independent Multicast) or MSDP (Multicast Source Discovery Protocol) may cause a rare memory corruption during the update of the MSDP Source Active route. This issue primarily affects highly scaled environments, leading to rpd (routing protocol daemon) coredumps and potential traffic loss.
PR NumberSynopsisCategory: OS IPv4/ARP/ICMPv4
1849296
Minor		The self-generated traffic on Junos platforms use the incorrect source IP with ECMP configuration
Product-Group=junos
Severity=Minor		On all Junos platforms configured with Equal-Cost Multi-Path (ECMP) routing, self-generated traffic selects an incorrect source (Internet Protocol) IP address. As a result, the peer device lacks the relevant route information, causing self-generated traffic to be dropped. This issue is specific to ECMP configurations and does not impact data traffic.
PR NumberSynopsisCategory: build tools
1874525
Major		FTP default mode changed from active to passive on 24.2R2
Product-Group=junos
Severity=Major		An upgrade to libfetch caused the default FTP mode to move from active to passive. This PR corrects this as customers more than likely expect the previous active FTP functionality on their networks.
PR NumberSynopsisCategory: FreeBSD Kernel Infrastructure
1872010
Major		Junos OS: A local attacker with shell access can execute arbitrary code (CVE-2025-21590)
Product-Group=junos
Severity=Major		An Improper Isolation or Compartmentalization vulnerability in the kernel of Juniper Networks Junos OS allows a local attacker with high privileges to compromise the integrity of the device. Please refer to https://supportportal.juniper.net/JSA93446 [juniper.net] for more information.
PR NumberSynopsisCategory: PTX10K Routing Engine
1870082
Critical		Image validation fails during the Junos VM validation.
Product-Group=junos
Severity=Critical		On all Junos platforms that use pkgs/junos-vmguest/mtx/vmhost-pkg-support when loading image to 25.3+, image validation fails.
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
Severity=Major		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.
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1823601
Minor		Protocol traffic drops were seen in the network for any configuration change in the protocol
Product-Group=junos
Severity=Minor		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.
1855990
Major		Traffic drop observed due to ECMP next-hop programming issue
Product-Group=junos
Severity=Major		On QFX5k, EX4k, EX2300 and EX3400 platforms, ECMP next-hop programming issue causes some prefixes to drop traffic. The issue is observed when the software-configured ECMP size (maximum-ecmp) exceeds the limit of 64 during a network churn event in the network. This triggers ECMP to skip updates, leading to stale forwarding paths and a temporary traffic freeze.
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1856424
Major		The dcpfe process crashes on all Junos QFX and EX platforms due to memory corruption
Product-Group=junos
Severity=Major		A memory corruption issue can result random dcpfe (dense concentrator packet forwarding engine) process crashes on all Junos QFX and EX platforms configured with VXLAN (Virtual Extensible Local Area Network) configuration.
1866130
Minor		Command "show pfe vxlan" is not supported on QFX5200 devices
Product-Group=junosvae
Severity=Minor		Support added for "show pfe vxlan" CLI command on QFX 5200 devices
1869042
Minor		Memory Corruption in Function for MULTICAST Components
Product-Group=junos
Severity=Minor		On all QFX5k Junos Operation Systems, memory corruption is detected during the execution of function which triggers a call to the abort function via the panic function with the message "Memory corruption in block" leading to application crash causing service impact.
PR NumberSynopsisCategory: QFX5K JUNOS Interface, MACSec, Optics, SDK, PHY
1845158
Major		Interface flap between the QFX5120 and QFX5210 with QSFP-100G-LR4-T2 optics
Product-Group=junos
Severity=Major		When the 100G port with QSFP-100G-LR4-T2 is used the interface is negotiating to CAUI4 and when this happens the Speed needs to be explicitly set which was missing in the code.
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platform optics related issues
1855279
Minor		Auto-negotiation issue will be observed on 10ge-type SFP in QFX5120-48YM platform
Product-Group=junosvae
Severity=Minor		On Junos QFX5120-48YM platforms, auto-negotiation is not enabled for 10ge-type transceivers. Resulting in the port remaining down when connected to a peer device with 1G/10G.
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platfom issues
1852227
Major		Unintended reboots on QFX5120-48Y and EX4650-48Y platforms with Acbel PSU
Product-Group=junosvae
Severity=Major		On QFX5120-48Y and EX4650-48Y platforms with Acbel PSU (Power Supply Unit) sudden reboots are seen during UPS (Uninterruptible Power Supply) switchover. This results in impact on the traffic switchover.
PR NumberSynopsisCategory: RPD Interfaces related issues
1842546
Major		Memory leak is detected when interfaces are configured
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms, 72-byte size memory leak is seen when interface configuration is added. But there is no traffic impact due to this issue.
PR NumberSynopsisCategory: KRT Queue issues within RPD
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
PR NumberSynopsisCategory: Remote Access VPN issues on SRX
1869192
Minor		Hostname with apostrophe causing connection failures on SRX
Product-Group=junos
Severity=Minor		On all SRX platforms, a character restriction prevents Remote Access VPN connections when the hostname includes an apostrophe. Any device with a hostname containing an apostrophe will fail to connect to SRX using Juniper Secure Connect. This issue is not limited to mobile devices and can affect any device using Remote Access VPN with a hostname that meets the affecting criteria.
PR NumberSynopsisCategory: SRX branch platforms
1851261
Major		The commit command failed due to a speed mismatch between the Ten-Gigabit Ethernet (XE) port and the Aggregated Ethernet (AE) interface to which it belongs
Product-Group=junos
Severity=Major		On all platforms running the Junos Operating System (OS), the commit command fails when the speed of XE interfaces is downgraded using a Small Form-factor Pluggable (SFP) module, causing a speed mismatch with the AE interface to which they belong. However, this does not affect the overall operation of the AE interface.
1853238
Minor		Flexible-vlan-tagging option is missing under interface hierarchy on SRX3xx series
Product-Group=junos
Severity=Minor		On SRX3xx series configured with flexible-vlan-tagging, after upgrading the device to Junos version 23.4R2 or higher the flexible-vlan-tagging option is missing under the interface hierarchy. This leads to a syntax error, stopping users from setting the flexible-vlan-tagging.
PR NumberSynopsisCategory: ZT/YTpfe bridging, learning, stp, oam, irb software
1861020
Major		In an EVPN with IRB solution underlying NH change can cause packet drops on certain MX/EX platforms
Product-Group=junos
Severity=Major		On Junos MX with MPC10/MPC11/LC9600 line cards and EX92K platforms, , when IRB (Integrated Routing and Bridging) is configured under EVPN (Ethernet Virtual Private Network) routing instance, and any event that cause changes in the existing target of indirect NH (Next Hop) to a new target, the new target's token is not updated in IRB NH, will result in OOO (Out of Order) errors and packet drops.
PR NumberSynopsisCategory: ZT/YT pfe l3 forwarding issues
1858076
Major		The aftd process crash is seen on Junos OS platforms running MPC10, MPC11, LC4800, LC9600 line cards and in Junos OS platforms MX304, EX9200-15C
Product-Group=junos
Severity=Major		On Junos OS platforms running MPC10, MPC11, LC4800, LC9600 line cards and in Junos OS platforms MX304, EX9200-15C, aftd process crash is seen resulting in crash of FPC (Flexible PIC Concentrator) line card while the route module of PFE (Packet Forwarding Engine) processing route churns as simultaneous actions (add/delete/read) by multiple threads on the process.
PR NumberSynopsisCategory: ZT/YT LUSS SW driver
1861147
Major		FPC crash will be seen due to memory access violation
Product-Group=junos
Severity=Major		On MX platforms with MPC10/MPC11/LC9600 and MX304, the FPC (Flexible PIC Concentrator) will crash, generating a coredump due to memory access violation. This will result in traffic loss until the FPC recovers on its own.
PR NumberSynopsisCategory: N/A:sw-trinity-pfe-inline-map
1855496
Minor		ICMPv6 packets may be dropped instead of being translated using MAP-T
Product-Group=junos
Severity=Minor		Depending on the configuration in use, on Junos MX platforms with MPC10/MPC11/LC9600 line cards and all Junos Evolved platforms, ICMPv6 packets may be dropped instead of being translated using MAP-T.
PR NumberSynopsisCategory: Trio pfe bridging, learning, stp, oam, irb software
1856573
Minor		Octet and frame count is displayed incorrectly in jnxMacStatsEntry.
Product-Group=junos
Severity=Minor		On all MX platforms with MPC10, MPC11 and LC9600, when the SNMP query is run using the command "show snmp mib walk jnxMac" . The output of jnxMacStatsEntry provides statistics from one of logical unit only even if there are multiple logical units configured and the vlan id information shows up as "0", whatever the actual vlan id is. This is a display issue with no impact.
1865605
Critical		ARP packet drops seen if proxy-arp restricted is configured on an IRB interface.
Product-Group=junos
Severity=Critical		On the Junos MX and EX9K platforms, when a Bridge Domain(BD) is configured with an integrated Routing and Bridging(IRB) interface that has proxy ARP set to restricted mode, the switch forwards ARP requests only to the Routing Engine(RE) without broadcasting them across the VLAN. Thus, impacting the hosts within the same VLAN.
PR NumberSynopsisCategory: Trio pfe l3 forwarding issues
1855624
Major		IPv6 neighbor discovery with DHCP packet getting dropped when no-snoop option is enabled for DHCP Relay
Product-Group=junos
Severity=Major		On Junos OS MX platforms with DHCP (Dynamic Host Configuration Protocol) Relay configured using the "no-snoop" option, DHCP packets are not being processed correctly. This prevents next-hop resolution for the DHCP packets, causing IPv6 (Internet Protocol version 6) Neighbor Discovery with DHCP packet to be dropped by an intermediate device. As a result, the client fails to obtain an IP address, leading to traffic impact.
1864237
Critical		Observing out-of-order packets when the TCP traffic gets passed over AE bundle and tunnelled via MPLSoUDP tunnel
Product-Group=junos
Severity=Critical		On Junos OS platforms, When "dynamic tunnels" configured and "set chassis loopback-dynamic-tunnel" knob is used and when TCP (Transmission Control Protocol) traffic passed via MPLSoUDP (Multi-Protocol Label Switching Over User Datagram Protocol) tunnel through an outgoing AE (Aggregated Ethernet) bundle interface having member interfaces, use of either inner or outer header hash calculations lead to out-of-order packets at the egress. It causes service impact on related flow of traffic due to out-of-order packets.
PR NumberSynopsisCategory: Authentication, Authorization, Accounting, PAM (RADIUS/tacplus)
1843935
Major		On SRX300 series DHCP relay stops working and the device generates coredump after upgrading to JunOS 23.4R2-S2.1
Product-Group=junos
Severity=Major		On SRX300 series devices, when TACACS accounting is configured, after an upgrade to Junos 23.4R2-S2.1, the DHCP-relay may not work anymore and the shm-rtsdbd process may produce coredumps.
1855393
Major		User root is shown as incorrect after power cycle of the device
Product-Group=junos
Severity=Major		After a power cycle, telnet login through the console fails. The issue occurs randomly and does not happen after every power cycle. To recover the device, another power cycle should be performed.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1854070
Minor		cli coredump genarated when the size of buffer area (user input) increased to 1GB
Product-Group=junos
Severity=Minor		Cli coredump genarated when the size of buffer area (user input) increased to 1GB.
1861063
Critical		Unexpected issues such as login failures or disabled interfaces observed following abrupt reboot during commit operation
Product-Group=junos
Severity=Critical		On Junos platforms with boot-time optimization enabled, an abrupt reboot during a commit operation can cause configuration file corruption, potentially leading to issues like login failures or disabled interfaces.
PR NumberSynopsisCategory: web filterig issues
1854519
Major		FPC crashing when web filtering type set to "juniper-enhanced" or "NG-juniper"
Product-Group=junos
Severity=Major		On all SRX platforms, when the web-filtering type set to "juniper-enhanced" or "NG-juniper" (NextGen-juniper), it might cause FPC (Flexible Port Concentrator) card crash and with "srxpfe" or "lcore" crash files generated.
PR NumberSynopsisCategory: VSRX platform software
1836084
Minor		LLDP is failing to operate on the vSRX series platform
Product-Group=junos
Severity=Minor		On vSRXv3 Platforms using Mellanox ConnectX-5 (MLX5) Virtual Function (VF) as Network Interface Card (NIC), even when the Link Layer Discovery Protocol (LLDP) is enabled, it does not function at all, resulting in packets with LLDP multicast destination MAC addresses being dropped by the MLX5 NIC.
1855010
Minor		Split brain scenario is observed on vSRX3.0 with public cloud MNHA deployment
Product-Group=junos
Severity=Minor		On vSRX3.0 platforms with public cloud (Azure/AWS/GCP) MNHA (Multinode High Availability) setup when manually failed over, split brain scenario will be observed.
1874848
Minor		The srxpfe process crash is observed on vSRX platform after set disable on the ge- interface and then rollback
Product-Group=junos
Severity=Minor		The srxpfe process crashes when disabling the ge- interface mapped to an SR-IOV interface, followed by a rollback. This issue cause a traffic impact.

 

 

24.2R2-S1 - List of Known issues 

PR NumberSynopsisCategory: CoS support on ACX
1811850
Minor		Traffic drops on ge interfaces configured for PTP
Product-Group=junos		On ACX2200 series, ge (gigabit ethernet) interfaces configured for PTP (Precision Time Protocol), after PTP is deactivated and activated or activated for the first time, traffic can experience packet drops.

Resolved In: junos:21.2R3-S9
PR NumberSynopsisCategory: access node control protocol daemon
1877794
Major		The L2BSA subscriber fails to logout when "auto-configure-trigger" knob is edited on ANCP neighbour of MX platforms
Product-Group=junos		On all MX platforms with Access Node Control Protocol(ANCP) configured, the knob auto-configure-trigger on ANCP neighbor if edited (deactivate and activate) between system boot-ups, is not getting applied to the ANCP neighbour correctly. As a result, if an ANCP session goes down and the adjacency-loss-hold-time expires, the Layer 2 Bit Stream Access(L2BSA) interface still remains up indefinitely and the subscribers will fail to logout. Chassis needs to be rebooted after editing the configuration.

Resolved In: evo:25.2R1-EVO evo:25.3R1-EVO junos:25.2R1
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=junos		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.

Resolved In: evo:22.4R3-S7-EVO evo:23.4R2-S5-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:22.4R3-S7 junos:23.4R2-S2-J13 junos:23.4R2-S5 junos:24.4R2 junos:25.2R1
1860786
Major		BGP queue deadlock on Junos/Junos OS Evolved/cRPD platforms leading to route advertisement failure and traffic loss
Product-Group=junos		On all Junos, Junos OS Evolved, and cRPD platforms, due to deadlock in internal processes, BGP (Border Gateway Protocol) route advertisement fails leading to traffic disruption.

Resolved In: evo:23.2R2-S4-EVO evo:23.4R2-S5-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:20.3X75-D442 junos:22.4R3-S7 junos:23.2R2-S4 junos:23.4R2-S5 junos:24.4R2 junos:25.2R1
1877261
Major		BGP updates missing graceful-shutdown community after quick sender knob flaps
Product-Group=junos		On all Junos and Junos Evolved platforms, when the graceful-shutdown sender knob is repeatedly deleted and subsequently re-added in quick intervals under a BGP-LU (Border Gateway Protocol-Labeled Unicast) session, the router CLI (command line interface) incorrectly indicates that the graceful-shutdown community is being advertised. However, the actual BGP update messages sent over the session do not include the graceful-shutdown community. This results in the graceful-shutdown community not being propagated to BGP peers during graceful shutdown events, which will potentially cause traffic forwarding issues.

Resolved In: evo:24.2R2-S2-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:24.2R2-J6 junos:24.2R2-S2 junos:24.4R2 junos:24.4R2-S1 junos:25.2R1
1877288
Major		rpd crash when changes are applied to as-path with dynamic-db in use
Product-Group=junos		On Junos OS platforms using as-path-groups (Autonomous System Path Group) with dynamic-db (dynamic Data base) feature enabled, rpd (Routing Protocol Daemon) may crash after as-path configuration changes.

Resolved In: evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:24.2R2-J4 junos:24.4R2 junos:25.2R1
PR NumberSynopsisCategory: Device Configuration Daemon
1858289
Major		Observing traffic loss on PS service interface after deactivate and activate VPLS/EVPN instance type
Product-Group=junos		On all Junos platforms with PS (Pseudowire Subscriber Interfaces), when PS interface is configured with multiple logical units and the transport interface (PS unit 0) is configured interface family type as VPLS or bridge and when deleting routing instance corresponds to transport interface causing the associated service interfaces packets to be dropped and traffic impact will be seen for the associated service interfaces.

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

Resolved In: evo:22.3X50-EVO evo:22.3X50-J3-EVO evo:22.3X80-D47-EVO evo:22.3X80-D49-EVO evo:23.4R2-S5-EVO evo:24.4R2-EVO evo:24.4X200-D10-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:23.4R2-S5 junos:24.4R2 junos:25.2R1
PR NumberSynopsisCategory: EVPN control plane issues
1821582
Major		Deactivating protocol evpn in a routing-instance configured with 'vrf-target auto' leads to the rpd crash on both REs
Product-Group=junos		On all MX platforms the deactivation a routing-instance configured with 'vrf-target auto' while also configured with protocol evpn (Ethernet Virtual Private Network) leads to the rpd crash in all the REs (Routing Engine) present in the chassis

Resolved In: evo:24.4R1-EVO evo:25.1R1-EVO junos:24.4R1 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:
1825281
Major		Random ports of EX4400 will not be created on upgrade or reboot
Product-Group=junos		On EX4400, any fiber SFP plugged into EX4400-24X PIC 0 ports or EX4400-48F PIC 0 ports 36-47, random interfaces will not be created when the device is upgraded or rebooted. Interfaces will not be listed in the device and will affect all functionalities of the optic or interface.

Resolved In: junos:23.4R2-S5 junos:23.4R2-S6 junos:24.4R2 junos:25.2R1
1833177
Major		EX2300/EX3400 : The status LED of uplink port is not working properly
Product-Group=junos		On EX2300 and EX3400, the status LED of uplink port always displays green regardless of the status of the link.

Resolved In: junos:25.2R2
1864715
Critical		EX4100: 10g-BASE-T didn't come up after dc-pfe restart
Product-Group=junos		After multiple iterations of dc-pfe process restart, we may see interface with 10g-base-t transceiver (part# 740-123734) will not come up.

Resolved In:
PR NumberSynopsisCategory: SRX1500 platform software
1831955
Major		The SRX1500 drops the packet if MTU matches the MRU of the receiving device
Product-Group=junos		On SRX1500 platforms, if the Maximum Transmission Unit (MTU) is configured to match the Maximum Receive Unit (MRU) of the receiving device, packet drops occur. This occurs because additional processing overhead increases the packet size beyond the MRU limit, causing the receiving device to drop the packets.

Resolved In: junos:22.2R3-S7 junos:22.4R3-S7 junos:23.2R2-S4 junos:23.4R2-S5 junos:24.2R2-S1 junos:24.4R1-S3 junos:24.4R2 junos:25.2R1
PR NumberSynopsisCategory: Kernel software for AE/AS/Container
1762490
Minor		JDI-RCT-MPC10E: Ksyncd crash on backup RE after fpc reboot
Product-Group=junos		On MX series, when PS over RLT is configured where all member LTs are hosted on the same FPC and user restarts this FPC then on rare occasion, ksyncd crash can occur on backup RE. However, there is no impact on the master and only backup RE is affected. This issue is not consistent and seen only once out of ~10 or 15 fpc restart operations.

Resolved In: evo:24.4R2-EVO evo:25.2R1-EVO junos:24.4R2 junos:25.1R1 junos:25.2R1
PR NumberSynopsisCategory: Flow Module
1847419
Minor		Type 5 VXLAN traffic drops are observed when SRX run as L3-VNI gateway and the ingress and egress traffic goes to the same Type-5 VXLAN peer
Product-Group=junos		On Junos OS SRX platforms running as L3-VNI (Layer 3 - Virtual Network Identifier) gateway in EVPN-VxLAN (Ethernet Virtual Private Network - Virtual Extensible LAN) scenario, traffic drops will be observed if traffic passes through two VxLAN tunnels and traffic fails to cross the two VxLAN tunnels when the PFE (Packet Forwarding Engine) is processing the packet having same remote IPs for two VXLAN tunnels.

Resolved In: junos:23.2R2-S2-J8 junos:23.2R2-S4 junos:24.4R2 junos:25.1R1 junos:25.2R1
PR NumberSynopsisCategory: IPSEC/IKE VPN
1868453
Major		IPSec tunnel inactive after multiple srg failovers on SRX platforms
Product-Group=junos		On all SRX platforms, IPSec tunnels remain inactive if multiple Service Redundancy Group (SRG) failovers occur within a short period. This issue is specifically observed when the IPSec VPN is configured with the default establish on traffic setting. During rapid failovers, if high volumes of traffic are present, the tunnel re-establishment process fails, leading to inactive tunnels and potential traffic disruption.

Resolved In: junos:24.4R1-S3 junos:24.4R2 junos:25.2R1
PR NumberSynopsisCategory: MX104 Software - Timing
1782868
Major		MX104 AFEB might crash following a change of PTP clock source.
Product-Group=junos		On MX104, the AFEB could crash and reboot following a change of PTP GM clock source, which affects traffic forwarding.

Resolved In: junos:21.2R3-S9
PR NumberSynopsisCategory: Category for tracking Olympus-MX issues
1873938
Major		The SPC3 card resets due to kernel memory exhaustion in MX Series platforms with highly scaled routing tables and Inline Active Flow Monitoring configured
Product-Group=junos		On MX240, MX480 and MX960 platforms with MX-SPC3 (Services Processing Card) service cards, when Inline Active Flow Monitoring (inline-jflow) is configured in a highly scaled routing environment (~4M routes), the SPC3 service card runs out of kernel memory, resulting in the PIC going offline or resetting and the services running on the SPC3 card gets disrupted.

Resolved In: junos:24.4R2 junos:25.3R1
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1876359
Minor		ON QFX5K and EX4K platforms a log is required for route leaking when destination table hits a platform limitation
Product-Group=junos		On Junos QFX5K and Junos EX4K switches, route leaking for IPv4 requires a minimum route mask of /16, and the leak destination table must have a prefix length longer than or equal to that of the leak prefix for proper routing. When this doesn't occur, traffic forwarding is affected, and there is no log associated with this event

Resolved In: junos:21.4R3-S11 junos:23.4R2-S5 junos:24.2R2-S2 junos:24.4R2 junos:25.2R1
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1851629
Minor		Next-hop APIs to support LDP stitching cases over BGP routes pointing to list of indirects
Product-Group=junos		On all Junos and Junos Evolved platforms this is an enhancement for Nexthop APIs to support LDP stitching cases over BGP routes pointing to list of indirects next-hops.

Resolved In: evo:24.4R1-S3-EVO evo:24.4R2-EVO evo:25.2R1-EVO junos:24.4R1-S3 junos:24.4R2 junos:25.2R1
PR NumberSynopsisCategory: SRX-1RU platfom datapath SW defects
1842873
Minor		Load balance hash-key forwarding persists when switching to Layer 3-only
Product-Group=junos		On Junos SRX4600, SRX1600, SRX2300 and SRX4300 platforms, when switching load balance from L3+L4 to L3, hash-key forwarding fails; the device retains L3+L4.

Resolved In: junos:23.4R2-S5 junos:24.4R1-S3 junos:24.4R2 junos:25.2R1
PR NumberSynopsisCategory: Trio pfe bridging, learning, stp, oam, irb software
1870522
Minor		STP/RSTP/MSTP/VSTP enters a disputed and blocked state when the anchor FPC of an AE link, with members distributed across multiple FPCs, goes offline
Product-Group=junos		On MX and EX9200 series platforms that operate in hyper mode by default, STP (Spanning Tree Protocol)/RSTP (Rapid Spanning Tree Protocol)/MSTP (Multiple Spanning Tree Protocol)/VSTP (VLAN Spanning Tree Protocol) transitions to a disputed and blocked state if the members of the AE (Aggregated Ethernet) link in the anchor FPC (Flexible PIC Concentrator) goes offline.

Resolved In: junos:24.4R2 junos:25.2R1
PR NumberSynopsisCategory: Authentication, Authorization, Accounting, PAM (RADIUS/tacplus)
1850776
Major		Multiple Products: RADIUS protocol susceptible to forgery attacks (Blast-RADIUS) (CVE-2024-3596)
Product-Group=junos		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.

Resolved In: junos:21.4R3-S10 junos:22.2R3-S6 junos:22.4R3-S6 junos:23.2R2-S3
1874078
Major		Unable establish gnmi session using Radius and TACACS auth
Product-Group=junos		Unable establish gnmi session using Radius and TACACS auth. Currently JADE (Junoscript authentication daemon) utility which does authentication for telemetry on cRPD has support for local authentication.

Resolved In: junos:24.4R2 junos:25.2R1
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
1863354
Minor		CLI stops responding when Ctrl+Z is pressed
Product-Group=junos		On Junos 24.2 or later releases using BSD15, cli process may be suspended when Ctrl+Z is pressed in CLI.

Resolved In:
PR NumberSynopsisCategory: Issues related to NETCONF
1792554
Minor		JUNOS: Netconf: Edit-config with operation attribute create for existing hierarchy is not working as per RFC 6241
Product-Group=junos		JUNOS: Netconf: Edit-config with operation attribute create for existing hierarchy is not working as per RFC 6241

Resolved In:
PR NumberSynopsisCategory: Issues related to YANG Data Models
1781023
Minor		Few yang package are occuring multiple place On Box
Product-Group=junos		Few yang package are occuring multiple place On Box

Resolved In:
PR NumberSynopsisCategory: MX10K platform
1852648
Critical		JUNOS_REG: MX10008 : Observing core-spmbpfe at cmty_doob_rcb_fpga_init, cmty_spmb_hw_init, cmty_spmb_module_init, __pthread_kill_implementation, __kernel_vsyscall
Product-Group=junos		spmbpfe core can be seen sometimes in these two case: 1. During ISSU when old master RE comes up with the new image, a spmbpfe core is generated when the old master RE goes down after reboot is given post new image installation. The core will be seen post the reboot. 2. When "request system reboot" cli command is executed, a spmbpfe core will occur when the junos goes down and the core will be seen post the system comes up. These cores generated at these stages will have no impact on a running system. The core are seen only when some kind of reboot is triggered.

Resolved In: