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.4R2 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.4R2 for the QFX5220.

Hardware

  • Support for QDD-400G-FR4 and QDD-400G-DR4 transceivers—Starting in Junos OS Evolved Release 19.4R2, the QFX5220-32CD switches support the QDD-400G-FR4 and QDD-400G-DR4 transceivers.

    [See the Hardware Compatibility Tool.]

Class of Service (CoS)

  • Support for CoS/QoS features through 400-Gigabit Ethernet interfaces (PTX Series and QFX Series)—Starting in Junos OS Evolved Release 19.4R2, support is provided for CoS/QoS features through 400-Gigabit Ethernet interfaces on PTX Series and QFX Series devices.

    [See Understanding Class of Service.]

Forwarding and Sampling

  • Customizing hashing parameters and shared-buffer alpha values for better load balancing (QFX5220)—The QFX5220 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. Starting with Junos OS Evolved Release 19.4R2, 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. You can also 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.]

Interfaces and Chassis

  • Support for dynamic load balancing (QFX5220)—Starting in Junos OS Evolved Release 19.4R2, QFX5220 switches support dynamic load balancing (DLB) for 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.4R2, 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)—Starting with Junos OS Evolved Release 19.4R2, the following multicast features are supported:

    • IPv4 and IPv6 multicast

    • Internet Group Management Protocol (IGMP)

    • Multicast Listener Discovery (MLD)

    • PIM source-specific multicast (PIM SSM)

    • PIM sparse mode (PIM SM)

    In this release, IGMP snooping, MLD snooping, MVPN, PIM MoFRR, PIM first hop router, rendezvous point (RP), and last hop router 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 Junos OS Evolved Release 19.4R2, 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 (PTX10003-80C, PTX10003-160C, QFX5220-32CD, and QFX5220-128C)—Starting in Junos OS Evolved Release 19.4R2, 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.4R2, 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.]

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)—Starting in Junos OS Evolved Release 19.4R2, you can use STP, RSTP, MSTP, and VSTP to provide Layer 2 loop prevention.

    [See Spanning Tree Protocol Overview.]

System Management

  • Boundary clock and enterprise profile support for Precision Time Protocol (PTP) (QFX5220)—Starting in Junos OS Evolved Release 19.4R2, 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.]

What’s Changed

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

What’s Changed in Junos OS Evolved Release 19.4R2-S1

Routing Protocols

  • Advertising /32 secondary loopback addresses to traffic engineering database as prefixes (PTX Series, QFX Series)—We've made changes to export multiple loopback addresses to the lsdist.0 and lsdist.1 routing tables as prefixes. This eliminates the issue of advertising secondary loopback addresses as router IDs instead of prefixes. In earlier releases, multiple secondary loopback addresses in the traffic engineering database were added to the lsdist.0 and lsdist.1 routing tables as part of node characteristics and advertised them as the router ID.

What’s Changed in Junos OS Evolved Release 19.4R2

Junos Telemetry Interface (JTI)

  • LLDP ON_CHANGE statistics support with JTI (PTX Series, QFX Series)—Enhanced telemetry ON_CHANGE event support provides the following LLDP attributes: - When LLDP is enabled on interfaces, LLDP interface counters are notified along with other interface-level attributes. - ON_CHANGE event reports LLDP neighbor age and custom TLVs, as well as when a neighbor is initially discovered

    [See Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface).]

Known Limitations

Learn about known behavior in Junos OS Evolved Release 19.4R2 for the QFX5220. For the most complete and latest information about known Junos OS Evolved defects, use the Juniper Networks online Junos Problem Report Search application.

Interfaces and Chassis

  • Using show interfaces to view traffic statistics does not show any traffic statistics for IPv6. PR1421685

MPLS

  • The maximum number of transit MPLS LSPs supported in QFX5220-32CD and QFX5220-128C switches is 16000. But depending on hash collisions, packet drops might be seen with more than 14,000 LSPs. PR1472100

User Interface and Configuration

  • In some cases, the command request support information might take more time to complete when journalctl gives a lot of boot messages as output, but functionality-wise there is no impact. PR1449792

Open Issues

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

Class of Service (CoS)

  • On QFX5220 platform running Junos OS Evolved, the CLI output of show class-of-service scheduler-map smap changed from Junos OS Evolved releases 19.2 to 19.4. PR1487189

Infrastructure

  • The following XML tags are missing in Junos OS Evolved for the show route forwarding-table command:

    • address-family

    • enabled-protocols

    • to

    PR1429413

Interfaces and Chassis

  • The show chassis in-service-upgrade and show chassis nonstop-upgrade CLI commands are not applicable to Junos Evolved Release 19.4R2. PR1425575

  • On multiple commits and rollback, there is a possiblilty that some physical interfaces are not created. As a workaround, one can restart the Pfemand application: cli> request system application app evo-pfemand restart node re0 . PR1482912

Platform and Infrastructure

  • The XML tags for show system virtual-memory are different in Junos OS Evolved as compared to Junos OS.

  • On QFX5220-128C platform, egress traffic might fail on any of the 10G channelized interfaces after channelization configuration or after a reboot. Multiple deletions and additions of AE and its member interfaces occasionally causes the port VLAN IDs of some of the member interfaces to reset to default value. PR1452493

  • For QFX5220-128C, traffic not is working for VLAN ID 1 with IRB configuration. PR1454468

  • On QFX5220-128C platform, random 10-Gigabit Ethernet channelized interfaces might not come up after reboot or after committing AE or MTU configuration changes. PR1485263

System Management

  • A QFX5220 switch might fail during an upgrade from Junos OS Evolved 19.3R2.1 to Junos OS Evolved 19.4-202002240046.0 or later releases due to clksyncd failure. PR1491803

User Interface and Configuration

  • Restart of App cmdd is failing with the following errors:

    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.4R2 for the QFX5220. For the most complete and latest information about known Junos OS Evolved defects, use the Juniper online Junos Problem Report Search application.

Interfaces and Chassis

  • Physical interface statistics retain old values after statistics are cleared and interfaces are deactivated and reactivated. PR1403606

  • A 400-Gigabit Ethernet interface might take a longer time (about 50 seconds) to come up. PR1450606

Routing Policy and Firewall Filters

  • Lo0 firewall filter might affect Layer 3 forwarding traffic on QFX5220 platforms. PR1475620

Routing Protocols

  • SFTP does not connect properly. The following error is displayed: Received message too long. PR1475255

Network Management and Monitoring

  • On platforms running Junos OS Evolved, multiple syslog servers are not being configured on the device when multiple syslog servers are configured on the DHCP server. PR1458931

System Management

  • PTP-FPGA access error printed because PTP-FPGA is not initialized. PR1457094

  • Sometimes dhclient generates a core file during ZTP retry when the dhclient process is exiting. PR1460906

  • Output 1PPS and 10MHz measurement ports on QFX5220-32CD are not fully available. PR1464452

  • The timingd process generates a core file rarely after a switch reboot. PR1464493

  • High CPU consumption is seen when a scaled VLAN configuration having 3965 VLANs is committed for 30 minutes. PR1474374

  • QFX5220-128C: INPHI firmware upgrade requires power cycling. PR1477124