Open Issues

VXLAN VNI (multicast learning) scaling on QFX5110 traffic issue is seen from VXLAN tunnel to Layer 2 interface. PR1462548

Pim VXLAN not working on TD3 chipsets enabling VXLAN flexflow after release 21.3R1. Customers Pim VXLAN or data plane VXLAN can use the version 21.3R1. PR1597276

QFX5100-24Q devices VC (Virtual-chassis) is in unstable state for 3-7 minutes causing traffic loss. PR1661349

When the remote end server and system reboots, QFX5100 platform ports with SFP-T 1G inserted might go into a hung state and remain in that state even after the reboot is complete. This might affect traffic after the remote end system comes online and resumes traffic transmission. PR1665800

When the power cable is removed or inserted, jnxPowerSupplyFailure and jnxPowerSupplyOK might not be generated on backup FPC. PR1667952

On QFX5100 platforms (both stand-alone and VC scenario) running Junos OS, 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. PR1679919

On Junos QFX5100 and EX4600-Virtual Chassis (VC) and Virtual Chassis Fabric (VCF) platforms on upgrading Virtual Chassis Fabric (VCF) and toggling the interface, when FPC (Flexible PIC Concentrators) is disabled and rebooted, the member fails to join the virtual chassis and the interface remains disabled even after been enabled. PR1689499

When TISSU upgrade is done from 22.4 release onwards, the box come up as backup Routing Engine. Work-around:- To make is primary following command needs to be run again. sysctl -w hw.lc.issuboot=0 sleep 10 sysctl -w hw.re.issu_state=0 sleep 10 sysctl -w hw.re.tissu=0 sleep 10 sysctl -w hw.product.pvi.config.chasd.no_re_status_on_backup=1 sleep 60. PR1703229

The show chassis hardware indicates duplicate entries for PSU and FAN tray after USB clean install or zeroize. PR1704106

On Junos OS and Junos OS Evolved platforms, the dcpfe (Dense Concentrator Packet Forwarding Engine) process crash will be observed due to memory fragmentation issue. This is a very rare case and would impact traffic as due to dcpfe failure the PFE restarts, so the interfaces will flap. PR1711860

On EX4650 and QFX5120-48Y, the SFP-LX interface will not be UP when different Small Form-factor Pluggable(SFP-10GBASE-T and SFP-LX) are plugged in within the same 4 port group. The presence of the 10GE-T SFP resets the speed of the quad back to 10G even if the quad port speed is set to 1G. Normally 10G interface by itself will be up when set to 1G if no other SFP is plugged in. PR1714833

In a VC of QFX5100-24Q with an expansion module EX4600-EM-8F, if VC is formed on 10G ports then after the reboot of VC, the 10G connections will be lost and the line card will show as not present. This will impact traffic on the 10G ports after connection is lost. PR1718062

On the Junos QFX5200 platform, sometimes 100G link will go down and will remain down. PR1725116

On QFX5000 platforms with QSFP+-40G-ACU10M and Virtual Chassis configured, traffic loss will be observed due to CRC (Cyclic redundancy check) errors. PR1729067

This problem is seen on QFX10000 platform, when ingress Sflow is enabled on bridged AE (tagged) interfaces and that incoming traffic gets forwarded through IRB interfaces on an ECMP path. In ECMP scenario, Sflow injects TAL request into the ASIC which are resulting in the traps tracked through this PR. Hence the forwarding traffic is unaffected. PR1729316

On QFX5100 platforms error occurs while configuring packet-forwarding-options. PR1730451

When the remote end server/system reboots, QFX5100 platform ports with SFP-T 1G inserted might go into a hung state and remain in that state even after the reboot is complete. This might affect traffic after the remote end system comes online and resumes traffic transmission. PR1742565

In a QFX51200-48YM-8C VC setup, after a primary switch over fan tray of linecard might not be displayed in show chassis hardware and show chassis environment. There is no functional impact. PR1758400

When there are a large number of aggregated (AE) interfaces on a system, deleting all of them together and adding them back can lead to a race condition. This could result in a few of the interfaces not being programmed correctly. PR1781955

Graceful Routing Engine Switchover (GRES) not supporting the configuration of a private route, such as fxp0, when imported into a non-default instance or logical system. PR1754351

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. PR1461339

On all Junos OS platforms, if a speed mismatch happens in the LAG (Link Aggregation) & member interface then a traffic drop will be seen. PR1725168

On QFX5100 and QFX5110, vendor-id format maybe incorrect for network ports. This does not impact the ZTP functionality or service. The DHCP client configuration is coming from two places, that is AIU script and VSDK sandbox. The DHCP client configuration coming from AIU script has the serial ID in vendor ID where as the default configuration from sandbox does not have. PR1601504

On Junos OS, 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. PR1692102

With SR4 optics on QFX5210 some times we can see partial continuous traffic drop observed on IPv4 and IPv6 streams (framing errors). PR1785882