Alert Type

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

Product Affected

ACX EX MX NFX PTX QFX SRX vSRX platforms running JUNOS software

Alert Description

Junos Software Service Release version 20.4R3-S10 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 needed and follow the prompts

Solution

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

20.4R3-S10 - List of Fixed issues 

PR NumberSynopsisCategory: EX4300 Platform
1747374SFP modules are not detected after upgrade
Product-Group=junos
After an upgrade, the SFP modules are not detected in case of EX4300 platforms and the ports remain down impacting traffic.
PR NumberSynopsisCategory: SRX Gen-3 RE, leveraged from Point Success Mt.Rainier
1774760RE switchover observed in SRX5K platforms when ethernet switchports failure scenario on SCB
Product-Group=junos
On SRX5K platforms when all ethernet switch ports on Switch Control Board(SCB) fail, it triggers the Routing Engine (RE) switch over and RE0 is stuck in "Disabled" state. As RE0 is disabled and RE1 does have the functionality to coordinate chassis. No PIC will turn up which were failed and triggered the failover and traffic impact will be there for those particular ports and the complete service impact will be there if RE1 had any issue when RE0 is in disable state. RE0 did not recover by its own from the disabled state until manual reboot is done.
PR NumberSynopsisCategory: SPC3 HW and SW Issues
1641793Traffic might be dropped due to the RX queue being full
Product-Group=junos
Incoming packets might be sent to RX queues of core0 or core14 mistakenly, might result in the queue buffer full and the packets getting dropped.
PR NumberSynopsisCategory: Application Quality of Experience
1743107flowd process crash observed in Junos branch SRX platforms
Product-Group=junos
This issue is observed on Junos SRX platforms supporting SD-WAN (Software-defined Wide Area Network) like SRX300, SRX320, SRX340, SRX345, SRX380, SRX550, SRX1500, SRX4100, SRX4200, SRX4600, SRX5600, SRX5800, cSRX and vSRX in AppQoE (Application Quality of Experience) scenario where the passive probe session of SD-WAN is not closed gracefully. This results in flowd crash and impacts user traffic.
PR NumberSynopsisCategory: A15 specific issue
1738188Failover can be seen on SRX5K cluster with SPC2 cards while executing RSI
Product-Group=junos
On all SRX5000 series platforms with SPC2 cards configured in a chassis cluster, when RSI is being collected which has the command 'i2csc fpc' in the script, an interrupt storm generates a CB (Control Board) alarm which triggers a failover. Intermittent traffic disruption could be seen till the failover is complete.
PR NumberSynopsisCategory: a20a40 specific issue
1645817Line cards fail to come online state when the device is powered on with multiple cards
Product-Group=junos
On SRX5k and MX240/MX480/MX960 platforms, when device is powered on with multiple line cards, power might not be sufficient and few line cards fail to come into online state.
1663839Syslog message CHASSISD_IPC_WRITE_ERR_NULL_ARGS are observed at commit
Product-Group=junos
Syslog message CHASSISD_IPC_WRITE_ERR_NULL_ARGS is observed at commit on SRX5K platforms. This is caused by unsupported chassis component connection on SRX5K platforms during commit checks. This syslog message is informational only for SRX5K, and was removed.
1681701"%DAEMON-4: Set system alarm failed: Operation not supported by device" message is seen on high end SRX
Product-Group=junos
On high end SRX platform, "%DAEMON-4: Set system alarm failed: Operation not supported by device" message is seen when system/chassis alarm is generated
1775880A flowd crash is observed if CP receives the packets due to some hardware memory issue
Product-Group=junos
On SRX5K platforms with SPC3 and SPC2 cards, flowd crash will be observed if CP (Central Point) receives the packets due to some hardware memory issue either on IOC (I/O card) or SPC (Services Processing Card) which requires session lookup.
PR NumberSynopsisCategory: COS for australia platform
1596172"show interfaces queue < interface>" command output not correctly displaying bps values for throughput higher than 4.25Gbps
Product-Group=junos
"show interfaces queue < interface>" command output not correctly displaying bps values for throughput higher than 4.25Gbps. This behaviour is only present for throughput higher than 4.25Gbps per interface output queue.
PR NumberSynopsisCategory: Bi Directional Forwarding Detection (BFD)
1698373A few BFD sessions might flap after FPC reload and stabilization
Product-Group=junos
On all Junos platforms and Junos Evolved with scaled BFD sessions, FPC reload/restart results in few BFD session flap.
PR NumberSynopsisCategory: Border Gateway Protocol
1709837Junos OS and Junos OS Evolved: A crafted BGP UPDATE message allows a remote attacker to de-peer (reset) BGP sessions (CVE-2023-4481)
Product-Group=junos
An Improper Input Validation vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). Please refer to https://supportportal.juniper.net/JSA72510 [juniper.net] for more information.
1775548The rpd crash can be seen with a scaled BGP sharding setup
Product-Group=junos
On all Junos and Junos OS Evolved platforms the rpd (Routing Protocol Daemon) crash can be seen in scaled setup. The issue will be seen in the BGP (Border Gateway Protocol) RIB (Routing Information Base) sharding scenario. This issue is very unlikely to be encountered.
1779533The 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 NumberSynopsisCategory: Enhanced Broadband Edge support for cos
1769800The traffic shaping rate gets impacted in a subscriber scenario on Junos MX BBE platforms
Product-Group=junos
The traffic shaping rate gets impacted on Junos MX BBE (Broadband Edge) platforms configured with COS (Class Of Service) and when TLV (Type, Length, and Value)#98 is configured on the external OLT (Optical Line Terminal) (which is most likely a default on the OLT in case PON (Passive Optical Network) TLV are activated) for PPPoE-IA (Point-to-Point Protocol over Ethernet) IFLset (interface-set) of the IFD (Interface Device) which allows a single subscriber to limit the throughput of the entire interface.
PR NumberSynopsisCategory: mgd, ddl, odl infra issues
1752374Subsequent commits hang will be seen, when transfer-on-commit fails
Product-Group=junos
On all Junos Evolved platforms, When transfer-on-commit is configured and it fails as the destination is unreachable or invalid, commit lock taken by automatic rollback commit is not released. Due to this, subsequent commits result in a hung state.
PR NumberSynopsisCategory: Express PFE L2 fwding Features
1770678Incorrect IFL value resulting in the PFE crash
Product-Group=junos
On Junos QFX10K platforms, the PFE crash is observed resulting in traffic loss due to an incorrect IFL (Logical Interface) value while static MAC address programming.
PR NumberSynopsisCategory: SRX4100/SRX4200 platform software
1689990Minor alarm "FPC Inefficient Port Mapping" won't be cleared
Product-Group=junos
In SRX4100/4200 platform, even assigning ports are balanced, minor alarm "FPC Inefficient Port Mapping" might not be cleared.
1761668False SNMP traps for power supply unit failure generated on SRX4100 and SRX4200 platforms
Product-Group=junosvae
On SRX4100/SRX4200 platforms, false SNMP traps for power supply unit failure generated as instability with the transmission in the hardware.
PR NumberSynopsisCategory: BSDX Software installation issues
1639610The error is seen during the NON-ISSU upgrade from 15.1 to 18.2 and later releases
Product-Group=junos
In SRX5400, SRX5600, SRX5800 platform while performing NON-ISSU software upgrade from 15.1 to 18.1 and later releases error is seen.
PR NumberSynopsisCategory: track re issu control procedure bugs
1740744ISSU doesn't break if INDB crashes
Product-Group=junos
On Junos platforms, when ISSU (in-service software upgrade) is initiated, a process called INDB (Incompatible Database) will be triggered to perform a pre-check on database compatibility. There could be some corner case that causes the INDB crash. If that happens, the ISSU should be aborted.
PR NumberSynopsisCategory: High Availability/NSRP/VRRP
1540654Both primary and secondary nodes in chassis cluster go into disabled state in HA link down scenario
Product-Group=junos
In case of single control link on (SRX5400, SX5600, SRX5800) chassis cluster setup, when HA control link goes down, both nodes go into disable state due to fabric link still UP.
1638794Post a series of actions MNHA functionality might not be available despite the configuration presence
Product-Group=junos
On specific SRX platforms (SRX5400/SRX5600/SRX5800/vSRX3.0) with Multinode High Availability (MNHA) configured, when the chassis high-availability configuration is deleted but not committed, if the device reboots it considers high-availability mode as not configured despite the configuration being in place, in turn impacting MNHA functionality.
1726753Traffic loss after RG1 failover
Product-Group=junos
On vSRX3.0, after an Redundancy Group (RG1+) failover, packets may be sent from the SRX physical interface's MAC address instead of the Redundant Ethernet interface (reth's) virtual MAC which can result in traffic loss.
1736498In SRX MNHA cluster setup the RSI takes long time to generate
Product-Group=junos
In SRX MNHA cluster setup the RSI takes long time to generate on the MNHA backup node. The RSI includes the command "show security flow session session-state warm" which will collect all the sessions in warm state on the MNHA backup node - this output can be extensive and RSI is being generated an extended period of time, in known instances this was 1-2 hours.
PR NumberSynopsisCategory: Security platform jweb support
1779376Junos 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 NumberSynopsisCategory: lacp protocol
1706224On all Junos MX Series and PTX Series routers, multiple LACP timeouts cause traffic loss due to ppman resource starvation
Product-Group=junos
On all MX Series and PTX Series routers running Junos OS, during congestion, the periodic packet manager (ppman) runs short of resources and fails to send protocol data units (PDUs). This could cause LACP timeout and aggregated Ethernet interface flap, leading to traffic loss.
PR NumberSynopsisCategory: Multiprotocol Label Switching
1575060The LSP might fail to be established when IS-IS-TE or OSPF-TE is enabled
Product-Group=junos
If IS-IS-TE or OSPF-TE is enabled, but extended admin groups (which is configured under routing-options) are configured after the peer router advertises the extended admin groups, the LSP with extended admin groups constraints might fail to be established.
1649565The error severity of the syslog message "ted_client reset" generated during the commit is incorrect
Product-Group=junos
On all Junos and Junos evolved platforms, the severity of the syslog message "ted_client reset" that is generated by the rpd process during the commit is incorrect. It only generates an error message in the syslog.
1678431Junos OS and Junos OS Evolved: A link flap causes patroot memory leak which leads to rpd crash (CVE-2024-21613)
Product-Group=junos
A Missing Release of Memory after Effective Lifetime vulnerability in Routing Protocol Daemon (RPD) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, adjacent attacker to cause an rpd crash, leading to Denial of Service (DoS). Please refer to https://supportportal.juniper.net/JSA75754 [juniper.net] for more information.
1775553Traffic drop in L2VPN scenarios when an access port flap or configuration change
Product-Group=junos
On Junos QFX5100 and EX4600 platforms in Layer 2 Virtual Private Network (L2VPN) scenarios, when an access port flaps or the port related configuration is deactivated and activated, the traffic ingressing or egressing out of that port gets dropped.
PR NumberSynopsisCategory: Odin Timing software
1745604[TWM Clocking Solution] - chassis clock status should not move to "holdover" while switching between PTP path alone
Product-Group=junos
[TWM Clocking Solution] - chassis clock status should not move to "holdover" while switching between PTP path alone
PR NumberSynopsisCategory: Category for tracking Olympus-MX issues
1670507Fabric Destination error and Fabric plane going in check state after changing the fabric redundancy mode
Product-Group=junos
On MX240/480/960 platforms, Fabric drops are observed when changing the fabric redundancy mode.
PR NumberSynopsisCategory: "ifstate" infrastructure
1714785Back to back GRES causes the vmcore to crash
Product-Group=junos
On all Junos platforms, vmcore crashes will be seen in a rare scenario after performing back to back GRES (Graceful Route Engine Switchover).
PR NumberSynopsisCategory: PFE Peer Infra
1747077Due to timing issues, PFE/PICs will be slow and traffic will be impacted on all Junos platforms
Product-Group=junos
On all Junos platforms, due to timing issues the PFE (Packet Forwarding Engine) /PICs (Physical Interface Card) will be slow and services will face slowness issue and error message: 'Minor potential slow peers are: X' will be seen. This is rare timing issue.
PR NumberSynopsisCategory: TCP/UDP transport layer
1761242TCP window scaling may be not applied to the first TCP packet sent to the client after the three-way handshake, leading to unnecessary segmentation.
Product-Group=junos
On all JUNOS platforms, the first TCP packet sent by Junos to the client after the three-way handshake may be unnecessarily segmented due to TCP window scaling option being not applied even if it was negotiated.
PR NumberSynopsisCategory: Kernel Tunnel Interface Infrastructure
1743306FTI interface status (up/down) does not sync between master and backup RE.
Product-Group=junos
FTI IFD's and IFL's are not cleaned up on new backup in a switchover where graceful-switchover is not configured. This leads to mismatch between interface status or even commit error.However, with gres config "set chassis redundancy graceful-switchover", no issue is seen.
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1771739The PVST BPDU packet get dropped in transparent EVPN-VXLAN on the ingress PE-CE port of SP style on Junos EX/QFX platforms
Product-Group=junos
On Junos QFX/EX platforms with SP (Service Provider)-style configuration and in the EVPN (Ethernet Virtual Private Network)-VXLAN (virtual Extensible Local Area Network) scenario at the ingress port of the CE (Customer Edge) host, PVST (Per VLAN Spanning Tree) VSTP (VLAN Spanning Tree Protocol) BPDUs (Bridge Packet Data Unit) are getting dropped when the VLAN-ID is set to none. It should be flooded into the VLAN (Virtual Local Area Network) including intra-VLAN ports and remote VTEP (Virtual Tunnel Endpoint).
PR NumberSynopsisCategory: QFX5100 Platfom related issues. CPLD, FPGA, FRU, Host, RE
1742565Ports with SFP-T 1G plugged in may go to hung state on QFX5100 (non-tvp-image) platforms
Product-Group=junos
When the remote end server/system reboots, QFX5100 platform ports with SFP-T 1G inserted may go into a hung state and remain in that state even after the reboot is complete. This may affect traffic after the remote end system comes online and resumes traffic transmission.
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platfom issues
1760948Traffic drop will be observed on QFX5120-48YM when LLDP is enabled
Product-Group=junosvae
On Junos QFX5120-48YM platform, the mac interface of jsrv takes precedence over the chassis hardware mac-address while using Link Layer Discovery Protocol (LLDP) due to this traffic impact will be seen on that interface.
PR NumberSynopsisCategory: KRT Queue issues within RPD
1774975Features utilizing inactive routes will not work properly after the device reboot
Product-Group=junos
On all Junos and Junos OS Evolved platforms, due to some software issue, after the device reboot features utilizing inactive routes in the routing table will not work properly. This will cause issues like some inactive routes not being advertised when selected as the best path, features like advertise-inactive not working properly as it utilizes an inactive route flash, high Routing Protocol Daemon (rpd) Central Processing Unit (CPU) utilization, etc.
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1768604Traffic 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).
PR NumberSynopsisCategory: show route table commands, tracing, and syslog facilities
1658834Junos OS and Junos OS Evolved: In a BGP rib sharding scenario an rpd crash will happen shortly after a specific CLI command is issued (CVE-2023-28980)
Product-Group=junos
A Use After Free vulnerability in the routing protocol daemon of Juniper Networks Junos OS and Junos OS Evolved allows a locally authenticated attacker with low privileges to cause Denial of Service (DoS). Please refer to https://supportportal.juniper.net/JSA70606 [juniper.net] for more information.
PR NumberSynopsisCategory: Resource Reservation Protocol
1661954A LSP might get stuck in the CSPF path computation stage
Product-Group=junos
A label-switched path (LSP) might get stuck in the Constrained Shortest Path First (CSPF) computation and might not finish the session setup. The LSP retry continues to fail when no error feedback is received from downstream routers.
PR NumberSynopsisCategory: SNMP Infrastructure (snmpd, mib2d)
1527251SNMP might not work when IS-IS is disabled under VRF instance
Product-Group=junos
On all Junos platforms, SNMP polling might not work if the IS-IS protocol is disabled under the same virtual routing and forwarding (VRF) instance through which SNMP requests are sent.
PR NumberSynopsisCategory: SRX branch platforms
1580667[SRX] error message tcp_timer_keep:Local(0x81100001:60753) Foreign(0x8f100001:33010) is seen in messages log every 80 seconds
Product-Group=junos
On SRX series platform with Chassis Cluster, tcp_timer_keep:Local(0x81100001:60753) Foreign(0x8f100001:33010) is seen in messages log every 80 seconds.
1611400VPLS interface fails to forward traffic on SRX platform
Product-Group=junos
On all Junos SRX platforms, VPLS(Virtual Private LAN Service) interface configured output filter with policer action may stop forwarding the traffic. The VPLS interface shows output bytes as 0, although the input packets and bytes are incremented.
1661816fxp0 works under disable state in SRX300
Product-Group=junos
SRX300 runs in HA mode, fxp0 could be unexpectedly UP even though "disable" is configured.
1739520Random physical interfaces doesn't come up after a reboot
Product-Group=junos
On SRX345, some interface ports couldn't able to get correct medium (FIBRE or COPPER) sometimes after multiple reboot due to that SFP optics inserted may not come up after a reboot.
1744108Commit panic reboot observed after implementing system processes watchdog timeout 180 on SRX hardware platforms
Product-Group=junos
On SRX hardware platforms, configuring set system processes watchdog related command causes commit panic reboot. Watchdog related commands are unsupported on SRX hardware platforms.
1746202Kernel CPU temperature becomes high and the flowd process crashes with dual VLAN tag configured
Product-Group=junos
On all SR3xx platforms having Q-in-Q tunnelling on VPLS (Virtual Private Local Area Network Service) over GRE (Generic Routing Encapsulation) tunnel, it is seen that due to dual VLAN (Virtual Local Area Network) tag configuration, the kernel CPU (Central Processing Unit) temperature becomes high along with the flowd process getting crashed.
PR NumberSynopsisCategory: MX10003/MX204 Linux issues (including driver issues)
1753908Device crash and control plane traffic gets impacted on Junos platforms
Product-Group=junos
On all Junos platforms, due to a timing issue, when monitor traffic is enabled on loopback interface (for debug purpose), in the presence of local TCP (Transmission Control Protocol) packet flow, it is observed that the device crashes and traffic gets impacted.
PR NumberSynopsisCategory: SRX-1RU platfom chassisd SW defects
1711467SRX4600 doesn't support ae interfaces
Product-Group=junos
On Junos SRX4600 platforms, ae interfaces doesn't come up or not work properly when configured in HA (High Availability) cluster mode.
PR NumberSynopsisCategory: SRX-1RU platfom related protocol, QoS, filtering features et
1566065CLI-command "show pfe statistics traffic" shows wrong output
Product-Group=junos
cli-command "show pfe statistics traffic" shows wrong output and will be disabled in future JunOS releases as the correct place to check these statistics on SRX is PFE/flow-based "show pfe statistic" command
1683213SRX4600HA might not failover properly due to a hardware failure
Product-Group=junosvae
In SRX4600 platform, there is a possibility of raising alarm function might not work in FPGA failure. It might affect device availability.
PR NumberSynopsisCategory: ZT/YT pfe l3 forwarding issues
1719763Incorrect forwarding lookup in Packet Forwarding Engine on MX platforms with MPC10E/11E/LC9600/MX304-LMIC16 line cards in an L2circuit Scenario with Flow-Label and Control-Word enabled
Product-Group=junos
On Junos MX platforms, packet drop is seen in Layer 2 circuit when flow-label is enabled along with control-word and the egress Provider Edge (PE) core facing interface is on MPC10E/11E/LC9600/MX304-LMIC16. Certain flows will get punted to RE (Routing Engine) instead of getting forwarded.
1774127Memory leak for deactivation/activation of SCU
Product-Group=junos
On MX platforms with MPC10, MPC11, LC9600, and MX304-LMIC16, the heap memory leaks every time the SCU (source-class-usage) policy is removed i.e. removed and re-applied resulting in restart of the line card. Heap leak is proportional to the number of source classes or indices being removed by related policy.
PR NumberSynopsisCategory: Trio pfe bridging, learning, stp, oam, irb software
1669478Traffic drop observed with SP style configuration for the logical tunnel in layer2 domain
Product-Group=junos
On MX platforms, when the configuration for the logical tunnel in the layer2 domain is in the service provider style observing traffic drop for traffic over IRB (Integrated routing and bridging).
1740606Host communication does not work in EVPN-L2VPN-CCC setup
Product-Group=junos
On Junos MX platforms, in Ethernet Virtual Private Networks-Layer 2 Virtual Private Networks-Circuit Cross-Connect (EVPN-L2VPN-CCC) setup, the integrated routing and bridging (IRB) interface over access logical tunnel (LT) interface is configured, it is sending vlan tagged packet on the access port and not removing it causing the host communication to break.
1772733In EVPN-MPLS/EVPN-VxLAN Multi-Home Active/Active scenario, random packet drops are observed
Product-Group=junos
On all Junos MX platforms, in Ethernet Virtual Private Network Multiprotocol Label Switching (EVPN-MPLS)/ Virtual eXtensible Local-Area (EVPN-VxLAN) Network Multi-Home Active/Active scenario, random packet drops will be observed on the Non-Designated-Forwarder for ARP-REPLY generated in response to ARP-REQUEST received for Virtual-Gateway-Address defined on the IRB interface.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1656565Commit and commit check fails when the knob "interface-range" is configured
Product-Group=junos
On all Junos and Junos Evolved platforms, when the knob "interface-range" is configured commit and commit check fails.
PR NumberSynopsisCategory: web filterig issues
1772232[SRX] Flowd core is generated by UTM web-filtering
Product-Group=junos
On SRX platform, flowd core might be generated when when TCP flow session for HTTP traffic is in error state due to some reason and UTM WF trying to apply fallback action.
 
 

20.4R3-S10 - List of Known issues 

PR NumberSynopsisCategory: chassisd related issues for high-end SRX platforms
1657958Archived files created by non-root users may not include some files
Product-Group=junos
On SRX 1500, 4100, 4200 and 4600 platforms, the file archive command under a non-root user account may not archive all files under /var/log.

Resolved In: junos:21.3R3-S3 junos:21.4R3-S4 junos:22.2R2 junos:22.2R3 junos:22.3R2 junos:22.4R1
PR NumberSynopsisCategory: MX Platform SW - FRU Management
1681716The device goes down when an FRU has over-temperature
Product-Group=junos
On MX240, MX480, and MX960, when the temperature for a particular FRU is above the over-temperature condition, the chassisd will start the timer(240 secs). If the over-temperature condition persists after completing 240secs, the chassis will be shut down instead of bringing down the particular FRU. This will impact the whole device traffic.

Resolved In: evo:24.1R1-EVO junos:24.1R1
PR NumberSynopsisCategory: ACX platform interface issues
1764303During the interface UP state the speed displays as "Unspecified" during the reboot scenario.
Product-Group=junos
On Junos ACX5448 device with SFP-T optics, speed displays wrong in CLI when executing "show interface " CLI command will display "Unspecified" speed. Speed value will not be updated properly. There is no traffic impact.

Resolved In: junos:21.4R3-S6
PR NumberSynopsisCategory: EX4400 platform
17417241G uplinks on EX4400 with pre-existing configuration do not come up after 4X10G ULM insertion
Product-Group=junos
On Junos EX4400 platforms, pre-configured 1G ports do not come up after 4X10G ULM (Universal Link Module) insertion event.

Resolved In: junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:22.4R3-S1 junos:23.2R2 junos:23.4R1 junos:24.1R1
PR NumberSynopsisCategory: Express PFE L3 Multicast
1774562PIM 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.

Resolved In: junos:22.4R3-S1 junos:23.2R2 junos:23.4R2 junos:24.1R1
PR NumberSynopsisCategory: SRX1500 platform software
1729671When there is a power outage happens after the first upgrade, the reboot device gets stuck at volume booting
Product-Group=junosvae
SRX1500 devices get stuck at volume booting after an upgrade and reboot, followed by a power outage. The device is stuck in this state and continues to boot.

Resolved In: junos:21.4R3-S6 junos:22.1R3-S3 junos:22.2R3-S1 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: Firewall Authentication
173221023.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 NumberSynopsisCategory: User Firewall related issues
1758332Junos OS: SRX Series and EX Series: Multiple vulnerabilities in J-Web can be combined to allow a preAuth Remote Code Execution (CVE-2023-36851)
Product-Group=junos
A Missing Authentication for Critical Function vulnerability in Juniper Networks Junos OS on SRX Series and EX Series allows an unauthenticated, network-based attacker to cause limited impact to the file system integrity and access confidential information. Please refer to https://supportportal.juniper.net/JSA72300 [juniper.net] for more information.

Resolved In: junos:22.1R3-S5 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R2-S2 junos:22.4R3 junos:23.2R1-S2 junos:23.2R2 junos:23.3R1 junos:23.3R2 junos:23.4R1 junos:24.1R1
PR NumberSynopsisCategory: SW PRs for MPC10E Interfaces
1719682LACP protocol down after link flaps aggresively within 100ms interval
Product-Group=junos
With repeated link flaps on 100G interface on an MPC10E line card, traffic stops egressing the affected interface and report syslog messages "XQSS_CMERROR_DSTAT_INT_REG_DROP0_QDEPTH_UNDRN" or "mqss_wo_coreif_conn_credits_wait_for_init_value" during link down event.

Resolved In: evo:23.2R2-EVO evo:23.4R1-EVO evo:24.1R1-EVO junos:20.3X75-D46 junos:21.2R3-S4-J33 junos:21.2R3-S5-J31 junos:21.2R3-S6-J6 junos:21.2R3-S6-J7 junos:21.2R3-S6-J8 junos:21.2R3-S7 junos:21.4R3-S3-J13 junos:21.4R3-S4-J14 junos:21.4R3-S5-J4 junos:22.2R3-S1-J10 junos:22.2R3-S3 junos:22.3R2-S1-J1 junos:22.3R3-S2 junos:22.4R2-S1-J4 junos:22.4R3 junos:23.2R2 junos:23.4R1 junos:24.1R1
PR NumberSynopsisCategory: MPC11 ULC platform software related issues.
1578987MPC11E might fail to upgrade
Product-Group=junos
On MX2010/MX2020 platforms with MPC11E linecard, some daemons like platformd and aft-ulcd would log stats log messages periodically without clear the log files (hidden files). In rare conditions the system might run on low memory day by day, then might cause the MPC11E to fail to upgrade.

Resolved In: evo:20.1R3-EVO evo:21.1R2-EVO evo:21.2R1-EVO evo:21.3R1-EVO junos:20.1R3 junos:20.3X75-D40 junos:20.3X75-D46 junos:21.1R2 junos:21.2R1 junos:21.3R1
PR NumberSynopsisCategory: Multiprotocol Label Switching
1669322Junos OS and Junos OS Evolved: A link flap causes patroot memory leak which leads to rpd crash
Product-Group=junos
A Missing Release of Memory after Effective Lifetime vulnerability in Routing Protocol Daemon (RPD) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, adjacent attacker to cause an rpd crash, leading to Denial of Service (DoS).

Resolved In: evo:21.4R3-EVO evo:22.1R2-EVO evo:22.1R3-EVO evo:22.2R2-EVO evo:22.3R1-EVO evo:22.4R1-EVO junos:19.3R3-S2-J1 junos:19.4R3-S9 junos:20.3R3-S5 junos:20.3X75-D35 junos:20.3X75-D42 junos:21.2R3-S1 junos:21.2R3-S2 junos:21.2X32-D10 junos:21.3R3-S1 junos:21.4R3 junos:22.1R2 junos:22.1R3 junos:22.2R1 junos:22.2R2 junos:22.3R1 junos:22.4R1
PR NumberSynopsisCategory: MX Timing software
1622575[G.8275.1]: High phase jump spikes of ~4000 to 5000 ns is observed during slave clock fail-over within same line card, due to config commit
Product-Group=junos
High phase jump spikes of ~4000 to 5000ns is observed during slave clock fail-over within same line card caused by a config commit

Resolved In: evo:21.3R3-EVO evo:21.4R2-EVO evo:22.1R2-EVO evo:22.2R1-EVO junos:20.4R3-S3 junos:21.2R3 junos:21.3R3 junos:21.4R2 junos:21.4R3-S1 junos:22.1R2 junos:22.2R1 junos:22.2R2
PR NumberSynopsisCategory: FreeBSD Kernel Infrastructure
1568757The image validation is not supported during upgrading from Pre 21.2 to 21.2 and onward
Product-Group=junos
When upgrading from releases before Junos OS Release 21.2 to Release 21.2 and onward, validation and upgrade might fail. The upgrade requires using the 'no-validate' option to complete successfully. https://kb.juniper.net/TSB18251 [juniper.net]

Resolved In:
PR NumberSynopsisCategory: vMX Data Plane Issues
1669261vMX crashes due to MBUF leaks
Product-Group=junos
vMX platforms (MX150) will crash as a result of the MBUF (Memory Buffer) leak.

Resolved In: junos:20.3X75-D43 junos:20.3X75-D46 junos:20.4R3-S5 junos:21.4R3 junos:22.1R3 junos:22.3R1 junos:22.3R2 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1729101dcpfe process core observed after restarting the l2-learning process with flex-hashing configuration
Product-Group=junosvae
On Junos QFX (except QFX5210) and EX platforms, dcpfe core will be observed after the l2-learning process restarts when 'flex-hashing' is configured.

Resolved In: junos:20.4R3-S8 junos:21.3R3-S5 junos:21.4R3-S4 junos:22.1R3-S3 junos:22.1R3-S4 junos:22.2R3-S1 junos:22.2R3-S2 junos:22.3R2-S2 junos:22.3R3 junos:22.3R3-S1 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: QFX analyzer, sflow
1777265The fxpc process crash is seen on a specific Junos QFX and EX platforms except EX4300 due to memory leak after VTEP IFLs configuration and un-configuration
Product-Group=junos
VTEP (VXLAN Tunnel Endpoint) IFLs (Logical Interfaces) configuration and un-configuration causes a memory leaks and it leads to the fxpx process crash on a specific Junos QFX and EX platforms except EX4300.

Resolved In: junos:21.4R3-S6 junos:22.1R3-S5 junos:22.2R3-S3 junos:22.3R3-S2 junos:23.2R2 junos:23.4R1 junos:24.1R1
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1760823Traffic drop will be seen when packets are sent with incorrect VLAN tag
Product-Group=junos
EVPN (Ethernet VPN) proxy arp with Multihome AE (ESI) responds with an incorrect VLAN (Virtual Local Area Network) tag. QFX5K, EX4400, and EX4650 platforms return proxy arp reply with incorrect vlan-id with native VLAN under ESI (Ethernet Segment Identifier) ae interface.

Resolved In: junos:21.4R3-S6 junos:22.1R3-S5 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:23.2R2 junos:23.3R2 junos:23.4R1 junos:24.1R1
1775672The PVST (VSTP) BPDU packet gets dropped in transparent EVPN-VXLAN on the ingress PE-CE port of SP style on Junos EX/QFX platforms
Product-Group=junos
On certain Junos QFX5k/Ex4K platforms with SP (Service Provider)-style configuration and in the EVPN (Ethernet Virtual Private Network)-VXLAN (virtual Extensible Local Area Network) scenario at the ingress port of the CE (Customer Edge) host, PVST (Per VLAN Spanning Tree) VSTP (VLAN Spanning Tree Protocol) BPDUs (Bridge Packet Data Unit) are getting dropped when the native VLAN-id is set to 400 and associated interface BD (Bridge Domain) VLAN-id is set to none. It should be flooded into the VLAN (Virtual Local Area Network) including intra-VLAN ports and remote VTEP (Virtual Tunnel Endpoint).

Resolved In: junos:22.1R3-S5 junos:22.2R3-S3 junos:23.2R2 junos:23.4R2 junos:24.1R1
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platform optics related issues
1726707On 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 NumberSynopsisCategory: Shard routing infrastructure within RPD
1727528The rpd process can crash during a race condition when BGP rib-sharding is configured
Product-Group=junos
On all Junos and Junos OS Evolved platforms, when BGP RIB sharding is configured, the rpd process crashes during a rare race condition where multiple threads try to initialise a single global variable. During the rpd crash and restart, all routing protocols will be impacted and traffic disruption will be seen due to the loss of routing information.

Resolved In: evo:23.3R1-EVO junos:22.2R3-S2-J2 junos:22.2R3-S3 junos:23.3R1
PR NumberSynopsisCategory: all ipv6 dhcp bugs on srx platforms
1770332DHCP server not responding to some clients
Product-Group=junos
SRX DHCP server does not respond to some clients after upgrading to 21.4R3-S5.

Resolved In: junos:21.2R3-S7 junos:21.4R3-S6 junos:22.1R3-S5 junos:22.4R3 junos:23.2R2 junos:23.4R1 junos:23.4R2 junos:24.1R1
PR NumberSynopsisCategory: SRX branch platforms
1581554Traffic is dropped to/through VRRP virtual IP on SRX380
Product-Group=junos
On SRX380, when using Integrated routing and bridging (IRB) interface, Virtual Router Redundancy Protocol (VRRP) VIP (Virtual IP) is not responding to pings (with accept-data configured) and traffic is not routed through the configured VRRP VIP address

Resolved In: junos:20.3R3-S1 junos:20.4R3 junos:21.1R2 junos:21.1R3 junos:21.2R2 junos:21.3R1 junos:21.4R1
1714620High 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:
1768050ARP resolution does not work if generated from the L3 Interface such as the IRB interface
Product-Group=junos
On SRX300 series platforms, ARP (Address Resolution Protocol) resolution does not work if it is generated internally from the L3 (Layer 3) interface such as the IRB (Integrated Routing and Bridging) interface. The routing protocol connections will not get established resulting in traffic impact.

Resolved In: junos:21.2R3-S7 junos:21.3R3-S5 junos:21.4R3-S6 junos:22.1R3-S5 junos:22.4R3 junos:23.2R2 junos:23.3R2 junos:23.4R1 junos:24.1R1
PR NumberSynopsisCategory: MX10003/MX204 MPC defects tracking
1686012100GE interface on JNP-MIC1 TIC module may keep flapping for 1 ~ 45 minutes after a specific 3rd party peer device (NRU02 from Arista/Pluribus) is booting up.
Product-Group=junos
100GE interface on JNP-MIC1 TIC module may keep flapping for 1 ~ 45 minutes after a specific 3rd party peer device (NRU02 from Arista/Pluribus) is booting up.

Resolved In: evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:20.3X75-D46 junos:20.4R3-S2-J19 junos:21.4R3-S5 junos:22.2R3-S3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: SRX-1RU platfom datapath SW defects
1732876Traffic drops will be observed when a BGP session comes up after the network flap
Product-Group=junos
On SRX platforms with BGP (Border Gateway Protocol) multipath and forwarding table policies configured, for the type 5 EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) tunnel routes traffic drops will be observed for a few composite next-hop that are not installed in PFE (Packet Forwarding Engine) when a BGP session comes up after the network flap. The issue can also happen when deactivating/activating OSPF (Open Shortest Path First) in the OSPF environment.

Resolved In: junos:23.2R2 junos:23.4R1 junos:23.4R2 junos:24.1R1
PR NumberSynopsisCategory: SRX-1RU platfom related protocol, QoS, filtering features et
1729284L2 channel error counter increases when unknown family packets received by interfaces
Product-Group=junos
On SRX4600 and SRX5K platforms, the L2 channel error counter will increase when some unknown family packets received by interfaces.

Resolved In: junos:21.2R3-S6 junos:21.3R3-S5 junos:21.4R3-S5 junos:22.1R3-S3 junos:22.2R3-S2 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: ZT/YT pfe firewall software
1692070The firewall bridge filter policers (attached to AE interface) are not working on all Junos MX platform with MPC10 card upon deactivate-activate a term intended to limit overall traffic
Product-Group=junos
Traffic policing will not work as expected on all Junos MX platform with MPC10 card after doing deactivation-activation of the term intended to limit overall traffic when the firewall and policers are applied to the bridge unit using shared-bandwidth-policers on AE (Aggregated Ethernet) interface.

Resolved In: evo:22.3R3-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:20.3X75-D46 junos:21.2R3-S4 junos:21.3R3-S4 junos:21.4R3-S3 junos:22.1R3-S1 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R1 junos:23.1R1
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1638847The mustd process crash might be observed with persist-group-inheritance
Product-Group=junos
On all Junos and Junos Evolved platforms configured with persist-group-inheritance, which is enabled by default from 19.4R3 onwards, might lead to mustd process crash in highly scaled configuration.

Resolved In: evo:22.3X50-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:20.3X75-D52 junos:20.4R3-S8 junos:21.2R3-S6 junos:21.2X32-D20 junos:21.3R3-S5 junos:21.4R3-S4 junos:22.1R3-S3 junos:22.2R3-S1 junos:22.3R2-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1-S1 junos:23.1R2 junos:23.2R1
1641025Unable to access configure exclusive mode after mgd process is killed
Product-Group=junos
On all Junos OS and Junos OS Evolved devices, when copy-config, get-configuration, and discard-change RPCs run in two parallel NETCONF sessions and the database is also accessed in parallel by two NETCONF sessions, it leads to database corruption and mgd-related services might crash.

Resolved In: evo:20.4R3-S3-EVO evo:21.1R3-S2-EVO evo:21.3R3-EVO evo:21.4R1-S2-EVO evo:21.4R2-EVO evo:22.1R1-EVO evo:22.1R2-EVO evo:22.2R1-EVO junos:19.4R3-S8 junos:20.1R3-S4 junos:20.2R3-S7 junos:20.3R3-S4 junos:20.3X75-D21 junos:20.3X75-D32 junos:20.3X75-D40 junos:20.4R3-S3 junos:21.1R3-S2 junos:21.2R3-S1 junos:21.2X32-D10 junos:21.2X32-D20 junos:21.3R2-S1 junos:21.3R3 junos:21.3X30-D10 junos:21.4R1-S2 junos:21.4R2 junos:21.4R3 junos:22.1R1-S1 junos:22.1R2 junos:22.2R1

 

Modification History

First publication 2023-01-31