Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Junos OS Release Notes: QFX Series


Review information specific to running Junos OS Release 18.2X75-D30 on the QFX Series.

What’s New in 18.2X75-D30

Learn about new features introduced in this release for QFX Series switches.

General Routing

  • vRR BGP convergence improvements—Starting with Junos OS Release 18.2X75-D30, virtual route reflectors (vRRs) can be configured to order BGP routes using the route prefix so that multiple paths for the same prefix are sent more closely together. To enable this function, use the send-addpath-optimization statement under the [edit protocols bgp] hierarchy.

    [See Understanding Virtual Route Reflector.]

Junos Telemetry Interface

  • Support for the Junos Telemetry Interface (PTX10000, QFX10002)—Starting with Junos OS Release 18.2X75-D30, you can you can provision sensors through the Junos Telemetry Interface to export telemetry data for several network elements without involving polling. You can stream data through UDP or gRPC.

    Only the following sensors are supported on PTX1000 routers:

    • Physical interfaces statistics

    • Label-switched-path (LSP) statistics

    • Network processing unit (NPU) memory

    • NPU memory utilization

    • CPU memory

    To provision sensors to stream data through UDP, all parameters are configured at the[edit services analytics] hierarchy level. To provision sensors to stream data through gRPC, use the telemetrySubscribe RPC to specify telemetry parameters for a specified list of OpenConfig command paths. Streaming telemetry data through gRPC also requires you to download the OpenConfig for Junos OS module and YANG models.

    [See Overview of the Junos Telemetry Interface.]

  • MPLS container LSPs and self-ping improvements—Starting with Junos OS Release 18.2X75-D30, MPLS container LSPs and self-ping information can be accessed through the Junos Telemetry Interface. A new syslog message indicates when MPLS self-ping fails due to timeout. MPLS container LSPs now support streaming and notification support.

    [See label-switched-path (Protocols MPLS).]

Routing Protocols

  • MPLS ping and traceroute for segment routing (MX Series, PTX Series, QFX Series)—Starting with Junos OS Release 18.2X75-D30, MPLS ping and traceroute are supported for labelled ISIS, labelled OSPF, and static SR paths. This is a simple and effective method of fault detection.

    [See Understanding Ping MPLS.]

  • Policy-controlled label allocation for BGP labeled unicast (QFX Series, PTX Series)—Starting with Junos OS Release 18.2X75-D30, a new type of routing policy called label mapping policy enables static and predictable label allocation for BGP-LU. Label mapping policies assigns a specific label to a prefix or maps a specific range of labels to a range of prefixes in a deterministic manner. BGP evaluates label mapping policies in the export process of IPv4 LU prefixes. For a given prefix, if BGP receives a specific label in the result, BGP will allocate the label from the static label range. Otherwise it will allocate a label from the dynamic label range.

    [See labeled-unicast.]

What’s Changed in 18.2X75-D30

Interfaces and Chassis

  • New XML tag element <lacp-hold-up-state> added in show lacp interfaces XML display (QFX Series)—In Junos OS Releases 18.2X75-D30, 18.2X75-D40, and 18.2X75-D50, the show lacp interfaces | display xml command displays a new XML tag element <lacp-hold-up-state>. The <lacp-hold-up-state> displays the time interval an interface holds before it changes from state, down to up. In earlier Junos OS releases, the LACP hold up the information for all interfaces were in a single <lacp-hold-up-information> XML tag. Now, for each interface it is displayed in a separate <lacp-hold-up-information> XML tag.

Network Management and Monitoring

  • Junos OS does not support managing YANG packages in configuration mode (QFX Series)—Starting in Junos OS Release 18.2X75-D30, Junos OS does not support adding, deleting, or updating YANG packages using the run command in configuration mode.

  • The NETCONF server omits warnings in RPC replies when the rfc-compliant statement is configured and the operation returns <ok/> (QFX Series)—Starting in Junos OS Release 18.2X75-D30, when you configure the rfc-compliant statement at the [edit system services netconf] hierarchy level to enforce certain behaviors by the NETCONF server, the server must not return an RPC reply that encloses both an <rpc-error> element and an <ok/> element. If the operation is successful, but the server reply would enclose one or more <rpc-error> elements of severity warning in addition to the <ok/> element, then the warnings are omitted. In earlier releases, or when the rfc-compliant statement is not configured, the NETCONF server might issue an RPC reply that encloses both an <rpc-error> element of severity warning and an <ok/> element.

Known Limitations

Learn about known limitations 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

  • 100G DAC/Copper cable connected between QFX5210-64C and QFX10K devices, links might not come up reliably. Rest of the 100G Optics/AOC, 40G Optics/DAC/Copper works well when connected between QFX5210-64C and QFX10K devices. PR1324600

  • In QFX10002, based on memory availability, it can scale up to 300 remote PE with a total of 600 tunnels. Its not recommended to go beyond this scale to avoid exceeding memory. PR1329243

  • Hardware watchdog does not work on QFX10008 and QFX10002-60C/PTX10002-60C. PR1343131


  • When a VLAN uses an IRB interface as the routing interface, the vlan-id parameter must be set to "none" to ensure proper traffic routing. This issue is platform independent. PR1287557

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

  • Single-bit and multiple-bit ECC errors are not logged on QFX5110 switches. PR1251917

  • On QFX10002 platform, SXE interfaces erroneously configured in configuration might cause MAC pause frames to be generated on these internal interfaces and cause PFE lockup. As a workaround, please delete SXE interfaces from the configuration and reboot. PR1281123

  • Traffic drop occurs on sending traffic over "et" interfaces due to CRC errors. PR1313977

  • Port 0 of Qfx5100-48t does not come up in mixed VCF. As a workaround, use "phy diag xe0 dsc" command as of now from BCM shell upon reboot which brings up the port and stays up continuously until the next reboot PR1323323

  • On PTX and QFX10K platforms, if a firewall filter is configured with action "then decapsulate gre routing-instance ", and the routing-instance is newly configured at the same time in one commit, then the firewall filter might not decapsulate the Generic Routing Encapsulation (GRE) traffic. PR1325104

  • On QFX5210-64C, SNMP MIB related to IEEE8023-LAG-MIB is not working PR1333575

  • On QFX5100 platforms with sFlow enabled, when deleting/deactivating the sFlow interface, all other interfaces might go down and fxpc cores will be observed. PR1356868

  • BGP session bounce may sometimes cause, NOT to flood BUM traffic to all Remote Vteps. PR1373093

  • Commit failures related to VRF instance configuration might be observed if interface other than loopback interface is configured under vrf routing instances. PR1375130

  • On the VxLAN network side, same address families need to be used to setup VxLAN Tunnels. For example, if L3-INET IFL is configured on an IFD to be underlay for establishing VTEPs, then an IRB IFL shouldn't be configured on the same IFD to establish VTEP. PR1376996

  • On QFX5100/QFX5110/QFX5200 series platforms or AS7816-64X (White box), the Layer3 traffic might be dropped if the Layer2 is deleted on the IFD (Physical port) having both Layer2 and Layer3 logical. PR1384144


  • CNH (chained-composite-next-hop) is must for EVPN pure type 5 with VXLAN encapsulation. Without this Packet Forwarding Engine would not program the tunnel NH. You have to explicit set it on QFX5110. set routing-options forwarding-table chained-composite-next-hop ingress evpn. QFX10K it is applied as part of default configuration. jnpr@QFX> show configuration routing-options forwarding-table | display inheritance defaults. PR1303246

Layer 2 Features

  • On QFX10016, after deleting and re-adding of 1k lag interfaces, traffic drops could be seen until ARP are refreshed even though all lag interfaces comes up. PR1289546

  • On QFX5000 Series platforms, if EVPN-TYPE 5 routes are present, when doing "restart routing" or a BGP session to a neighbor device flaps, the dcpfe core file might be seen. It might cause service impact and traffic impact. PR1387360

  • When the IPv6 NS (Neighbor Solicitation)/NA (Neighbor Advertisement) packets are received from the remote VTEP (Virtual Tunnel Endpoints) through the VXLAN (Virtual Extensible LAN protocol) tunnel, these packets are not getting forwarded to the local host. The issue results in the IPv6 neighbor discovery in the local host fail. PR1387519

  • In EVPN-VXLAN (Ethernet VPN - Virtual Extensible LAN) ESI (Ethernet Segment Identifier) multihomed scenario, the unicast IPv6 NS/NA (Neighbor Solicitation/Neighbor Advertisement) packets received over VTEP (Virtual Tunnel Endpoints) from an ESI host are incorrectly flooded back to the ESI host. The issue might cause loop and result in packet loss. PR1405820


  • There could be some lingering RSVP state which would keep some labeled-routes programmed in the Packet Forwarding Engine longer than they should be. This RSVP state eventually expires and then delete the RSVP MPLS routes from FIB. However, traffic losses is not anticipated due to this lingering state or the corresponding label routes in the FIB. In the worst case, in a network, where there is persistent link flapping going on, this lingering state could interfere with the LSP scale being achieved. PR1331976

  • On all Junos OS products, when LSPs are configured with no-cspf and without any strict ERO, the LSP remains down after link-flap. PR1339916

  • Statistics of transit traffic does not increment LSP statistics signaled by RSVP-TE. PR1362936

Platform and Infrastructure

  • When chassis control restart is done with the COS rewrite rule configured on AE interface, the "Platform failed to bind rewrite" messages could be seen in syslog. Issue is specific to AE interfaces. It is a timing issue that can occur when logical interface deletion is delayed due to high scale and when logical interfaces come up again post restart they have different indices. PR1315437

  • Traffic drops on Packet Forwarding Engine as "invalid L2 token" when protocol changes from VPLS to EVPN. PR1368802

Routing Protocols

  • On a scaled setup, when the host table is full and the host entries are installed in LPM table, OSPF sessions might take more time to come up. PR1358289

Resolved Issues

Learn which issues were resolved 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 dual Routing Engine systems like QFX10K8/16 platforms and high scale, the backup Routing Engine might experience a crash, causing vmcore to be generated on the master Routing Engine. The master Routing Engine performance is not affected. PR1346218

  • Packets are dropped after removing the filter from the interface when the same filter was applied on input and output at the same time. PR1372957

Platform and Infrastructure

  • On the QFX10000 platforms, if the virtual router redundancy protocol (VRRP) feature is configured on sub-interfaces, this function does not work well. Configuring VRRP on IRB interfaces instead of sub-interfaces can avoid this issue. PR1338256