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 

Known Issues

This section lists the known issues in hardware and software in Junos OS Release 15.1X53-D64 for QFX10000 switches.

High Availability (HA) and Resiliency

  • On QFX10008 and QFX10016 switches, IPv4 and IPv6 distributed BFD sessions might flap in high availability due to a master reboot or an unplanned Routing Engine switchover. PR1176745
  • On QFX10000 switches, VRRP is not converging in an MC-LAG environment, because the default routing instance, lo0.0, has been moved to a user-defined routing instance. As a workaround, do not move lo0.0 to the user-defined routing instance—use a different lo0 logical interface in the user-defined routing instance, such as lo0.1 or lo0.2. PR1274204


  • In an IP-CLOS topology with a QFX10000 switch as a leaf node using EVPN-VxLAN and acting as a Layer 2 or Layer 3 gateway (in a collapsed scenario), rebooting the leaf node might a cause a PFE process core.PR1285705


  • On QFX10000 switches, an FPC major alarm might be raised when the system detects parity errors and the following error messages might be displayed: DLU: ilp memory cache error and DLU: ilp prot1 detected_imem_even error. The alarm might be cleared without intervention. No traffic drops or traffic blackholing occurs when this alarm is raised. PR1251154

Interfaces and Chassis

  • On a QFX10000 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. As a workaround, delete the configuration and then reconfigure it. PR1057527
  • On QFX10008 and QFX10016 switches, during a Routing Engine switchover, BGP on the IRB interface might flap when the IRB interface and the underlying Layer 2 logical interface are configured with different MTU values. As a workaround, configure the same MTU value on both the Layer 2 logical interface and the IRB interface. PR1187169
  • On QFX10000 switches with a large number of LAG interfaces (for example, more than 400), if a few of those LAG interfaces are flapped (for example, 10 LAG interfaces are disabled and then the disabling is committed), other LAG interfaces might also flap. PR1250741
  • On QFX10000 switches, the values for LAG interface bundle input counters shown in the Bytes column of the show interfaces interface-name detail command output might become smaller over time, which is unexpected as this counter should be an accumulated number. PR1266062
  • On QFX10002 switches, if MTU over an IRB logical interface is configured but is not configured on the underlying Layer 2 interfaces or on the IRB physical interface, interfaces' link may take up to 15 minutes to come up after reboot. As a workaround, configure MTU over the IRB physical interface. PR1266697

Layer 2 Features

  • On QFX10000 switches, MAC limiting does not take effect on the Packet Forwarding Engine. PR1131502


  • On QFX10008 and QFX10016 switches, after a high availability (HA) graceful Routing Engine switchover (GRES), the show mpls lsp autobandwidth command might display an incorrect bandwidth on the new Routing Engine. As a workaround, use the show rsvp session extensive command. If the LSP is resignaled, the problem is corrected. PR1149863

Multicast Protocols

  • 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

Network Management and Monitoring

  • If a QFX10008 or a QFX10016 switch is fully populated with line cards and all the interfaces are configured, SNMP timeouts can occur if the switch is simultaneously polled by multiple network management stations. PR1147934
  • On QFX10000 switches, sFlow monitoring technology output might display a negative number of samples after a long run. As a workaround, issue the clear sflow collector command to show or reset the count. PR1244080

Platform and Infrastructure

  • On QFX10008 and QFX10016 switches, micro Bidirectional Forwarding Detection (BFD) sessions might flap during a graceful Routing Engine switchover (GRES). PR1165509
  • On QFX10008 switches, if you reboot a QFX10000-36Q line card or a QFX10000-30C line card with traffic running, sometimes framing errors are displayed in the CLI output. This is only a display issue. No actual framing errors have occurred, and traffic is unaffected. PR1223330

Routing Protocols

  • When VRF route leak is configured along with a static route next hop over an IRB interface on QFX10000 switches, ARP requests for these routes might not be resolved. PR1147176
  • Modifying the route-distinguisher identifier flushes all the routes, including interface routes, from the virtual routing and forwarding (VRF) routing information base (RIB), also know as the routing table. As a result, the VRF RIB remains empty. As a workaround, deactivate the VRF before you modify the route-distinguisher identifier and then reactivate the VRF. PR1155647
  • The no-indirect-next-hop configuration statement that was mandatory in Junos OS Release 15.1X53-D30 and earlier releases is no longer required on QFX10000 switches in Release 15.1X53-D60. Delete it from the configuration before you upgrade to Release 15.1X53-D60. PR1187482
  • On QFX10000 switches configured as route type-5 peers, when only peer 1 advertises routes, that peer might not install the decap next-hop (NH) route. As a result, type-5 encapsulated traffic sent by peer 2 is dropped until peer 2 advertises any route type-5. As a workaround, configure a static route pointing to discard on peer 2 and advertise that route as a type-5 route to peer 1. PR1191092
  • On QFX10000 switches, when a type-5 route is also learned through another protocol with a lower preference or is statically configured, the switch installs the type-5 route even though it is not the preferred route. PR1200519
  • On QFX10000 switches, the Packet Forwarding Engine sorts next-hop constituent element next hops by their weights in ascending order before installing them in the forwarding plane. The inefficiency of the sorting algorithm means that the unilist next-hop programming acknowledgments are delayed. As a result, BGP route updates can fail because no buffer is available. PR1225309

Software-Defined Networking (SDN)

  • Configuring an IRB interface as an underlay on a Layer 2 gateway/leaf node may impact forwarding. As a workaround, configure a Layer 3 interface as the underlay. PR1267201

Related Documentation

Modified: 2017-06-26