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 Behavior

This section lists known behavior, system maximums, and limitations in hardware and software in Junos OS Release 15.1X53-D64 for QFX10000 switches.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Infrastructure

  • On QFX10000 switches, during a large-scale configuration churn, the switch might hit a race condition in which an egress line card deletes a next hop before the ingress line card deletes the route pointing to that next hop. This leads to traffic hitting the invalid next hop and causing desc_addr_err messages. This is a temporary condition and has no impact on any functionality. PR1257329
  • The interface-mac-limit configuration is not supported on Q-in-Q interfaces on QFX10000 switches; do not configure the following commands:
    • set switch-options interface-mac-limit
    • set switch-options interface interface-name interface-mac-limit

    As a workaround, use the VLAN interface-mac-limit configuration:

    • set vlans vlan-name switch-options interface-mac-limit

    PR1259956

Interfaces and Chassis

  • On a QFX10000 switch configured as an MC-LAG peer, approximately 7 through 9 seconds of traffic might be impacted when the ICCP/ICL interface goes down. PR1191337
  • On QFX10008 and QFX10016 switches, when ICCP cannot reach the mclag-cfgchkd daemon on a remote MC-LAG peer, configuration consistency check cannot compare the configurations, and all of the MC-LAG parameters are marked as PASS. When the remote MC-LAG peer and the mclag-cfgchk daemon become reachable, configuration consistency check exchanges the configurations and compares them. As a workaround, make sure that the mclag-cfgchkd daemon is running on both MC-LAG peers and that ICCP can reach the MC-LAG peers. PR1220630
  • When you use a QFX10000 switch as a PE device in a 6VPE topology, you must enable family inet6 on the core-facing interfaces that will be used for the IPv6 traffic. If you do not do so, these interfaces drop the IPv6 traffic. PR1226014
  • On QFX10002-36Q line cards, configuration of an IRB interface in the same OSPF area as that of underlay interfaces is not supported. PR1257128
  • On QFX10000 switches, FEC counters are not cleared after a power-on or link bringup, because FEC statistics shown in the CLI are the residue of link bringup, and those statistics remain steady throughout. As a workaround, issue the clear interfaces statistics interface-name command to clear these FEC statistics. PR1257551

Layer 3 Features

  • When you upgrade the software on a QFX10000 switch to Junos OS Release 15.1X53-D60 or 15.1X53-D61, BFD sessions might flap after the upgrade. As a workaround, restart the periodic packet management process (ppmd) after the upgrade. PR1210316

MPLS

  • Having the unsupported Entropy label feature configuration on QFX10000 switches might result in unexpected switch behavior. We recommend that you remove this unsupported configuration. PR1260995

Network Management and Monitoring

  • On QFX10008 and QFX10016 switches, sFlow external router data is not updated in sFlow datagrams if sampling is in the egress direction for flows going across FPCs. The updating issue does not occur if samples are taken at the ingress FPC for such flows or if flows are within the same FPC. PR1241362

Routing Protocols

  • When EVPN-VXLAN is configured on QFX10002 switches, the number of ARP entries supported depends on the number of VTEPs, number of VNIs and number of IFBDs (port * vlan). The above mentioned objects along with ARP entries share a global resource pool. PR1206633

Related Documentation

Modified: 2017-06-26