Alert Type
SRN - Software Release Notification
Risk
Risk Description
Low/Notification
Software Release Notification
Impact
Impact Description
Low/Notification
Software Release Notification
Product Affected
ACX, EX, MX, NFX, SRX, vSRX
Alert Description
Junos Software Service Release version 23.4R1-S1 is now available for download from the Junos software download site
Download Junos Software Service Release:
Go to
Junos Platforms - Download Software page
Input your product in the "Find a Product" search box
From the Type/OS drop-down menu, select
Junos SR
From the Version drop-down menu, select your version
Click the Software tab
Select the Install Package as need and follow the prompts
Solution
Junos Software service Release version 23.4R1-S1 is now available.
23.4R1-S1 - List of Fixed issues
PR Number
Synopsis
Category: MX/PTX 20A AC power Software Issues
1768500
MX10k4/MX10k8 - AC - PSM - Partial upgrade -Unable to Track Upgrade status using "show system firmware"
Product-Group=junos
Ability to track partially upgraded PSM is not available under show system firmware. This is due to current limitation of show system firmware Show system firmware currently doesn't list PEM FRU's which are offline. This is a legacy behaviour of Junos based systems. When there is a mismatch in firmware between Instances of Primary MCU's, then PEM Fimware shutsdown the PEM output, which lead to PEM tranisitoning to offline state. Upgrade of PEM in such state, i.e, pem offline due to firmware mismatch is now allowed in Junos. But tracking of firmware upgrade for these PEMs in such state, is not avaialble under show system firmware because of "show system firmware" legacy behaviour of not listing offline pem's. As a workaround user can track the upgrade, via chassid logs with below prints, Example chasd logs print: Nov 9 12:28:18 pem_tvp_fwupgrade_timer: FW Upgrade Done Nov 9 12:29:18 pem_tvp_fwupgrade_timer: FW Upgrade Done
PR Number
Synopsis
Category: Accounting Profile
1778726
Traffic statistics display issue may observed on AE bundle for child links with MPC10E linecard enabled
Product-Group=junos
On All Junos and Evolved platforms with MPC10E linecard enabled, the traffic statistics does not show on the AE (Aggregated Ethernet) bundle child members when the member links are deleted from the line-card, whereas the physical link would show the Input/output traffic statistics. There would not be any impact to the functionality of the service, only rate will not show when the command "show interface cli" is given.
PR Number
Synopsis
Category: "agentd" software daemon
1765344
The telemetry stops streaming data when the jsd CPU utilization goes high
Product-Group=junos
On Junos and Junos Evolved platforms, when it enables telemetry and uses the gRPC dial-out method, jsd might be stuck with high CPU utilization, and stop streaming data.
1772435
"/components/component/power-supply/" sensor leaves and values are not streamed in gNMI and the data is streamed via gRPC in latest master 24.1 builds
Product-Group=junos
On all evo platforms, power-supply data is not getting streamed via gnmi. Issue shall be resolved in D41
PR Number
Synopsis
Category: a20a40 specific issue
1787219
Insufficient power alarm observed in SRX5K platforms
Product-Group=junos
On Junos SRX5600 and SRX5800 platforms, FPC (Flexible PIC Concentrator) will not come online due to insufficient power, leading to service disruption.
PR Number
Synopsis
Category: Border Gateway Protocol
1779533
The RPD crash is observed on Junos and Junos Evolved platforms in Route Reflector scenario
Product-Group=junos
On all Junos and Junos Evolved platforms, the RPD (Routing Protocol Daemon) crash can be seen in BGP-multipath scenario if it has more than 512 routes for a prefix. The RPD crash will cause a traffic drop but the system will self-recover.
PR Number
Synopsis
Category: Captive Portal, Content Delivery Daemon, and Service Plugin
1781264
23.4R1:SFW:commit should fail after deleting existing service-set ss1 and adding a new service set ss2 on a same interface with SFW configuration, but commit success which is unexpected behavior.
Product-Group=junos
commit should fail after deleting existing service-set ss1 and adding a new service set ss2 on a same interface with SFW configuration, but commit success which is unexpected behavior.
PR Number
Synopsis
Category: MX304 Chassis specific platform
1731237
MX304 Major Alarm " Host 0 detected AER correctable error" after RE switchover.
Product-Group=junos
MX304 Major Alarm " Host 0 detected AER correctable error" after RE switchover.
PR Number
Synopsis
Category: CoS support on DNX
1770491
Traffic convergence is longer than usual after the CoS rewrite
Product-Group=junos
On ACX5448 and ACX710 platforms, traffic convergence takes more time than the expected 50ms i.e. traffic loss is more than expected observed for CoS (Class-of-service) rewrite change after a link failover in the MPLS (Multiprotocol Label Switching) scenario with FRR (Fast Reroute) and LSP (Label-Switched Path) link-protection configured.
1773980
Traffic forwarding will be affected over physical interface if user try to configure "hierarchical-scheduler" knob on AE member interface
Product-Group=junos
On Junos Evolved ACX and PTX platforms, Traffic forwarding will be affected over physical interface if user try to configure "hierarchical-scheduler" knob on AE(aggregate-ethernet) enabled physical interface.
PR Number
Synopsis
Category: Dynamic rendering infrastructure
1745615
Telemetry data is not exported in an IS-IS scaled Segment Routing scenario
Product-Group=junos
On all Junos and Junos OS Evolved platforms configured with SR-ISIS and with gRPC/gNMI telemetry, subscription to the path: "/junos/services/segment-routing/sid/usage/" will not work and the output could not be proper. The issue could happen only in scaled configuration (Approximately, 4000 or more per-sid ingress sensors and 4000 or more IPv4/IPv6 per-sid egress sensors are configured).
PR Number
Synopsis
Category: JDHCP daemon for EVO platform to handle DHCP protocol
1775275
EVO(EVPN Fabric): DHCP packets are getting relayed even after deleting the dhcp relay configuration from the leaf
Product-Group=junos
TBA
PR Number
Synopsis
Category: jdhcpd daemon refactored for evo
1730717
We may encounter jdhcpd core during initialization. The core in rare, and there is no service impact because of this core (as the process recovers immediately)
Product-Group=junos
We may encounter jdhcpd core during initialization. The core in rare, and there is no service impact because of this core (as the process recovers immediately)
PR Number
Synopsis
Category: mgd, ddl, odl infra issues
1783888
[Junos OS Evolved] Traceoptions log sometimes shows UTC timestamp, although non UTC time-zone is configured
Product-Group=junos
On all Junos OS Evolved platforms, traceoptions log sometimes shows UTC timestamp, although non UTC time-zone is configured.
PR Number
Synopsis
Category: EX4100 RE, Platform Infra, Drivers
1775479
Peer device ports connected to Gigabit Physical ports of EX4100 transition to up state momentarily during reboot of EX4100
Product-Group=junosvae
When Junos EX4100 undergoes reboot or power cycle, peer device ports connected to GPHY (Gigabit Physical) ports of EX4100 transition to up state momentarily and can impact traffic on the peer device.
PR Number
Synopsis
Category: EX4400 PFE software
1754344
EX4400 Platforms Virtual Chassis (VC) - HGOE enabled causes system crash when system memory becomes unavailable for cumulative protocol daemons traffic.
Product-Group=junos
When HiGig Over Ethernet (HGOE) is enabled in EX4400 platforms system will crash when Route Engine (RE) experiences high memory utilization due Broadcom restriction to manage packets in one array.
PR Number
Synopsis
Category: EX4400 platform
1754548
EX4400 Virtual Chassis has boot-up issues
Product-Group=junos
EX4400 could be stuck during boot, when one end of the twisted pair cable is connected to the primary console port and the other end is left unconnected/dangling.
PR Number
Synopsis
Category: PFE EVPN / VxLAN related issues on EX platforms
1788573
Traffic loss after PIC restart if the packet has a VLAN tag of 4095
Product-Group=junos
On EX4400, EX4100, EX4650, and QFX5120 platforms in the EVPN-VXLAN (Ethernet VPN - Virtual Extensible LAN) IPv6 (Internet Protocol Version 6) underlay environment, after the PIC (Physical Interface Card) restart few AE (Aggregated Ethernet) member interfaces go down and comes back up traffic loss is observed if the packet has a VLAN tag of 4095. The issue happens because PFE (Packet Forwarding Engine) will not receive any new next-hop addition to PFE as the AE interface is already present in PFE as next-hop.
PR Number
Synopsis
Category: Express PFE L2 fwding Features
1779527
At the interface level, only half of the traffic is policed when applying a policer
Product-Group=junos
On QFX10002-36q, QFX10002-72Q, QFX10008 and QFX10016 platforms, when applying a policer at the interface level only half of the traffic is policed.
PR Number
Synopsis
Category: Express PFE L3 Multicast
1774562
PIM join are not learnt for multicast IPs
Product-Group=junos
On Junos PTX platforms, with PIM BIDR (Protocol Independent Multicast- Bidirectional) mode with "set protocols pim rp bidirectional address <> group-ranges <>" configuration, PIM/MLD joins will not be learnt for multicast IPs other than link local IP and MY IP which will lead to traffic impact. Also, lo0 filter which were introduced with PR 1701756 for IGMP and MLD will be applied only for MY IPs and Link local IPs. For any other IPs other than above, lo0 filter will not work.
PR Number
Synopsis
Category: Port Mirroring feature on express PFE
1508627
Serviceability:Good to have CLI validation for remote port mirroring with TOS/DSCP setting
Product-Group=junos
Show forwarding-options port-mirroring shows correct NH ip and destination (NULL) to NA in qfx10K remote port-mirroring
PR Number
Synopsis
Category: FIPS related issues
1723499
Transition Junos OS kernel random number generator from hashing algorithm SHA-256 to SHA-512
Product-Group=junos
On all platforms except those running an ARM processor, the kernel random number generator has been modified to use the cryptographically stronger hashing algorithm SHA-512. This is to comply with the "Commercial Solutions for Classified (CSfC) Selections for Internet Protocol Security (IPsec) Virtual Private Network (VPN) Gateways" standard dated October 3, 2022.
PR Number
Synopsis
Category: ISIS routing protocol
1760334
Routing loop will be observed during ISIS-FRC implementation
Product-Group=junos
On Junos and Junos Evolved platforms, routing loop will be observed, when configuring FRC (Flood-Reflector Client) and processing anycast Layer 2 prefix advertisements, it leads to the installation of ISIS routes with incorrect nexthops .
1778841
With protocol ISIS configured, any new LSP generation triggers SPF
Product-Group=junos
On all Junos platforms, with ISIS configured, when commit or any operation that attempts for LSP generation, an SPF is triggered.
1781103
Gradual memory leak seen in the rpd process on Junos based PTX and QFX10002/10008 platforms
Product-Group=junos
On Junos based PTX and QFX10002/10008 platforms configured as Intermediate System to Intermediate System (ISIS) Flood-Reflectors (FR client/servers) and running images between 20.3X75-D44.4 and 20.3X75-D44.8, the Routing Protocol Daemon (rpd) process shows gradual and consistent increase in memory utilisation which eventually leads to swap memory exhaustion and the rpd process restarts impacting service. The leak is caused due to special handling of ISIS-FR routes during installation.
1782887
Traffic blackhole due to Flex-algo not removing stale entries from ISIS database
Product-Group=junos
On all Junos and Junos Evolved platforms, in an ISIS scenario using Flex-algo , the system does not remove the stale (outdated) entries from the ISIS database causes traffic blackholing. This issue could lead to some traffic loss, as the routing information stored in the ISIS database does not get properly updated.
PR Number
Synopsis
Category: jdhcpd daemon
1743611
DNS received through DHCP is lost after a commit and not able to ping internet
Product-Group=junos
If name-server information is changed via CLI after the DHCP subscribers are up, DNS obtained from DHCP server is overwritten by local config. This may result in DNS look up failures in some cases.
PR Number
Synopsis
Category: Flow Module
1761542
In a chassis cluster setup the flowd crashes and SPC cards will fail
Product-Group=junos
On SRX platforms, in a chassis cluster setup configured in Active/Active mode, the fabric forward packet enters the flow module causing the flow processing daemon (flowd) to crash, impacting the traffic forwarding and failing the Services Processing Card (SPC).
PR Number
Synopsis
Category: IPSEC/IKE VPN
1778106
SCTP does not work correctly on SRX platforms
Product-Group=junosvae
On SRX1600, SRX2300 and SRX4300 platforms, SCTP (Stream Control Transmission Protocol) does not work correctly. SCTP packets are dropped by Intel ddp driver.
PR Number
Synopsis
Category: Security platform jweb support
1779376
Junos OS: SRX Series and EX Series: J-Web doesn't sufficiently sanitize input to prevent XSS (CVE-2024-21620)
Product-Group=junos
An Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in J-Web of Juniper Networks Junos OS on SRX Series and EX Series allows an attacker to construct a URL that when visited by another user enables the attacker to execute commands with the target's permissions, including an administrator. Please refer to https://supportportal.juniper.net/
JSA76390
[juniper.net]
for more information.
PR Number
Synopsis
Category: Layer2 forwarding on EX/NTF/PTX/QFX
1790064
The l2ald process will crash, with rapid configuration changes followed by rpd and l2ald restart process
Product-Group=junos
On all Junos and Junos OS Evolved platforms with EVPN -VXLAN and high scaling configuration, rapid configuration changes followed by restart of rpd and l2ald will result in l2ald process crash and traffic drop will be observed.
PR Number
Synopsis
Category: lacp protocol
1773827
The LAG with member interface enabled with 'force-up' can flap after switchover
Product-Group=junos
On Junos and Junos Evolved QFX/EX platforms if the member link of an AE (Aggregation Ethernet) interface is configured with force-up, the LAG (Link Aggregation Group) can flap after switchover through GRES (Graceful Routing Engine Switchover) or during ISSU (In Service Software Upgrade). Traffic that goes through the LAG will be dropped when the interface flaps.
1783793
All AEs bundles configured in Active-Standby mode for EVPN-MPLS routing-instances will flap on the first commit post a fresh system reboot
Product-Group=junos
On all Junos MX and EX platforms with MPC family of line cards, all the Aggregated-Ethernet (AEs) bundles configured in Active-Standby mode for Ethernet Virtual Private Network-Multiprotocol Label Switching (EVPN-MPLS) routing-instances on the system will flap on the first commit after a fresh system reboot.
PR Number
Synopsis
Category: Issues related to Junos licensing infrastructure
1775463
The RE goes into amnesiac mode upon license check validation failure
Product-Group=junos
On all Junos Platforms, the RE (Routing Engine) goes into amnesiac mode upon reboot if node locked license is configured via the "set system license keys key <>".
PR Number
Synopsis
Category: MPC11 ULC fabric software related issues.
1762114
Linecard loses all fabric planes when another linecard is powered off ungracefully
Product-Group=junos
On MX2020/MX2010/MX10K4/MX10K8 platforms and MPC11E, LC9600, LC4800 line cards , linecard loses all fabric planes (no links active) and takes all interfaces down when another linecard is powered off ungracefully .
PR Number
Synopsis
Category: For multicast snooping on MX
1781059
Multicast traffic loss observed when IGMP/MLD snooping is toggled on a VPLS routing-instance
Product-Group=junos
On all Junos and Junos Evolved platforms, when IGMP (Internet Group Management Protocol) or MLD (Multicast Listener Discovery) Snooping is toggled on a specific routing-instance with snooping already enabled on multiple instances with VPLS (Virtual Private LAN Services) configured, it leads to multicast control and data traffic forwarding issues.
PR Number
Synopsis
Category: Track Mt Rainier RE platform software issues
1782062
The interface fxp0 deactivation or activation is not captured due to improper date format
Product-Group=junosvae
On all VMhost platforms, the interface fxp0 state is not captured since the script to bring up the interface is not parsing the output from the date field.
PR Number
Synopsis
Category: QFX L2 PFE
1781955
A few AE interfaces will drop traffic when a large number of AE interfaces are deleted and added back
Product-Group=junos
On EX4100, EX4100 Multigigabit, EX4100-F, EX4400, EX4400 Multigigabit, EX4650-48Y, QFX5120-48Y, QFX5120-32C, QFX5120-48T, QFX5110 and QFX5120-48YM platforms with Ethernet VPN-Virtual Extensible LAN (EVPN-VxLAN) configured, a few AE interfaces will drop traffic when a large number of Aggregated Ethernet (AE) interfaces are deleted and added back. When this issue happens AE interfaces will be UP but traffic would be dropped.
PR Number
Synopsis
Category: QFX L3 data-plane/forwarding
1782762
MTU Adjustment on Junos QFX5K platforms with GRE Causes FPC and Link Partner FPC Reboots
Product-Group=junos
On Junos QFX platforms with Generic Routing Encapsulation (GRE) tunnels enabled, when attempting to adjust the MTU (Maximum Transmission Unit) configuration of a physical interface, a reboot of the FPC is triggered which would leads to crash and impacts the traffic.
PR Number
Synopsis
Category: QFX EVPN / VxLAN
1774366
The dcpfe process crash due to stale memory
Product-Group=junos
On Junos QFX platforms, stale memory references are causing dcpfe crashes triggering PFE (Packet Forwarding Engine) to restart resulting in traffic disruptions.
1778725
Traffic drop is observed when VIPs become unreachable due to GARP sent on VLANs to which the VIP does not belong
Product-Group=junos
Under a rare scenario, on all Junos and Junos Evolved platforms configured with EVPN-VXLAN (Ethernet Virtual Private Network-Virtual Extensible Local Area Network) type 5 routes, Bridge-Domain, IRB (Integrated Routing and Bridging) and having L4 (Layer 4 device like an application load balancer) devices as single-homed with each border leaf and when VIP (Virtual Internet Protocol) entries are learnt on a leaf and L4 failover happens, it is observed that the VIPs announced by GARP (Gratuitous Address Resolution Protocol) is sent on VLANs that the VIP does not belong to and the incorrect GARP is not handled as per the expectation.
1781691
With EVPN-VXLAN configured, when a Layer 3 interface or underlay IRB interface deletion results in a traffic blackhole
Product-Group=junos
On QFX5K and EX4K platforms in the EVPN-VXLAN (Ethernet Virtual Private Network - Virtual Extensible LAN) environment, a traffic blackhole is observed when we delete the L3 or underlay IRB (Integrated Routing and Bridging) interface, both the L3 egress and ingress hardware interface are deleted.
1783397
The fxpc process crash and the device reboots after deleting Aggregated Ethernet (AE) Interface along with its associated physical interface and then applying new interface configuration on the associated physical interface in an EVPN-VXLAN scenario
Product-Group=junos
On an Ethernet Virtual Private Network (EVPN) / Virtual eXtensible Local-Area Network (VXLAN) scenario, after removing an Aggregated Ethernet (AE) Interface along with its associated physical interface on a QFX5k series device and then applying any configuration to the physical interface, the fxpc process crashes and the device undergoes an automatic reboot.
PR Number
Synopsis
Category: RPD Next-hop issues including indirect, CNH, and MCNH
1768604
Traffic blackhole due to incorrect NH entries with incorrect filter-id in CCNH table
Product-Group=junos
On all Junos platforms, the firewall filter mapping in Routing protocol process(rpd) table goes out of sync with the Dynamic Firewall process(dfwd) and hold old filter-id value in filter entry which leads to incorrect next-hop(NH) entries in Chained composite next hops(CCNH).
1785884
The rpd crash is observed due to segment fault
Product-Group=junos
On Junos OS Evolved platforms, when no acknowledgment is received from PFE (Packet Forwarding Engine) within timeout results in the rpd (Routing Process Daemon) crash. This issue happens when routes requesting acknowledgment do not receive acknowledgment leading to segment fault.
PR Number
Synopsis
Category: Shard routing infrastructure within RPD
1773820
The rpd process crashes with firewall filter configuration
Product-Group=junos
On all Junos and Junos Evolved platforms, the rpd process crashes when firewall filter is configured. Due to this all the routing protocols will be impacted causing traffic loss.
PR Number
Synopsis
Category: PTX10K specific platform PRs
1767840
Obsidian_PTX: Ambient-temperature value constantly changes after config
Product-Group=junos
"set chassis ambient-temperature" is not supported for PTX10004/8/16 platform. It will be removed in future releases.
PR Number
Synopsis
Category: Issues related to control plane security
1781732
Junos OS and Junos OS Evolved: Impact of Terrapin SSH Attack (CVE-2023-48795)
Product-Group=junos
An Improper Validation of Integrity Check Value vulnerability in OpenSSH before 9.6 of Juniper Networks Junos OS and Junos OS Evolved allows a remote attacker to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka the Terrapin Attack. Please refer to https://supportportal.juniper.net/
JSA76462
[juniper.net]
for more information.
PR Number
Synopsis
Category: SRX-1RU infrastructure SW defects
1784983
Chassis alarm not present for if /var partition usage exceeds 100%
Product-Group=junos
When /var partition disk space is greater than 100%, "RE 0 /var partition usage is high" chassis alarm gets cleared
PR Number
Synopsis
Category: SRX-1RU platfom datapath SW defects
1775083
Traffic drop observed right after boot up on Junos SRX 4600 platforms
Product-Group=junosvae
On SRX 4600 platforms running the Field Programmable Gate Array (FPGA) firmware versions 163, 165, 171, 175 the Packet Forwarding Engine (PFE) may experience a 25% drop in performance after bootup.
PR Number
Synopsis
Category: ZT/YTpfe bridging, learning, stp, oam, irb software
1761792
High heap memory utilization is observed on FPC's, when high-scaled logical interfaces and scaled vlan inner-list per logical interface is configured
Product-Group=junos
On all MX platforms with line cards MPC10/MPC11/LC9600/MX304, high heap memory utilization on FPC with high-scaled double-tagged IFL (logical interface) configuration. The issue occurs because the configuration of scaled inner vlan-list (a large range) along with corresponding high-scaled logical interfaces creates as high as 14 million or more double-tagged streams. This results in high memory utilization on the FPC.
PR Number
Synopsis
Category: Trio pfe stateless firewall software
1738672
FPC crashes due to back-to-back GRES
Product-Group=junos
On line cards such as MPC5E/MPC7E/LC480/MPC10E/11E/LC9600 and MX304 platforms, when multiple times Graceful Routing Engine Switchover (GRES) is performed, all the FPCs crashed.
PR Number
Synopsis
Category: Trio pfe bridging, learning, stp, oam, irb software
1729970
L2-Trans: pm_soam_frame_rx count is not incrementing as expected
Product-Group=junos
L2-Trans: pm_soam_frame_rx count is not incrementing as expected
1763325
VRRP host inject packets get corrupted when preserve-nexthop-hierarchy knob is configured
Product-Group=junos
On MX platforms with Junos, on MPLS Networks, VRRP host inject packets get corrupted when "preserve-nexthop-hierarchy " knob is configured and VRRP (Virtual Router Redundancy Protocol) will not work correctly.
PR Number
Synopsis
Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1771991
RSI is more than 3.7 GB
Product-Group=junos
The CLI command output of "show system processes extensive" should not have an 'srd' entry on PTX.
1772201
unexpected commit error - error: VLAN-ID must be specified on tagged ethernet interfaces
Product-Group=junos
unexpected commit error like 'error: VLAN-ID must be specified on tagged ethernet interfaces', due to 'commit check' reset internal flag incorrectly after load overide configuration in rare condition.
PR Number
Synopsis
Category: Web-Management UI
1776688
High storage is reported in /var/jail/log due to http.log and http-trace.log on all Junos platforms
Product-Group=junos
Disk usage will be high in /var/jail/log due to http.log and http-trace.log on all Junos platforms. Further install will be blocked until this folder is cleaned up.
23.4R1-S1 - List of Known issues
PR Number
Synopsis
Category: QFX VC Datapath
1785882
JDI-RCT : IPCLOS:Azurite:Partial continuos traffic drop observed on ipv4 and ipv6 streams (framing errors)
Product-Group=junos
With SR4 optics on QFX5210 some times we can see Partial continuous traffic drop observed on ipv4 and ipv6 streams (framing errors)
Resolved In:
PR Number
Synopsis
Category: MX304 line card platform software
1758480
JDI-REGRESSION: MX304 core-spmbpfe-bugatti-pvl-b1-node seen in re1
Product-Group=junos
JDI-REGRESSION: MX304 core-spmbpfe-bugatti-pvl-b1-node seen in re1
Resolved In:
junos:22.4R3 junos:23.2R2
PR Number
Synopsis
Category: EX4100 RE, Platform Infra, Drivers
1775479
Peer device ports connected to Gigabit Physical ports of EX4100 transition to up state momentarily during reboot of EX4100
Product-Group=junos
When Junos EX4100 undergoes reboot or power cycle, peer device ports connected to GPHY (Gigabit Physical) ports of EX4100 transition to up state momentarily and can impact traffic on the peer device.
Resolved In:
junos:22.3R3-S3 junos:22.4R3-S2 junos:23.2R2 junos:23.4R1-S1 junos:23.4R2 junos:24.1R1 junos:24.2R1
PR Number
Synopsis
Category: EX4400 platform
1754931
The transceiver fails to get detected after the system reboot
Product-Group=junos
On certain EX platforms, when the device is rebooted, transceivers will not be detected. Failing to detect the transceiver results in no IFD.
Resolved In:
junos:21.4R3-S6 junos:22.1R3-S5 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:22.4R3-S2 junos:23.2R2 junos:23.3R2 junos:23.4R1 junos:24.1R1
1758042
EX-hardening: EX4400: set chassis config-button no-clear is not working
Product-Group=junos
EX-hardening: EX4400: set chassis config-button no-clear is not working
Resolved In:
junos:22.4R3-S2 junos:23.2R2 junos:23.4R2 junos:24.2R1
PR Number
Synopsis
Category: SRX4100/SRX4200 platform software
1739559
SRX4100/4200 accepts the datapath-debug configuration although it does not support it
Product-Group=junos
It is possible to set and commit the datapath-debug configuration on platforms SRX4100/SRX4200 although datapath debugging is not supported on those platforms. because of this unsupported configuration being accepted the RE (Routing Engine) load can go high and cause traffic outage. The workaround is to remove the datapath-debug configuration and perform a commit.
Resolved In:
junos:20.4R3-S8 junos:21.2R3-S6 junos:21.2R3-S8 junos:21.3R3-S5 junos:21.4R3-S7 junos:22.1R3-S4 junos:22.2R3-S2 junos:22.3R3-S1 junos:22.4R3-S2 junos:23.1R2 junos:23.2R1-S1 junos:23.3R1 junos:23.4R1 junos:23.4R2 junos:24.1R1 junos:24.2R1
PR Number
Synopsis
Category: ISIS routing protocol
1781138
The rpd process keeps on restarting on all Junos and Junos OS Evolved platforms due to memory exhaustion
Product-Group=junos
On all Junos and Junos OS Evolved platforms with Topology-Independent Loop-Free Alternate (TILFA) enabled and in a grid topology interconnect involving several nodes and links (more specifically this is seen with a 30x30 grid topology), the routing protocol daemon (rpd) process keeps on restarting due to high memory exhaustion.
Resolved In:
evo:23.2R2-EVO evo:23.4R2-EVO evo:24.1R1-EVO evo:24.2R1-EVO junos:22.4R3-J2 junos:22.4R3-S2 junos:23.2R2 junos:23.4R2 junos:24.1R1 junos:24.2R1
PR Number
Synopsis
Category: Firewall Authentication
1732210
23.1R2:ISSU:USERFW-CP: Clearpass Auth entry's are getting deleted post successful ISSU
Product-Group=junos
On SRX devices on aruba-clearpass webapi configuration set system services webapi <*> authentication entries could be lost during ISSU or during Junos version upgrades to 23.1 from prior versions. Due to this issue any dataplane traffic using the ClearPass Authentication entries will require reauthentication.
Resolved In:
junos:23.4R2 junos:24.1R1
PR Number
Synopsis
Category: Issues related to Junos licensing infrastructure
1775463
The RE goes into amnesiac mode upon license check validation failure
Product-Group=junos
On all Junos Platforms, the RE (Routing Engine) goes into amnesiac mode upon reboot if node locked license is configured via the "set system license keys key <>".
Resolved In:
evo:23.2R2-EVO evo:23.4R1-S1-EVO evo:23.4R2-EVO evo:24.1R1-EVO junos:21.4R3-S7 junos:22.1R3-S6 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R2-S1-J7 junos:22.4R3 junos:23.2R2 junos:23.4R1 junos:23.4R2 junos:24.1R1
PR Number
Synopsis
Category: PTX1000 platform
1653316
Junos OS: PTX Series: In an FTI scenario MPLS packets hitting reject next-hop will cause a host path wedge condition (CVE-2024-21600)
Product-Group=junos
An Improper Neutralization of Equivalent Special Elements vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on PTX Series allows a unauthenticated, adjacent attacker to cause a Denial of Service (DoS). Please refer to https://supportportal.juniper.net/
JSA75741
[juniper.net]
for more information.
Resolved In:
junos:18.2X75-D67 junos:19.1R3-S11 junos:19.2R3-S8 junos:19.3R3-S9 junos:19.4R3-S11 junos:20.2R3-S7 junos:20.3R3-S6 junos:20.3X75-D36 junos:20.3X75-D41 junos:20.4R3-S8 junos:21.1R3-S4 junos:21.2R3-S6 junos:21.2X32-D10 junos:21.3R3-S3 junos:21.4R3-S5 junos:22.1R2-S2 junos:22.1R3 junos:22.2R2-S1 junos:22.2R3 junos:22.3R1 junos:22.4R2 junos:22.4R3
PR Number
Synopsis
Category: Multicast for L3VPNs
1747703
The MVPN traffic starts dropping after RE switchover
Product-Group=junos
On all Junos and Junos Evolved platforms with Dual RE and MVPN ((Multicast Virtual Private Network) enabled, when the user initiates a GRES ( Graceful Routing Engine Switchover) switchover, it triggers a route change from the MVPN . During this process, there's a gap where traffic loss is observed because the flood next hop pointed to by the route gets deleted.
Resolved In:
evo:24.2R1-EVO junos:24.2R1
PR Number
Synopsis
Category: QFX5200/5110/5120/5210 Platform optics related issues
1726707
On QFX5120-48y-8c platform 10G ports go down in a port group if 25G SFP is inserted in the same group
Product-Group=junos
QFX5120-48y-8c platform, if a 25G SFP is inserted in 10G speed configured port which is also a part of port group, all the interfaces in same port group will go down. Traffic will be impacted as all the interfaces in port group is going down.
Resolved In:
junos:22.2R3-S3 junos:22.4R3 junos:23.2R2 junos:23.4R2 junos:24.1R1
PR Number
Synopsis
Category: QFX5200/5110/5120/5210 Platfom issues
1758400
JUNOS_REG: QFX51200-48YM: Fan status output was not same after/before device vc-switch over.
Product-Group=junos
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
Resolved In:
PR Number
Synopsis
Category: Bug and Review Tracking for Segment routing traffic eng
1763406
LDP traffic to destination route might be lost when TI-LFA is configured
Product-Group=junos
On all Junos and Junos OS Evolved platforms, when LDP tunnel over SR-TE route or over RSVP and LFA/rLFA/TI-LFA backup path for the same destination is configured, or if rLFA/LFA with L-ISIS as backup path is configured, the route to the destination is missing. LDP route for the destination is deleted because SR-TE LSP next hop is deleted by processing L-ISIS route with the backup path. Due to this LDP route gets deleted, LDP traffic to destination route is lost.
Resolved In:
evo:21.4R3-S6-EVO evo:22.1R3-S5-EVO evo:22.3R3-S2-EVO evo:22.4R3-EVO evo:23.2R2-EVO evo:23.4R1-EVO evo:23.4R2-EVO evo:24.1R1-EVO junos:21.4R3-S6 junos:22.1R3-S5 junos:22.3R3-S2 junos:22.4R3 junos:23.2R2 junos:23.4R1 junos:23.4R2 junos:24.1R1
1778946
The SRV6 traceroute with more than 3 SIDs does not work
Product-Group=junos
On Junos and Junos Evolved PTX platforms, a packet containing SRH (Segment Routing Header) with more than three SIDs (Segment Identifiers) causes the ICMP (Internet Control Message Protocol) header to fall outside the 128-byte range leading to potential packet drop.
Resolved In:
evo:23.4R2-EVO evo:24.1R1-EVO junos:23.4R2
PR Number
Synopsis
Category: SRX branch platforms
1714620
High latency will be observed while pinging to peer device
Product-Group=junos
On Branch SRX Platforms, The delay will be observed while pinging to peer device due to high latency when VLAN(Virtual Local Area Network) tagged DHCP(Dynamic Host Configuration Protocol) packets arrive at IRB (Integrated Routing and Bridging) interface.
Resolved In:
junos:21.2R3-S8 junos:22.4R3-S2 junos:23.4R2 junos:24.2R1
PR Number
Synopsis
Category: SRX-1RU platfom datapath SW defects
1775083
Traffic drop observed right after boot up on Junos SRX 4600 platforms
Product-Group=junos
On SRX 4600 platforms running the Field Programmable Gate Array (FPGA) firmware versions 163, 165, 171, 175 the Packet Forwarding Engine (PFE) may experience a 25% drop in performance after bootup.
Resolved In:
junos:21.2R3-S8 junos:21.4R3-S7 junos:22.1R3-S6 junos:22.2R3-S3 junos:22.2R3-S4 junos:22.3R3-S3 junos:22.4R3-S2 junos:23.2R2 junos:23.2R2-S1 junos:23.4R1-S1 junos:23.4R2 junos:24.1R1 junos:24.2R1
PR Number
Synopsis
Category: ZT/YT LUSS SW driver
1765394
Fatal(MQSS and XQSS errors) error on FPC leads to PIC card offline and traffic impact
Product-Group=junos
On Junos MX304 and MX platforms with LC9600 linecards, With the current error handling mechanism upon receiving fatal error on Flexible pic concentrators(FPC), leads to disable both the Packet Forwarding Engine(PFE) on a Physical Interface Cards(PIC) card and seen traffic impact.
Resolved In:
evo:24.1R1-EVO junos:24.1R1
PR Number
Synopsis
Category: MX10K linecard
1781424
Interfaces may not come up post pfe-reset to correct any major errors
Product-Group=junos
When below configuration is present to reset the PFE to recover for any major PFE errors reported from the FPC, "set chassis fpc error major action reset-pfe" interfaces do not come up after the pfe-reset operation after encountering major error in pfe. Workaround : None. To recover from this condition, you need to restart the FPC (this will affect the traffic on the other interfaces of the FPC, which were not impacted by the PFE errors).
Resolved In:
junos:23.2R2 junos:23.4R2
Modification History
First publication 2024-03-27
23.4R1-S1: Software Release Notification for JUNOS Software