Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
[+] Expand All
[-] Collapse All

Known Issues

The following issues are outstanding in Junos OS Release 14.1X53 for the QFX Series. The identifier following the description is the tracking number in our bug database.

For the latest, most complete information about outstanding and resolved issues with the Junos OS software, see the Juniper Networks online software defect search application at

Authentication and Access Control

  • On an EX4300, EX4600, EX9200, or QFX5100 standalone switch or its Virtual Chassis or VCF, with a port configured in access mode and with dot1x enabled, if this port is converted to trunk mode, then this port might not be able to learn a MAC address or might drop packets silently. PR1239252

Firewall Filters

  • The command show firewall log detail shows incorrect packet lengths in the output. PR1223256

High Availability (HA) and Resiliency

  • On a Virtual Chassis Fabric, NSSU might fail in the following situations: there is routed traffic with no end hosts, or hosts are missing because of an NSSU node reboot. PR1199744
  • On a QFX5100 switch, you cannot perform a unified in-service software upgrade (ISSU) from Junos OS Release 14.1X53-D30 to Junos OS Release 14.1X53-D40. As a workaround, during a maintenance window, download the new software version, perform a regular software upgrade, and reboot the switch. PR1229272
  • On QFX5100 switches, unified ISSU is not supported with MPLS configuration. PR1264786
  • In a QFX Series Virtual Chassis/Virtual Chassis Fabric (VCF) nonstop software upgrade (NSSU), if the next FPC/group begins to reboot before the previous FPC's upgrade is completed and if a LAG interface has two member links on the two different FPCs, the redundant LAG link goes down. This problem might cause the redundant LAG link to stop forwarding for several minutes. PR1272240


  • QFX5100: string and hex-string do not work as expected for DHCP option 119. PR1307979
  • Upgrading to 16.1R5 without redundancy-group-id-list statement prior in ICCP leads to commit failure during bootup. PR1311009

Interfaces and Chassis

  • A configuration statement for a configurable MRU-PAD was introduced for MX Series. The default value of the knob is MTU+8. Non-MX platforms that do not support the MRU-PAD may incorrectly display as MRU of zero bytes in the show interface command output. PR1033901
  • From Junos OS Release 13.3R1, when we configure interface aliases to specify custom names for interfaces and refer to them in a configuration with a large number of logical interfaces (for example, 46K), an RPD scheduler slip might be observed if the "commit full" command is issued or if a a large number of logical interfaces are changed. It might cause a service impact, for example, LDP/BGP sessions flap when the slip goes high. PR1104951
  • On a QFX5100 switch, with a fully meshed MC-LAG topology configured, sometimes there is more traffic loss when the ICL interface goes down and then back up compared to when you have Junos OS Release 14.1X53-D35 software installed. The root cause has been identified, and this issue does not affect MC-LAG functionality. PR1209322
  • Multicast Listener Discovery (MLD) messages are seen continuously on QFX Series switches if management ports are connected through a network. QFX5100 will cause these messages, because the eth0 interface is generating the MLD query packets every 125 seconds. On QFX5100 there is bridging between em0 and eth0 interface. The MLD packet will get generated from the em0 interface with the chassis MAC address (eth0 is using the chassis MAC address). PR1277618
  • [QFX3600] Filter on me0 interface not working. PR1310184
  • If minimum links and FUP are configured, then an aggregated Ethernet interface will be down even when fewer than 2 interfaces are down, i.e., when only single interface is UP, AE will be DOWN. PR1313873

Layer 2 Features

  • On EX4600/QFX3500/QFX3600/QFX5100 Series switches, if the same VLAN-ID is configured on user-to-network interface (UNI) and network-to-network interface (NNI) in Q-in-Q scenario, feature swap-swap might not work as expected. PR1297772


  • On QFX5100 switches, the traceroute mpls ldp command output shows incorrect information when using an IRB interface between the ingress provider edge (PE) switch and the provider (P) switch. This occurs when running LDP over RSVP over an MPLS core network. PR1217132

Multicast Protocols

  • When a static multicast route with a next-table nexthop is changed from a table that cannot forward the traffic to one that can and then reverted back to the original table, the traffic might continue to flow out the downstream interface even though the static route is no longer pointing to the table that allowed for the traffic increase. PR1217958
  • On QFX5100 switches, multicast route leaking does not support a Layer 3 interface (IPv4) as an upstream port. As a workaround, use an integrated routing and bridging (IRB) interface. PR1250430

Network Management and Monitoring

  • QFX3500: The SNMP daemon is not running on Junos OS devices with incorrect source addresses. PR1285198

Routing Protocols

  • BGP routes are rejected as cluster ID loop prevention check fails due to a misconfiguration. But when the misconfiguration is removed, BGP routes are not refreshed. PR1211065

QFabric Systems

  • On QFabric systems, excess mount points might be created on the DRE that could result in multiple TCP connections being opened between the DRE and the NFS server. As a workaround, reboot the DRE. PR1259008
  • The ccif service in the QFabric directors is responsible for spawning VMs (like Fabric Manager, Network Node Group, and so on) and load-balancing them between the two Director Groups. The ccif service uses a GFS-based shared-disk file system to share data across the two Director Groups. The ccif service is managed by the RedHat Cluster Management. Due to hard-disk errors, the ccif service could encounter I/O errors while accessing the shared file system. When this happens, the Cluster Manager moves the ccif service to the Failed state. PR1277504
  • On QFabric systems, if IGMP snooping is enabled, unknown multicast traffic might be lost after an NNG switchover during a DG upgrade, due to misprogramming of mrouter ports in VLANs. As a workaround, issue the clear igmp-snooping membership command. PR1280110
  • On a QFabric system, sfid-bcm can core if IFDTX sfid trace is enabled. PR1295750


  • Multiple Products: "Dirty COW" Linux Kernel Local Privilege Escalation, please refer to for more information. PR1227266

Virtual Chassis and Virtual Chassis Fabric (VCF)

  • On EX Series or QFX Series Virtual Chassis, if new members are not zeroized prior to being added to the Virtual Chassis, and then one of the new members splits from the Virtual Chassis, then whenever you run commit or commit check, the commit might hang for a long time and then report a timeout error on the FPC that split from the Virtual Chassis. PR1211753
  • Virtual Chassis: Traffic might be lost for about 10 seconds if the master member FPC reboots. PR1283702


  • On QFX5100 switches, the Layer 3 routes that form virtual extensible LAN (VXLAN) tunnels use per-packet load balancing by default, which means that load balancing is implemented if there are ECMP paths to the remote tunnel endpoint. This is different from normal routing behavior in which per-packet load balancing is not used by default. (Normal routing uses per-prefix load balancing by default.) PR1018814
  • On QFX5100 switches when VXLAN is configured, a VXLAN table is created to resolve routes to remote VTEPs. If the underlay is OSPF IS-IS or EBGP, the routes can distribute the traffic over multiple paths if load balancing is configured. However, if the underlay is IBGP, the route will select one of the available paths rather than using all the available paths. PR1154961

Modified: 2017-11-29