Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?



  • We haven't introduced new QFX Series hardware in Junos OS Evolved 21.1R1. Use the following table to learn about some of the new features supported on the QFX5130-32CD switch.

    Table 1 summarizes the features added to the QFX5130-32CD in Junos OS Evolved Release 21.1R1

    Table 1: Feature Support Added to the QFX5130-32CD Switches



    Class of service (CoS)

    • Support for priority-based flow control (PFC) of untagged traffic at Layer 3 using DiffServ Services Code Points (DSCPs). This enables lossless traffic across Layer 3 routers that connect Layer 2 subnets. DSCP-based PFC is required to support Remote Direct Memory Access over Converged Ethernet version 2 (RoCEv2).

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

    Forwarding options

    • Support for storm control, which enables the switch to:

      • Monitor traffic levels.
      • Drop broadcast, multicast, and unknown unicast (BUM) packets before they can cause a traffic storm.

      [See Understanding Storm Control.]

    Layer 2 features

    • Support for Q-in-Q tunneling with a service-provider-style configuration in addition to the enterprise style that is already supported. You can enable the configuration for a physical interface using the set encapsulation flexible-ethernet-services command. Q-in-Q tunneling with service-provider-style configuration has these restrictions:
      • Untagged traffic is supported only if you use the native-vlan-id command for the physical interface. Untagged traffic will egress the network-to-network interface (NNI) or service VLAN interface as a single-tagged S-VLAN.
    • Insertion of native-vlan-id as the inner tag is not supported. The input-native-vlan-push configuration command is not supported.
    • Swap-push/pop-swap operations on single-tagged interfaces and swap-swap operations on double-tagged interfaces are not supported.
    • Multiple user-to-network interfaces (UNIs, or C-VLAN interfaces) with different VLAN IDs or with different Q-in-Q operations on the same bridge-domain are not recommended. C-VLAN traffic on one logical interface might leak into another.
    • Swap operation with the inner-vlan-id configuration command on the UNI is not supported.
    • Custom Tag Protocol Identifier (TPID) configuration and translation is not supported.
    • IRB logical interfaces and C-VLAN (UNI) logical interfaces cannot coexist on the same VLAN.
    • The vlan-id-list configuration is supported only on interfaces with valid I/O maps.
    • [See Flexible Ethernet Services Encapsulation and Configuring Q-in-Q Tunneling.]

    Timing and synchronization