Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Junos OS Evolved Release Notes for QFX5220 Switches


What’s New

Learn about the new features and enhancements to existing features in the Junos OS Evolved main release and the maintenance releases for QFX5220-32CD switches.

What New in Junos OS Evolved Release 19.1R2

Class of Service (CoS)

  • Layer 3 CoS support extended (QFX5220-32CD)—Layer 3 CoS support has been extended to the QFX5220-32CD switch. Both IPv4 and IPv6 unicast routing are supported. Other CoS features supported include forwarding class (FC) to queue mapping, BA classifier - DSCP, fixed classifier and MF classifier, rewrite – DSCP, scheduling, WRED, ECN, and shared buffer. To provide higher port speed support, the following CLIs specific to rate configuration are updated to reflect a maximum possible rate of 400 Gbps:

    • set class-of-service schedulers sch1 transmit-rate

    • set class-of-service schedulers sch1 shaping-rate

    [See Understanding Class of Service].


  • QFX5220-32CD Switch—The QFX5220-32CD offers 32 ports of 400 Gigabit Ethernet in a low-profile 1-U form factor. With a 12.8-Tbps bandwidth, the QFX5220-32CD is optimally designed for spine-and-leaf deployments in enterprise, service provider, and cloud data centers. The high-speed ports support a wide variety of port configurations that include speeds of 400 Gbps, 100 Gbps, 50 Gbps, 40 Gbps, and 25 Gbps, and 10 Gbps.

    An Intel Xeon D-1500 processor drives the QFX5220 control plane, which runs the Junos Evolved software. The Junos OS Evolved software image is stored on two internal 50-GB solid-state drives (SSDs). The QFX5220-32CD is available with either ports-to-FRUs or FRUs-to-ports airflow and with AC power supplies.

    [See QFX5220 System Overview.]

Interfaces and Chassis

  • Mirroring support (QFX5220-32CD)—Mirroring is supported on Layer 3 interfaces. There is no Layer 2 support (analyzer or port-mirroring).


  • New IDL files that adhere to standardized guidelines (QFX5220-32CD)—API files are to be made consistent with each other. Support of this feature is restricted to FE, GE, XE, and AE interfaces. Only the following functionality is included: Add, Delete, Modify, and GET for supported interface objects. There is also a Unit Permissions Get API, which is used to get the following information on an already created logical interface: was the logical interface was configured using APIs or CLI and, if it was configured using APIs, which client created the logical interface.

Junos Telemetry for Interfaces

  • Junos Telemetry Interface (JTI) support (QFX5220-32CD)—OpenConfig support through gRPC and JTI is available for the following telemetry sensors that were previously only supported on Junos OS:

    • Sensor for Routing Engine internal interfaces (physical interface state and statistics)

    • Sensor for Routing Engine internal Logical interfaces (logical interface state and statistics)

    • Sensors for ARP

    • Sensor for Network Discovery Protocol (NDP)

    • Sensor for operational state of AE with LACP

    • Sensor for operational state of LLDP (neighbors information)

    To provision the sensor to export data through gRPC streaming, use the telemetry Subscribe RPC to specify telemetry parameters. Streaming telemetry data through gRPC also requires the OpenConfig and Network Agent packages.

    [See Configuring a Junos Telemetry Interface Sensor (CLI Procedure).]

Routing Protocols

  • Profile image (Layer 3 profile) delivered (QFX5220-32CD)—The protocols under the Routing Protocol process (rpd) are built as separate modules. By selecting which modules are included, rpd can be tailored to provide a given set of functionality, in effect, a leaner rpd. The Layer 3 fabric rpd is the first such lean rpd, known as a profile image. Any libraries not required for this functionality have been removed, reducing the executable size. CLI configuration related to the removed rpd protocol libraries has been removed. ISIS, OSPF, BGP, Static, BFDv4, and BFDv6 are supported. MPLS (LDP and RSVP), SR and SRTE, PIM, MLDP, EVPN, L2VPN, L2circuit, and dynamic tunnels are not supported.

  • MPLS features supported (QFX5220-32CD):


    • Static and Dynamic LSPs

    • LDP and RSVP

    • L3 VPN for IPv4 and IPv6

    • RSVP traffic engineering

    • Penultimate-hop popping

    • MPLS with ECMP

    • MPLS over LAG

    [See MPLS Overview.]

  • GRE features supported (QFX5220-32CD):

    • GRE tunnels over GigE, LAG, and VLAN

    • Payload protocol for IPv4 and IPv6

    • Delivery protocol for IPv4

    • Tunnel statistics

    • VRF with GRE

    • Time-to-live

    • IPv4 as GRE delivery header

    • IPv4 and IPv6 over GRE

    • ISO over GRE

    • Copying TOS to outer-IP for Routing Engine traffic

    [See Generic Routing Encapsulation (GRE).]

  • LACP features supported (QFX5220-32CD):

    • LACP load balancing

    • OpenConfig

    • Telemetry

    • Sync-reset with minimum-link

    • LACP force-up

    • LACP hold up

    [See Understanding Aggregated Ethernet Interfaces and LACP.]

  • Support for BFD (QFX5220-32CD)—QFX5220-32CD switches support bidirectional forwarding detection (BFD). BFD is a simple mechanism that detects failures in a network and works in a wide variety of network environments and topologies.

    [See Understanding Bidirectional Forwarding Detection (BFD).]

  • Support for Layer 3 forwarding (QFX5220-32CD)—QFX5220-32CD switches support IPv4 and IPv6 unicast routing as well as 128-way ECMP and Layer 3 load balancing. Reverse path forwarding is not supported.

    [See Understanding Layer 3 Logical Interfaces.]

Routing Policy and Firewall Filters

  • Firewall filter support on Layer 3 interfaces (QFX5220-32CD)—You can now configure a firewall filter on the switch and apply it to a Layer 3 (routed) interface. To configure the filter, you specify the family address type (inet or inet6 ), match condition, and the action to take if a match occurs. You configure firewall filters at the [edit firewall] hierarchy level. This feature was previously supported in an "X" release of Junos OS.

    [See Firewall Filter Match Conditions and Actions (QFX5220).]

Software Installation and Upgrade

  • Software upgrade support (QFX5220-32CD)—A single CLI command, request system software add, is used to upgrade the device. The restart option, allows you to upgrade the system using an application-level restart, that is, no system reboot. First the system determines how many applications need to restart (start with a new version), and then, after sending output to the CLI session, it restarts those applications. The applications upgraded receive their state from the system.

User Interface

  • Zero Touch Provisioning (ZTP) supported (QFX5220-32CD)—ZTP can dramatically reduce the time to provision the network in a data center and decrease the opportunity for introduction of human error into the network. The image and configuration files are placed centrally in a network server. The device is shipped with factory default configuration along with ZTP configuration. Upon booting up, the device downloads the image from the central location, upgrades itself and, upon rebooting, applies the configuration that it fetched from the network server. In this release, only the management interface (vmb0) can run ZTP.

    [See Zero Touch Provisioning.]

What New in Junos OS Evolved Release 19.1R1

There are no new or changed features introduced in Junos OS Evolved Release 19.1R1 for QFX5220 switches.

What’s Changed

There are no differences in behavior and syntax in Junos OS Evolved for QFX5220 devices in this release.

Known Behavior

Learn about known behavior in Junos OS Evolved for QFX5220 devices.

Authentication and Access Control

  • Here template user authorization paramaters are being tests, this functionality is not currently supported. Support for template user authorization is planned as part of RLI-38945 PR1415949


  • On the QFX5220-32CD switch, the serial port LED is not supported. PR1417226


  • In an network where the QFX5220-32CD acts as PE or P router, traffic loss can be seen during FRR triggers like node/link failure. The duration of the loss depends on the number of routes and next-hops in the switch and varies between 300 milliseconds to 1 second. PR1416946

  • During frequent route updates or link flaps, the system may not achieve the full scale of 4K ECMP next-hops. PR1419943

User Interface and Configuration

  • For large yang file, augmentation may not work PR1416972

  • In Junos OS Evolved for 19.1R2, vlans between 3968 to 4095 reserved for L3 interfaces by default. So this vlans can not be used for L2 interfaces. As of now there is no commit check added for this purpose. User should take care of this while configuring vlan for L2. PR1423468

Open Issues

Learn about open issues in Junos OS Evolved for QFX5220 devices.


  • Some features are documented but not supported in lean rpd profile image for Junos OS Evolved Release 19.1R2. Following are some examples of the unsupported CLI:

    • Use of advanced routing-related keywords in the policy options stanza, such as route distinguisher, rtf-prefix-list, family (evpn | esis | l2vpn | l2circuit | | msdp | pim | rsvp | spring-te | vpls), dynamic-tunnels, label-allocation, no-entropy-label-capability, p2mp-lsp-root, prefix-segment, ssm-source, selected-mldp-egress

    • Use of the family (ccc | mpls | vpls) for an interface configuration

    • The output for the show bfd client sessions command for rsvp and vpls

    • Help apropos for various keywords

    PR1387985, PR1387955, PR1387991, PR1388008, PR1388058, and PR1388102

  • ICMP mib table is not implemented in Junos OS Evolved and as such SNMP walk/get on this table will not yield any values. PR1378659

  • "Queues in use:" CLI output always shows value as 8 when the CLI command "show interfaces queue" is executed. PR1421176

  • picd and clksynced apps are not supported for ISSU upgrade on QFX5220-32CD. In order to upgrade these apps, the system needs to be rebooted. PR1423150

Routing Protocols

  • the command "show pfe route summary" is not supported PR1405448

  • Hidden BGP routes suppressed by Damping feature continue to hold reference on the route's Nexthop, even though the route is uninstalled from FIB. On an EVO system, this prohibits the deletion of the IFL,IFD objects from completing, when the interface is deactivated in configuration. And EVO does not allow an object to be un-deleted or a new-incarnation to be created until old one is really gone. So even if the interface is re-activated in config, ping does not pass. PR1423122

User Interface and Configuration

  • Multiple configd object anomalies seen after restart configd followed by triggers like deactivate interfaces/chassis and activate interfaces chassis PR1415643

  • IP is not getting assigned to the interface after delete and add interface PR1424442

Resolved Issues


  • pcep configuration and operational commands are visible in Junos OS Evolved Release 19.1R1 lean rpd profile image but are not supported. PR1387980

  • 100G PSM4 optics are not supported in this release PR1406553

  • As per MSA standards, link training needs to be enabled and that is reason behind link between Spirent and QFX5220-32CD is not UP. PR1417749

  • When the PICD app is restarted, the interface queue stats do not reflect the forwarding counters immediately in the "show interface extensive" output. They will start displaying the counters accurately when the forwarded packet count exceeds the value which was cached before the PICD restart. PR1424251

  • If the SSH session under which 'monitor interface traffic' is being run is killed, the iftop utility will stay at 100% CPU utilization. PR1426069

  • When physical links were removed and plugged back in immediately under a sec, there is intermittent chance that link might not be UP. PR1426541

  • sflowd core seen when few interface related operations are performed. PR1426902

  • ZTP file transfer will fail when using an FTP server that requires binary transfer mode to be explicitly defined, such as ProFTP. PR1432727

Routing Policy and Firewall Filters

  • This is new CLI:

    • set firewall family ethernet-switching filter <filter-name> term <term-name> from source-port-match-optimize <port>

    • set firewall family ethernet-switching filter <filter-name> term <term-name> from destination-port-match-optimize <port>


Software Installation and Upgrade

  • When software upgrade is performed wherein a set of components get upgraded, the customer may potentially notice that the versions of some other components change across the upgrade even though they were not really upgraded. There is no functional impact here and the components that did not get upgraded for which the versions show up as changed, wont be impacted during the upgrade process. PR1422573

  • When 'request system software rollback reboot' is executed, the expected behavior is to print a message that says 'Rollback Done' and let the user know that device would be going for a reboot. This message is not getting printed under some scenarios. PR1423921