Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Open Issues

Learn about open issues in this release for QFX Series switches.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Class of Service (CoS)

  • On QFX5100 switches, traffic might not get classified based on a fixed classifier in MPLS in the VXLAN scenario. PR1650051

Layer 2 Ethernet Services

  • The DHCP client configuration comes from two places that is, AIU script and vsdk sandbox. The DHCP client configuration comes from AIU script has the serial ID in the vendor ID where as the default configuration from sandbox does not have. There is no impact on functionality or service. PR1601504

Layer 2 Features

  • In case of the access-side interfaces used as SP-style interfaces, when you added a new logical interface and if already a logical interface on the physical interface exist, there is 20 to 50 milliseconds traffic drops on the existing logical interface. PR1367488

Platform and Infrastructure

  • On all Junos platforms, while using source-address NTP configuration parameter and issue the set ntp date command from the CLI, packets gets sent with the source address of the outgoing interface rather than the manually configured IP address. Typically, the manually configured IP address would be a loopback address. The problem does not apply to automatically generated NTP poll packets.PR1545022

  • On QFX5100 line of switches, inserting or removing optics on a port might cause a Packet Forwarding Engine Manager CPU spike and an eventual microcode failure. PR1372041

  • VXLAN VNI (multicast learning) scaling on QFX5110 devices, traffic issue occurs from VXLAN tunnel to Layer 2 interface. PR1462548

  • 5M DAC connected between QFX10002-60C devices does not link up. But with 1M and 3M DAC this interop works as expected. The QFX10002-60C or traffic generator the same 5M DAC works seamlessly. There seems to be certain SI or link level configuration on the QFX10002-60C devices, which needs to be debugged with the help from HW and SI teams and resolved. PR1555955

  • To avoid the additional interface flap, interface hold time needs to be configured. PR1562857

  • Pim VXLAN does not work on TD3 chipsets enabling VXLAN flexflow after Junos OS release 21.3R1. Customers Pim VXlan or data plane VXLAN can use Junos OS release 21.3R1. PR1597276

  • On QFX5100 switches, optical power appers after you detach and attach the QSFP on a disable interface. PR1606003

  • On QFX5120-48Y devices, when a scaled configuration and baseline configurations gets loaded multiple times one after other without much wait time in between then traffic or protocols on pure Layer 3, interfaces might behave in an undefined or unexpected manner. PR1612973

  • On QFX10002-60C switches after the system gets rebooted, the FPC 0 Major Errors alarm might appear due to a rare timing issue. The issue could cause the host path traffic to get dropped. It is a rare issue and does not always happen during reboot. You must use the request vmhost reboot command for recovery. PR1613229

  • The backup FPC loses their connection to primary when you add the new members to the VCF (Virtual Chassis Fabric). PR1634533

  • On all devices running Junos OS, where this is a high BGP scale with flapping route and the BGP Monitoring Protocol (BMP) collector or station is very slow, the rpd process might crash due to memory pressure. PR1635143

  • When you enable MACSEC and VRRP on QFX5120 Virtual Chassis, the MACSEC sessions flaps at random times. Without VRRP this issue does not occur. PR1640031

  • On all QFX5100 Virtual Chassis platforms, after the reboot, Virtual Chassis port (VCP) ports might not establish a VCP connection and Cyclic Redundancy Check (CRC) errors gets generated. PR1646561

  • On QFX switches, IPv6 traffic output byte (ipv6-transit-statistics) would not be in expected range as per traffic generator status. PR1653671

  • QFX5100-24Q Virtual Chassis in the Unstable state for 3 to 7 minutes causes traffic loss. PR1661349

  • When the remote end server or system reboots, QFX5100 switches port with SFP-T 1G inserted might go into the 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

  • Each locally learned ARP/ND nexthop requires unique fabric token from Kernel. This unique token maps to physical address in HW and this address points to EDF memory for the ARP/ND nexthops. Token pool in kernel is also used by different features like flood nexthops, arp/ndp nexthops. Token usage has increased as tokens are now used by IRB interfaces and default mesh groups also. 96,000 ARP/ND scale might not be achievable always. It is recommended to scale upto 95,000 ARP/ND. PR1673626

  • On QFX5100 devices, media type for SFP+-10G-CU1M and SFP-T cables gets displayed as Fiber. PR1570555

  • On QFX5110 Virtual Chassis, FPC might gets disconnected with 24000 DHCPv6 relay scaling after the traffic stops. The pfe_listener_disconnect error message gets generated. PR1594748

  • On QFX10008 devices, statistics for multicast packets is not as expected as the packets has Layer 2 header strips during replication in the Packet Forwarding Engine because of which it is not forwarded to the next hop. PR1678723