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.3R1 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.3R1 for the QFX5220.

Class of Service

  • Support for class of service (CoS) features (QFX5130-32CD)—Starting in Junos OS Evolved Release 20.3R1, QFX5130-32CD switches support all class of service (CoS) features except the following: 802.3X Ethernet PAUSE is not supported; CoS flexible hierarchical scheduling (ETS) is not supported; MPLS EXP ingress packet classification and egress rewrite rules are not supported; classifiers and rewrite rules are applied to logical interfaces instead of physical interfaces.

    [For a complete list of feature support, see CoS Support on QFX Series Switches, EX4600 Line of Switches, and QFabric Systems.]

Junos OS XML API and Scripting

  • Routing instance support in Python 3 applications (PTX Series and QFX Series)—Starting in Release 20.3R1, devices running Junos OS Evolved support specifying the routing instance used by a process or socket in Python 3 applications that are executed from the Linux shell. Python 3 applications can import the libpyvrf module and use the module’s functions to set the Linux VRF corresponding to the Junos OS routing instance for a specific context.

    [See How to Specify the Routing Instance in Python 3 Applications on Devices Running Junos OS Evolved.]

Junos Telemetry Interface

  • ARP and NDP table state, ON_CHANGE support for JTI (QFX5220 switches)—Junos OS Evolved Release 20.3R1 supports ON_CHANGE export of Address Resolution Protocol (ARP) and Neighbor Discovery Protocol (NDP) table states to an outside collector using Junos telemetry interface (JTI) and remote procedure call (gRPC) services. ARP and NDP periodic streaming and ON_CHANGE support is already available in Junos OS Evolved. This feature adds interface address (IPv4, IPv6) telemetry data.

    The supported resource paths (sensors) are:

    • /interfaces/interface/subinterfaces/subinterface/ipv4/neighbors/neighbor/state/ supporting leafs ip, link-layer-address. origin,

    • /interfaces/interface/subinterfaces/subinterface/ipv6/neighbors/neighbor/state/ supporting leafs ip, ink-layer-address. origin, is-router, neighbor-state, and is-publish.

    • /interfaces/interface/subinterfaces/subinterface/ipv4/addresses/address/state/ supporting leafs ip, prefix-length, and origin.

    • /interfaces/interface/subinterfaces/subinterface/ipv4/addresses/address/state/ supporting leafs ip, prefix-length, and origin.

    • /interfaces/interface/subinterfaces/subinterface/ipv4/unnumbered/state/ supporting leafs enabled, interface-ref/state/interface, interface-ref/state/subinterface,

    • /interfaces/interface/subinterfaces/subinterface/ipv4/state/ supporting leafs enabled and mtu.

    • /interfaces/interface/subinterfaces/subinterface/ipv6/addresses/address/state/ supporting leafs ip, prefix-length, origin, and status.

    • /interfaces/interface/subinterfaces/subinterface/ipv6/unnumbered/state/enabled.

    • /interfaces/interface/subinterfaces/subinterface/ipv4/unnumbered/state/ supporting leafs enabled, interface-ref/state/interface, interface-ref/state/subinterface,

    • /interfaces/interface/subinterfaces/subinterface/ipv6/unnumbered/interface-ref/state/interface/subinterface/.

    • /interfaces/interface/subinterfaces/subinterface/ipv6/state/ supporting leafs enabled and mtu.

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

Routing Protocols

  • Support for Unified Forwarding table and Layer 3 sub-interface (QFX5130-32CD)—Starting with Junos OS Evolved Release 20.3R1, the following Unified Forwarding table and Layer 3 sub-interface features are supported:

    • Unified Forwarding Table— Unified Forwarding Table stores both Layer 2 and Layer 3 entries that allow you to set default sizes for different entries. The following applications share Unified Forwarding Table search banks:

      • Layer 2 MAC addresses

      • IPv4 and IPv6 host routes

      • Layer 2 and Layer 3 multicast routes

      • IPv4 and IPv6 LPM or prefix entries that are supported in Unified Forwarding Table through Algorithmic Longest Prefix Match (ALPM)

      The following Unified Forwarding Table Profiles are supported:

      Profile

      Layer 2 MAC

      Layer 3 Host Unicast

      Layer 3 Host Mulitcast

      IPv4 and IPv6 LPM

      lpm-profile

      32,000

      32,000

      16,000

      IPv4 720,000 and IPv6 550,000

      host-profile

      160,000

      160,000

      32,000

      IPv4 65,000 and IPv6 50,000

      host-acl-profile

      160,000

      160,000

      32,000

      IPv4 65,000 and IPv6 22,000

      default-profile (same as lpm-profile)

      32,000

      32,000

      16,000

      IPv4 720,000 and IPv6 550,000

      Note

      The evo-pfemand Packet Forwarding Engine application restarts when one of the Unified Forwarding Table profile is configured. The default profile is active when no configuration is added. The configuration guidelines to delete the routes or MACs before changing the Unified Forwarding Table configuration, might not install all the entries from the previous Unified Forwarding Table profile due to the table size.

    • Layer 3 sub-interfaces— You can configure Layer 3 sub-interfaces to route traffic between the VLANs. The following interfaces scales are supported:

      • Layer 2 VLANs or IRB interfaces: 1 to 4095

      • Layer 3 sub-interfaces VLAN-token: 1 to 4095

      Note

      The maximum VLAN scale is 4095 due to which the interfaces and VLANs share the same token space.

Security

  • Secure boot support (QFX5130-32CD)—Starting in Junos OS Evolved release 20.3R1, the QFX5130-32CD router supports secure boot. It works by safeguarding the BIOS itself from tampering or modification and then maintaining that protection throughout the boot process.

    [See Software Installation and Upgrade Overview.]

Software Licensing

  • Juniper Agile Licensing (QFX5220-32CD, QFX5220-128C, PTX10003-80C, and PTX10003-160C) —Starting in Junos OS Evolved Release 20.3R1, Juniper is moving towards licensed based software features. Juniper Agile Licensing will be used to support this enforcement on QFX5220-32CD, QFX5220-128C, PTX10003-80C, and PTX10003-160C devices.

    Juniper Agile Licensing provides simplified and centralized license administration and deployment. You can install and manage licenses for hardware and software features using Juniper Agile Licensing.

    You need new license keys to use the features on QFX5220-32CD, QFX5220-128C, PTX10003-80C, and PTX10003-160C devices. Contact Customer Care for exchanging license keys releases earlier than Junos OS Evolved Release 20.3R1.

    Table 3 describes the licensing support on the QFX5220-32CD and QFX5220-128C devices.

    Table 5: Licensed Features on QFX5220-32CD and QFX5220-128C Device

    QFX Switch License Model

    Detailed Features

    Standard license for integrated SKUs (standard hardware and software platform)

    Filters (Layer 2 and Layer 3), Layer 2 (xSTP, 802.1Q, LAG), Layer 3 (static), QoS (Layer 2 and Layer 3), and SNMP.

    Advanced license for integrated and advanced SKUs

    Advanced 1: BGP, FBF, GRE, IS-IS, JTI, MC-LAG, OSPF, sFlow, VRF and VRRP.

    Advanced 2: Includes Advanced 1 features + CFM, Layer 2 and Layer 3 multicast, OAM, Packet Timestamping, PTP, and Q-in-Q.

    Premium license for integrated and premium SKUs

    Includes Advanced 2 features + EVPN-MPLS, MPLS, Layer 2 circuit, Layer 3 VPN, LDP, RSVP, Segment routing, and SR-TE.

    Table 4 describes the licensing support for the PTX10003-80C and PTX10003-160C devices.

    Table 6: Licensed Features on PTX10003-80C and PTX10003-160C

    License Model

    Detailed Features for Fabric Management

    Scale

    Security License

    Standard

    Filters (Layer 2 and Layer 3), Layer 2 (xSTP, 802.1Q, LAG), Layer 3 (static), quality of service or QoS (Layer 2 and Layer 3), and SNMP

    64K FIB

    The PTX10003 and PTX10008 router supports the MACsec feature, but you must purchase a license separately to use the feature.

    Advanced

    Advanced 1

    BGP, FBF, GRE, IS-IS, Junos telemetry interface (JTI), OSPF, sFlow, VRF, and VRRP

    256K FIB, 3M RIB, and 1K VR

    Advanced 2

    Advanced 1 features, CFM, EVPN-VXLAN, Multicast, OAM, PTP, and Q-in-Q

    256K FIB, 3M RIB, and 1K VRs/VRF (VXLAN)

    Premium

    Premium 1

    Advanced 2 features, EVPN-MPLS, IPFIX, Layer 2 circuit, Layer 3 VPN, LDP, RSVP, SR, and SR-TE

    2M FIB, 6M RIB, 1K VRs/VRF (VXLAN), 32 VRF (MPLS Layer 3 VPN), and 32K LSP

    Premium 2

    Premium 1 features and fine-grained QoS

    2M to 4M FIB, 60M to 80M RIB, 1K+ VRs/VRF (VXLAN), 32+ VRF (MPLS Layer 3 VPN), and 32K+ LSP

    * Scaling is based on the device capacity.

    [See Supported Features on QFX5220-32CD and QFX5220-128C device, Supported Features on PTX10003-80C and PTX10003-160C device, Juniper Agile Licensing Guide, and Configuring Licenses in Junos OS.]

What's Changed

Learn about what changed in Junos OS Evolved Release 20.3R1 for the QFX5220.

Junos OS XML API and Scripting

  • Changes to Junos XML RPC request tag names (PTX Series, QFX Series)—We've updated the Junos XML request tag name for some operational RPCs to ensure consistency across the Junos XML API. Devices running Junos OS still accept the old request tag names, but we recommend that you use the new names going forward. The changes include::

    • Most, but not all, request tag names that start with show replace show with get in the name.

    • Uppercase characters are converted to lowercase.

    [See Junos XML API Explorer - Operational Tags.]

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.

System Management

  • Due to a hardware limitation, ICMP type and ICMP code matches are not supported for egress ACLs. The complete filter does not work even if a single term has an ICMP type or ICMP code match. PR1503168

User Interface and Configuration

  • For large YANG files, augmentation might not work. PR1416972

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.

Routing Protocols

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

System Management

  • When a 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

  • When changing a physical interface from a VLAN ID list to multiple single VLAN IDs or VLAN ID lists that fall within the original VLAN range, we might see one or more of the new physical interfaces not notified. For example, in the current commit we have the following configuration: set interfaces ae100 unit 1 vlan-id-list 1-100. In the next commit, if we run the set interfaces ae100 unit 1 vlan-id 1 set interfaces ae100 unit 2 vlan-id 2 command, we might see that one of the two physical interfaces is not notified. PR1504374

  • Not all the applications in Junos OS Evolved are allowed to listen to rt updates due to scale considerations. Mirrord does not get rt updates and hence analyzer or port-mirror instance state is always seen as UP in ERSPAN case irrespective of whether it is reachable or not. PR1527505

  • fsck gets automatically run but is not guaranteed to recover disk corruption after an abrupt power cycle. Secondary disk or partition and snapshot functionality is available to help recover from such issues. PR1533232

Resolved Issues

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

General Routing

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

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

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

  • 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

Infrastructure

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