Alert Type

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

Product Affected

ACX EX MX PTX QFX NFX SRX vSRX

Alert Description

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

unos Software service Release version 24.2R2-S3 is now available.

24.2R2-S3 - List of Fixed issues

PR NumberSynopsisCategory: EX4300 Mutlicast implementation
1873129
Major		The PTP packets are dropped when IGMP snooping is enabled
Product-Group=junosvae
Severity=Major		On EX4400, EX4100, QFX5120 and EX4650 platforms running Junos Operation System (OS), when Internet Group Management Protocol (IGMP) snooping is enabled on Virtual Extensible Local Area Network (VXLAN) Virtual Local Area Network (VLAN), all unknown multicast packets will be dropped. As a result, PTP (Precision Time Protocol) packets that use reserved multicast addresses are also discarded affecting the synchronization of the device with the clock server.
PR NumberSynopsisCategory: "agentd" software daemon
1889924
Major		Data still seems to be streaming somewhere when the DialOut (Established) connection on the port is already closed
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms, the existing gRPC-DialOut connection does not disconnect completely on the DUT, causing any other DialOut connections to fail.
PR NumberSynopsisCategory: chassisd related issues for high-end SRX platforms
1887000
Minor		SRX4600 node 1 enters hardware failure during upgrade
Product-Group=junos
Severity=Minor		On SRX4600 platforms running Junos OS and configured in High Availability (HA), a hardware alarm is triggered during Low Impact Cluster Upgrade (LICU) procedures due to incorrect alarm logic tied to control link status. This condition affects Node 1 and causes Redundancy Group 1 (RG1) to failover to Node 0, even if Node 0 interfaces are not yet active, resulting in a traffic outage.
PR NumberSynopsisCategory: A20/A40 IOC card
1883027
Minor		SRX Firewalls with IOC3 triggers a temperature alert on the FPC 2 PLX PCIe Switch Chip
Product-Group=junos
Severity=Minor		On SRX5400, SRX5600, and SRX5800 platform with MPC3-40G10G and MPC3-100G10G (IOC3) interface card, a temperature alarm is triggered when the Peripheral Component Interconnect Express (PCIe) switch chip temperature exceeds 75 Celsius degrees.
PR NumberSynopsisCategory: Border Gateway Protocol
1875144
Minor		Longer convergence is seen for a BGP neighbor having validation configured in its import policy
Product-Group=junos
Severity=Minor		On all Junos and Junos Evolved platform, when any BGP peer has validation policy configured for import, it is observed that there is an extra walk to re-evaluate the routes in the loc-rib for validation even though the policy/unrelated configuration is changed for an unrelated peer.
1887911
Major		The rpd process crashes after BGP configuration commits involving group-split-size and RIB-sharding
Product-Group=junos
Severity=Major		On Junos and Junos OS Evolved platforms, configuring "group-split-size" with BGP RIB-sharding(Border Gateway Protocol Routing Information Base Sharding) can lead to a crash in the routing protocol daemon (rpd) when a route update for a non-negotiated NLRI(Network Layer Reachability Information) is received in the update thread. This occurs if the NLRI is targeted at other BGP peers within the group that have negotiated it.
1889749
Major		BGP Prefix-SID Label collision causing RPD crash
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms, In Segment Routing the RPD ( Routing Protocol Daemon ) crash was observed due to different prefixes were trying to use same label, when Bgp prefix SID ( Segment Identifier ) feature was configured and labels were derived using the SID index.
1898734
Major		The rpd process crashes in an Inter-AS Option-AB L3VPN with BGP multipath list-nexthop enabled
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms, in an Inter-AS (Autonomous System) Option-AB L3VPN (Layer3 Virtual Private Network) scenario, if 'bgp multipath list-nexthop' is configured and a VRF (Virtual Routing and Forwarding) generates a route with list-nexthop that is advertised to an Option-AB peer, the rpd process crashes and generates a core-dump.
PR NumberSynopsisCategory: Captive Portal, Content Delivery Daemon, and Service Plugin
1836516
Major		On MX platforms with SPC3 with non-USF mode CPCD CLI Statistics are not displayed for Captive Portal Interfaces
Product-Group=junos
Severity=Major		On MX platforms with SPC3 where captive portal is enabled in non-USF mode, the CLI command 'show services captive-portal-content-delivery statistics interface si-' does not display packet statistics due to incorrect internal flag settings. This is a cosmetic issue and does not impact functionality or traffic.
PR NumberSynopsisCategory: MX304 Routing Engine issues
1854658
Major		The chassisd process crashes when commit command is issued multiple times
Product-Group=junos
Severity=Major		On Junos VMhost platforms, when commit command is issued 50-60 times in a minute, this leads to ssh session exhaustion and slow response which causes configuration commit delays and subsequently leads to a chassisd process crash and restart causing FPC restart.
PR NumberSynopsisCategory: QFX Access Control related
1901304
Major		[ex4000]:: Dot1x client remains in server-fail vlan post radius-reachability timer expiry
Product-Group=junos
Severity=Major		As a best practice dot1x server-timeout should be configured higher than radius-timeout * (retries + 1). Radius reachability feature is supposed to trigger periodic check if server is reachable and if it is then trigger reauth for all the clients in server-fail. There is a corner case which breaks this feature where no action is taken when reachability timer fires. In such scenario client will remain in server-fail unless its reauth timer fires.
PR NumberSynopsisCategory: Platform PR for 1G/10G LC
1858079
Major		JUNOS_REG:: MX10008: After doing offline fpc, observing major alarms on FPC
Product-Group=junos
Severity=Major
PR NumberSynopsisCategory: Firewall Filter
1889028
Minor		Filter name mapping error in routing instances with attached firewall filter
Product-Group=junos
Severity=Minor		On all Junos OS and Junos OS Evolved platforms, After the upgrade, the system is reporting that the ## reference not found for all routing instances which has a firewall filter attached to an Interface. This error is cosmetic and there is no service impact.
PR NumberSynopsisCategory: CoS support on DNX
1897336
Major		ARP resolution and device discovery failure is observed due to unexpected VLAN tags on ARP replies
Product-Group=junos
Severity=Major		On ACX710 and ACX5448 platforms, due to VLAN edit profile remapping and VLAN translation, all the packets are getting VLAN-tagged. The RE ( Routing Engine ) drops ARP ( Address Resolution Protocol ) reply packets that contain VLAN ( Virtual Local Area Network ) tags, if the interface encapsulation was set to ethernet-ccc and VLAN configuration was removed. As a result, ARP resolution fails, leading to ping and device discovery failure.
PR NumberSynopsisCategory: Covers Application classification workflows apart from custo
1890791
Major		IDP installation update fails on secondary node in SRX chassis cluster
Product-Group=junos
Severity=Major		On SRX devices running in a chassis cluster, when installing IDP (Intrusion Detection and Prevention) updates using the offline method, the secondary node may fail the installation. As a result, the update completes successfully on the primary node but fails on the secondary node.
PR NumberSynopsisCategory: Lacp related problems and issues.
1898531
Major		AE interfaces flap during GRES following an RE reboot on all Junos Evolved platforms
Product-Group=junos
Severity=Major		On all Junos Evolved platforms, Aggregate Ethernet (AE) interfaces with LACP configured will experience a flap due to a timing issue when Graceful Routing Engine Switchover (GRES) is performed after a Routing Engine (RE) reboot, resulting in traffic loss during the flap.
PR NumberSynopsisCategory: EVO Socket replication
1895827
Major		Adding a new key to authentication-key-chain causes kernel crash
Product-Group=junos
Severity=Major		On all Junos Evolved platforms, when setting/changing the tolerance value of key-chain to max value of 4294967295 and committing and then adding a new key to a key-chain and performing a commit action will result in kernel crash. Device self-recovers after the crash. "show system core-dumps" can be used to check the core. Core name starts with vmcore*
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
Severity=Major		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
1889092
Major		The rpd EVPN module sends a redundant license message to the license infrastructure
Product-Group=junos
Severity=Major		On Junos platforms, when loading the baseline configuration or during BGP flaps or Routing Instance deactivation, and a large number of Group-Based Policy (GBP) tagged routes are removed, a redundant GBP license update message is sent to the license infrastructure for every route deletion. This issue has no impact on traffic.
PR NumberSynopsisCategory: EX4000 PFE issues
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
1901837
Minor		PFE crashes on QFX5K and EX4K platforms in standalone and VC setups due to logging of PFE
Product-Group=junos
Severity=Minor		On Junos QFX5K and EX4K platforms, both in standalone and VC (Virtual Chassis) deployments, the PFE (Packet Forwarding Engine) unexpectedly crashes and restarts due to UKERN_GBL and DDOS packet logging in PFE because of incorrect file access in JUNOS code, resulting in an fxpc crash file being generated.
PR NumberSynopsisCategory: EX4400 PFE software
1866815
Major		On Junos QFX5000 series and EX4000 series platforms, an fxpc process crash triggers an FPC reboot
Product-Group=junos
Severity=Major		On QFX5000 series and EX4000 series platforms running Junos Operating System (OS), during normal operation, the fxpc process crashes due to a routing entry continues to reference a HOLD next-hop after the associated topology neighbor has already been removed by the system causing the Flexible Physical Interface Card (PIC) Concentrator (FPC) to reboot and generate a crash file.
1894136
Major		Physical Interface device remains down by continuous system reboots on EX and QFX5K platforms
Product-Group=junos
Severity=Major		On Junos EX and QFX5K platforms in a scaled setup having high number of Virtual Chassis members (5 or more VC members) , the physical interface device (IFD) remains down when continuous system reboots are performed (5-6 reboots), thus impacting network availability. This is a rare case scenario.
PR NumberSynopsisCategory: EX optics issues
1858986
Major		EX4400: Error message 'Failed to read eeprom' intermittently on SFP-T
Product-Group=junos
Severity=Major		On EX4400, error message 'Failed to read eeprom' is seen intermittently on SFP-T.
PR NumberSynopsisCategory: Express PFE L2 fwding Features
1884163
Major		IFL Memory Leak on QFX10K8/16 device
Product-Group=junos
Severity=Major		On QFX10K8/16 , IFL memory is not freed on non-local interface of FPC during configuration changes (eg: IFL delete/deactivate) for L3IFL/L2IFL on AE/Scalar interfaces. Fix is present in common code and risky. It is a day one issue and the per IFL leak is minimal (0.00016% of total Kernel heap size) .
PR NumberSynopsisCategory: SRX1500 platform software
1896794
Major		On SRX1500 platforms, after PFE crash, FPC cannot come online
Product-Group=junosvae
Severity=Major		On SRX1500 platforms, when transit packets get stuck, PFE crash and PFE core-dump is generated. FPC remains 'present' state until reboot, all the services running on that FPC will be impacted.
PR NumberSynopsisCategory: SRX4100/SRX4200 platform software
1706125
Major		ifHCOutOctets unexpected spikes in value
Product-Group=junos
Severity=Major		On SRX4100 and SRX4200 platforms, the ifHCOutOctets interface counter values may sometimes incorrectly spike and exceed interface speed.
1822662
Major		SRX:MNHA:ICL:[Longevity] - MNHA Conn State and ICL are down after 48+ hours of device being up with background traffic.
Product-Group=junos
Severity=Major		MNHA Conn State is going down after 48+ hours with some background traffic when MNHA ICL is configured with link-encryption
PR NumberSynopsisCategory: Libjtask for RPD tasks, scheduler, timers, memory, and slip
1861810
Major		The process rpd is cored while adding or removing dynamic-tunnels
Product-Group=junos
Severity=Major		On all Junos Evolved platforms, the indexing of next hop while adding or deleting dynamic tunnels causes the rpd process to core and restart. This is a timing issue.
PR NumberSynopsisCategory: JFlow bug tracker for SRX platforms
1863356
Minor		The flowd process crash on SRX with IPFIX and MPLS enabled
Product-Group=junos
Severity=Minor		On all SRX Series platforms, enabling IPFIX (IP Flow Information Export) on devices configured with MPLS (Multiprotocol Label Switching) results in flowd process crash. Traffic is interrupted due to the crash.
PR NumberSynopsisCategory: jpppd daemon
1870878
Minor		Simultaneous login by multiple PPPoE subs with same MAC address fails
Product-Group=junos
Severity=Minor		On Junos MX platform with subscriber management enabled, simultaneous login by multiple PPPoE subs with same MAC address fails
PR NumberSynopsisCategory: Flow Module
1895420
Major		First path SM interest check fail on SRX4100
Product-Group=junos
Severity=Major		When traffic is processed application services which uses tcp proxy in flowd, the usage of object cache increases and possible to drop traffic.
PR NumberSynopsisCategory: flow ha module
1895134
Minor		ISSU Failure and Core Dump on Primary Node During HA Upgrade
Product-Group=junos
Severity=Minor		On all Junos SRX platforms, performing ISSU (In-Service Software Upgrade) with the no-validate option in HA ( (High availability ) setups can cause ISSU failure and a core dump on the primary node.
PR NumberSynopsisCategory: SRX PFE side multicast
1877771
Major		The flowd process crash is observed on all Junos SRX platforms in multicast scenario with PIM
Product-Group=junos
Severity=Major		On all Junos SRX platforms, the flowd process crash will be observed when device is acting as MHR (Middle Hop Router) and PIM (Protocol Independent Multicast) register packet from FHR (First Hop Router) tries to build the control/data session for the same PIM register packet.
PR NumberSynopsisCategory: SRX PFE side GRE/IPIP/DS-Lite/IPSec/PIM/VXLAN tunnel
1884150
Major		Policy match failure for VXLAN EVPN type-5 cross vrf traffic
Product-Group=junos
Severity=Major		On all SRX platforms, Ethernet Virtual Private Network (EVPN) Type-5 Virtual Extensible LAN (VXLAN) cross-Virtual Routing and Forwarding (VRF) traffic fails to match security policies when the ingress and egress VRFs are mapped to different VRF groups.
PR NumberSynopsisCategory: High Availability/NSRP/VRRP
1895790
Major		Backup node stuck in cold sync failure after all FPCs reset due to SPC crash files in SRX chassis cluster
Product-Group=junos
Severity=Major		On all SRX platforms, in a chassis cluster scenario, the SPCs on the backup node crash. After the crash files are fully generated, this triggers a reset of all FPCs. Following the crash and FPC resets, the backup node enters a cold sync failure state and remains in that state until it is manually rebooted.
PR NumberSynopsisCategory: l2 flow module
1852047
Major		Traffic drops are observed when SRX380 platform is configured in l2 transparent-bridge mode
Product-Group=junos
Severity=Major		On Junos OS SRX380 platforms, traffic drops are observed due to the default drop ACL (Access Control List) (L2 unknown unicast packets) getting applied. The issue happens when the device is configured in L2 (Layer 2) transparent-bridge mode.
PR NumberSynopsisCategory: IPSEC/IKE VPN
1892539
Major		IKE Processing Order Causing Gateway Misconfiguration and Tunnel Failures
Product-Group=junos
Severity=Major		On SRX platforms, when both gateways, the local-address and the IFA (Interface address) are changed and if the IKE (Internet Key Exchange) configuration is processed before the IFA update, gateways lacking an explicit local-address will be misconfigured, leading to tunnel failures.
PR NumberSynopsisCategory: Security platform jweb support
1876075
Minor		Upgrade and Downgrade will fail from J-Web in SRX4600
Product-Group=junos
Severity=Minor		On SRX4600, upgrades and downgrades will fail from J-Web with the error message: "Installation Progress failed at Receive Package File" from release 23.4 and above.
PR NumberSynopsisCategory: Layer 2 Circuit issues
1863228
Major		IFL configured on the LAG interface goes down when the VLAN operation is changed
Product-Group=junos
Severity=Major		On all Junos OS and Junos OS Evolved platforms, when EVPN is configured with the 'df-election-granularity per-esi' feature, any change in VLAN operation causes the IFL (logical interface) configured on the LAG (Link Aggregation Group) interface to go down, impacting all services associated with that interface.
PR NumberSynopsisCategory: Multicast for L3VPNs
1888630
Major		MVPN Source PE might incorrectly send mcast traffic on SPT while actual receiver is still on RPTree
Product-Group=junos
Severity=Major		In currently flow when a provider tunnel is being deleted, it is assumed the cmcast routes associated to the ptnl would've have been updated before. This is fine for inclusive tunnels, however for selective tunnels especially wild card scenarios the cmcast routes may not be updated. So in cases where the ptnl is deleted like configuration based removal or underlying tunnel going down, there is chance that the forwarding routes are still not deleted. The cmcasts are deleted later in the flow but when they are deleted the corresponding forwarding routes are still not deleted since there is no corresponding ptnl for the cmcast. This will create issues if forwarding is supposed to happen via different forwarding entry like a *, G entry but since the more specific S, G stale entry exists, traffic will hit the later and lead to unexpected behavior like traffic black-holing if S, G is Pruned entry.
1902405
Major		The rpd process crash is observed with MVPN and RIB sharding enabled
Product-Group=junos
Severity=Major		On Junos MX and Junos Evolved PTX platforms , with RIB sharding enabled and if either IPv4 or IPv6 address family is disabled in MVPN (multicast virtual private network), the unicast route flow from shard tries to access MVPN data structures without validation leading to rpd (Routing Protocol Daemon) process crash.
PR NumberSynopsisCategory: FreeBSD Kernel Infrastructure
1879079
Major		SRX5600 and SRX5800 SPC3 are going offline after software upgrade
Product-Group=junos
Severity=Major		On SRX5600 and SRX5800 platforms configured in active/passive cluster, upgrading to Junos OS versions 24.4R2.1 or 25.X results in the Services Processing Card 3 (SPC3) on the primary node transitioning to an 'offline' state.
PR NumberSynopsisCategory: Kernel Tunnel Interface Infrastructure
1897240
Major		Chassis-Control restart triggers when configuring GRE interface across multiple routing-instances leading to kernel crash
Product-Group=junos
Severity=Major		On Junos series devices, the kernel crash occurs when creating and configuring a identical GRE(Generic Routing Encapsulation) interface across different routing-instances.
PR NumberSynopsisCategory: Express Chip L3 software
1865171
Critical		FPC crashes if the BGP protocol next-hop gets resolved over a discard logical interface (dsc.0)
Product-Group=junos
Severity=Critical		On Junos OS PTX and QFX10k platforms, FPC crashes and reboot is seen due to the corruption of the data structures associated with dsc.0 (Discard Interface).
PR NumberSynopsisCategory: Phone-Home-Client Infrastructure
1871802
Critical		High memory and CPU usage due to unintended phone-home client activation
Product-Group=junos
Severity=Critical		On Junos OS Evolved platforms, high memory and CPU usage may occur if the phone-home client (PHC) is unintentionally triggered, such as when the device boots with factory default settings or when phone-home is manually configured. This can lead to system slowness, crashes, and eventual device reboots.
PR NumberSynopsisCategory: Issues related to PKI daemon
1892297
Major		The pkid crash is observed during enrolment of device's local certificate through SCEP
Product-Group=junos
Severity=Major		On Junos OS platforms that use the pki service (public key Infrastructure) for device's local certificate enrolment via SCEP (Simple Certificate Enrolment Protocol), the pki daemon crashes during the enrolment process due to the user misconfiguration in CA (Certificate Authority) profile, specifically the key-usage of the CA certificate for the CA profile lacks the certificate-signing, resulting in impact to services relying on certificate verification.
PR NumberSynopsisCategory: QFX access control list
1863813
Minor		On particular QFX and EX devices firewall filter counters display double the actual packet count
Product-Group=junos
Severity=Minor		When Filter-Based Forwarding (FBF) or Policy-Based Routing (PBR) is configured with firewall filter counters on platforms QFX5120, EX4650, EX4100, EX4400, the CLI output for FBF/PBR filter statistics shows double the actual packet count, there is no workaround for this issue.
PR NumberSynopsisCategory: QFX L2 PFE
1885220
Minor		Unable to learn the MAC address on a switch interface when using "interface-mac-limit" command
Product-Group=junosvae
Severity=Minor		On all Junos QFX 5k platform, unable to learn the MAC address on a switch interface when using "interface-mac-limit" command.
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1856424
Major		The dcpfe process crashes on specific 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 specific Junos QFX and EX platforms configured with VXLAN (Virtual Extensible Local Area Network) configuration.
1895903
Major		Traffic loss will be observed when VPLAG is configured on Junos QFX5k and EX4k platforms
Product-Group=junos
Severity=Major		On Junos QFX5k and EX4k platforms, if VPLAG(Virtual Private Link Aggregation group) is configured and if there is event change which could make ECMP(Equal Cost Monitoring Protocol) programming to change like ECMP link flap, dcpfe restart, system reboot etc which causes traffic loss.
PR NumberSynopsisCategory: QFX5K JUNOS Interface, MACSec, Optics, SDK, PHY
1845045
Major		On QFX5120-48YM port remains down when speed shifts from 1G to 10G
Product-Group=junos
Severity=Major		On QFX5120-48YM, if a port is transitioned directly from 1G to 10G either by swapping the SFP or by changing port and chassis speed settings without intermediate reset. The 10G link will remain down.
1890867
Major		QFX5120 - SFP+ Modules disappear/down post upgrade
Product-Group=junos
Severity=Major		On QFX5120-48T platforms, QSA-SFP+ adapter(100G/40G ) modules disappear/go down after software upgrade. Due to unsupported QSA usage in the impacted release, which will trigger a dcpfe (Dataplane Packet Forwarding Engine) crash.
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platfom issues
1758400
Major		JUNOS_REG: QFX51200-48YM: Fan status output was not same after/before device vc-switch over.
Product-Group=junos
Severity=Major		In a QFX51200-48YM-8C VC setup, after a a mastership switch over fan tray of linecard may not be displayed in show chassis hardware and show chassis environment. There is no functional impact
1800862
Major		On all dual disk QFX5K platforms having QFX-5e image with secondary (sdb) disk failure, WRITE DMA errors are observed and the device goes unresponsive
Product-Group=junos
Severity=Major		Due to a the disk failure reboot support was not added for dual disk scenario, hence system was not booting in case of disk failure on sdb (the other disk) on QFX platform.
1882472
Major		JMA package fails to initialise after a power cycle on EX4650/QFX-5E series devices
Product-Group=junos
Severity=Major		On Junos EX4650/QFX-5E series, after installing the JMA(Junos Mist Agent) package, a graceful reboot (using request system reboot or request system halt) is required to commit the changes. An abrupt power cycle before a graceful reboot causes the system to lose the installed JMA package.
1902869
Critical		Significant system slowness is observed post software upgrade on QFX5120-48YM
Product-Group=junosvae
Severity=Critical		On QFX5120-48YM devices, after performing a software upgrade to versions containing the fix for PR1882472, users may observe significant system slowness immediately following the first boot. This slowness manifests as degraded performance across multiple system parameters, including increased reboot time, slower interface initialization, and longer service restoration periods.
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1881012
Major		The rpd crash would be observed when two separate next-hops in rpd map to the same next-hop-index in the kernel
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms, when a route is getting installed to the forwarding table, associated next-hops also get installed in the forwarding table. As part of this installation process, the Junos kernel allocates the next-hop-index for the next-hop. The rpd sets this next-hop-index in its database when two separate next-hops for instance NH1 and NH2 in the rpd map to the same next-hop NH in the kernel. In such case, NH1 and NH2 next-hops in rpd will have the same next-hop-index leading to the rpd crash.
PR NumberSynopsisCategory: Resource Reservation Protocol
1893822
Major		Record Route Object displayed in show mpls lsp output is trucated if number of hops is sixteen or more
Product-Group=junos
Severity=Major		If the number of RSVP LSP hops is sixteen or higher, the RRO displayed in show mpls lsp extensive output may get truncated
1896022
Major		More bandwidth may be admitted onto a TE link when Label Switched Paths (LSPs) undergoing make-before-break re-route over the same link carrying the bypass LSP during local repair
Product-Group=junos
Severity=Major		If Label Switched Paths (LSPs) undergo local repair and subsequently undergo global repair in make-before-break fashion such that the LSPs are re-routed over the same TE link that carries the bypass LSP that protect the LSPs during local repair, then more re-routed LSPs may be admitted on the TE link carrying the bypass LSP than that should be admitted. This may result in some re-routed LSPs remaining on the TE link causing additional traffic sent on the TE link than the capacity of the TE link.
PR NumberSynopsisCategory: SRX branch platforms
1859188
Minor		Branch SRX unstable NTP issue
Product-Group=junos
Severity=Minor		On Branch SRX platforms (SRX300, SRX320, SRX340, SRX345 and SRX380), NTP time reset message is often seen due to SRX NTP issue
1889549
Major		The XE interfaces of SRX380 platform with 1G SFP (fiber) are flapping continuously when LACP is enabled
Product-Group=junos
Severity=Major		When LACP (Link Aggregation Control Protocol) is enabled using 1G SFP(Small Form-factor Pluggable)-fiber (such as SFP-SX, SFP-LX etc) over XE interfaces, frequent state transitions will repeatedly trigger configuration updates. Due to LACP instability, the interfaces will continuously flap. As a result, the port configuration will be re-applied automatically which leads to a loop of re-configurations until the LACP state stabilizes.
1893957
Minor		SRX Cluster Loaded with McD Configuration Experienced DHCP Assignment Failures and ARP Resolution Issues to the Default Gateway
Product-Group=junos
Severity=Minor		In SRX clusters configured with the McD template, connected devices obtain DHCP IP addresses but fail to resolve ARP for the default gateway. ARP replies are sent by the SRX but do not reach the connected devices, with corresponding packet discards observed in the Packet Forwarding Engine (PFE).
1902810
Minor		[Branch SRX] backup option for "request system firmware upgrade re bios" command was removed from Junos 24.2
Product-Group=junos
Severity=Minor		On Branch SRX platforms, backup option in "request system firmware upgrade re bios" was unexpectedly removed on Junos 24.2 release.
PR NumberSynopsisCategory: MX10003/MX204 MPC defects tracking
1876314
Minor		Intermittent link-up failure on MX10003 after peer device reboot
Product-Group=junos
Severity=Minor		On Juniper MX10003 platforms equipped with MIC1, interfaces using QSFP optics fail to come up or remain down after a connected third-party device is rebooted. This behavior results from a timing mismatch, where the software delays link initialization while waiting for a stable optical signal, potentially missing the brief window when the remote device restarts its transmit signal. This is an interoperability issue and may require manual intervention for service restoration.
1886937
Major		Interfaces either fail to come up or flap or a delay is observed on MX10003 platforms when the interface is reset or the devices is restarted
Product-Group=junos
Severity=Major		On MX10003 platforms peering to third-party devices, interfaces remain down or flap or a delay is observed while it comes back up after the device is restarted or the Flexible PIC Concentrator (FPC) is restarted or when the interface is reset. The symptoms is not consistent and any of the mentioned behaviour could be seen. Due to the interface going down or in case of a flap/delay, services running over the interface will be impacted or traffic flowing through that interface will be dropped.
PR NumberSynopsisCategory: ZT/YT pfe CDA issues
1882845
Critical		MPC 10/11/12E, LC9600 and LC4800 Line cards and MX304, interface statistics stop after interrupt
Product-Group=junos
Severity=Critical		On all MX platforms with MPC 10/11/12E, LC9600 and LC4800 Line cards and MX304, in a race condition related to the interrupt handling, interface counters are stuck and not incrementing. Issue not reproducible and there is no service impact due to this issue.
PR NumberSynopsisCategory: ZT/YT pfe infra issues
1897464
Major		Memory allocation failure on all FPC's with error Add failed memory allocation failure nh-id:
Product-Group=junos
Severity=Major		Memory allocation failure on all FPC's with error Add failed memory allocation failure nh-id:
PR NumberSynopsisCategory: Issues related to broadband edge apps (PPP, DHCP) on Trio ch
1865649
Major		Traffic drop from subscriber will be observed when rpf-check knob is enabled under subscriber dynamic-profile with static underlying VLAN interface
Product-Group=junos
Severity=Major		On all Junos MX platforms with BBE subscribers (Broadband Edge) over static IFLs (Logical Interface) with static underlying VLAN (Virtual Local Area Network) interface and ISSU (In-Service Software Upgrade) is performed, traffic drop will be observed when rpf-check (Reverse-path forwarding) knob is enabled under subscriber dynamic-profile.
PR NumberSynopsisCategory: Trio pfe l3 forwarding issues
1891110
Major		A GRE tunnel configured with a tunnel key drops MPLS-encapsulated traffic
Product-Group=junos
Severity=Major		On MX platforms with line cards MPC1-9, a Generic Routing Encapsulation (GRE) tunnel configured with a tunnel key drops Multi-Protocol Label Switching (MPLS) encapsulated traffic as it is unable to find the key.
PR NumberSynopsisCategory: Junos Automation, Commit/Op/Event and SLAX
1872284
Major		master-eventd will fail after multiple RE switchover
Product-Group=junos
Severity=Major		On Junos and Junos OS Evolved platforms with dual RE(Routing Engine) , master-eventd will fail to start after multiple RE switchovers when event-options policies are configured. This happens only if a process is still waiting for an action (like file transfer or SSH) to complete.
PR NumberSynopsisCategory: Configuration management, ffp, load action
1854461
Major		Configured TFTP server connection and rate limits are not applied
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms configured as Trivial File Transfer Protocol (TFTP) server , "connection-limit" or "rate-limit" values are not updated as per configured values.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1873253
Major		The "show system storage" command output should show only true and distinct storages
Product-Group=junos
Severity=Major		On all Junos platforms, the "show system storage" command output is modified to list only all real UFS filesystem ie { 'ffs', 'tmpfs', 'ufs' } instead of virtual filesystem like '/var/jails/rest-api'.
1878430
Major		The mgd process crash is seen on all Junos and Junos Evolved platforms when FQDN is configured along with ephemeral database
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms, Fully Qualified Domain Name(FQDN) configured in static database in presence of ephemeral database instances results in the mgd process crash. As a result, mgd session gets terminated and commit fails. There is no traffic impact due to this issue. The issue is seen with FQDNs that resolve to multiple IP addresses.
PR NumberSynopsisCategory: Track Windriver Linux issues
1631579
Critical		A few line cards will be stuck in the 'Present' state and later go 'Offline'
Product-Group=junos
Severity=Critical		A system equipped with specific line cards, the line cards will be stuck in the 'Present' state and later go 'Offline' after the line card or router is rebooted. Ideally, the Line Card should go 'Online' instead it goes 'Offline'.

 

 

24.2R2-S3 - List of Known issues

PR NumberSynopsisCategory: ISSU
1898501
Major		EX4650/QFX5120-48Y: ISSU incompatibility with previous releases
Product-Group=junos		EX4650/QFX5120-48Y: Older releases (that do not contain the 1882472 fix) are ISSU incompatible with current releases that have 1882472 fix.

Resolved In:
PR NumberSynopsisCategory: "agentd" software daemon
1885622
Major		The aaasd process stops responding for RPC calls
Product-Group=junos		On all Junos and Junos Evolved platforms with gRPC configured, the aaasd process rejects incoming RPCs. This issue occurs in some rare cases, and aaasd will stop listening for authentication requests from reverse proxy. This issue does not cause a traffic impact.

Resolved In: evo:24.4X200-D10-EVO evo:24.4X200-D20-EVO evo:25.2R1-S1-EVO evo:25.2R2-EVO junos:24.2X1 junos:25.2R1-S1 junos:25.2R2
PR NumberSynopsisCategory: BBE multicast related issues
1882756
Major		The bbe-smgd process crash triggered by a multicast event failure
Product-Group=junos		On all MX platforms with Broadband Edge Subscriber Management configured, the bbe-smgd process crashes when the multicast sync service add publish fails. This crash is automatically recovered by the system without requiring manual intervention.

Resolved In: evo:25.3R1-EVO junos:25.3R1
PR NumberSynopsisCategory: Bi Directional Forwarding Detection (BFD)
1888400
Major		EX4100/EX4400 8 member VC: Observing high convergence on GRES
Product-Group=junos		Traffic convergence issue was resolved with the work around provided. BFD issue was known limitation.

Resolved In:
PR NumberSynopsisCategory: MX304 Routing Engine issues
1877895
Major		Martian logs observed on the device.
Product-Group=junos		On all Junos and Junos Evolved OS, martian logs are observed on FPC (Flexible Physical Interface Card) and on Routing Engine 0.

Resolved In: evo:24.4R2-S1-J1-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:23.4R2-S6 junos:24.4R2-S2 junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: Firewall Filter
1903047
Minor		Intermittent traffic loss after pfe reset due to FLT filters
Product-Group=junos		On all Junos MX platforms with line cards MPC7/8/9 (EA Asic) , if any PFE restarts as part of any encountered CM Error defects, then fast-lookup-table filters will not work properly and traffic black holing will be seen.

Resolved In: evo:25.2R2-EVO evo:26.1R1-EVO junos:23.2R2-J22 junos:24.2R2-J11 junos:24.2R2-S4 junos:25.2R1-S2 junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: EVO L2 Control Plane PRs
1899530
Major		MAC learning failure when moving the AE interface from one VLAN to another VLAN in a single commit
Product-Group=junos		On Junos OS Evolved platforms, when an Aggregated Ethernet (AE) logical interface (IFL) is moved from one Virtual LAN (VLAN) to another VLAN in a single commit, Layer 2 forwarding tables fail to update correctly. This causes Media Access Control (MAC) learning failure and traffic disruption.

Resolved In: evo:24.4R2-S2-EVO evo:25.2R2-EVO evo:25.4R1-EVO evo:26.1R1-EVO junos:22.4R3-S9 junos:24.2R2-S4 junos:24.4R2-S2 junos:25.2R1-S2 junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: EVPN control plane issues
1846266
Major		The inet filters attached to the IRB interface will not function as expected
Product-Group=junos		On Junos QFX5k and EX4k platforms, in an Ethernet VPN-Virtual Extensible LAN (EVPN-VXLAN) scenario, inet filters applied to Integrated Routing and Bridging (IRB) interfaces will not function as expected, and the associated actions of the filter are not enforced.

Resolved In: junos:24.4R1-S1 junos:24.4R1-S3 junos:24.4R2 junos:24.4R2-S1 junos:25.1R1 junos:25.2R1 junos:25.2R1-S1
1862755
Critical		The associated EVPN RI peers are not learning routes when there is change in EVPN RI name or EVPN RI is deleted and added back
Product-Group=junos		On all Junos and Junos OS Evolved platforms with Dual RE with NSR enabled, if automatic RD (Route-Distinguisher) is used for EVPN (Ethernet VPN) RI (Routing Instances) in a scaled configuration setup, and when there is a change in the EVPN RI or the EVPN RI is deleted and added back, the associated EVPN RI remote peers are not learning routes, which results in traffic loss.

Resolved In: evo:24.4R2-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:24.4R2 junos:25.2R2 junos:25.3R1
1889092
Major		The rpd EVPN module sends a redundant license message to the license infrastructure
Product-Group=junos		On Junos platforms, when loading the baseline configuration or during BGP flaps or Routing Instance deactivation, and a large number of Group-Based Policy (GBP) tagged routes are removed, a redundant GBP license update message is sent to the license infrastructure for every route deletion. This issue has no impact on traffic.

Resolved In: evo:24.2R2-S3-EVO evo:25.2R1-S1-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:24.2R2-S2 junos:25.2R1-S1 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: Firewall Policy
1894033
Critical		SRX5K traffic disruption due to REPFE policy sync issues from FQDN and file-serialization Errors
Product-Group=junos		On SRX5K series devices with file-serialization enabled, frequent policy synchronization issues occur between the Routing Engine (RE) and Packet Forwarding Engine (PFE) . This can result in traffic matching the incorrect default deny policy instead of matching the expected user-defined security policy. The issue is triggered during commit or request security policies check/resync operations, particularly when Fully Qualified Domain Name(FQDN)-based address objects are involved and have short Domain Name System Time to Live(DNS TTLs).

Resolved In: junos:24.4R2 junos:25.2R1-S1 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: IPSEC/IKE VPN
1801028
Major		VPN TPS performance is degraded on SRX5K series
Product-Group=junos		VPN TPS performance is degraded in Release 24.2R2 on SRX5K series with dpdk-22.11.

Resolved In: junos:24.4R1
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1892944
Minor		EX4300 VC L2ALD core after upgrade from 21.4R3-S3.4 to latest 21.4R3-S6 and above versions
Product-Group=junos		On EX4300 switch running Junos version 21.4R3-S6 and above, when SNMP polling is done for oid 1.3.6.1.2.1.17.7.1.4.5.1 with redundant-trunk-group interfaces configured there will be L2ALD memory leak seen on the switch.

Resolved In: evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: Multiprotocol Label Switching
1889546
Major		MPLS ping/trace not working for direct peers via routing-instance over MPLS protocols
Product-Group=junos		On all Junos and Junos OS Evolved platforms, when a routing instance is configured at the destination device, an echo request packet is received over this routing instance interface. This routing instance should have a valid route to reach the source device. But the default routing instance should not have a valid route to reach the source device. This issue is not specific to MPLS ping over SR alone. This issue is applicable for all the protocols MPLS ping.

Resolved In: evo:24.4R2-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:24.4R2-S2 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: Odin Timing software
1810429
Major		ACX710 PTP ports marked 'passive' instead of 'master' during T-GM selection
Product-Group=junos		In a scenario where two T-GM devices (Telecom Grandmaster clocks) have identical BMCA (Best Master Clock Algorithm) parameters, except for steps removed or grandmaster ID, the ACX710 running the G.8275.1 profile can experience a failure in proper PTP (Precision Time Protocol) clock synchronization. This issue arises because the default BMCA is used instead of the expected Alternate BMCA profile in G.8275.1. This mismatch leads to incorrect PTP clock states, with master ports being marked as 'Passive' instead of 'Master'.

Resolved In: junos:23.2R2-S3 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: "ifstate" infrastructure
1882329
Minor		em0 mgmt port is unreachable after RE switchover
Product-Group=junos		On MX10008 with em0 disabled, the em0 port remains unreachable after performing RE switchover and re-enabling em0.

Resolved In: junos:25.4R1
PR NumberSynopsisCategory: PTX10K Routing Engine
1849593
Major		After code upgrade to 22.4R3-S5.11 S/Ns of both the CBs are Same
Product-Group=junosvae		As part of this PR, both control boards in the router display the same serial number, which is not expected. This happened because the system was trying to read serial numbers using a specific path (0x59 address) that isn't accessible on the backup board.

Resolved In: junos:22.4R3-S5-J3 junos:22.4R3-S6 junos:22.4R3-S7 junos:22.4R3-S8 junos:24.2R2 junos:24.4R1 junos:24.4R2 junos:25.1R1 junos:25.2R1
PR NumberSynopsisCategory: QFX analyzer, sflow
1854310
Minor		MAC resource is not been tracked properly with configurations in HWRM
Product-Group=junos		remote mac addresses learnt via evpn vxlan or any other way cannot be tracked

Resolved In:
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platfom issues
1796218
Major		The 100G VCP will go down upon restarting or upgrading the device
Product-Group=junos		On Junos QFX5K platforms in a Virtual Chassis scenario, the 100G VCP (Virtual Chassis Port) will go down and remain in a down state after a device or VCP restart or device upgrade.

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

Resolved In: evo:25.2R2-EVO evo:25.3R1-EVO junos:23.2R2-S2-J9 junos:23.4R2-S5 junos:25.2R2 junos:25.3R1
PR NumberSynopsisCategory: Resource Reservation Protocol
1881609
Minor		RSVP hello messages uses secondary address when primary/preferred address are present for same interface
Product-Group=junos		On all Junos and Junos OS Evolved platforms where RSVP (Resource Reservation Protocol) configuration is present and a RSVP enabled interface has 2 IP address of which one is configured as primary/preferred in that case the RSVP Hello message uses the secondary IP address to form neighborship.

Resolved In: evo:25.3R1-EVO junos:25.3R1
PR NumberSynopsisCategory: Generic platform and infra issues for MS-MIC and MS-MPC(XLP)
1899178
Critical		Service session drops are observed when CPU throttling is configured on platforms with service cards installed
Product-Group=junos		On all Junos MX platforms that have MS-MPC or MS-MIC service cards installed, the use of the CPU throttling can cause the production service sessions to be dropped.

Resolved In: junos:21.2R3-S10 junos:21.2R3-S6-J16 junos:22.4R3-S7-J5
1901021
Major		Service-Set Configuration Bug Leading to Kernel Panic on Junos MX
Product-Group=junos		On Junos MX platforms with MS-MPC, when new rules are added to a service-set, the configuration size increases incrementally. This growth will cause failures during the commit process, potentially leading to a kernel panic. As a result, new configurations may not be successfully applied.

Resolved In: evo:25.2R2-EVO evo:25.4R1-EVO junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: SRX branch platforms
1895179
Major		The kern.maxfiles limit exceeded observed due to log rotation resulting in unresponsive SSH
Product-Group=junos		On all Junos OS platforms, Configuring multiple syslog servers causes duplicate routing-instance map entries, leading to an eventd file descriptor leak during log rotations. Once the threshold is exceeded, the SSH connection becomes unresponsive.

Resolved In: junos:23.4R2-S6 junos:24.4R2-S2 junos:25.2R2
PR NumberSynopsisCategory: ZT/YT pfe infra issues
1885754
Major		MX304 LNS: FPC restart and aft-trio core after LMIC OIR when SI pool spans both MICs
Product-Group=junos		On MX304 routers acting as LNS, an FPC restart and aftd-trio core may occur if a MIC is offlined (LMIC OIR) while the service-device pool of SI interfaces spans both MICs on the same FPC. This may result in transient loss of subscriber sessions and service impact.

Resolved In: evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:24.4R2 junos:24.4R2-S2 junos:25.2R1-S1 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: ZT/YT pfe qos software issues
1851317
Minor		Packet drops are observed on rate-limited queues
Product-Group=junos		On MX platforms with MPC10E, MPC11E, MX304 and JNP10K-LC9600 with Class-of-Service (COS), packet drops are seen in rate-limited queues with high, medium-high or strict-high priority due to shallow buffer-size.

Resolved In: evo:25.2R1-EVO junos:23.4R2-S6 junos:24.2R2-S2 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: 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: VMHOST platforms software
1787608
Critical		The chassisd crashes at first boot up after reboot
Product-Group=junos		Additional logging has been added to the primry Routing Engine. This is to help narrow down the issue which chassisd process restarted unexpectedly at snmp_init_oids( ) function on the primary Routing Engine while booting up.

Resolved In:
PR NumberSynopsisCategory: QFX10002 Platform
1869232
Major		CRC errors increase continuously after interface flap on some 100G transceivers with Rx CDR LOL support
Product-Group=junos		On Junos PTX10002-60C, and QFX10002-60C platforms, when using 100G QSFP modules with CDR LOL support, CRC errors have been observed on odd-numbered ports, leading to traffic disruptions.

Resolved In: junos:22.4R3-S7-J1
PR NumberSynopsisCategory: usf flow and datapath issue on SPC3
1882490
Minor		BFD fail to establish over an IPsec tunnel on Juniper MX Series with the SPC3
Product-Group=junos		On Juniper MX Series platforms equipped with Services Processing Card version 3 (SPC3), Bidirectional Forwarding Detection (BFD) session establishment over an Internet Protocol Security (IPsec) tunnel may fail due to an unintended Time to Live (TTL) decrement on self-generated BFD traffic.

Resolved In: junos:21.4R3-S13 junos:23.2R2-S5 junos:23.4R2-S6 junos:24.4R2 junos:25.2R1-S2 junos:25.2R2 junos:25.3R1 junos:25.4R1
PR NumberSynopsisCategory: usf nat related issues
1881192
Major		NAT Pool Installation failure due to Service-Set name length mismatch
Product-Group=junos		On MX240, MX480, and MX960 platforms with SPC3 ( Services Processing Card 3 ) , new NAT ( Network Address Translation ) pools may fail to install, this is due to a mismatch in service-set name length handling. The system stores only 32 characters for service-set information, causing failures when names exceed this limit.

Resolved In: evo:25.4R1-EVO junos:25.2R1-S2 junos:25.2R2 junos:25.4R1

 

 

Modification History

First publication 2025-10-31 - Happy Halloween