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

What’s New in Junos OS Evolved Release 20.2R2

There are no new features or enhancements to existing features for the QFX5220 switches in Junos OS Evolved Release 20.2R2.

What’s New in Junos OS Evolved Release 20.2R1

Class of Service (CoS)

  • Priority-based flow control (PFC) using Differentiated Services code points (DSCP) at Layer 3 for untagged traffic (QFX5220)—Starting in Junos OS Evolved Release 20.2R1, to support lossless traffic across Layer 3 connections to Layer 2 subnetworks on QFX5220 switches, you can configure PFC to operate using 6-bit DSCP values from Layer 3 headers of untagged VLAN traffic, rather than IEEE 802.1p priority values in Layer 2 VLAN-tagged packet headers. DSCP-based PFC is required to support Remote Direct Memory Access (RDMA) over converged Ethernet version 2 (RoCEv2).

    [See Understanding PFC Using DSCP at Layer 3 for Untagged Traffic.]

Multicast

  • IGMP snooping support (QFX5220)—Starting with Junos OS Evolved Release 20.2R1, you can configure IGMP snooping.

    Support includes:

    • IGMP snooping with IGMPv1, IGMPv2, and IGMPv3

    • Any-source multicast (ASM) and source-specific multicast (SSM) modes

    • IGMP querier at Layer 2

    Limitations include:

    • IGMP proxy mode is not supported.

    • Devices receiving IGMP group-specific queries on a multicast router interface forward those queries to all other interfaces in the VLAN.

    • Make before break (MBB) is not supported for multicast receivers on existing Layer 2 aggregated ethernet (aex) or link aggregation group (LAG) interfaces, including for member additions, deletions, and link up or down events.

    • The devices forward all unregistered IPv4 and IPv6 multicast packets to the multicast router interfaces in the VLAN even if you configured an interface as a multicast router interface only for IGMP snooping.

    • IGMP snooping using IRB interfaces is not supported.

    • IGMP snooping is not supported in EVPN-VXLAN or EVPN-MPLS networks.

    [See IGMP Snooping Overview.]

What's Changed

Learn about what changed in Junos OS Evolved Release 20.2R2 for the QFX5220.

Changes in CLI Statements and Commands

What’s Changed in Junos OS Evolved Release 20.2R2

Class of Service (CoS)

  • On QFX5130 and QFX5220, you must map all PFC-enabled IEEE 802.1P code-points to a lossless (no-loss) forwarding class. If a CNP has code-points that are mapped to a lossy forwarding class, the entire CNP will not be programmed in hardware..

EVPN

  • New output flag for the show bridge mac-ip table command—The Layer 2 address learning daemon does not send updated MAC and IP Address advertisements to the Routing Protocol daemon when an IRB interface is disabled in an EVPN-VXLAN network. Junos has added the NAD flag in the output of the show bridge mac-ip-table command to identify the disabled IRB entries where the MAC and IP address advertisement will not be sent.

    [See show bridge mac-ip-table.]

MPLS

  • Change in auto-bandwidth adjustment (QFX5130-32CD and QFX5220)—If auto-bandwidth adjustment fails because of bandwidth unavailable error, the router tries to bring up the LSP with the same bandwidth during the subsequent reoptimization. In earlier releases, when the auto-bandwidth adjustment fails, the current bandwidth is reset to the bandwidth that was already active.

    [See rsvp-error-hold-time.]

Routing Protocols

  • Advertising /32 secondary loopback addresses to Traffic Engineering Database (TED) as prefixes (PTX Series and QFX Series)—We've made changes to export multiple loopback addresses into 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 TED were added into lsdist.0 and lsdist.1 routing tables as part of node characteristics and advertised them as the router-id.

  • Control plane DDoS protection packet type option for ARP traffic (PTX Series and QFX Series)— Starting in this release, we've renamed the arp-snoop packet type option in the edit system ddos-protection protocols arp protocol group to arp. This packet type option enables you to change the default control plane distributed denial of service (DDoS) protection policer parameters for ARP traffic.

    [See protocols (DDoS) (PTX Series and QFX Series)..]

What’s Changed in Junos OS Evolved Release 20.2R1

General Routing

  • Support for full inheritance paths of configuration groups to be built into the database by default (PTX10003, PTX10008, and QFX5220)—Starting with Junos OS Evolved Release 20.2R1, the persist-groups-inheritance option at the [edit system commit] hierarchy level is enabled by default. To disable this option, use no-persist-groups-inheritance.

    [See commit (System).]

  • Modified request system storage cleanup command (PTX10003, PTX10008, and QFX5220)—Starting in Junos OS Evolved Release 20.2R1, the request system storage cleanup command does not remove Junos OS Evolved images from the device. It removes all core files, log files from /var/log/, and all /var/log/* files. To remove old images from the device, use the request system software delete command.

    [See request system storage cleanup and request system software delete.]

High Availability (HA) and Resiliency

  • Install or activate the RIFT package to include the request rift package activate-as-top-of-fabric option—Install or activate the RIFT package to include the request rift package activate-as-top-of-fabric option. This option is same as the activate option but it adds additional configuration to act as a top-of-fabric node.

Interfaces and Chassis

  • Support for 40-Gbps speed on QSFP28 ports (QFX5220-128C)—The QFX5220-128C consists of 128 high-density 100-Gigabit Ethernet QSFP28 ports. Starting in Junos OS Evolved Release 20.2R1, you can configure all the QSFP28 ports to operate at 40-Gbps speed.

    In earlier Junos OS Evolved releases, you can configure 40-Gbps speed only on even-numbered QSFP28 ports.

    [See QFX5220-128C Port Panel.]

Juniper Extension Toolkit (JET)

  • Updates to IDL for RIB service API bandwidth field (PTX10003, PTX10008, and QFX5220)—The Interface Definition Language (IDL) file for the RouteGateway RIB service API has been updated to document additional rules for the bandwidth field. You must set bandwidth only if a next hop has more than one gateway, and if you set it for one gateway on a next hop, you must set it for all gateways. If you set bandwidth when there is only a single usable gateway, it is ignored. If you set bandwidth for one or more gateways but not all gateways on a next hop, you see the error code BANDWIDTH_USAGE_INVALID.

    [See Juniper EngNet.]

Routing Protocols

  • Recommendation to include the local-address statement when configuring IBGP and multihop EBGP—When a device peers with a remote device’s loopback interface address, use the local-address statement at the [edit protocols bgp group internal-peers] hierarchy to specify the source information in BGP update messages. Although a BGP session can be established when only one of the paired routing devices has local-address configured, we strongly recommend that you configure local-address on both paired routing devices for IBGP and multihop EBGP sessions. The local-address statement ensures that deterministic fixed addresses are used for the BGP session end-points.

    [See local-address (Protocols BGP) and BGP Peering Sessions.]

Known Limitations

Learn about limitations in this release 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

  • QFX5220 does not support mixed-speed aggregated Ethernet. PR1515041

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 Junos Problem Report Search application.

Class of Service (CoS)

  • On all Junos OS Evolved platforms, the cosd anomalies might be seen if CoS is configured on an interface using wildcard (like et-*, et-1/*/*, ae*, and fti*). These anomalies can cause traffic impact. The issue is due to some out-of-order internal events. PR1494573

Routing Policy and Firewall Filters

  • On QFX5220 platforms with Junos OS Evolved images, when the lo0 firewall filter (inet/inet6) is used, Layer 3 forwarding traffic might be discarded by the lo0 filter. PR1475620

Routing Protocols

  • The virtual-router option is not supported under routing-instance in lean rpd image. PR1494029

System Management

  • CLI changed in Junos OS Evolved 20.1R1 release to align with Junos OS:

    All the boot device options and events that are available at request system shutdown reboot are moved under the request node options.

    Boot device options: usb, network, disk1 and disk2.

    Event options: reboot, halt, power-off, power-on, offline, and online. PR1456037

  • PTP-FPGA access error displayed as PTP-FPGA is not initialized. PR1457094

  • When link goes up or down, Tx/Rx loss of signal alarm from diagnostics optics might take a long time (around 10 minutes) to show up. PR1499741

User Interface and Configuration

  • On QFX5220-32CD, VLANs between 3968 and 4095 are reserved for Layer 3 interfaces by default. So, these VLANs cannot be used for Layer 2 interfaces. As of now there is no commit check added for this purpose. You need to take care of this while configuring VLANs for Layer 2. PR1423468

Resolved Issues

Learn which issues were resolved in Junos OS Evolved Release 20.2R2 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.

Resolved Issues: 20.2R2

Routing Policy and Firewall Filters

  • The JET APIs related to firewall filter might fail on QFX5220-32CD and QFX5220-128C with Junos OS Evolved 20.1R1 and later releases. PR1515850

Routing Protocols

  • The protocol LLDP might not be enabled after factory default. PR1536531

System Management

  • QFX5220 does not support the following matches, which were supported on QFX5200: first-fragment, tcp-established, Is-fragment, and hop-limit. PR1499009

  • SFP+-40G-CU1M's media type appears as fiber. PR1499408

  • The evo-aftmand process might be stuck at 100% CPU usage in a scaled setup. PR1511597

  • The temperature-thresold settings for yellow alarms are not reset back to original values after changing temperature thresholds on sensor components. PR1513097

  • QFX5220-32CD: CRC errors are seen with 4x100G FR4 and DR4 optics in the environmental stress test. PR1520133

  • Scheduling variance will be seen when queues 3 and 4 are congested on QFX5220. PR1521531

Resolved Issues: 20.2R1

Class of Service (CoS)

  • The cosd anomalies are observed after committing the EBGP baseline configuration. PR1494573

Infrastructure

  • fibd generates core files that can be seen after commit when the VLAN ID of a VLAN is changed. PR1497790

Interfaces and Chassis

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

  • The 400 GbE link might take a longer time (about 50 seconds) to come up. PR1450606

  • The interface is not a part of member VLAN when configured. PR1495207

Platform and Infrastructure

  • Junos OS and Junos OS Evolved: A specific IPv4 packet can lead to FPC restart. (CVE-2020-1638) PR1493176

Routing Protocols

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

System Management

  • Output MTU Error statistics do not increase when the show pfe statistics traffic command is issued. PR1434860

  • Event options and device options are moved from request system shutdown reboot to request node. PR1456037

  • The switch-options configuration not available on lean rpd images. PR1457825

  • 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

  • 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

  • SSH service is unresponsive after setting system services ssh key-exchange dh-group1-sha1. PR1467467

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

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

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

  • ZTP: Image upgrade using HTTPS does not work in Junos OS Evolved 20.2R1. PR1479125

  • Failed to start MGD initialization of schema and database while upgrade from Junos OS Evolved 19.3R2.1 to 19.4-202002240046.0-EVO ]: mgd-init service fails due to clksyncd failure. PR1491803

  • cmdd crashes when request system shutdown reboot disk1 command is exceuted.PR1492955

  • QFX5220-32CD and QFX5220-128C: evo-pfemand core file is seen if loopback filter is applied with input-list and after switch is rebooted. PR1497909

  • On a QFX5220 :: show firewall cli shows error error: communication failure with /re0/evo-pfemand/ when unique filter is applied over all physical interfaces. PR1499294

  • ACL does not get applied to ingress when single filter is applied to both input and output direction of intf. PR1501015

User Interface and Configuration

  • CMDD application restart issue: command-handler subsystem does not respond. PR1434409

  • The following error is observed The command-handler subsystem is not responding to management requests while upgrading from Junos OS Evolved 19.3R2.1-EVO to Junos OS Evolved 19.4R2.3. PR1499018