Alert Type

PSN - Product Support Notification
Low/NotificationSoftware Release Notification
Low/NotificationSoftware Release Notification

Product Affected

ACX EX MX NFX PTX QFX SRX vSRX

Alert Description

See TSB71463 [juniper.net] for the list of FIXED issues in Junos software version 22.2R3-S1

 

Junos Software Service Release version 22.2R3-S1 is now available for download from the Junos software download site

Download Junos Software Service Release:

  1. Go to Junos Platforms - Download Software page
  2. Input your product in the "Find a Product" search box
  3. From the Type/OS drop-down menu, select Junos SR
  4. From the Version drop-down menu, select your version
  5. Click the Software tab
  6. Select the Install Package as need and follow the prompts

 

Solution

22.2R3-S1 - List of Known issue

PR NumberSynopsisCategory: Daily JUNOS build failures - automated builder use only
1691209Use latest os-package when upgrading
Product-Group=junos		Upgrade to 22.3R1 while using os-package published between July 2022 and November 2022 may incorrectly link os-libs package

Resolved In: junos:21.2R3-S4 junos:21.3R3-S3 junos:21.4R3-S2 junos:22.1R3-S1 junos:22.2R2-S1 junos:22.2R3 junos:22.3R1-S2 junos:22.3R2 junos:22.4R1 junos:22.4R2
PR NumberSynopsisCategory: EX4300 PFE
1720219PFE process crash is observed on Junos EX4300 platforms
Product-Group=junos		In a rare scenario, due to timing issues, the Packet Forwarding Engine (PFE) crash is observed on Junos EX4300 platforms. This causes traffic loss until the PFE comes up.

Resolved In: junos:21.4R3-S4
PR NumberSynopsisCategory: EX4300 Platform
1710203on EX4650 even after PEM is detected sometimes the alarm "PEM not powered" doesn't get cleared.
Product-Group=junos		on EX4650 even after PEM is detected sometimes the alarm "PEM not powered" doesn't get cleared.

Resolved In: 
PR NumberSynopsisCategory: EX4300 Layer 2 implementation
1697995Dot1x authentication failure for EVPN VXLAN enabled port
Product-Group=junos		On Junos EX4300-48MP platforms, dot1x authentication fails with EVPN-VXLAN (Ethernet VPN-Virtual extensible LANs) end to end configuration on a user port.

Resolved In: junos:21.4R3-S3 junos:21.4R3-S4 junos:22.1R3-S1 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: EX4300 Platform implementation
1708123QSFPs are displayed as UKNOWN after the upgrade
Product-Group=junos		On EX4300 & EX4300MP platforms, QSFPs are displayed as UKNOWN after the upgrade.

Resolved In: junos:21.4R3-S3 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
1714056On EX4650, jnxOperatingDescr.1.1.0.0 is populated with blank
Product-Group=junos		On EX4650, jnxOperatingDescr.1.1.0.0 is populated with blank

Resolved In: junos:21.4R3-S4 junos:22.2R3-S1 junos:22.3R3 junos:22.3R3-S1 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: EX2300/3400 PFE
1695771Traffic loss is seen when a MAC moves from dot1x port to non-dot1x port
Product-Group=junos		On all Junos and Junos OS Evolved platforms is having dot1x enabled interface. When two or more MAC addresses are learnt on a dot1x port, and if one of them is shifted to a non-dot1x port, the MAC address that was moved is still seen as a MAC-based VLAN entry on the Layer2 Address Learning Manager (l2alm). This could lead to network traffic being lost.

Resolved In: evo:21.4R3-S4-EVO evo:22.3R2-S1-EVO junos:20.4R3-S7 junos:21.1R3-S5 junos:21.2R3-S5 junos:21.3R3-S4 junos:21.4R3-S4 junos:22.1R3-S2 junos:22.2R3 junos:22.3R2-S1 junos:22.3R3 junos:22.4R2 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: EX2300/3400 platform
1580560On EX2300, EX3400, :EX4300-48MP and EX4300 , Pause frames counters does not get incremented when pause frames are sent.
Product-Group=junos		On EX2300, EX3400, :EX4300-48MP and EX4300 , Pause frames counters does not get incremented when pause frames are sent.

Resolved In: 
1700093JUNOS_REG:EX2300-48MP:FXPC core is seen with Backtrace dcbcm_discover, pic_discover, cmqfx_pic_sw_init, cmqfx_all_pic_sw_init, cmqfx_module_init, , module_entry_thread
Product-Group=junos		Release note needed

Resolved In: 
PR NumberSynopsisCategory: EX-Series VC Infrastructure
1700133One of the Virtual Chassis members on EX4600-VC might be disconnected during VC initialization
Product-Group=junos		On EX4600-VC, when "request system reboot all members" is executed, post-reboot one of the VC member/Flexible PIC Concentrator(FPC) might disconnect and join the VC back due to Packet Forwarding Engine (PFE) restart. Traffic loss is seen when FPC is disconnected.

Resolved In: junos:20.2R3-S7 junos:21.4R3-S4
PR NumberSynopsisCategory: Anything related to Multicast
1461339Mcast traffic drops is observed with the following error message: brcm_rt_ip_mc_ipmc_install.
Product-Group=junos		Following two Failure messages seen brcm_rt_ip_mc_ipmc_install:2455 Failed (Invalid parameter:-4) This message is due to IPMC Group being used is not created, when RE tried to add this check indicates there is a parameter mis-match. brcm_rt_ip_mc_ipmc_install:2455 Failed (Internal error:-1) This message is due to Failure to read IPMC Table or any memory/register

Resolved In: 
PR NumberSynopsisCategory: QFX VC Datapath
1692102Traffic loss on QFX5100 Virtual Chassis setup due to CRC alignment errors
Product-Group=junos		On Junos QFX5100 platforms running qfx-5e images in Virtual Chassis setup, when Virtual Chassis Port (VCP) links are connected between PHY and PHYLESS ports, CRC alignment errors will be seen. As a result, there can be traffic loss on these links.

Resolved In: junos:21.4R3-S4
PR NumberSynopsisCategory: SRX DNS DGA and tunneling related
1727122Nstraced process is running high on the primary node after the Junos upgrade
Product-Group=junos		On all Junos SRX/vSRX platforms, nstraced process spikes to 100% usage after upgrading to Junos version 21.4R3-S2 or any later releases without having any traces/debugs explicitly configured in the RE (Routing Engine) or PFE (Packet forwarding Engine) of the device.

Resolved In: junos:22.1R3-S3 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
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.

Resolved In: junos:21.2R3-S6 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: BBE OS Infrastructure library
1732216'max-db-size' configuration is optional in routers having DRAM greater than or equals to 32GB
Product-Group=junos		On Junos MX platforms, to enable Enhanced Subscriber Management feature without 'max-db-size' configuration on router >=32GB DRAM(Dynamic Random Access Memory), router needs to be rebooted only once instead of rebooting twice.

Resolved In: evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:20.2R3-S4-J9 junos:21.2R3-S5-J3 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: Border Gateway Protocol
1635700The BFD session might be down when multiple addresses of same subnet are configured
Product-Group=junos		In the single-hop BFD for BGP scenario, when multiple addresses of the same subnet are configured on the interface of the BFD session, the BFD session might be down.

Resolved In: evo:21.2R3-EVO evo:21.3R3-EVO evo:21.4R2-EVO evo:22.1R2-EVO evo:22.2R1-EVO junos:20.2R3-S4 junos:20.3R3-S4 junos:20.3X75-D50 junos:21.2R3 junos:21.3R3 junos:21.4R2 junos:22.1R2 junos:22.2R1
1689904BGP LU Advertisements fail with the message "BGP label allocation failure: Need a gateway"
Product-Group=junos		On all Junos and Junos Evolved platforms BGP-LU (Border Gateway Protocol Labeled-Unicast) Advertisements fail with the message "BGP label allocation failure: Need a gateway" based on timing conditions involving route resolution and installation.

Resolved In: evo:22.3R3-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:22.1R3-S2 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1 junos:23.2R1
1690213BMP will not send EOR message
Product-Group=junos		On all Junos and Junos Evolved platforms, BMP(BGP Monitoring Protocol) will not send EOR(End of RIB) message for some releases. This will impact some data collections.

Resolved In: evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.2R3 junos:22.3R2 junos:22.4R2 junos:23.1R1 junos:23.2R1 junos:23.3R1
1691131Backup Path is Not Found in ASBR6 MPLS Table while verifying BGP Multipath Protection functionality
Product-Group=junos		Backup Path is Not Found in ASBR6 MPLS Table while verifying BGP Multipath Protection functionality

Resolved In: evo:22.2R3-EVO junos:21.4R3-S2 junos:22.1R3 junos:22.2R3
1712527The PE advertises incorrect next-hop towards CE although BGP export policy configured with next-hop under policy-statement
Product-Group=junos		Show route advertising-protocol bgp reporting NextHop self rather than IP in the configured policy-statement for next-hop. Behavior change observed after JUNOS upgrade from 18.4 to 20.4. #set policy-options policy-statement set-NH-MX term to-PP-All then next-hop nh-addr

Resolved In: evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
1728455The rpd process crashes when BGP is cleaned up
Product-Group=junos		On Junos and Junos OS Evolved platforms, if static default RT-C (Route Target -Constrain) is configured when BGP is cleaned up, the routing process might crash.

Resolved In: evo:21.2R3-S6-EVO evo:21.3R3-S5-EVO evo:22.1R3-S3-EVO evo:22.3R3-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:21.2R3-S6 junos:22.1R3-S3 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
1728604Traffic impact is seen when there is a single peer in the proxy BGP group connected to the BGP route reflector
Product-Group=junos		On all Junos and Junos OS Evolved platforms, if the proxy BGP (Border Gateway Protocol) route reflector is connected to the only peer present in the BGP group then it stops advertising the routes coming from the remote cluster and that leads to proxy route-target routes not getting added which causes traffic disruption.

Resolved In: evo:21.2R3-S6-EVO evo:21.3R3-S5-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:21.2R3-S6 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: Track PRs in BGP BMP area & is part of BGP inside RPD.
1635143The rpd may crash due to memory pressure for high BGP scale with flapping route and BGP Monitoring Protocol (BMP) collector/station is very slow on all Junos and EVO platforms
Product-Group=junos		On all devices running Junos OS or Junos OS Evolved, where this is a high BGP scale with flapping route and the BGP Monitoring Protocol (BMP) collector/station is very slow, the rpd process might crash due to memory pressure.

Resolved In: junos:20.3X75-D45
1713444The rpd process will crash when BMP is configured
Product-Group=junos		On all Junos and Junos Evolved platforms, the rpd process will crash when BGP Monitoring Protocol (BMP) is configured. This will cause rpd to restart and affect routing protocols.

Resolved In: junos:21.4R3-S4 junos:22.1R3-S3 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: BBE Remote Access Server
1687998The authd process crashes during GRES recovery phase
Product-Group=junos		On MX platforms, during recovery phase of Graceful Routing Engine Switchover (GRES), authd process crashes.

Resolved In: evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:21.2R3-S3 junos:22.1R3 junos:22.2R2 junos:22.2R3 junos:22.3R1-S1 junos:22.3R2 junos:22.4R1 junos:23.1R1
1723183Subscriber sessions will fail to login post GRES and scaled subscriber scenario
Product-Group=junos		On MX platforms in a scaled subscriber scenario (8K subscribers) and post GRES (Graceful Routing Engine Switchover), the session database and IP pool database can get out of sync on the backup RE if there is a subscriber churn. After the RE switchover, this condition will lead to the immediate termination of new subscriber sessions if the assigned IP address is still in use by an existing subscriber.

Resolved In: evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:20.4R3-S8 junos:21.2R3-S6 junos:21.4R3-S2-J4 junos:22.1R3-S3 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: MX304 Chassis specific platform 
1731237MX304 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.

Resolved In: 
1735719FPC cores may be seen when Both the RE's are rebooted using CLI and GRES is enabled
Product-Group=junos		When both the RE's are rebooting, since all the different components are being disabled, in some corner cases, some of the apps on FPC may panic intentionally due to access failures. This happens before FPC is rebooted. So, we can safely ignore these cores and FPC will reboot and comes up properly. So, recommendation is - Try one of the below options 1) Ignore the cpss and ukern cores when both the RE's are rebooted with GRES enabled. 2) Don't trigger both the RE's reboot with GRES enabled 3) If you want to reboot both the RE's with GRES enabled, then first reboot one of the RE's. Once the first RE reboots and comes back, reboot the second RE 4) Reboot both the RE's by disabling the GRES.

Resolved In: 
PR NumberSynopsisCategory: MX304 interface specific 
1697272Link down post changing port speed in a special sequence
Product-Group=junos		In Junos MX304 platform, in a special sequence when the port speed is moved from 25G to 10G on a link and back to 25G on the same link, the link doesn't come up in 25G.

Resolved In: evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2
PR NumberSynopsisCategory: MX304 Routing Engine issues
1664592RE - FPC physical link down event does not generate an alarm
Product-Group=junos		If the physical link status of the ethernet link between the RE and FPC goes down, there are recovery attempts to bring up the link again. Log messages indicate the recovery attempts and the success/failure status of the attempt. However an alarm is not raised when this failure occurs

Resolved In: junos:23.3R1
PR NumberSynopsisCategory: Virtual-chassis platform/chassisd infrastructure PRs for MX
1686425Interface_check_up verification is not as expected on alisha device
Product-Group=junos		This issue is specific to MXVC only and the issue is not seen during manual execution of the test case. Issue is seen only with the test script that too rarely and hence the exact trigger of the issue is not clear.

Resolved In: 
PR NumberSynopsisCategory: OpenSSH and related subsystems
1664512SSH access is possible without ssh setting.
Product-Group=junos		From 21.4R1, SSH login is possible even though there is no config allowing SSH access under system services hierarchy. To disable SSH access, the following command will be implemented in resolved releases. # set system services ssh access-disable-external

Resolved In: junos:22.1R3 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: Device Configuration Daemon
1679952After changing the settings related interface, a particular interface does not flap but a LAG interface may flap on all Junos platforms except MX
Product-Group=junos		The LAG (Link Aggregation Group) member links may flap on all Junos platforms except MX when the configuration of any interface is changed/modified. The flap is not seen always.

Resolved In: junos:21.4R3 junos:21.4R3-S4 junos:22.1R3 junos:22.1R3-S2 junos:22.2R2 junos:22.2R3 junos:22.3R1 junos:22.3R2 junos:22.4R1
1712800On Junos platforms the dcd will flap the IFLs which are part of EVPN routing-instance
Product-Group=junos		On Junos platform that support VPLS and/or EVPN, on configuring IGMP-Snooping or VPLS, over Bridge-domain (BD), the data-carrier-detect (dcd) will flap the Logical Interface (IFLs) which are part of this EVPN routing-instance.

Resolved In: junos:21.4R3-S4 junos:22.1R3-S3 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
1714267The interface speed gets set to a lower speed when the interface is disabled and enabled because renegotiation of the interfaces happens at the previously negotiated speed
Product-Group=junos		On Junos platforms with MPC line cards, negotiated interfaces will try to come up with the speed already negotiated instead of using the original interfaces speed even if re-negotiation happens like reinserting cable.

Resolved In: junos:20.4R3-J12 junos:20.4R3-S8 junos:21.2R3-S6 junos:22.1R3-S3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: CoS support on DNX
1704589Traffic drops seen after making COS configuration change on ACX710
Product-Group=junos		On Junos ACX710 platforms, when CoS (Class-of-Service) scheduler changes are done for buffer usage and when traffic is flowing which involves bursty traffic, traffic drops are seen.

Resolved In: junos:21.2R3-S6 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: EVPN ELAN/E-TREE
1702615Leaf to leaf traffic flow is observed on Junos ACX5448 platform with EVPN E-Tree configuration
Product-Group=junos		ACX5448 Ingress PE is pushing label 0 instead of leaf label, hence traffic received on other PE is sending traffic out of leaf IFL (Logical Interface).

Resolved In: junos:21.4R3-S4 junos:22.1R3-S1 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: VPWS, L2 CKT, EVPN-VPWS
1683900The traffic drop is observed in the l2circuit scenario with control-word configuration
Product-Group=junos		On Junos ACX5448/ACX710 platforms in the layer2 circuit (l2circuit) scenario, if the control-word configuration is enabled/disabled, the complete traffic drop is observed for the affected l2circuit.

Resolved In: junos:21.2R3-S5 junos:21.3R3-S4 junos:21.4R3-S1 junos:22.1R3 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:23.1R1
1731081Traffic drops on ACX platform after it is rebooted
Product-Group=junos		On Junos ACX5448 and ACX710 platforms, when the router is rebooted with a new image then the RT (Routing-Table) programming fails in the PFE (Packet Forwarding Engine) with VPWS (Virtual Private Wire Service) configuration which causes traffic drop.

Resolved In: junos:22.1R3-S3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: Layer 3 forwarding, both v4+v6
1695292Traffic loss is more than expected with OSPF TI-LFA node- protection enabled and the primary path is down
Product-Group=junos		On ACX710 and ACX5448 platforms, with Open Short Path First Topology-Independent Loop-Free Alternate (OSPF TI-LFA) Node protection, Layer 3 Virtual Private Network (L3VPN) traffic loss will be more than the expected convergence time when the primary path goes down along with the 4 MultiProtocol Label Switching (MPLS) labels to be programmed in the secondary path.

Resolved In: junos:21.4R3-S4 junos:22.1R3-S3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
1712564Transit traffic drop is observed for the BGP-LU route prefixes with ECMP forwarding path on Junos ACX5448/ACX710 platforms
Product-Group=junos		On Junos ACX5448/ACX710 platforms, if the BGP-LU route prefixes points towards the ECMP forwarding path, the transit traffic drop is observed for the BGP-LU routes, due to the incorrect programming for the routes.

Resolved In: junos:22.1R3-S2 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: Gnats category for dynamic rendering infrastructure
1690598VMX :: Incorrect data encoding format is used for the parameter ISIS extended reachability TLV - max link bandwidth when passed to Influx DB server via GNMI
Product-Group=junos		For leaves of data type ieeefloat32, the value will be encoded in bytes while being streamed to collector. The value contained in such leaves may not be completely accurate.

Resolved In: evo:23.3R1-EVO
1698192EVO jkey path changed under protocol/isis. "isis/levels" is missing
Product-Group=junos		When using the proprietary subscribe RPC for telemetry, the "isis/levels" keyword is missing from the jkey output for leaf lists.

Resolved In: evo:22.1R3-S2-EVO evo:22.2R3-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:22.1R3-S2 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: EVO MACSEC Platform Independent Implementation
1712554The MACsec on the channelized IFD impacts the MACsec traffic on other channelized IFL interfaces within the same port and vice versa
Product-Group=junos		If both MACsec(media access control security) IFL(interface logical) and MACsec IFD(physical interface device) coexist on the channelized interface, enabling MACsec on the channelized IFD impacts the MACsec traffic on other channelized IFL interfaces within the same port and vice versa. This issue is applicable to MPC10E and MPC11E platforms.

Resolved In: evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.1R3-S3 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: EVPN control plane issues
1675054Junos OS and Junos OS Evolved: RPD core upon receipt of a specific EVPN route by a BGP route reflector in an EVPN environment (CVE-2022-22219)
Product-Group=junos		Due to the Improper Handling of an Unexpected Data Type in the processing of EVPN routes on Juniper Networks Junos OS and Junos OS Evolved, an attacker in direct control of a BGP client connected to a route reflector, or via a machine in the middle (MITM) attack, can send a specific EVPN route contained within a BGP Update, triggering a routing protocol daemon (RPD) crash, leading to a Denial of Service (DoS) condition. Continued receipt and processing of these specific EVPN routes could create a sustained Denial of Service (DoS) condition. Please refer to https://kb.juniper.net/JSA69898 [juniper.net] for more information.

Resolved In: evo:21.4R3-EVO evo:22.1R1-S2-EVO evo:22.1R3-EVO evo:22.2R2-EVO evo:22.3R1-EVO evo:22.4R1-EVO junos:21.3R3-S2 junos:21.4R2-S2 junos:21.4R3 junos:22.1R1-S2 junos:22.1R3 junos:22.2R2 junos:22.3R1 junos:22.4R1
1732414EVPN-VXLAN interconnection DCI forwarding problem observed when one of the AGW IRB interfaces deactivated
Product-Group=junos		On Junos platforms, using the Ethernet Virtual Private Network-Virtual extensible Local Area Network (EVPN-VXLAN) setup with active-active Anycast Gateway (AGW) within two different Data Centers (DCs). On the spine routers dc1-spine1 and dc2-spine1 the same Integrated routing and bridging (IRB) AGW address is configured. There is only one IRB interface in DC2 and no IRB in DC1. When IRB interface in DC1 is deactivate, the trigger of reprogramming same MAC received from DC2 missed as there is a separate macdb entry with vlan-id and VNI even if both are same Bridge domain (BD). Usually, it is expected to configure IRB on all Gateway (GW) nodes. If the user trying with IRB only on one GW node. If configuring with IRB on all GW nodes, the hosts will lose connectivity to the Virtual-gateway-address (VGA) address.

Resolved In: evo:22.4R3-EVO evo:23.2R1-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:22.1R3-S2-J1 junos:22.3R3 junos:22.4R3 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1715343Ping overlay vxlan replies Overlay-segment present even the bridge-domain has been deactivated
Product-Group=junos		The vxlan ping overlay request is recevied for a certain VNI on MX and the bridge-domain associcated with the VNI has been deactivated. However the MX still responses with "Overlay-segment present" sub-code in the reply message.

Resolved In: evo:22.3R3-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.1R3-S2 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
1718369[evpn_vxlan][dcf10] BUM Traffic received on DC-GW in ERB POD from Remote POD are not sent out
Product-Group=junos		Release note required from Development

Resolved In: 
PR NumberSynopsisCategory: EX4400 PFE software
1716902IGML/MLD queries may get dropped if received on the backup node when IGMP/MLD snooping is enabled
Product-Group=junos		On Junos QFX and EX in the VC (Virtual Chassis) scenario, when switch is acting as pure L2 (Layer 2), and forwarding IGMP (Internet Group Management Protocol)/MLD (Multicast Listener Discovery) query as transit traffic, if IGMP/MLD snooping is enabled then IGMP/MLD queries may get dropped if received on backup node resulting in IGMP/MLD groups to expire.

Resolved In: junos:21.4R3-S4 junos:22.4R2-S1 junos:23.1R2 junos:23.2R1 junos:23.2R2
PR NumberSynopsisCategory: EX4400 platform
1683753The mib walk with jnxOperatingDescr.1.1.0.0 returns blank, but jnxOperatingState.1.1.0.0 returns value
Product-Group=junos		On EX/QFX series switch, jnxOperatingDescr.1.1.0.0 returns blank, but jnxOperatingState.1.1.0.0 returns value.

Resolved In: evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:21.4R3-S3 junos:21.4R3-S4 junos:22.2R3 junos:22.3R1-S2 junos:22.3R2 junos:22.3R2-S1 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
1697678EX4400: Output of 'show chassis led' does not reflect accurately for port beacon configuration
Product-Group=junos		When the beacon LED for a port is configured as OFF, output of 'shot chassis led' incorrectly shows it as GREEN instead of OFF. When the beacon LED for a port is configured as ON, output of 'shot chassis led' incorrectly shows it as GREEN instead of 'GREEN Blinking'. Physical LED behavior reflects correctly as per beacon configuration

Resolved In: 
1709431MACsec:Traffic loss is seen while testing macsec scale.
Product-Group=junos		When high number of MACsec sessions present (more than 200) and traffic is passed over these interface, some of the MACsec session flap and there is traffic drop.

Resolved In: 
1710599On EX4400, links on a PIC may go down when FAST OIR is done with out recommended wait time.
Product-Group=junos		Links on a PIC may go down when FAST OIR is done with out recommended wait time. This may be device specific.

Resolved In: 
1714116EX4400 Link/Activity LED is not lit when it transits to the factory default configuration by pressing the Factory Reset/Mode button
Product-Group=junos		Press the Factory Reset/Mode button on the far right side of the front panel for 10 seconds. EX4400 transitions into factory-default configuration and the Link/Activity LEDs on the network ports and the QSFP28 ports should be lit steadily in green color but were off.

Resolved In: junos:21.4R3-S4 junos:22.3R2-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
1729464EX4400: While exporting telemetry data, transceiver data is also streamed when there is no transceiver in device itself.
Product-Group=junos		When data is streamed through telemetry, transceiver data is also streamed, even when there is no transceiver in device itself. There is no functional impact. There is no workaround for this issue.

Resolved In: 
PR NumberSynopsisCategory: MPC10 platform specific issues on EX92xx platform
1692365A self-ping blackhole is seen along with fmpc process crash in a rare scenario causing traffic loss
Product-Group=junos		On MX platforms with MPC10, MPC11, and LC9600, traffic impact is seen on the fabric links due to self-ping blackhole and fmpc process crash under the scaled config scenario.

Resolved In: evo:22.3R3-EVO junos:20.4R3-S7 junos:21.2R3-S5 junos:21.4R3-S3 junos:22.1R3-S3 junos:22.2R3 junos:22.3R3 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: SRX4100/SRX4200 platform software
1630981BGP down due to BFD expired; failover restored services
Product-Group=junos		All VPN traffic may internally drop during encryption / decryption processing in HW engine requiring PFE plane reset.

Resolved In: junos:20.4R3-S7 junos:21.4R3-S3 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: Integrated Routing & Bridging (IRB) module
1629345Inter vlan ipv6 traffic loss for some hosts after configuration remove and restore.
Product-Group=junos		For a topology with VSTP and VRRP configured and IPV6 traffic, if VSTP bridge priority is changed a couple of times (to trigger toggling of root bridge), it is possible that V6 traffic drop is seen on some of the streams.

Resolved In: 
PR NumberSynopsisCategory: jdhcpd daemon
1694952Auto image upgrade is not present when EX-VC is zeroized and VC is formed
Product-Group=junos		When an EX series VC (Virtual Chassis) members are zeroized or if it powered on for the first time after halt, "set chassis auto-image-upgrade" configuration is not configured during the process of ZTP (Zero-touch Provisioning) flow and VC formation. Absence of this configuration will not allow user to download configuration and images via ZTP.

Resolved In: junos:21.4R3-S4
1713619A jdhcpd process crash is observed on all Junos platforms
Product-Group=junos		On all Junos platforms with DHCP (Dynamic Host Configuration Protocol) relay/server/client configured, a jdhcpd process crash is observed when FPC (Flexible PIC Concentrator) is restarted or rebooted and the DHCP functionality could be impacted.

Resolved In: evo:22.4R3-EVO junos:21.2R3-S4-J16 junos:21.2R3-S5 junos:21.3R3-S4 junos:22.1R3-S2 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: Flow Module
166179622.2R1:SRX5K:SD-WAN: To track RE and PFE sync issue with NAT configs and closed scan session counter issue
Product-Group=junos		This issue exists in 22.2R1, 22.2R2 and 22.3R1.

Resolved In: junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:23.1R1
1661935In SD-WAN the association between VRF instance and VRF group fails for ISSU from 19.2~21.1 to 22.2R1
Product-Group=junos		On SRX and MX-SPC3 (Services Processing Card) supporting MX platforms in SD-WAN (Software-Defined Wide-Area Network), ISSU (In-Service Software Upgrade) from 19.2~21.1 to 22.2R1 will result in relationship failure of VRF (Virtual Routing and Forwarding) instance and VRF-group.

Resolved In: evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO junos:22.2R1-S2 junos:22.2R2 junos:22.2R3 junos:22.3R1 junos:22.3R2 junos:22.4R1
PR NumberSynopsisCategory: Firewall Policy
1724048Traffic loss will be observed after committing faulty or incorrect configuration
Product-Group=junos		On all Junos SRX, vSRX and NFX series platforms, commit after faulty or warning-induced configuration will trigger warning on the console which invoke unstable or unexpected behavior with the system. It can even invoke iked/kmd process to flap VPN resulting in traffic outage.

Resolved In: junos:20.4R3-S8 junos:21.2R3-S5 junos:22.1R3-S3 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
1724777The nsd process crash is seen when ISSU is performed on the cluster
Product-Group=junos		The nsd (Network Security Daemon) process crash is observed when ISSU (In Service Software Upgrade) is performed on HA (High Availability) clusters using Destination NAT (Network Address Translator).

Resolved In: junos:22.1R3-S3 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1722889[evpn-vxlan][dcf9] Duplicate BUM traffic is received on EVPN VXLAN on 22.2R3.13
Product-Group=junos		Release note required from Development

Resolved In: 
1727954On all Junos and Junos Evolved platforms, the l2ald process memory usage is seen to increase over time
Product-Group=junos		Service disruptions are seen due to a consistent increase in l2ald (Layer 2 Address Learning Daemon) memory usage.

Resolved In: evo:21.4R3-S4-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:22.1R3-S3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: Port-based link layer security services and protocols that a
1698687Traffic loss can be seen while switching between primary and fallback sessions in MACsec setup
Product-Group=junos		On all Junos and Junos Evolved platforms supporting MACsec (Media Access Control security), traffic drop can be seen when MACsec Primary and fallback sessions are configured and there is a higher transmit-delay time (~6 sec). This is a timing issue and occurs when switching from primary to fallback or vice-versa when changing the pre-shared-key's CAK (Connectivity Association Key) value in CLI (Command Line Interface) on the non-key-server side and at the same time key-server generates a new SAK (Secure Association Key) for pre-shared-key due to expiration of sak-rekey timer, i.e. sak-rekey & primary to fallback key-switch both occurs at the same time. This issue is self-recovered once the SAK from fallback is recovered.

Resolved In: evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: SW PRs for MPC10E Fabric
1676777Traffic drop can be seen on MX platforms with MPC10E-10C line card
Product-Group=junos		On MX platforms with MPC10E-10C line card, with line rate traffic, continuous traffic drop can be seen when fabric mode is changed from increased bandwidth to redundant.

Resolved In: evo:22.1R3-EVO evo:22.2R2-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO junos:20.4R3-S8 junos:21.2R3-S3 junos:21.2R3-S6 junos:21.3R3-S3 junos:21.4R3-S1 junos:21.4R3-S4 junos:22.1R3 junos:22.1R3-S3 junos:22.2R2 junos:22.2R3 junos:22.3R2 junos:22.4R1
PR NumberSynopsisCategory: For multicast snooping on MX
1699784The mcscnoopd process will be stuck in resync state after snooping configuration is deleted and added again immediately
Product-Group=junos		On all Junos platforms, when the multicast snooping configuration is deleted and added again immediately, the mcscnoopd (multicast-snooping process daemon) process will be stuck in the resync state, impacting the multicast traffic.

Resolved In: evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:21.4R3-S4 junos:22.3R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: Multicast for L3VPNs
1700345The rpd crash happens when Multicast VPN (Virtual Private Network) is configured with separate route-targets scenario
Product-Group=junos		This happens only when MVPN protocol has separate route targets configured and then both the address families are disabled. rpd (Routing process daemon) infra parsing does not check if MVPN protocol is disabled and hence will create the auto policies for route-targets if configured. So if those policies are not marked as active in MVPN configuration flow, it does not get resolved and thereby the policy object may not be valid thus leading to the core.

Resolved In: evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:22.4R3 junos:23.1R2 junos:23.2R1
1708572The pseudowire interface is not showing after performing the switchover
Product-Group=junos		On all Junos and Junos Evolved platforms, after performing RE(Routing Engine) switchover the pseudowire interface is not showing and traffic will be blackhole.

Resolved In: evo:23.2R1-EVO junos:23.2R1
PR NumberSynopsisCategory: MX Timing software
1652275PTP Playback Engine reset error is reported sporadically with PTP FPGA Firmware version A4 7
Product-Group=junos		PTP Playback Engine reset error is reported sporadically with PTP FPGA Firmware version A4 7 No functionality impact.

Resolved In: evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:20.4R3-S8 junos:21.2R3-S6 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
1704644Software improvement for PTP nbr-update || lcinfo_bmc || utc_arrival_time || lcinfo_msg || utc_arrival_time
Product-Group=junos		Enhancement needed on PTP nbr-update to improve user experiences.

Resolved In: evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:20.4R3-S6 junos:21.2R3-S6 junos:22.1R3-S1 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: MX10K platform
1684728An interface configured as 1G may flap on a port with the mixed speeds of 1G and 10G after a PIC restart
Product-Group=junos		On MX10008, MX10004, and MX10016 platforms with LC2101, when the channelized interfaces of a port are configured with mixed port speeds of 1G and 10G, after a Physical Interface Card (PIC) reboot the 1G channelized interface will keep flapping. Or, it may also remain down. This will impact all the services running through the 1G channelized interface.

Resolved In: evo:22.1R3-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO junos:21.4R3-S1 junos:22.1R3 junos:22.2R2 junos:22.2R3 junos:22.3R1 junos:22.3R2 junos:22.4R1
PR NumberSynopsisCategory: Category for tracking Olympus-MX issues
1671649Traffic loss may be seen due to SPC3's packets getting stuck
Product-Group=junos		On Junos MX960, MX480 and SRX5000 series platforms with SPC3 card, Flowd restart or PIC (Physical Interface Card) going offline/online may cause SPC3's sending of packets to get stuck.

Resolved In: evo:22.1R3-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:20.4R3-S5 junos:21.1R3-S4 junos:21.2R3-S3 junos:21.3R3-S3 junos:21.4R3-S1 junos:22.1R2-S1 junos:22.1R3 junos:22.2R1-S2 junos:22.2R2 junos:22.2R3 junos:22.3R1-S1 junos:22.3R2 junos:22.4R1 junos:23.1R1
PR NumberSynopsisCategory: FreeBSD Kernel Infrastructure
1681783On Ex4400 upgrade failure happens when upgrading through a USB drive.
Product-Group=junos		On EX4400 upgrade failure happens when upgrading through a USB drive.

Resolved In: junos:19.1R3-S10 junos:19.2R3-S7 junos:19.4R3-S10 junos:20.3R3-S6 junos:20.3X75-D43 junos:20.3X75-D46 junos:20.4R3-S5 junos:21.2R3-S3 junos:21.2R3-S4 junos:21.3R3-S2 junos:21.3R3-S3 junos:21.4R3-S1 junos:21.4R3-S4 junos:22.1R2-S1 junos:22.1R2-S2 junos:22.1R3 junos:22.2R1-S2 junos:22.2R2 junos:22.2R2-S1 junos:22.2R3 junos:22.3R1-S1 junos:22.3R2 junos:22.4R1
1691036Enable kvmclock time source with vDSO support
Product-Group=junos		Earlier implementation of kvmclock with vDSO (virtual Dynamic Shared Object) which helps avoid the system call overhead for user space applications had problem of time drift, the latest set of changes takes care of initializing the clock after all auxiliary processors are launched so that the clock initialization is accurate.

Resolved In: junos:23.1R2 junos:23.3R1
1717710Unable to take recovery snapshots after USB upgrade is performed on ACX710
Product-Group=junos		On ACX710 platform, the OAM (Operations, Administration and Maintenance) volume seems unpopulated when an upgrade is performed with USB (Universal Serial Bus) drive or zeroize media. This leads to failure in taking recovery snapshots.

Resolved In: junos:21.2R3-S5 junos:21.3R3-S4 junos:21.4R3-S4 junos:22.1R3-S2 junos:22.2R3 junos:22.3R2-S1 junos:22.3R3 junos:22.4R1-S2 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: "ifstate" infrastructure
1714785VMcore crashes in a rare scenario
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).

Resolved In: junos:21.1R3-S5 junos:21.2R3-S5 junos:21.3R3-S4 junos:22.1R3-S2 junos:22.3R3 junos:22.4R2 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: Express Chip L3 software
1713279Next-hop programming issue at PFE on Junos PTX and QFX10k platforms when the member of unilist is in hold state
Product-Group=junos		On PTX Series routers and the QFX10000 line of switches, traffic going over unilist is dropped when unilist member goes from next-hop hold state to unicast/aggregate state.

Resolved In: junos:20.3X75-D42 junos:20.3X75-D43 junos:20.3X75-D46 junos:20.3X75-D51 junos:20.4R3-S8 junos:21.2R3-S5-J5 junos:21.2R3-S6 junos:21.4R3-S4 junos:22.1R3-S3 junos:22.3R3 junos:22.4R2 junos:22.4R2-S1 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: Path computation client daemon
1678970The pccd process might crash during MBB for an externally controlled LSP
Product-Group=junos		On MX and PTX platforms the pccd (Path Computation Client Process) might crash when MBB (Make before break) update is received from rpd.

Resolved In: evo:22.1R3-EVO evo:22.2R2-EVO evo:22.3R1-EVO evo:22.3R2-EVO evo:22.4R1-EVO junos:21.2R3-S3 junos:22.1R3 junos:22.2R2 junos:22.3R1 junos:22.3R2 junos:22.4R1
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:23.1R1
PR NumberSynopsisCategory: Phone-Home-Client Infrastructure
1687926Zero touch provisioning of the EX4100 virtual chassis might fail in rare situations
Product-Group=junos		When EX4100 devices are first powered on, the zero touch provisioning by phone home will provision the devices. In rare situations where the powered devices are already connected with VCP cables to form a VC, the zero touch provisioning using phone home might keep retrying. The workaround for the issue is to power cycle all the devices in the VC.

Resolved In: 
PR NumberSynopsisCategory: QFX access control list
1710704FPC is down on QFX5k after committing an IPv6 filter
Product-Group=junos		On Junos QFX5k series platforms, traffic is getting dropped as FPC (Flexible PIC Concentrators) is not up. The issue is seen when a 'flexible-match-range' is configured in an IPv6 firewall filter term and that filter is applied to any IPv6 interface. FPC goes down after committing the filter.

Resolved In: junos:21.4R3-S3 junos:22.1R3-S2 junos:22.3R3 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: QFX L2 PFE
1705853Tracking PR to add the null check for list_get_head if magic is NULL.
Product-Group=junos		as list_get_head function is called in multiple places in pfe we needed previous 3 functions on the stack which had called list_get_head so we could debug why 'list_get_head list has bad magic ' this error has occured.

Resolved In: junos:20.2R3-S8 junos:20.4R3-S8 junos:21.2R3-S6 junos:22.1R3-S3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
1730076Packets received on a port that is in "LACP Detached" state is getting forwarded
Product-Group=junos		On all Junos EX46xx/QFX5k (except QFX5100) platforms, child links that are in LACP (Link Aggregation Control Protocol) detached state are up and accepting incoming traffic, expecting it to drop.

Resolved In: junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1666260Traffic loss might be seen when l2circuit configurations are deactivated and activated on QFX5110
Product-Group=junosvae		On QFX5110 platforms with more than one l2circuit configured, deactivating and activating the l2circuit configurations successively might cause traffic drop on one or more l2circuits.

Resolved In: junos:20.2R3-S8 junos:20.4R3-S8 junos:21.2R3-S6 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
1695847Traffic forwarding fails when deleting all L2 related configurations
Product-Group=junos		On QFX and EX series platforms, traffic loss will be observed for deleting all Layer2 related configurations when both L2 and Layer3 configurations are present.

Resolved In: junos:20.4R3-S7 junos:21.1R3-S5 junos:21.2R3-S5 junos:21.3R3-S4 junos:21.4R3-S3 junos:22.1R3-S2 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1688323Traffic loss is observed in IP fabric when there is a change in the underlay network
Product-Group=junos		On Junos QFX5K series platforms, configuration-change/protocol flapping/port flapping in Ethernet Virtual private network (EVPN) Virtual Extensible LAN (VXLAN) can cause traffic loss (changes related to the underlay network).

Resolved In: junos:20.4R3-S7 junos:21.2R3-S5 junos:21.4R3-S4 junos:22.3R3 junos:22.3R3-S1 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: QFX5100 Virtual Chassis
1679919PFE process crash might be observed on QFX5100 platforms
Product-Group=junos		On QFX5100 platforms (both stand-alone and VC scenario) running Junos, occasionally during the normal operation of the device, PFE (Packet Forwarding Engine) can crash resulting in total loss of traffic. The PFE reboots itself following the crash.

Resolved In: junos:20.2R3-S8 junos:20.4R3-S7 junos:21.2R3-S5 junos:21.3R3-S4 junos:21.4R3-S2
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platfom issues
1709938VC members are split when removing and inserting em0 cable
Product-Group=junosvae		On QFX5120-48YM, QFX5120-48Y-8C, QFX5120-32C and EX4650-48Y platforms, when the management em0 cable is removed and reinserted in the Virtual Chassis (VC) environment, the VC members will split into separate VCs. The VC members will remain in the split state for approximately 5 mins.

Resolved In: junos:21.2R3-S5 junos:21.3R3-S4 junos:21.4R3-S4 junos:22.1R3-S2 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1-S1 junos:23.1R2 junos:23.2R1
1710205On EX4650, show chassis hw exten doesn't give fan tray info
Product-Group=junos		On EX4650, show chassis hw exten doesn't give fan tray info

Resolved In: 
PR NumberSynopsisCategory: RPD infrastructure issues related to NSR, GRES, switchover, 
1732702JDI-RCT:- Observed (BRCM-VIRTUAL, brcm_virtual_tunnel_destroy_overlay_nh(), 2145:Failed to delete egr_if(400248) err-Operation still running ) with evpn vxlan end to end config after switchover master VC via cli
Product-Group=junos		after GRES, indirect-next hop index may change, this is not harmful to traffic.

Resolved In: 
PR NumberSynopsisCategory: KRT Queue issues within RPD
1721032Local route is not added in the secondary FIB on all Junos SRX platforms and routes will be permanently stuck in KRT queue
Product-Group=junos		On all Junos SRX platforms when ST (Secure-Tunnel) interface with P2MP (Point-to-Multipoint) is configured and interface routes are leaked via RIB-group (Routing Information Base), local route of the ST interface will not be leaked into forwarding-table of the secondary-RIB and it will be stuck in the KRT (Kernel Routing Table) queue.

Resolved In: evo:21.2R3-S6-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:21.2R3-S6 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1716436Traffic loss due to incorrect route resolution and KRT queue getting stuck with 'EINVAL -- Bad parameter in request' error
Product-Group=junos		On all Junos and Junos OS Evolved platforms, due to a bug in route resolution over specific types of next hops, the route can resolve over itself and the nexthop chain keeps expanding. Due to this issue, the depth of recursion gets higher than supported and the KRT (Kernel Routing table) queue returns errors for nexthops. As a result, there will be incorrect route resolution, traffic loss and occasionally, the rpd (routing protocol deamon) crashes. The necessary configurations and conditions that will result in this issue are below 1. BGP (Border Gateway Protocol) Prefix-Independent Convergence (PIC) ("protect core") is configured and BGP receives same prefix from EBGP and IBGP neighbors 2. BGP LU (Labeled Unicast) with "protection" to create backup path to protect the active and BGP receives same prefix from EBGP and IBGP neighbors 3. Mutually recursive Route resolvability situations like Resolving using Default-route (not having proper resolution config)

Resolved In: evo:23.2R2-EVO evo:23.3R1-EVO junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1677749High CPU is seen on the platforms running IPv6
Product-Group=junos		On all Junos platforms, high CPU is seen due to ipv6 router-advertisement.

Resolved In: evo:22.1R3-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO junos:22.1R3 junos:22.2R3 junos:22.3R1-S1 junos:22.3R2 junos:22.4R1
PR NumberSynopsisCategory: Resource Reservation Protocol
1685182RSVP path tear is not encapsulated by the MPLS header when bypass is configured
Product-Group=junos		On all Junos and Junos Evolved platforms, RSVP(Resource Reservation Protocol) path tear is not encapsulated by the MPLS(Multiprotocol Label Switching ) header, when "no-enhanced-frr-bypass" is configured on the routers that undertake FRR(fast re-route) procedures after the failure.

Resolved In: evo:21.2R3-S3-EVO evo:21.3R3-S3-EVO evo:21.4R3-EVO evo:22.1R3-EVO evo:22.2R2-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO junos:21.2R3-S3 junos:21.3R3-S3 junos:21.4R3-S1 junos:22.1R3 junos:22.2R2 junos:22.2R3 junos:22.3R2 junos:22.4R1
1713392PathErr with RoutingProblem error code generated unexpectedly during dual failure local repair
Product-Group=junos		When an LSR acts as a Point of Local Repair (PLR) as well as a Merge Point (MP) for an LSP during a double failure scenario, the LSR incorrectly originates one or two PathErr messages with RoutingProblem (code=24/2) instead of originating PathErr with NotifyError (code/subcode=25/3). This will not cause any service impact if the ingress LER would not react adversely to RoutingProblem error (code=24/2).

Resolved In: evo:21.4R3-S4-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:21.4R3-S4 junos:22.1R3-S2 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: SW PRs for SCBE3 fabric
1724007Complete traffic blackhole from one PFE to another on fabric links after injecting/reporting CRC errors on fabric links of MX10008
Product-Group=junos		On the MX10008 platform, the low-priority stream might be marked as a destination error and as a result, the low-priority stream is stuck and all traffic might get dropped. Complete traffic blackhole is observed from one PFE to another.

Resolved In: junos:21.4R3-S4 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: Secure Web Proxy functionality on Junos
1719703The flowd process crash is observed when the web proxy packet reinjection fails
Product-Group=junos		On SRX-branch series, SRX4100, SRX4200, and vSRX platforms, packet reinjection fails if the load on the system is high and the web proxy tries to reinject the packet.

Resolved In: junos:20.2R3-S8 junos:20.4R3-S7 junos:21.2R3-S5 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: Generic platform and infra issues for MS-MIC and MS-MPC(XLP)
1700462JDI-REG: MX2010: mspmand.core.ms91.0.gz
Product-Group=junos		Release note needed

Resolved In: 
PR NumberSynopsisCategory: Bug and Review Tracking for Segment routing traffic eng
1720031The rpd process crash will be observed while creating/updating the PCEP tunnel
Product-Group=junos		On Junos and Junos OS Evolved platforms, when SR (Segment Routing) PCEP (Path Computation Element Protocol) provisional tunnel is configured along with the template but the template has delegation configured, then the PCEP update message received for creating/updating tunnels is causing the rpd process crash and tunnel creation/update will fail for PCEP provisional tunnel.

Resolved In: evo:22.3R3-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:21.2R3-S5 junos:21.4R3-S4 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1-S1 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: Remote Access VPN issues on SRX
1732746nsd crash impacting remote access vpn on SRX devices
Product-Group=junos		nsd crash can be observed on SRX platforms when the SSL certificate does not have the common name (CN), Organization Unit (OU) and Organization field, this leads to break in remote access connectivity.

Resolved In: junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: SRX branch platforms
1713759Continuous vmcores observed on the secondary node when committing the "set system management-instance" command
Product-Group=junos		On Junos SRX3xx series platforms, when the "set system management-instance" command is committed on the secondary node, continuous vmcores are observed on primary and secondary nodes. No recovery action is needed for the primary node and the secondary node of the cluster reboots automatically to recover from the error. The cluster redundancy is not restored until the management-instance knob is removed using the "delete system management-instance".

Resolved In: junos:20.4R3-S8 junos:21.2R3-S6 junos:21.4R3-S3 junos:22.1R3-S2 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.1R2 junos:23.2R1
1715247Interface speed stays 100Mbps when removing speed and duplex command separately
Product-Group=junos		On SRX platforms, Interface speed stays 100Mbps when removing speed and duplex command separately

Resolved In: junos:20.4R3-S8
PR NumberSynopsisCategory: SRX-1RU platfom datapath SW defects
1620773SRX4600 - Packet drop or srxpfe coredump might be observed
Product-Group=junosvae		Packet drop or srxpfe coredump might be observed on SRX 4600 during periods of high traffic

Resolved In: junos:22.1R3-S3 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.1R1-S1 junos:23.2R1 junos:23.2R2 junos:23.3R1
1712167Ping drop is observed between directly connected devices in SRX4600
Product-Group=junos		On Junos SRX4600 platform may encounter upto 25% packet packet loss after upgrade to Junos image using FPGA v1.63.

Resolved In: junos:21.4R3-S4 junos:22.1R3-S3 junos:22.3R3 junos:22.4R3 junos:23.1R1-S1 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: Trio LU, IX, QX, MQ chip drivers, ucode & related SW
1649555Errors "CTRL:: PpmCtrl:: sessionDown: Received session down event for invalid client clientId" are seen after restart chassisd
Product-Group=junos		Following error can be seen on AFT based platforms/line-cards on MX platforms after the "restart chassisd" "CTRL:: PpmCtrl:: sessionDown: Received session down event for invalid client clientId"

Resolved In: 
PR NumberSynopsisCategory: Trio pfe qos software
1732690Heap memory leak on MPCs used for subscriber termination.
Product-Group=junos		Heap memory leak on access MPCs used for subscriber termination may be observed in a subscriber-management environment.

Resolved In: evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:22.4R3 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: Trio pfe bridging, learning, stp, oam, irb software
1731564VPLS traffic gets blackholed by qualified-bum-pruning mode
Product-Group=junos		On all MX and EX9K platforms, qualified-bum-pruning-mode completely blackholes VPLS (Virtual Private LAN Service) traffic with network-services configured in enhanced-ip mode.

Resolved In: evo:23.3R1-EVO evo:23.4R1-EVO junos:20.4R3-S7-J1 junos:20.4R3-S8 junos:23.3R1
PR NumberSynopsisCategory: Trio pfe multicast software
1686068Disabling PFE triggers the memory leak which may cause FPC to crash
Product-Group=junos		On Junos MX platforms with specific line cards, when PFE (Packet Forwarding Engine) is disabled, scenarios like multicast receiver join/leave that result in allocation and de-allocation of memory on disabled PFE can cause a memory leak. This is because memory is allocated on the disabled PFE, but not freed.

Resolved In: evo:22.4R3-EVO evo:23.2R1-EVO junos:21.2R3-S5 junos:22.4R3 junos:23.2R1
PR NumberSynopsisCategory: PTX/QFX100002/8/16 interface software
1712007The interface does not come up or keeps flapping
Product-Group=junos		On Junos PTX10008/PTX100016 devices with LC1101/LC1102 line cards, any event that causes an interface state change can lead to interface flapping or the interface may not come back at all. This leads to traffic impact on that interface.

Resolved In: junos:20.4R3-S4-J14 junos:20.4R3-S6-J4 junos:20.4R3-S7 junos:21.1R3-S5 junos:21.2R3-S5 junos:21.3R3-S4 junos:21.4R3-S3 junos:22.1R3-S2 junos:22.2R3 junos:22.3R3 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: VMHOST platforms software
1726775Upgrading the i40e NVM Firmware on Routing Engines with VM Host Support
Product-Group=junosvae		Steps for Upgrading the i40e NVM Firmware on Routing Engines with VM Host Support is described in https://www.juniper.net/documentation/us/en/software/junos/junos-install-upgrade/topics/task/vmhost-nvm-upgrade.html i40e NVM version 6.01 is the prerequisite to install a LTS19 based image, else image installation will fail. This prerequisite is not needed now.

Resolved In: junos:21.4R3-S4 junos:22.1R3-S3 junos:22.2R3-S1 junos:22.3R2-S1 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: Xellent Platform issues
1709817Ports with QSA adapter are down
Product-Group=junos		On Junos PTX1000 and PTX10002-60C/QFX10002-60C platforms, ports which use the QSA (QSFP-to-SFP Adapter) may not come up when running software version containing the fix for PR 1620527.

Resolved In: junos:20.4R3-S7 junos:21.1R3-S5 junos:21.2R3-S5 junos:21.3R3-S4 junos:21.4R3-S3 junos:22.1R3-S2 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.1R2 junos:23.2R1


 

Modification History

2025-01-21 - Correct the access to be public.

First Publication 2023-06-15