Open Issues

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

PIM VXLAN does not work on the TD3 chipsets that enables the VXLAN flexflow. PR1597276

When the remote end server or 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

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

On Junos QFX5100-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

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

On all QFX5000 platforms, with VXLAN (Virtual Extensible LAN) configured and due to a stale next hop entry of vtep (vxlan tunnel end point) interface, dcpfe (Dense Concentrator Packet Forwarding Engine) process crash was observed. PR1712175

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

If we observe any slowness in accessing the VTY and could see any hogging or scheduler slip messages in syslog. It is advised to run the debug commands manually, instead of running it through RSI.PR1721297

FRR with Type-1 ESI takes more time to converge as Type-1 ESI is build on partner systemid and adminkey. When the link goes down partner system ID is lost and interface is withdrawn from the ESI.PR1722348

On the Junos QFX5200 platform, sometimes upon restarting the device the 100G link will not come up and will remain down, impacting the traffic flowing through it.PR1725116

On all Junos OS and Junos OS Evolved platforms in the EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) scenario, when the configuration statement switch-options no-mac-learning is configured, the MAC-IP entry will still be learned even though the MAC learning is disabled due to which the proxy ARP (Address Resolution Protocol) will not work properly on the leaf device and it will respond with a wrong MAC address for the ARP request.PR1727119

On all Junos QFX5000 (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. PR1730076

QFX5120 VSTP on VLAN-bridge might block all packets on family inet/inet6 interfaces in SP style. PR1732718

On all inserted FPCs of Junos OS based QFX10008 and QFX10016 platforms, due to SIB (Switch Interface Board) ASIC (Application-Specific Integrated Circuit) issue on fabric, packets are getting dropped and major errors PECHIP_CMERROR_EPW_MISC_INT_EVENTS_CRC_ERR (0x2101aa) are reported. These errors are not auto-cleared on a couple of FPCs.PR1734735

On QFX5120-48YM-8C : PTP 1PPS measurement will not be supported. PR1736385

In a combination of EX4650 connected to EX4400 and Junos OS based QFX5000 platforms connected to EX4400 using 25G-LR(Long Range) optics, FEC(Forward Error Correction) value mismatch between directly connected devices would cause the link to go down on Junos release version 20.4R3-S8 and above and leads to complete traffic loss. PR1738077

On Junos OS QFX5000 platforms, no MAC-learning on the interface results in traffic drop due to hardware programming not being updated for the child interface under AE (Aggregated Ethernet) when encapsulation ethernet-bridge is configured on the AE interface associated with VxLAN (Virtual Extensible LAN) VLAN. PR1738205

On Junos OS QFX5000 platforms in the EVPN-VxLAN scenario, due to high convergence time, traffic loss is more than expected when the uplink to the spine disabled (CLI initiated uplink failover). PR1738276

On Junos OS QFX10000 platforms, on configuring diffServ code point (DSCP) classifier and when inet or inet6 is configured with custom dot1p on interface, default DSCP classifiers are not getting removed properly. PR1738981

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

Pim VXLAN does not work on the TD3 chipsets that enables the VXLAN flexflow. PR1597276

When the remote end server or 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

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 OS QFX5100 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

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

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

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

On QFX5100 and QFX5110, vendor-id format might be 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 it. PR1601504

In EVPN VXLAN topology with DHCP stateless relay (forward-only) configured at Layer 3 gateways, Jdhcpd broadcasts snooped unicast offer packets. That leads to the offer getting dropped on its way to the client and then the IP negotiation fails. PR1722082

On all Junos OS and Junos OS Evolved platforms, if the nexthop of a flow route is the same as it was before when reconfiguring flow routes, memory leak occurs. High memory use of routing process daemon(rpd) is seen as a result of this leak. A kernel out of memory message is observed which results BGP flap. PR1742147

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