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

  • Backup Routing Engine might crash after GRES occurs continuously for more than 10 times. PR1348806

  • When VLAN is added as an action for changing the VLAN in both ingress and egress filters, the filter is not installed. PR1362609

  • Due to transient hardware condition, single-bit error (SBE) events are corrected and have no operational impact. Reporting of those events had been disabled to prevent alarms and possibly unnecessary hardware replacements. This change applies to all Platforms using Hybrid Memory Controller (HMC). PR1384435

  • 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

  • On Junos QFX platform, the Jflow service might not report the accurate throughput rate. This issue is seen when there is high sampled traffic rate with low flow cache hit ratio. PR1502645

  • 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

  • FIPS mode is not supported. PR1530951

  • 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

  • The BCMX calls are deprecated and needs to be replaced with BCM calls. PR1541159

  • 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

  • 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

  • In mixed QFX5100, EX4300 VCF setup, duplicate traffic might be observed for some Layer 3 multicast traffic streams . PR1568152

  • 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 QFX5100, while checking DHCP smart relay over IRB interfaces, the renew-ack's may not be seen in the dhcp client. PR1581025

  • 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

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

  • Read write lock is not acquired during the sysctl invocation. The assert triggered in the interface state function call leads to go Routing Engine 1 to debug (db>) prompt. PR1598814

  • After performing an upgrade, the peer device is rebooted or the peer interface is disabled or enabled, then the SFP-T port might remain in up state but could not forward traffic. PR1600291

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

  • On QFX10000 platforms supporting DHCP (Dynamic Host Configuration Protocol), when relay is configured in non-default routing instance and DHCP renew process is triggered due to lease time expiry, renew packets might get flooded to all members in VLAN instead of unicast forwarding. PR1603444

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

  • On QFX10008 and QFX10016 platforms, the system reboot takes approximately 9 minutes for FPCs to come online after system reboot command is issued. PR1605002

  • Dfwd cored when accessing ephemeral db files which is deleted through script. PR1609201

  • In QFX10002-60C under MAC statistics output-mac-control-frames and output-mac-pause-frames does not increment. PR1610745

  • As per design change, QFX10002, QFX10008, and QFX10016 devices have max token allocation limit of 104,000 combined for l2/l3/BUM routes. These tokens are used as egress nexthop IDs for route lookup in HW. Out of 104,000 tokens, 8000 tokens are reserved for maximum VXLAN tunnels and 16,000 tokens are reserved for IRB interfaces, and locally learned ARP/NDP nexthops also require tokens to install in HW which will be allocated from free pool of tokens left after the reservations. So, total tokens available in free pool after reserving [8000 (vxlan tunnels) + 16,000(IRBs)] is 80,000 tokens. Thus, maximum of 80,000 local ARP entries can be supported on QFX10,000 (Elit/Ultimate) devices. PR1616224

  • On all QFX5000 platforms, when the IRB (Integrated Routing and Bridging) is configured and removed from the VLAN, Layer3 bits enabled in hardware are not reset, hence the Layer 3 lookup on the VLAN is not deactivated while IP address/IRB is not configured. So, any Layer 2 traffic coming with dmac as my mac might be dropped. PR1618425

  • Log messages fpc0 SRIRAM Tx VxLAN Ucast: ifd_out = vtep dst_gport is (c00000X) so do not process pkt further can show up on QFX5000 switches. These are harmless messages. PR1624925

  • On QFX5100 platforms with the Virtual Chassis scenario, if the Virtual Chassis Ports (VCPs) are connected through QSFP+40GE-AOC cable, post upgrading to 17.3 or later releases, VCPs might not come up or flap impacting VC functionality and services. PR1633998

  • On QFX platforms in VxLAN scenario, if STP is enabled on all the interfaces of the switch, ethernet table might not get populated to locally connected devices resulting in traffic blackhole. PR1636950

  • When L2PT (Layer2 Protocol Tunneling) is enabled on a transit switch using SP style configuration, protocol convergence between end nodes might fail. PR1637249


  • 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

  • Modifying the I-ESI value is traffic effecting event. If this must be done then follow the below steps in order to avoid this PR 1) deactivate interconnect stanza for the routing-instance in question 2) Modify the I-ESI value 3) activate the interconnect stanza. PR1600600

  • In all Junos and Junos OS Evolved platforms, EVPN-VXLAN scenario, with proxy-macip-advertisement statement configured, few ARP/ND/MAC entries might get missing. PR1609322

  • This problem happens only with the translation VNI when MAC is moved from DC1 to DC2. VM moves across DC where there is no translate VNI configuration in the interconnect works as designed. PR1610432

  • Multiple memory leaks might be seen, which might lead to the process rpd crash. Issue 1- On QFX platforms configured with EVPN-VxLAN memory leaks might be seen due to BGP communities. Issue 2- On all Junos platforms memory leaks might be seen due to MAC mobility. PR1626416


  • The following messages are seen during FTP: ftpd[14105]: bl_init: connect failed for /var/run/blacklistd.sock (No such file or directory) messages are seen during FTP. PR1315605

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

  • On all Junos platforms configured as DHCP (Dynamic Host Configuration Protocol) server or relay-agent, the file system storage under /var directory might get filled up with DHCP ERA (Event Rate Analyzer) logs which is enabled by default and could result in other processes not having storage space to log details of router functionalities. PR1617695

  • With Non-Flex images ZTP will not work on QFX5200. PR1629441


  • 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

  • When the DHCP relay mode is configured as no-snoop, we are observing the offer gets dropped due to incorrect ASIC programming. This issue only affects while running DHCP relay on EVPN/VXLAN environment. 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

  • On all platforms, traffic drops might be seen when incorrect VPN labels are allotted. When there is a change in the nexthop by BGP policy, the traffic is still forwarded to the old label. This leads to traffic drops for prefixes sending traffic to the old nexthop. PR1617691

  • In the single-hop BFD of BGP scenario, when multiple addresses of the same subnet are configured on the interface of the BFD session, the BFD session might be down. PR1635700