Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


What's Changed

Learn about what changed in this release for QFX Series switches.


  • Default behavior changes and new options for the easy EVPN LAG configuration (EZ-LAG) feature—The easy EVPN LAG configuration feature now uses some new default or derived values, as follows:
    • Peer PE device peer-id value can only be 1 or 2.

    • You are required to configure the loopback subnet addresses for each peer PE device using the new loopback-subnet peer1-subnet and loopback peer2-subnet options at the [edit services evpn device-attribute] hierarchy level. The commit script uses these values for each peer PE device's loopback subnet instead of deriving those values on each PE device. The loopback-subnet option at the [edit services evpn device-attribute] hierarchy level has been deprecated.

    • If you configure the no-policy-and-routing-options-config option, you must configure a policy statement called EXPORT-LO0 that the default underlay configuration requires, or configure the new no-underlay-config option and include your own underlay configuration.

    • The commit script generates "notice" messages instead of "error" messages for configuration errors so you can better handle [edit services evpn] configuration issues.

    • The commit script includes the element names you configure (such as IRB instance names and server names) in description statements in the generated configuration.

  • This feature also now includes a few new options so you have more flexibility to customize the generated configuration:

    • no-underlay-config at the [edit services evpn] hierarchy level—To provide your own underlay peering configuration.

    • mtu overlay-mtu and mtu underlay-mtu options at the [edit services evpn global-parameters] hierarchy level—To change the default assigned MTU size for underlay or overlay packets.

    [See Easy EVPN LAG Configuration.]

  • Change in options and generated configuration for the EZ-LAG configuration IRB subnet-address statement—With the EZ-LAG subnet-address inet or subnet-address inet6 options at the edit services evpn evpn-vxlan irb irb-instance hierarchy, you can now specify multiple IRB subnet addresses in a single statement using the list syntax addr1 addr2 ?. Also, in the generated configuration for IRB interfaces, the commit script now includes default router-advertisement statements at the edit protocols hierarchy level for that IRB interface.

    [See subnet-address (Easy EVPN LAG Configuration).]

Junos XML API and Scripting

  • Ability to commit extension-service file configuration when application file is unavailable—When you set the optional option at the edit system extension extension-service application file file-name hierarchy level, the operating system can commit the configuration even if the file is not available at the /var/db/scripts/jet file path.

    [See file (JET).]

Network Management and Monitoring

  • Changes to the RPC response for <validate> operations in RFC-compliant NETCONF sessions (ACX Series, PTX Series, and QFX Series)—When you configure the rfc-compliant statement at the [edit system services netconf] hierarchy level, the NETCONF server emits only an <ok/> or <rpc-error> element in response to <validate> operations. In earlier releases, the RPC reply also includes the <commit-results> element.

  • NETCONF <copy-config> operations support a file:// URI for copy to file operations (ACX Series, PTX Series, and QFX Series)—The NETCONF <copy-config> operation supports using a file:// URI when <url> is the target and specifies the absolute path of a local file.

    [See <copy-config>.]

Platform and Infrastructure

  • Previously, shaping of Layer 2 pseudowires did not work on logical tunnel interfaces. This has been fixed for all platforms except QX chip-based MICs and MPCs.

Routing Protocols

  • In Junos OS Evolved platforms, show route snooping and show route forwarding-table does not show /56 routes in the VPLS address family table.

  • Optimized mesh group routes (QFX5130 and QFX5700)— show route snooping for inet.1/inet6.1 table and show route snooping table inet.1/inet6.1 display only CE mesh group routes for platforms that support EVPN-MPLS or EVPN-VxLAN multicast. In earlier releases, other mesh groups like the VE mesh group were also displayed.

  • Before this change most list were ordered by the sequence in which the user configured the list items, for example a series of static routes. After this change the list order is determined by the system with items displayed in numerical sequence rather than by the order in which the items were configured. There is no functional impact to this change.

  • The primary routing instance then starts index (hrStorageIndex) at 1, incrementing each time after assigning index to an entry in this list. If a mount is unmounted, the other mount's indices will not shift. hrstoragetable indices persist during the lifetime of mib2d. When a new mount is detected, it is assigned the next free index in the system. If there is no free index, it is assigned the last index +1.

Software Installation and Upgrade

  • The request system software validate-restart command output indicates the upgrade method (QFX5220-32D)—The request system software validate-restart command output summarizes the method required to perform the indicated upgrade, for example, an application restart, an in-service kernel warm restart, or a system reboot. [See request system software validate-restart (Junos OS Evolved).]

User Interface and Configuration

  • Viewing files with the file compare files command requires users to have maintenance permission — The file compare files command in Junos OS and Junos OS Evolved requires a user to have a login class with maintenance permission.

    [See Login Classes Overview.]