Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Known Issues


This section lists the known issues in hardware and software for the QFX Series switches in Junos OS Release 17.1R2.


  • On a QFX10002 platform, some random ports, when using 100 Gigabit Ethernet Lumentum optics, might not come up after a reboot. This is a timing issue because of failures during optics read on some ports. When hitting this issue, remove and insert the optics, which might bring up the ports. PR1227029


  • When there is a high route churn or when there is a high rate of route updates being pushed to the kernel, the show interface command might show a delay or not show all statistics due to route updates being prioritized over statistics messages. PR1250328

Layer 2 Features

  • On QFX5100 Virtual Chassis interfaces on which the flexible-vlan-tagging statement is specified, STP, RSTP, MSTP, and VSTP are not supported. PR1075230

Network Management and Monitoring

  • On a QFX10002 switch, when a new interface is added to an existing link aggregation group (LAG) interface which acts as an input analyzer interface, traffic sent to the added interface might not be mirrored. PR1057527

Open vSwitch Database Management Protocol (OVSDB)

  • OVSDB (QFX10000 switches)-- Use of OVSDB is not recommended on these switches with Junos OS 17.1R1 and 17.1R2. PR1288227


  • OpenFlow (QFX10000 switches)-- Use of OpenFlow is not recommended on these switches with Junos OS 17.1R1 and 17.1R2. PR1288227

Platform and Infrastructure

  • On QFX5100 switches, the amount of time that it takes for Zero Touch Provisioning to complete might be lengthy because TFTP might take a long time to fetch required data. PR980530

  • On QFX10002 switches, the "request system snapshot" command does not work. PR1048182

  • On a QFX10002 switch, insert a small form-factor pluggable (SFP) on the management interface (em1). After a system reboot, replace the SFP with a copper SFP, the management interface might not work properly with speed 10m/100m. PR1075097

  • On a mixed-mode Virtual Chassis Fabric (VCF), nonstop software upgrade (NSSU) cannot be used to upgrade from a Junos OS Release 14.1X53 image to a Junos OS Release 15.1 or later image. PR1087893

  • While using SSH to log into a VNF, an error with the message Unrecognized command is seen. This has no impact on the functionality. PR1108785

  • On a fully loaded QFX10008 chassis, line cards might take as much as 15 minutes to become operational after startup. PR1124967

  • With multihop BFD, traffic loss of around 5 to 10 seconds is observed when intermediate interface is shut down. After 5 to 10 seconds, traffic recovers and no action is needed. PR1150695

  • The Junos OS CLI file copy command uses the "/var/home/<user>" as a temporary staging directory for downloads. This behavior is the same on all Junos OS platforms. When you run file copy as “user1,” then /var/home/user1 is the temporary staging directory. For QFX10000 switches, /var is ~480 MB. So running file copy on a file that is more than 480 MB will fail on QFX10000 switches. PR1195599

  • There are basically three arguments (periodic, diagnostic, and tx) for the lcdd_cmd -f 0 -d chassism -c command. These top-level commands expect different numbers of arguments. If any one of the arguments is missing when the command is executed on a QFX3500 or QFX3600 switch, the chassisd process might crash. PR1206328

  • Software enhancements were done to improve link stability of ASIC-Hybrid Memory Cube links. PR1208455

  • On disable and re-enable of a 1 GB port on a 60X10GB Line Card in both QFX10008 and QFX100016 systems, pechip_cmerror_set_error:3113: Level: Major, cmerror_code: 0x21060e (id=1550), recover_err: 0 (counter: 0), fh_msg: 0x0 messages are logged. There was no functionality impact observed. PR1238269

Routing Protocols

  • L3 multicast traffic does not converge to 100% and a few continuous drops are observed after bringing an interface down and back up again or while an FPC comes online after fpc restart. This behavior is seen when scaling beyond 2000 VLANs or 2000 IRBs with VLAN replication configured. PR1161485

  • On QFX10000 switches, during a Routing Engine switchover, BGP on the IRB interface might flap when the IRB interface and the underlying Layer 2 logical interface (IFL) are configured with different MTU values. PR1187169

  • On QFX10000 switches, traffic drop is seen with IS-IS version 6 traffic during convergence in either of the following two scenarios: 1. While doing port unshutdown (that is, bringing up the ports after bringing them down). 2. While FPC comes online after doing an FPC restart. This behavior is seen while flapping one of the IS-IS version 6 sessions. PR1190180

  • During a graceful Routing Engine switchover (GRES) on QFX10000 switches, some IPv6 groups might experience momentary traffic loss. This issue occurs when IPv6 traffic is running with multiple paths to the source, and the join-load-balance statement for PIM is also configured. PR1208583

  • On EX4300/EX4600/QFX5100/QFX10000 switches, traffic drops might occur in MC-LAG configurations. This occurs when an interchassis data link (ICL) interface and then the MC-LAG interface are brought up. The traffic drop occurs because the ARP next-hop update is not recognized on the Packet Forwarding Engine. To recover the traffic path over the MC-LAG interfaces, issue the clear arp command. To avoid the issue, enable ICL interfaces and MC-LAG interfaces at the same time. PR1236201

  • On QFX10000 platforms, during route next-hop churn or earliest deadline first (EDF) job priority changes, memory corruption may happen leading to processing issues and constant packet drop. PR1243724

  • When polling the SNMP MIB jnxFirewallsEntry and if more than one firewall filter was configured and attached toany logical interfaces on the QFX3500 platform, the counters for only one firewall filter would be returned. Now all filters and counters are returned when polling the MIB. PR1250776

System Management

  • On QFX10000 switches with enhanced MC-LAG IRB next hops, member links of the aggregated underlying Layer 2 interfaces might not be present on all Packet Forwarding Engine instances in a given FPC. Under this condition, during IRB next-hop installation for the Packet Forwarding Engine instance where the underlying Layer 2 interface link is not present, failure logs are generated for the PFE uKernel. Those failure logs do not impact traffic or performance on the switch, and they are harmless. PR1221831