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.

General Routing

  • On QFX10000, source MAC and TTL values are not updated for routed multicast packets in EVPN-VXLAN. PR1346894

  • Storm-control does not rate-limit ARP packets on QFX10000 although shutdown action works. PR1461958

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

  • On QFX5000 series platforms with "instance-import", deleting route which has "next-table" used might result in unexpected route next-hop. PR1477603

  • When running the command, show pfe filter hw filter-name filter name, the command fails to retrieve the Packet Forwarding Engine programming details of the filter. PR1495712

  • After repeated deletion and addition of logical switch on 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 runtime (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

  • The MSDP sessions might reset after a GRES reset even when nonstop routing state is synchronized and ready for switchover. PR1526679

  • On QFX5100 devices that do not run the QFX-5e codes (non-TVP architecture), when an image with the vendor SDK upgrade (6.5.x) is installed, the CPU utilization may go up by around 5%. PR1534234

  • 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 sflowed. 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

  • 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 a certain SI or link-level configuration on both QFX10002-60C and MX2010 which 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 a licensed features. Customer might see alarms, commit warnings, and the following show system license. 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

  • On QFX5110 platforms in VXLAN Layer 3 gateway scenario, untagged traffic routed over native-vlan-id interface might be dropped. PR1560038

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

  • Starting 21.1R1, Junos will be shipping with python3 (python2 is no longer supported). In ZTP process, if a python script is being downloaded, please ensure the python script follows python3 syntax (there are certain changes between python2 and python3 syntax). Also, so far (ie until 20.4R1), the python script had #!/usr/bin/python as the first line (ie the path of the python interpreter). The same needs to be changed to #!/usr/bin/python3 from 21.1R1. PR1565069

  • The pic_create_ifname: 0/0/0 pic type F050 not supported log messages generated under chassisd and other messages in logs. PR1566440

  • The Broadcast, Unknown Unicast, and Multicast (BUM) traffic replication over VTEP is sending out more packets than expected and there seems to be a loop also in the topology. PR1570689

  • On the QFX10000 series platforms with EVPN-VXLAN setup, ARP MAC move between local side and remote side or moving from a MAC-VRF table to the default switch table might cause DCPFE/FPC to crash. PR1572876

  • The ksyncd core may be hit when we reboot node with EVPN VXLAN configurations on QFX10008 and QFX10016 platforms. PR1574594

  • JUNOS:JDI_REGRESSION:PROTOCOLS:SWITCHING:QFX-EVPN_VXLAN: After performing run restart l2-learning, ISIS sessions were not established. PR1580971

  • On QFX5100, while checking DHCP smart relay over IRB interfaces, the renew-ack's may not be seen in the dhcp client. PR1581025

  • On some QFX series, using Ethernet Virtual Private Network (EVPN) with Virtual Extensible LAN protocol (VXLAN) when the Flexible PIC Concentrator (FPC) is rebooted, in rare occasions some of the Address Resolution Protocol (ARP) entries might be found missing intermittently on the FPC rebooted spine leading to intermittent connectivity issues. PR1594255

  • On QFX series, switches with the vendor chip as Packet Forwarding Engine, if IS-IS is enabled on an integrated routing and bridging (IRB) interface and the maximum transmission unit (MTU) size of the IRB interface is configured with a value great than 1496 bytes, the IS-IS hello (IIH) PDUs with jumbo frame size (i.e., great than 1496 bytes) might be dropped and not sent to the IS-IS neighbors. The following is the product list of QFX series switches with vendor chip as Packet Forwarding Engine. QFX3500/QFX3600/QFX5100/QFX5110/QFX5120/QFX5130/QFX5200/QFX5210/QFX5220PR1595823

  • Post In-Service Software Upgrade (ISSU) Issue will be seen on deleting and adding back sample configuration below. interfaces { ge-0/2/5 { flexible-vlan-tagging; encapsulation flexible-ethernet-services; gigether-options { ethernet-switch-profile { tag-protocol-id 0x0800; } } unit 1 { vlan-id 1; family inet { filter { input inet4filter; output inet4filter; } address; } family inet6 { filter { input inet6filter; output inet6filter; } address 2002:0000:0000:0000:0000:0000:1000:0641/126; } } } } PR1596483

  • If the egress firewall filter with policier is configured on the aggregated Ethernet interface on QFX5000 platforms, traffic might drop after the backup FPC is rebooted in a virtual chassis scenario. PR1596773

  • QFX10002: dcpfe core is observed after booting the device with EVPN-VXLAN configurations. PR1597479

  • On QFX5000 series (QFX5100 , QFX5110, QFX5120, QFX5200 and QFX5210) platforms DDOS violations could be reported for IP multicast miss traffic (CPU Queue 28) even though rate of IP multicast miss traffic is much lower than the configured ddos rate limit. PR1598678

  • Convergence time degradation is seen in IS-ISv6, OSPFv2, and OSPFv3. PR1602334

  • In a GRE tunnel in a routing instances scenario, GRE has to be configured on a routing-instance (not the default one) and route leakage is configured between VRFs. When the destination to tunnel changes, the optimal nexthop in the vrf is not updated for the tunnel. The traffic cannot be forwarded out of the tunnel. PR1602391

  • On QFX5120, traffic loss might be seen when primary link disabled with aggregated Ethernet Link Protection configuration. PR1604350

  • On QFX5000 platforms, if IPv6 packet is received whose 17th byte of Layer 3 header is 0x888e, the packet might be misinterpreted as L2PT(Layer 2 Protocol Tunneling) Ether type and PACKET DMA heap will be exhausted as these packets might not be freed which can result in total traffic (data/control) loss and can cause fxpc cores or system instability. PR1603531

  • If Link Layer Discovery Protocol (LLDP) packets are received on Virtual Extensible LAN (VxLAN) enabled port, these LLDP packets might be flooded unexpectedly. The issue could make LLDP session keep swapping. As a result, services like Power over Ethernet (PoE) etc might be affected. PR1607249

  • On QFX Series switches, the fxpc process might crash and generate a core dump. PR1607372

  • In an EVPN-VXLAN (spine-leaf) scenario, any route received as Type-5 might not be reachable. When we are pinging an IP learned over Type-5, the packet should be mapped to one of the IRB in that routing instance, else the packet is discarded. Fix is to use all the available routes in the routing instance for this mapping. PR1610093


  • End-hosts might not communicate via Ethernet VPN with Virtual Extensible LAN encapsulation (EVPN-VxLAN) domain after Ethernet Segment Identifier (ESI) failover. This issue affects QFX5000 platforms only. Please refer to restoration steps when this issue is encountered. PR1584595

  • On all Junos and Junos Evolved platforms with EVPN-VxLAN scenario, the number of MAC-IP binding counters may reach the limit when MAC-IP is moved between interfaces. Since MAC-IP counters are not decremented when entry is deleted due to this defect, repeated moves will result in a limit (default value is 1024) that will be reached even though there are fewer entries. Meanwhile, traffic loss could be seen. PR1591264

Layer 2 Features

  • On QFX5100 platforms, if a change related to TPID is made in the Device Control Daemon, traffic might be dropped in Packet Forwarding Engine due to failure on layer 2 learning or interfaces flapping. PR1477156

Layer 2 Ethernet Services

  • It was observed occassionally that issuing a request system zeroize did not trigger ZTP. A simple workaround is to re-initiate ZTP. PR1529246


  • The rsvp interface update threshold configuration syntax has changed between Junos OS Release 18.2X75-D435 and Junos OS Release 20.3X75-D10 to include curly braces around the threshold value. Upgrading and downgrading between these releases is not entirely automatic. PR1554744

Platform and Infrastructure

  • Arrival rates were not seen at system level when global-disable fpc is configured on QFX. PR1438367

  • When the DHCP relay mode is configured as no-snoop, we are observing the offer gets dropped due to incorrect ASIC programming. PR1530160

Routing Policy and Firewall Filters

  • On all Junos OS platforms with set policy-options rtf-prefix-list configured, when upgraded to a specific version, the device might fail to validate its configuration, which eventually causes rpd to crash unexpectedly. The reason should be 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 are configured in a single filter, then the last decapsulate filter term is used to program the entire filter terms. PR1580468

  • On QFX10002 platforms, the multi-hop BFD session might flap if collecting RSI or some other outputs (such as show interface or configuration). It is caused by the missing BFD packets because the PPMAN thread is not scheduled within the BFD timers which are 300 milliseconds with a multiplier of 3. PR1589765