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 Devices

 

These release notes accompany Junos OS Evolved Release 19.4R1 for QFX5220-32CD and QFX5220-128C switches. They describe new and changed features, limitations, and known and resolved problems in the hardware and software.

What’s New

Learn about new features introduced in Junos OS Evolved Release 19.4R1 for QFX5220-32CD and QFX5220-128C switches.

Class of Service

  • Support for Class of Service (CoS) / Quality of Service (QoS) features through 400G interfaces on QFX-series and PTX-series platforms—Starting in Junos OS Evolved Release 19.4R1, support is provided for CoS/QoS features through 400G interfaces on QFX Series and PTX Series devices.

    [See Understanding Class of Service.]

Forwarding and Sampling

  • Customizing hashing parameters and shared-buffer alpha values for better load balancing (QFX5220)—The QFX220 switches achieve load balancing through the use of a hashing algorithm, which determines how to forward traffic over LAG bundles or to next-hop devices when ECMP is enabled. The hashing algorithm makes hashing decisions based on values in various packet fields. Starting with Junos OS Evolved Release 19.4R1, you can explicitly configure some hashing parameters to make hashing more efficient. The shared-buffer pool is a global memory space that all ports on the switch share dynamically as they need buffers. The switch uses the shared-buffer pool to absorb traffic bursts after the dedicated-buffer pool is exhausted. The shared-buffer pool threshold is dynamically calculated based on a factor called alpha. Also starting with Junos OS Evolved Release 19.4R1, you can specify the alpha, or dynamic threshold, value to determine the change threshold of shared buffer pools for both ingress and egress buffer partitions.

    To specify hashing parameters:

    user@switch# set forwarding-options enhanced-hash-key hash-parameters (ecmp | lag)

    To specify a threshold value for a particular queue:

    user@switch# set class-of-service shared-buffer (ingress|egress) buffer-partition buffer dynamic-threshold value

    [See hash-parameters and buffer-partition.]

General Routing

  • View ARP table entries and IPv6 neighbor information (QFX5220)—Starting in Junos OS Evolved Release 19.4R1, on QFX5220 switches, you can view the following:

    • Address Resolution Protocol (ARP) details such as the next-hop reference count and the next-hop current state, using the commands show arp reference-count and show arp state.

    • IPv6 neighbor cache information. The following commands are supported: show ipv6 neighbors flags, show ipv6 neighbors host, show ipv6 neighbors interface interface-name, show ipv6 neighbors reference-count, andshow ipv6 neighbors vpn vpn-name.

    [See show arp and show ipv6 neighbors.]

Interfaces and Chassis

  • Support for dynamic load balancing (QFX5220)—Starting in Junos OS Evolved Release 19.4R1, QFX5220 switches support dynamic load balancing (DLB) for equal-cost multipath (ECMP). DLB is an enhancement to static load balancing. DLB considers member bandwidth utilization along with packet content for member selection.

    You can use the following DLB modes to load-balance traffic:

    • Flowlet

    • Assigned flow

    • Per-packet

    To configure DLB for ECMP, include the ecmp-dlb statement at the [edit forwarding-options enhanced-hash-key] hierarchy level.

    Note

    You cannot configure both DLB and resilient hashing at the same time.

    [See Understanding Dynamic Load Balancing and Configuring Dynamic Load Balancing.]

Layer 2 Features

  • Spanning-Tree Protocol (STP), Rapid Spanning-Tree Protocol (RSTP), Multiple Spanning-Tree Protocol (MSTP), and VLAN Spanning-Tree Protocol (VSTP) support (QFX5220 switches)—Starting in Junos OS Evolved Release 19.4R1, You can use STP, RSTP, MSTP, and VSTP to provide Layer 2 loop prevention.

    [See Spanning-Tree Protocol Overview.]

Multicast

  • Support for multicast forwarding (QFX5220-32CD and QFX220-128C switches)—Starting with Junos OS Evolved Release 19.4R1, the following multicast features are supported:

    • IPv4 and IPv6 multicast

    • Internet Group Management Protocol (IGMP)

    • Multicast Listener Discovery (MLD)

    • Protocol Independent Multicast source-specific multicast (PIM SSM)

    • Protocol Independent Multicast sparse mode (PIM SM)

    In this release, IGMP snooping, MLD snooping, MVPN Multicast, PIM MoFRR, PIM First Hop router (FHR), Rendezvous point (RP), and Last Hop Router (LHR) are not supported.

    [See Multicast Routing Protocols ].

Network Management and Monitoring

  • Support for running a Puppet agent as a Docker container (PTX10003-80C, PTX10003-160C, QFX5220-32CD, and QFX5220-128C)—Starting in Release 19.4R1, devices running Junos OS Evolved support running a Puppet agent as a Docker container. As an alternative to using the Puppet agent that is integrated into the Junos OS Evolved software image, you can use the Puppet agent Docker container provided by Juniper Networks. Using the container enables you to use standard Docker tools to manage the container and mount or unmount the Puppet agent as needed.

    [See Installing Puppet for Junos OS.]

  • Support for running a Chef client as a Docker container (QFX5220-32CD, QFX5220-128C)—Starting in Release 19.4R1, devices running Junos OS Evolved support running a Chef client as a Docker container. As an alternative to using the Chef client that is integrated into the Junos OS Evolved software image, you can use the Chef client Docker container provided by Juniper Networks. Using the container enables you to use standard Docker tools to manage the container and mount or unmount the Chef client as needed.

    [See Deploying Chef for Junos OS.]

Routing Policy and Firewall Filters

  • Support for 2000 egress firewall filters (QFX5220)—Starting in Junos OS Evolved Release 19.4R1, you can configure up to 2000 VLAN firewall filters on the QFX5220 switch. This feature is supported only in the egress direction (traffic exiting the VLAN). To configure, include the egress-scale option under the eracl-profile statement at the [edit system packet-forwarding-options firewall] hierarchy level.

    [See eracl-profile and Configuring Firewall Filters.]

System Management

  • Install third-party software on devices running Junos OS Evolved (QFX5220)—Starting in Junos OS Evolved Release 19.4R1, you can install a third-party software package onto a QFX5220 switch running Junos OS Evolved the same way you install new releases of the Junos OS Evolved software, by using the request system software add pathname/filename command. The only difference is that the third-party software files are .tgz files and the Junos OS Evolved software files are .iso files.

    [See How to Install Third-Party Software on Devices Running Junos OS Evolved.]

  • Boundary clock and enterprise profile support for Precision Time Protocol (PTP) (QFX5220)—Starting in Junos OS Evolved Release 19.4R1, the enterprise profile, which is based on PTPv2, provides the ability for enterprise and financial markets to timestamp on different systems and to handle a range of latency and delays.

    The enterprise profile supports the following options:

    • IPv4 multicast transport

    • Boundary clocks

    • 512 downstream slave clocks

    You can enable the enterprise profile at the [edit protocols ptp profile-type] CLI hierarchy level.

    [See Understanding the Precision Time Protocol Enterprise Profile.]

Spanning Tree Protocols

  • Spanning-Tree Protocol (STP), Rapid Spanning-Tree Protocol (RSTP), Multiple Spanning-Tree Protocol (MSTP), and VLAN Spanning-Tree Protocol (VSTP) support (QFX5220 devices)—Starting in Junos OS Evolved Release 19.4R1, You can use STP, RSTP, MSTP, and VSTP to provide Layer 2 loop prevention.

    [See Spanning-Tree Protocol Overview.]

What’s Changed

Learn about what changed Junos OS Evolved Release 19.4R1 for QFX5220-32CD and QFX5220-128C switches.

Changes in CLI Statements and Commands

User Interface and Configuration

  • The request system shutdown (reboot | power-off | halt) command is deprecated on Junos OS Evolved (PTX10003 and QFX5220)—The command for reboot, power-off, or halt for Junos OS Evolved is request system (reboot | power-off | halt) instead of request system shutdown (reboot | power-off | halt) as it was previously. Junos OS Evolved uses the same commands for this functionality as Junos OS.

    [See request system reboot, request system power-off, and request system halt.]

Known Behavior

General Routing

  • It takes up to 420 seconds in QFX5220-128C for interfaces to come up after reboot when all ports are channelized. The higher time is due to the time taken to download firmware for all 64 dies. PR1433083

  • Auto-RP announce and mapping is not currently supported for Junos OS Evolved; only discovery is supported. In order to enable this feature, PIM and Packet Forwarding Engine jointly needs to provide a fix. From PIM's POV, we only need to enable the CLI configuration for PTX Series platforms and remove an Junos OS Evolved check in our codepath for announce- which is a very minimal change. But from Packet Forwarding Engine's side we do not need to know what modifications are needed as Packet Forwarding Engine might need to support Local NH as RPF NH for the required platform- which is the main change required here. PR1459187

  • When many member links are added to an AE or MTU is changed for many interfaces at the same time, CPU can remain high for many minutes. The CPU remains high till the all interfaces are flapped. PR1470353

System Management

  • XML Tags are missing for the output of the show system statistics command. A complete list of the tags missing in the output is listed in the Description tab of the PR. PR1429644

User Interface and Configuration

  • For large YANG file, augmentation may not work. PR1416972

Open Issues

Learn about open issues in this release for QFX5220-32CD and QFX5220-128C switches. For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Juniper Problem Report Search application.

General Routing

  • When removing and inserting a 400G AOC module, there can be up to 90 seconds delay before the link establishes after insertion. PR1454259

Infrastructure

  • During boot installation, ntpd.service fails to start in the scenario when upgrade is done by selecting boot from GRUB menu. PR1421946

Interfaces and Chassis

  • QFX5200 running Junos OS Evolved: Physical interface stats retain old values after clear stats & deactivate/activate on interface where MTU was configured. Workaround is to run clear interfaces statistics once after deactivate/activate interface (for which MTU is configured). PR1403606

  • The show chassis in-service-upgrade and show chassis nonstop-upgrade cli commands are not applicable to this Junos OS Evolved release. PR1425575

  • When exposed to traffic with packet sizes greater than the interface MTU and the do-not-fragment bit set, the traffic is dropped as expected. The "Output MTU Error" counter does not increase when you issue the show interfaces extensive command. PR1434860

  • QFX5220-128C: The channelization ports might be marked as down or missing with rapid add or delete configuration multiple times on the interface. To fix the issue, configure all whole block 4 ports to unused and delete the unused ports. This should bring up the interfaces. PR1442657

  • Two physical interfaces flaps are observed for each physical interface if mtu or lacp configuration is changed. The flaps might be observed up to 15 minutes apart if the channelized configuration is present and mtu is applied for all 128 interfaces. PR1446214

  • After a link flap, a 400G link may take up to 50 seconds before returning stably to "up". PR1450606

Network Management and Monitoring

  • With LACP configurations present, some of the channelized interfaces remain down after a reboot. PR1459554

  • After committing the IPCLOS scaled profile configuration with 32 ports or software image upgrade, some DAC interfaces might remain down. Workaround: Reboot the switch with the saved IPCLOS configuration. PR1460442

Routing Protocols

  • To view management interfaces in the ARP table, use the command show arp vpn mgmt_junos. PR1435537

System Management

  • show system uptime points to correct clock. PR1453595

User Interface and Configuration

  • The Junos CLI communicates with MGD over an internal unix-domain socket and is granted special permission to open this protected mode socket. Due to a misconfiguration of the internal socket, a local, authenticated user may be able to exploit this vulnerability to gain administrative privileges. PR1406219

  • On QFX5220-32CD, VLANs between 3968 to 4095 are reserved for L3 interfaces by default. So, these VLANs cannot 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

  • The Junos OS Evolved output for the CLI "show LLDP neighbors" is different than in Junos OS. Some of the XML tags for the CLI show lldp neighbors interface and show lldp are missing. PR1430795

  • Restart of App cmdd is failing with below error: error: abnormal communication termination with command-handler daemon error: the command-handler subsystem is not responding to management requests. PR1434409

Resolved Issues

Learn which issues were resolved in Junos OS Evolved Release 19.4R1 for QFX5220-32CD and QFX5220-128C switches.

Infrastructure

  • Differences in xml tags for show route forwarding-table cli.PR1429413

  • DHCP packets might not be received by jdhcpd on all interfaces. PR1455435

Interfaces and Chassis

  • MIB entPhysicalTable does not show Xcvr/optics data.PR1414503

  • Intermittently one or more channelized interfaces might not come up after a reboot. PR1446755

  • Interface not coming up after deactivate/activate AE on DUT. PR1448436

  • QFX5220-128C: Interfaces OIR might take up 50 seconds to come up on Junos OS Evolved 19.2R1 release. PR1449416

  • SNMPD traps are not generated in DC PSM testing. PR1450037

  • 40/100G interface went down after committing the profile configuration. PR1454412

  • Multiple interfaces go down after committing the configuration with the error as Interface: cannot get pfe_portE for ifd: PR1461868

Layer 2 Features

  • show ethernet-switch statistics command is not supported in Junos OS Evolved Release 19.3R1. PR1457307

  • If RSTP is to be enabled on a switch that has a mix of AE and individual network ports, only first 7 AEs (ae0-ae6) can be configured under RSTP. PR1462059

Network Management and Monitoring

  • In certain configurations DHCPv6 client fails to bind over L2 LDRA-connected DHCPv6 Relay. PR1458040

Routing Policies and Firewall Filters

  • Lo0 firewall filter might affect L3 forwarding traffic on QFX5220 EVO platforms PR1475620

Routing Protocols

  • LLDP neighborship is not established if interface family configuration is not activated. PR1433295

  • For dual stack configuration, platform does not support different MTU for IPv4 and IPv6. PR1447183

System Management

  • DCQCN:after delete congestion-notification-profile, DCQCN should stop working. PR1451911

  • 128 Traffic not working for vlan-id 1 with irb configuration. PR1454468