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

  • BGP VRR convergence improvements (QFX Series)—Starting with Junos OS Release 18.2X75-D30, you can configure virtual route reflectors (VRRs) to order BGP routes using the route prefix so that multiple paths for the same prefix are sent 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 (QFX10002)—Starting with Junos OS Release 18.2X75-D30, you can provision sensors through the Junos Telemetry Interface to export telemetry data for several network elements without the need for polling. You can stream data through UDP or gRPC.

    Only the following sensors are supported on QFX10002 switches:

    • Physical interfaces statistics

    • Label-switched path (LSP) statistics

    • Network processing unit (NPU) memory

    • NPU memory utilization

    • CPU memory

    [See Overview of the Junos Telemetry Interface.]

  • MPLS container LSPs and self-ping improvements (QFX Series)—Starting with Junos OS Release 18.2X75-D30, you can access information about MPLS container LSPs and self-ping through the Junos Telemetry Interface (JTI). A new syslog message indicates when MPLS self-ping fails due to timeout. MPLS container LSPs now support streaming and notifications.

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

Routing Protocols

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

    [See Understanding Ping MPLS.]

  • Policy-controlled label allocation for BGP labeled unicast (QFX 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 labeled unicast. 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 the label mapping policies while exporting IPv4 labeled unicast prefixes. For a given prefix, if BGP receives a specific label in the result, BGP allocates the label from the static label range. Otherwise BGP allocates 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 management of YANG packages in configuration mode (QFX Series)—Starting in Junos OS Release 18.2X75-D30, adding, deleting, or updating YANG packages using the run command in configuration mode is not supported.

  • 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, if the server reply after a successful operation includes both an <ok/> element and one or more <rpc-error> elements with a severity level of warning, 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 includes both an <rpc-error> element with a severity level of 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.


  • 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. PR1287557

General Routing

  • The 100G DAC/Copper cable connected between QFX5210-64C devices and QFX10000 line of devices, links might not come up reliably. PR1324600

  • Based on the memory availability, the QFX10002 can scale up to 300 remote PE devices with a total of 600 tunnels. To avoid exceeding memory, we recommend that you do not go beyond this scale. PR1329243

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

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, when SXE interfaces are erroneously configured, the MAC pause frames might get generated on these internal interfaces and might lockup Packet Forwarding Engine. As a workaround, please delete SXE interfaces from the configuration and reboot. PR1281123

  • When traffic is sent over "et" interfaces the packets might be dropped because of cyclic redundancy check (CRC) errors. PR1313977

  • On 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 the QFX5210-64C, SNMP MIB related to IEEE8023-LAG-MIB does not work. PR1333575

  • On the QFX5100 line of devices with sFlow enabled, when deleting or deactivating the sFlow interface, all other interfaces might go down and fxpc core files will be generated. PR1356868

  • BGP session bounce might prevent BUM traffic from being flooded to all remote visual tunnel endpoint (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

  • The same address family (subnet logical interface or IRB logical interface, but not both) needs to be configured for establishing VTEPs. PR1376996

  • On QFX5100, QFX5110, and QFX5200 Series platforms, the Layer 3 interface might stop pinging the directly connected link address after the Layer 2 interface is deleted on the physical interface. PR1384144

Layer 2 Features

  • On the QFX10016, after 1000 lag interfaces are deleted and added back, the traffic drops until ARP is refreshed even though all the lag interfaces come up. PR1289546

  • EVPN-VXLAN fails to forward the IPv6 NS packet from the remote VTEP to the local host when the IPv6 neighbor solicitation (NS) or neighbor advertisement (NA) packets are received from the remote virtual tunnel endpoints (VTEP) through the virtual extensible LAN protocol (VXLAN) tunnel. PR1387519

  • When an EVPN-VXLAN Ethernet Segment Identifier (ESI) is multihomed, the unicast IPv6 Neighbor Solicitation/Neighbor Advertisement (NS/NA) packets received over VTEP from an ESI host are incorrectly flooded back to the ESI host resulting in packet loss. PR1405820


  • The lingering RSVP state might keep some labeled routes programmed in the Packet Forwarding Engine longer than they should be. This RSVP state eventually expires and deletes the RSVP MPLS routes from the FIB. Traffic loss is not anticipated because of 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 option and without any strict ERO, the LSP remains down after link-flap. PR1339916

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

Platform and Infrastructure

  • When chassis control restarts with the CoS rewrite rule configured on aggregated Ethernet interface, the Platform failed to bind rewrite messages might be seen in the syslog. Issue is specific to aggregated Ethernet interfaces when a restart chassis control is done. There might be a timing issue that can occur when the logical interface deletion is delayed due to high scale and when logical interfaces come up again post restart. They have different indices. PR1315437

  • Traffic silently drops and get discarded on the Packet Forwarding Engine as invalid L2 token when the protocol changes from VPLS to EVPN. PR1368802

Routing Protocols

  • In a scaled setup, when the host table is full and the host entries are installed in an 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

  • The backup Routing Engine might crash, causing vmcore to be generated on the master Routing Engine, master Routing Engine performance will not be affected. PR1346218

  • Packets are dropped after removing the filter from the interface when the same filter is 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. PR1338256