Hardware

Table 1 summarizes the features added to the ACX7100-48L in Junos OS Evolved Release 21.2R1.

Table 1: Feature Support Added to the ACX7100-48L
Feature	Description
DHCP	Support for DHCP server and DHCP relay configuration for IPv4 and IPv6 services. [See DHCP Overview.]
Ethernet OAM	Support for Operations, Administration, and Maintenance (OAM). You can configure connectivity fault management (CFM) and the ITU-T Y.1731 standard for Ethernet service OAM. The ACX7100-48L also supports the following link-fault management (LFM) features: Discovery Link monitoring Remote fault detection [See ITU-T Y.1731 Ethernet Service OAM Overview.]
High availability	Support for the following BFD features: BFD for IPv4 and IPv6 routes Single-hop BFD in inline mode with an interval range of 10 milliseconds to 1 second Single-hop BFD in distributed mode with an interval of 1 second or more Single-hop BFD in centralized mode with a minimum interval of 1 second to detect IRB failures Multihop BFD with an interval of 1 second or more Micro-BFD for LAG in centralized or distributed mode with an interval of 1 second or more [See Bidirectional Forwarding Detection (BFD).]
Layer 2 VPN	Support for VPLS. The ACX7100-48L routers support a single VLAN for each `virtual switch` routing instance type. Junos OS Evolved does not support the `family vpls` option. To configure VPLS on the ACX7100-48L routers, configure the `instance-type virtual switch` statement at the `[edit routing-instances routing instance]` hierarchy level. If you configure normalized VLANs, either by not configuring VLAN IDs or by including the `vlan-id none` statement, then you must also include the `service-type single` statement at the `[edit routing-instances routing-instance protocol vpls]` hierarchy level. [See Introduction to Configuring VPLS.]
Layer 3 VPN	Support for the following Layer 3 VPN features: IP-VPN services: Virtual routing and forwarding (VRF) and virtual-router instance type All control plane configuration options Per-prefix and per-table label signaling Layer 3 VPN support with ECMP BGP policies support for different Layer 3 VPN use cases such as full mesh VPN, hub-spoke VPN, management VPN, and leaking routes Layer 3 VPN with `vrf-table-label` mode Layer 3 VPN with `chained-composite-next-hop` mode Layer 3 VPN ping using `ping mpls l3vpn prefix prefix-name l3vpn-name` command Note: The ping command works only with the `vrf-table-label` configuration. 6PE and 6VPE with PE-CE routing-static and PE-to-CE BGPv6
	Import and export of routes across non-default to non-default virtual routing and forwarding (VRF) Note: Table next hop is not supported. Inter-autonomous system (Inter-AS) options A, B, and C Note: You can deploy inter-AS option B in a hierarchical network design within a single IGP autonomous system. Provider edge-to-customer edge (PE-to-CE) route using static route and routing protocols such as eBGP, IS-IS, OSPF, and RIP Currently, we do not support virtual tunnel (VT) interface-based Layer 3 VPN. [See Layer 3 VPNs User Guide for Routing Devices.]
Layer 3 features	Support for the following Layer 3 features: Longest prefix match (LPM) Exception packet handling VLAN tagging modes Neighbor solicitation Unicast reverse path forwarding (unicast RPF) The ACX7100-48L also supports interior gateway protocols (IGPs) such as OSPF, IS-IS, RIP, and ECMP.
Network management and monitoring	Support for NETCONF event notifications. NETCONF clients can subscribe to NETCONF event notifications to receive alerts for events that might impact device operations or management activities. The events include netconf-config-change, netconf-session-start, and netconf-session-end events. [See NETCONF Event Notifications.]
MPLS	Support for the following MPLS features: IP/MPLS infrastructure feature set for the Layer 3 VPN service Basic BGP control plane features such as LDP-DOD, CSPF, single-area CSPF MPLS label stack MPLS protections: Fast reroute (FRR)/ Make-before-break (MBB) Link protection Node protection Label-switching router (LSR) Shared Risk Link Group (SRLG) for MPLS RSVP label-switched path (LSP) over IPv4 including refresh reduction LDP LSP over IPv4 RSVP 1:1
	RSVP-Traffic Engineering (RSVP- TE) LDP over RSVP Inter-autonomous Systems LSP intra-area LSP [See MPLS Overview.]
Multicast	Support for IPv4 multicast for Layer 3. You can configure IGMP snooping with IGMPv2 and IGMPv3, which includes support for the following: Auto-rendezvous point (auto-RP) Anycast RP IGMP filter IGMP querier Protocol Independent Multicast source-specific multicast (PIM SSM) PIM sparse mode (PIM SM) [See IGMP Snooping Overview.] Note: In this Junos OS Evolved release, the ACX7100-48L doesn't support IPv6 multicast and Layer3 multicast protocols (such as IGMP, MLD, or PIM) over IPv4 and IPv6 IRB interfaces.
Services applications	Support for RFC 5357, Two-Way Active Measurement Protocol (TWAMP) monitoring service. You can configure the TWAMP monitoring service, which sends out probes to measure network performance. You often use TWAMP to check compliance with service-level agreements. In Junos OS Evolved, you configure TWAMP at the `[edit services monitoring twamp]` hierarchy level. The support for this service is limited to the following: IPv4 traffic only for control sessions and test sessions Probe statistics and history Control and test session status Test session probe generation and reception as well as reflection Timestamps set by the Routing Engine or the Packet Forwarding Engine Error reporting through system log messages only Unauthenticated mode only [See Understanding Two-Way Active Measurement Protocol on Routers.]
Timing and synchronization	Support for enhanced Ethernet equipment clock (eEEC). Enhanced EEC enables new clocks to operate with different quality levels defined in the Synchronous Ethernet chain. To enable enhanced EEC on your router, configure the `enable-extended-ql-tlv` statement at the `[edit chassis synchronization]` hierarchy level. The ACX7100-48L supports the following new clock quality levels for enhanced EEC: Enhanced primary reference time clock (ePRTC) Primary reference time clock (PRTC) Enhanced primary reference clock (ePRC) Enhanced Ethernet equipment clock (eEEC) [See enable-extended-ql-tlv, Ethernet Synchronization Message Channel Overview, and synchronization (ACX Series).]
Timing and synchronization	Support for frequency synchronization using the Synchronous Ethernet protocol in accordance with the ITU-T G.8262 and G.8262.1 standards. [See Synchronous Ethernet Overview.]

New ACX7100-32C Router (ACX Series)—In Junos OS Evolved Release 21.2R1, we introduce the ACX7100-32C, a fixed-configuration and high-performance router with deep buffer capabilities. With high port density and MACsec-ready ports, the ACX7100-32C routers are ideal for secure and high-end service aggregation, large enterprises, and top-of-rack, spine-and-leaf data center applications.

The ACX7100-32C provides several capabilities that include a comprehensive set of features, advanced programmability, and seamless integration with emerging distributed edge compute architectures and spine-and-leaf data center applications.

With a 1-U, energy-efficient, and fixed-configuration design, the ACX7100-32C has a 4.8-Tbps-forwarding-capacity ASIC and the following port configurations:

Thirty-two QSFP28 ports (ports 0 through 31) that operate at 100-Gbps or 40-Gbps speeds.
Four double-density QSFP56-DD ports (ports 32 through 35) that operate at a default speed of 400-Gbps.

We ship the ACX7100-32C routers with redundant power supply modules (PSMs). You can order router models with either AC or DC PSMs. The router supports only front-to-back airflow.

To install the ACX7100-32C router hardware and perform initial software configuration, routine maintenance, and troubleshooting, see the ACX7100-32C Router Hardware Guide.

Table 2 summarizes the ACX7100-32C features supported in Junos OS Evolved Release 21.2R1.

Table 2: Feature Support on the ACX7100-32C
Feature	Description
Chassis	Support for a built-in Routing Engine. The ACX7100-32C doesn't support pluggable or redundant Routing Engines. As a result, you cannot use GRES on this router. [See show chassis hardware.]
	Support for environmental monitoring and field-replaceable unit (FRU) management. [See show chassis hardware.]
	Interface support. The ACX7100-32C has 32 built-in QSFP28 ports that can operate at a default speed of 100 Gbps and 4 built-in QSFP56-DD ports that can operate at a default speed of 400 Gbps. You can channelize the QSFP28 ports into: Four 25GbE interfaces Four 10GbE interfaces Two 50GbE interfaces You can channelize the QSFP56-DD ports into: Four 100GbE interfaces Two 100GbE interfaces Eight 50GbE interfaces Two 50GbE interfaces Eight 25GbE interfaces Four 10GbE interfaces See [Port Speed on ACX7100-32C Router Overview.]
Class of service (CoS)	Support for classification and rewrite rules of all types (Inet-Prec, DSCP, DSCP-v6, IEEE-802.1p, and IEEE-802.1ad) at the logical interface level. [See Classifiers and Rewrite Rules at the Global, Physical, and Logical Interface Levels Overview.]
Class of service (CoS)	Support for port shaping and scheduling with eight virtual output queues (VoQs) per port and two scheduling priority levels (strict-high and low). This release also supports for multiple strict-high priority queues (round-robin scheduling), multiple low-priority queues (weighted fair queuing, or WFQ, scheduling), and default deep buffers. [See Schedulers Overview for ACX Series Routers and Shared and Dedicated Buffer Memory Pools on ACX Series Routers.]
DHCP	Support for DHCP server and DHCP relay configuration for IPv4 and IPv6 services. [See DHCP Overview.]
Ethernet OAM	Support for Operations, Administration, and Maintenance (OAM). You can configure connectivity fault management (CFM), BFD, the ITU-T Y.1731 standard for Ethernet service OAM, and the following link-fault management (LFM) features: Discovery Link monitoring Remote fault detection [See ITU-T Y.1731 Ethernet Service OAM Overview.]
Firewall filters	Support for firewall filters and policers. You can configure firewall filters with packet match conditions for the `bridge domain`, `IPv4`, and `IPv6` families. This release introduces support for the following match conditions in the egress direction for IPv4 and IPV6 traffic: For IPv4: ttl tcp-flags For IPv6: destination-ip next-header traffic-class hop-limit L4 ports icmp-type/code tcp-flags The ACX71000-32C also supports firewall filter actions that include `count`, `discard`, `log`, `syslog`, and `policer`. [See Overview of Firewall Filter Match Conditions and Actions on ACX Series Routers.]
High availability	Support for the following BFD features: BFD for IPv4 and IPv6 routes Single-hop BFD in inline mode with an interval range of 10 milliseconds to 1 second Single-hop BFD in distributed mode with an interval of 1 second or more Single-hop BFD in centralized mode with a minimum interval of 1 second to detect IRB failures Multihop BFD with an interval of 1 second or more Micro-BFD for LAG in centralized or distributed mode with an interval of 1 second or more [See Bidirectional Forwarding Detection (BFD).]
Layer 2 features	Support for the following advanced Layer2 features: Unqualified bridging support Bridge domain without a `vlan-id` `number` statement Bridge domain with the `vlan-id` value set to none Bridge domain with a single VLAN ID Single-learning domain MAC limiting Ethernet service types: E-Line with AC interface types port, VLAN, Q-in-Q, VLAN list, and VLAN maps E-Line E-LAN E-Access E-Transit LLDP LACP IRB interface Link aggregation group (LAG) support with the following hashing algorithms: For family `multiservice`, destination and source MAC addresses For family `inet`, Layer 3 and Layer 4 For family `inet6`, Layer 3 destination and source addresses For family `inet6`, Layer 4 destination and source ports Encapsulation types: `extended-vlan-bridge` `vlan-bridge` Q-in-Q tunneling [See Understanding Layer 2 Bridge Domains and Q-in-Q Tunneling on ACX Series.]
Layer 2 VPN	Support for VPLS. The ACX7100-32C routers support a single VLAN for each `virtual switch` routing instance type. Junos OS Evolved does not support the `family vpls` option. To configure VPLS on the ACX7100-32C routers, configure the `instance-type virtual switch` statement at the `[edit routing-instances routing instance]` hierarchy level. [See Introduction to Configuring VPLS.]
Layer 3 VPN	Support for the following Layer 3 VPN features: IP-VPN services: Virtual routing and forwarding (VRF) and virtual-router instance type All control plane configuration options Per-prefix and per-table label signaling Layer 3 VPN support with ECMP BGP policies support for different Layer 3 VPN use cases such as full mesh VPN, hub-spoke VPN, management VPN, and leaking routes Layer 3 VPN with `vrf-table-label` mode Layer 3 VPN with `chained-composite-next-hop` mode Layer 3 VPN ping using `ping mpls l3vpn prefix prefix-name l3vpn-name` command. Note: The ping command works only with the `vrf-table-label` configuration. Import and export of routes across non-default to non-default virtual routing and forwarding (VRF) Note: Table next hop is not supported. Inter-autonomous system (Inter-AS) options A, B, and C. Note: You can deploy inter-AS option B in a hierarchical network design within a single IGP autonomous system. Provider edge-to-customer edge (PE-to-CE) route using static route and routing protocols such as eBGP, IS-IS, OSPF, and RIP 6PE and 6VPE with PE-CE routing-static and PE-to-CE BGPv6 Currently, we do not support virtual tunnel (VT) interface-based Layer 3 VPN. [See Layer 3 VPNs User Guide for Routing Devices.]
Layer 3 features	Support for the following Layer 3 features: Longest prefix match Exception packets handling VLAN tagging modes Neighbor solicitation Unicast RPF Interface-based routing The ACX7100-32C router also supports interior gateway protocols such as OSPF, IS-IS, RIP, and ECMP. [See Configure ICMP Features, Enabling VLAN Tagging, Neighbor solicitation, Understanding Unicast RPF (Routers), OSPF Overview, IS-IS Overview, RIP User Guide, and BGP Overview.]
Layer 3 features	Support for BGP for IPv4 and IPv6. [See BGP Overview.]
MPLS	Support for the following MPLS features: IP/MPLS infrastructure feature set for the Layer 3 VPN service Basic BGP control plane features such as LDP-DOD, CSPF, single-area CSPF MPLS label stack MPLS protections: Fast reroute (FRR)/ Make-before-break (MBB) Link protection Node protection Label-switching router (LSR) Shared Risk Link Group (SRLG) for MPLS RSVP label-switched path (LSP) over IPv4 include refresh reduction LDP LSP over IPv4 RSVP 1:1 RSVP-Traffic Engineering (RSVP- TE) LDP over RSVP Inter-autonomous Systems LSP intra-area LSP [See MPLS Applications User Guide.]
Multicast	Support for IPv4 multicast for Layer 3. You can configure IGMP snooping with IGMPv2 and IGMPv3, which includes support for the following: Auto-rendezvous point (auto-RP) Anycast RP IGMP filter IGMP querier Protocol Independent Multicast source-specific multicast (PIM SSM) PIM sparse mode (PIM SM) [See IGMP Snooping Overview.] Note: In this Junos OS Evolved release, the ACX7100-32C doesn't support IPv6 multicast and Layer3 multicast protocols (such as IGMP, MLD, or PIM) over IPv4 and IPv6 IRB interfaces.
Multicast	Support for Layer 2 multicast-related features, including support for IGMP and Multicast Listener Discovery (MLD) snooping. You can configure IGMP snooping with IGMPv1, IGMPv2, and IGMPv3, which includes support for the following: IGMP snooping in a bridge domain IGMP snooping with IRB interface configured in a bridge domain MLD snooping in a bridge domain MLD snooping with IRB interface configured in a bridge domain [See IGMP Snooping Overview.]
Network management and monitoring	Support for NETCONF event notifications. NETCONF clients can subscribe to NETCONF event notifications to receive alerts for events that might impact device operations or management activities. The events include netconf-config-change, netconf-session-start, and netconf-session-end events. [See NETCONF Event Notifications.]
Resiliency	Support for platform resiliency to handle failures and faults related to components such as CPU, fan trays, temperature sensors, power supply units, FPGA, and optics. Fault handling includes detecting and logging the error, raising alarms, sending SNMP traps, providing indication about the error through LEDs, self-healing, and taking components out of service. [See show system errors active.]
Routing policy	Unicast reverse path forwarding (unicast RPF) support for IPv4 and IPv6. You can reduce the impact of denial-of-service (DoS) attacks for IPv4 and IPv6 interfaces by configuring unicast RPF. You can use unicast RPF to determine the source of attacks and reject packets from unexpected source addresses on interfaces. However, we do not support unicast RPF checking for: Transit packets exiting a tunnel source interface Asymmetrical routing [See Understanding Unicast RPF (Routers).]
Services applications	Support for RFC 5357, Two-Way Active Measurement Protocol (TWAMP) monitoring service. You can configure the TWAMP monitoring service, which sends out probes to measure network performance. You often use TWAMP to check compliance with service-level agreements. In Junos OS Evolved, you configure TWAMP at the `[edit services monitoring twamp]` hierarchy level. The support for this service is limited to the following: IPv4 traffic only for control sessions and test sessions Probe statistics and history Control and test session status Test session probe generation and reception, as well as reflection Timestamps set by the Routing Engine or the Packet Forwarding Engine Error reporting through system log messages only Unauthenticated mode only [See Understanding Two-Way Active Measurement Protocol on Routers.]
Services applications	Support for RFC 2544-based benchmarking tests. We support only the Layer 3 reflector function for these tests. The support is further restricted to: `family inet` only IPv4 source and destination addresses Software-based reflection, with a maximum frame rate for the traffic flows of 1000 kbps You use the RFC 2544 benchmarking tests to measure and demonstrate the service-level agreement (SLA) parameters before service activation. The tests measure throughput, latency, frame loss rate, and number of back-to-back frames. You can configure these tests at the `[edit services monitoring rfc2544]` hierarchy level. [See RFC 2544-Based Benchmarking Tests Overview.]
Software installation and upgrade	Support for either WAN interfaces or management interfaces to automatically download and install the appropriate software and the configuration file on your device during the ZTP bootstrap process. [See Zero Touch Provisioning.]
Software installation and upgrade	Support for secure-boot implementation based on the UEFI 2.4 standard. [See Software Installation and Upgrade Guide.]
Timing and synchronization	Support for enhanced Ethernet equipment clock (eEEC). Enhanced EEC enables new clocks to operate with different quality levels defined in the Synchronous Ethernet chain. To enable enhanced EEC on your router, configure the `enable-extended-ql-tlv` statement at the `[edit chassis synchronization]` hierarchy level. The ACX7100-32C supports the following new clock quality levels for enhanced EEC: Enhanced primary reference time clock (ePRTC) Primary reference time clock (PRTC) Enhanced primary reference clock (ePRC) Enhanced Ethernet equipment clock (eEEC) [See enable-extended-ql-tlv, Ethernet Synchronization Message Channel Overview, and synchronization (ACX Series).]
	Support for frequency synchronization using Synchronous Ethernet. [See Synchronous Ethernet Overview.]
	Support for Synchronous Ethernet with Precision Time Protocol (PTP) Transparent Clock. The transparent clock measures the residence time of PTP packets as the packets pass through the router. The network load and device architecture might result in queuing or buffering delays. These delays are the main source of packet delay variation in the router. Transparent clock adds the residence time into the correction field of the PTP packet. The client or boundary clocks can determine this resident time while they receive the PTP packet from the upstream transparent clock router. The client clock can estimate and remove these delays from the offset computation and reduce the packet’s jitter effects. In syntonized transparent clock, the transparent clock requires physical layer frequency based on the ITU-T G.8262/.1 standard. Synchronous Ethernet configuration is mandatory for enabling syntonized transparent clock. Use the `show protocols ptp` and `show ptp global-information` commands to verify the PTP transparent clock configuration status. To enable PTP transparent clock on your router, configure `syntonized-e2e-transparent` statement at the `[edit protocols ptp]` hierarchy level. See [Understanding Transparent Clocks in Precision Time Protocol and show ptp global-information.]

To view the hardware compatibility matrix for optical interfaces, transceivers, and DACs supported on ACX7100-32C, see the Hardware Compatibility Tool.

New QFX5700 Switch (QFX Series)—In Junos OS Evolved Release 21.2R1, we introduce QFX5700 switch as the first modular chassis from Juniper that uses Broadcom’s Trident 4 chipset to support and deliver a diverse set of use cases. Featuring a 5-U form factor, QFX5700 supports very large, dense, and fast 400GbE IP fabrics with a fully redundant 12.8Tb capacity that benefits large public cloud providers. It also offers 10/40/100/400GE high port density and delivers high-performance, scale, and flexibility to support IP services and functions for service provider, web, and enterprise networks.

Note:

Upgrade to Junos OS Evolved Release 21.2R2 for the latest software features and bug fixes.

Table 3 summarizes the QFX5700 features supported for Junos OS Evolved Release 21.2R1.

Table 3: Features Supported by the QFX5700 Switches
Class of service	Support for class of service (CoS) configuration with these limitations: 802.3X Ethernet PAUSE is not supported. CoS flexible hierarchical scheduling, also known as enhanced transmission selection (ETS), is not supported. Neither MPLS EXP ingress packet classification nor egress rewrite rules are supported. Classifiers and rewrite rules are applied to logical interfaces instead of physical interfaces. [See CoS Support on QFX Series Switches, EX4600 Line of Switches, and QFabric Systems.] CoS support on EVPN-Virtual Extensivle LAN (VXLAN). Support is provided for defining classifiers and rewrite rules on leaf (initiation and terminations) and spine nodes for EXPN VXLANs. Support is also provided for defining schedulers, interpolated drop profiles, explicit congestion notification (ECN), and priority based flow control (PFC). [See CoS Support on EVPN VXLANs.]
DHCP	Support for DHCPv4 and DHCPv6 stateless relay over Layer 3 (L3) interfaces. Support includes: Option-82 for DHCPv4. Option-18 and Option-37 for DHCPv6. Virtual router aware DHCPv4/v6 stateless relay. Note: Support does not include IRB interfaces. [See DHCP Relay Agent.]
EVPN	EVPN-VXLAN support for unicast traffic using media access control (MAC) virtual routing and forwarding (VRF) routing instances. The switch can be a leaf device or a spine device in an edge-routed bridging or centrally routed bridging overlay design. You can configure multiple EVPN instances (EVIs) of type `mac-vrf`. Each EVI can support a different EVPN service type (`vlan-based`, `vlan-aware`, or `vlan-bundle`). The switch creates and uses one virtual tunnel endpoint (VTEP) logical interface per remote provider edge (PE) device by default, regardless of the number of routing instances. This implementation improves VXLAN VTEP scaling with multiple routing instances. EVPN-VXLAN support on this switch includes: External BGP (EBGP) and internal BGP (IBGP) overlays. Single-homing and all-active multihoming. Layer 2 and Layer 3 unicast for IPv4 and IPv6 with ARP suppression. Proxy ARP and ARP suppression for Layer 2 and Layer 3 IRB traffic. Proxy Neighbor Discovery Protocol (NDP) and NDP suppression for Layer 2 and Layer 3 IRB traffic. Service provider style configuration with Q-in-Q support, supported for Layer 2 gateways only and only with MAC VRF `vlan-bundle` service type. Storm control. MAC mobility, MAC limiting, MAC move limiting, and duplicate MAC detection. Core isolation. Proxy re-advertisement of EVPN Type 2 MAC+IP routes by all provider edge devices on the same Ethernet segment identifier (ESI). Virtual machine traffic optimization (VMTO). OSPF and BGP routing protocols on IRB interfaces. [See EVPN User Guide.] Support for sFlow monitoring technology in EVPN-VXLAN fabrics. [See Overview of sFlow Technology.] Support for port mirroring in EVPN-VXLAN fabrics. [See How to Configure Remote Port Mirroring for EVPN-VXLAN Fabrics.] Support for EVPN Type-5 routes in EVPN-VXLAN fabrics. [See Understanding EVPN Pure Type-5 Routes.] Support for EVPN-VXLAN firewall filtering and policing. [See Firewall Filter Match Conditions and Actions (QFX and EX Series Switches).]
Hardware	The QFX5700 switch supports up to 8 line cards and each line card supports 16 QSFP28 ports that operate at 100GbE speed or 4 QSFP56-DD ports that operate at 400GbE speed. The QFX5700 switch has AC or DC power supplies and front-to-back airflow. [See QFX5700 Hardware Guide.]
High availability (HA) and resiliency	Resiliency support for Routing and Control Board (RCB) includes CPU memory and dual in-line memory module. You can configure fault-handling actions such as logging the error, raising alarms, sending SNMP traps, and indicating error conditions by using LEDs. [See routing-engine (Chassis).] Resiliency support for the chassis, line card (JNP-FPC-4CD), and Forwarding Engine Board (FEB)—QFX5130-FEB—includes handling the faults related to the links between components; for example, between a line card (such as JNP-FPC16C) and the switch fabric. [See QFX Hardware Components.]
Interfaces and chassis	Support for GRE tunneling. [See Generic Routing Encapsulation.] Support for qualifying optics on the 100GbE and the 400GbE FPC line cards includes software monitoring, sensor diagnostics, FPC interfaces node level failure or restoration, events, and error logging. [See QFX Hardware Components.] Support for two new FPCs introduced for QFX5700 switches: JNP-FPC-16C: The line card contains a total of 16 QSFP28 ports that support 100Gbps and 40Gbps speeds. You can channelize the ports operating at: 100Gbps to four 25Gbps channels. 40Gbps to four 10Gbps channels. JNP-FPC-4CD: The line card contains a total of four QSFP56-DD ports that support 400Gbps, 100Gbps, and 40Gbps speeds. You can channelize the ports operating at: 400Gbps to four 100Gbps channels. 100Gbps to four 25Gbps channels. 40Gbps to four 10Gbps channels. [See Port Settings.] Support for one or two RCBs. [See QFX5700 Routing and Control Board.] Support for the FEB with field-replaceable unit (FRU) management that includes: Health monitoring Fault handling Systems alarms Notification by LEDs Power budgeting Cooling Management [See request chassis feb.]
IP tunneling	Support for IPv4 and IPv6 unicast IP-over-IP (IPv4) filter based decapsulation. [See Overview of Next-Hop-Based Dynamic Tunneling Using IP-Over-IP Encapsulation.]
Juniper extension toolkit	Support for Firewall Service and Interfaces Service JET APIs. [See Juniper Engineering Network website.]
L2 features	Support for L2 control protocols: xSTP, LACP, and LLDP. [See Ethernet Switching User Guide.] Support for these L2 features: Enhanced L2 Software (ELS) 802.1D 802.1Q VLAN tagging 802.1Q VLAN trunking 802.1p Routed VLAN interface (RVI) MAC address aging configuration Static MAC address assignment for an interface Disable MAC learning [See Ethernet Switching User Guide.]
MPLS	RSVP-Traffic Engineering (TE) supports preempting secondary label-switched paths (LSPs) that are signaled but not active. [See RSVP Overview.]
Multicast	Support for these multicast forwarding features: IPv4 and IPv6 multicast IGMP Multicast Listener Discovery (MLD) protocol Protocol Independent Multicast source-specific multicast (PIM SSM) Protocol Independent Multicast sparse mode (PIM SM) Note: Support does not extend to features beyond those listed above. In this release, IGMP snooping, MLD snooping, multicast virtual private network (MVPN) Multicast, PIM multicast-only fast reroute (MoFRR), PIM first hop router (FHR), rendezvous point (RP), and last hop router (LHR) are not supported. In addition, the IRB interface is not supported as either a source or as a receiver. Make-before-break (MBB) is not supported for existing L3 aggregated Ethernet (AE) or LAG receivers (member addition/deletions or up/downs). [See Multicast Overview.] Support for these IGMP snooping with IRB features: IGMP V1, V2, and V3 with plain L2 snooping with IRB (only if device acts as an LHR) Proxy mode Enterprise-style CLI only Any-source multicast (ASM) and source-specific multicast (SSM) modes Limitations include: IGMP group-specific queries received on a multicast-router interface are forwarded to all other interfaces in the VLAN. MBB on existing L2aggregated Ethernet or LAG interfaces, including for member additions, deletions, and link up or down events. All unregistered IPv4 and IPv6 multicast packets are forwarded to the multicast router interfaces in the VLAN, even if an interface is configured as a multicast router interface only for IGMP snooping. Neither MLD snooping, PIM snooping, snooping with VPLS, EVPN-VXLAN, nor EVPN-MPLS is supported. [See IGMP Snooping Overview and Integrated Routing and Bridging.]
Network management and monitoring	Support for sFlow monitoring technology. [See Understanding How to Use sFlow Technology for Network Monitoring.] Support for port mirroring. [See Understanding Port Mirroring and Analyzers.]
Protection against distributed denial of service (DDoS) attacks	Support for DDoS protection, which is enabled by default. [See Control Plane Distributed Denial-of-Service (DDoS) Protection Overview.]
Routing policy and firewall filters	L3 support for firewall filters and policers. [See Firewall Filter Match Conditions and Actions (QFX and EX Series Switches).]
Routing protocols	Support for Unified Forwarding Table (UFT) and L3 sub-interface features—The QFX5700 line of switches supports these UFT and L3 sub-interface features: The UFT feature enables you to allocate forwarding table resources to optimize the memory available for different address types based on the needs of your network. The UFT stores both the L2 and L3 entries that enable you to set default sizes for different entries. These applications share UFT search banks: L2 MAC addresses. IPv4 and IPv6 host routes. L2 and L3 multicast routes. IPv4 and IPv6 longest prefix match (LPM) or prefix entries that are supported in UFT through algorithmic longest prefix match (ALPM). [See forwarding-options.] Support for redistribution of IPv4 routes with IPv6 next hop into BGP. [See Understanding Redistribution of IPv4 Routes with IPv6 Next Hop into BGP.]
Software installation and upgrade	Support for zero-touch provisioning (ZTP) on the management and the WAN interfaces. [See Zero Touch Provisioning Overview.] Support for secure boot—The implementation is based on the UEFI 2.4 standard. [See Junos OS Software Installation and Upgrade Guide.]

Support for the QSFP-100G-DR and QSFP-100G-FR transceivers (QFX5220-32CD and QFX5220-128C)—Starting in Junos OS Evolved Release 21.2R1, the QFX5220-32CD and QFX5220-128C switches support the QSFP-100G-DR and QSFP-100G-FR transceivers.

[See Hardware Compatibility Tool.]