Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


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.


  • A core may be seen when global level telemetry sensor is enabled and data streamed every 1 second. PR1570757

General Routing

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

  • After repeated deletion and addition of a logical switch on an NSX-V setup, with OVSDB configured, ping between the VM to the baremetal server fails intermittently (only on a few iterations out of the total number of iterations). PR1506097

  • Changing the scaled firewall profiles on the fly does not release the TCAM resources as expected. PR1512242

  • On the QFX10000 line of switches, when an explicit Layer 2 classifier is applied on a Layer 3 interface, the default Layer 3 classifiers are not removed. By design, the Layer 3 classifier takes precedence over the Layer 2 classifier. PR1520570

  • After performing NSSU and GRES from Junos OS Release 20.1 or Release 20.2 to Junos OS Release 20.3 on the QFX5000 line of switches, the land backup member of Virtual Chassis might be in unstable state with db> prompt. PR1533874

  • On QFX10002 devices acting as PHP, egress sFlow samples do not report MPLS explicit-null label in the raw packet header. The MPLS payload can be of IPv4 or IPv6 protocol. PR1537946

  • "Socket to sflowd closed" error is seen when the ukern socket to sflowd daemon (server) is closed. The error is rectified by itself when the connection is re-established in the subsequent attempts. When these errors are consistent, it indicates the communication issue between sFlow running on the FPC with the sflowd. PR1538863

  • EVPN-VXLAN: vmcore seen on primary and backup Routing Engines of QFX10008 with Layer 2 or Layer 3 multicast configuration. PR1539259

  • Moving WRL7 SDK to RCPL31 for QFX10000 platforms. RCPL31 provides tweaking of build infra and fixes related to performance enhancements and vulnerabilities in WRL7 Linux. PR1547565

  • 100G AOC from InnoLight does not come up after multiple reboots. It recovers after the interface is disabled and then enabled. PR1548525

  • Traffic does not get load-balanced by QFX10000 platforms over ESI links with EVPN-VXLAN configured, PR1550305

  • 5M DAC connected between QFX10002-60C and MX2010 doesn't link up. But with 1M and 3M DAC this interoperation works as expected. Also it is to be noted on QFX10002-60C and ACX Series devices or traffic generator, the same 5M DAC works seamlessly. There seems to be certain SI or link-level configuration on both QFX10002-60C and MX2010 that needs to be debugged with the help from HW and SI teams and resolved. PR1555955

  • In Junos OS Release 20.2, some features show up as licensed features. Customer might see alarms, commit warnings, and the following show system license output. However, there would be no functional impact. user@router> show system license License usage: Licenses Licenses Licenses Expiry Feature name used installed needed esi-lag 1 0 1 invalid. PR1558017

  • In VXLAN Layer3 Gateway scenario, untagged traffic routed over native-vlan-id interface might drop. The issue is seen on the QFX5110 line of switches because of the BRCM hardware errata, where routing of an untagged packet does not delete the internal VLAN tag assigned to the packet. PR1560038

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

  • RPD core file is generated when the device reboots and daemon restarts. Daemon recovers and there is no service impact on routing protocol usage.PR1567043

  • vport's refcnt will not be proper with stale entries seen sometimes due to out of order messages for aggregated Ethernet interfaces when deletion/addition sequence is done multiple times. PR1569879

  • With reference to the topology used in the PR, out of all IS-IS sessions only below IS-IS sessions are not getting established:- that is between the r0(mx240) and r3/r4(Qfx10k) devices. The above devices are connected by intermediate nodes r1 and r2. The issue seems to be specific to these intermediate nodes and its config No issue is seen between the routers that is, between r3 and r4, here IS-IS sessions are all up between these nodes. PR1580971

  • The renew-ack's might not be seen in the dhcp client while checking DHCP smart relay over IRB interfaces in QFX5100 device running Junos OS Release 21.1R1. PR1581025

  • Issue is seen in telemetry when set services analytics streaming-server configuration statement is present, and server is not reachable. PR1581192

  • l2ald core may be seen occasionally when there is a race between svtep and rvtep creation. System will recover automatically after the core. PR1582128

Layer 2 Ethernet Services

  • It was observed rarely that issuing a "request system zeroize" did not trigger ZTP. A simple workaround is to reinitiate ZTP. PR1529246

Platform and Infrastructure

  • Upgrading satellite devices may lead to some SDs in SyncWait state. Cascade port flap does not cause this issue. PR1556850

Routing Policy and Firewall Filters

  • On all Junos OS platforms with "set policy-options rtf-prefix-list" configured, if upgraded to a specific version, the device might fail to validate its configuration, which eventually causes rpd to crash unexpectedly due to a software fault. PR1538172

Routing Protocols

  • On QFX5000 platforms, when the host forwarding table is full and the host entries are installed in the LPM forwarding table, or when lpm-profile with unicast-in-lpm option is used, the Layer 3 IP route might not be installed in the LPM forwarding table if there are SER errors, hence there might be traffic impact. PR1429504

  • Currently IPIP, IPv6 and gre decapsulations are supported. It is not recommended to configure gre and IPIP/IPv6 in a single filter. If gre and IPIP/IPv6 are configured in a single filter, then the last decapsulate filter term is used to program the entire filter terms. PR1580468