Hardware

Chassis

• QFX5130-48C is a high-density 100GbE Ethernet/IP switch based on a single chip that offers 8-Tbps forwarding capacity​.

• Support for the next-generation, high-density, and cost-efficient 100GbE and 400GbE optimized fixed system

  The QFX5130-48CM switch features:

  • Forty-eight SFP56-DD 100GbE ports for server connectivity

  • Eight QSFP-DD 400GbE uplink ports

  • Up to 16-Tbps (bidirectional)/2.7-bpps throughput

  • Using breakout cables, you can increase the total number of supported 100/25/10GbE ports per switch to 72.

• To view the hardware compatibility matrix for optical interfaces, transceivers, and DACs supported , see the Hardware Compatibility Tool.

Class of service

• CoS support on EVPN VXLAN networks.

  [See CoS Support on EVPN VXLANs.]

• Support for priority-based flow control (PFC) of untagged traffic at Layer 3 using Differentiated Services Code Points (DSCP).

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

Ethernet switching and bridging

• Support for Q-in-Q tunneling with a service-provider-style configuration.

  [See Configuring Q-in-Q Tunneling.]

• LLDP support.

  [See Device Discovery Using LLDP.]

• Support for MAC move limit with EVPN-VXLAN.

  [See Understanding MAC Move Limiting.]

Forwarding options

• Support for port mirroring in EVPN-VXLAN environments.

  [See How to Configure Remote Port Mirroring for EVPN-VXLAN Fabrics.]

High availability

• VRRP support on Packet Forwarding Engine.

  [See VRRP Overview].

Interfaces

• Support for BGP flowspec.

  [See BGP.]

• Support for 48 SFP-DD and 8 QSFP-DD ports. Each switch also supports two 10GbE SFP+ ports. We support the following port configurations on each switch:

  • 48x100/50/25/10GbE SFP-DD ports

  • 8x400/200/100/40GbE QSFP-DD ports

  • 2x10GbE SFP+ ports

  [See Port Settings (Interface Guide for Switches).]

• Support for MACsec on physical interfaces on QFX5120-48CM. This platform supports MACsec in dynamic connectivity association key (CAK) mode with GCM-AES-128, GCM-AES-256, GCM-AES-XPN-128, and GCM-AES-XPN-256 encryption. MACsec is supported on physical interfaces for switch-to-host and switch-to-switch links.

  [See Configuring MACsec.]

• Each switch has 48 SFP-DD and 8 QSFP-DD ports. QFX5130-48C/ 48CM also supports two SFP+ ports with 10 GbE. It supports the following port configurations:

  • 48x100G / 50GbE / 25GbE / 10GbE on SFP-DD ports

  • 8x400G / 200GbE / 100GbE / 40GbE on QSFP-DD ports

  • 2x10GbE on SFP+ ports

  [See Port Speed on QFX5130-48C and QFX5130-48CM Switches.

Junos Telemetry Interface (JTI)

• JTI streaming support for hardware Routing Engine-based sensors. Subscribe to /components/sensor to stream hardware operational stages. Statistics include Routing Engine, power supply unit (PSU), Control Board (CB), FPC, and PIC states.

  [See Junos YANG Data Model Explorer.]

Multicast

• MLD snooping and IRB stitching support .

  [See Understanding MLD Snooping.]

• Support for multicast forwarding.

  [See Multicast Overview.]

• IGMP snooping support.

  [See PIM Overview.]

• IGMP, MLD multicast snooping, and IRB elaboration with MBB.

  [See IGMP Snooping Overview.]

  [See Understanding MLD Snooping.]

Network management and monitoring

• Support for sFlow.

  [See Overview of sFlow Technology.]

• Support for analyzers and port mirroring.

  [See Understanding Port Mirroring and Analyzers.]

• IPsec support for OSPFv2 and OSPFv3.

  [See Overview of IPsec.]

  [See Configuring OSPF Authentication.]

  [See Configuring IPsec Security Associations.]

• DHCP stateless relay MIB support.

  [See Enterprise-Specific MIBs for Junos OS Evolved.]

Protection against DDoS attacks

• Supports DDoS protection, which is enabled by default.

  [See Control Plane Distributed Denial-of-Service (DDoS) Protection Overview.] and protocols (DDoS) (ACX Series, PTX Series, and QFX Series).]

Platform and infrastructure

• Platform resiliency support for hardware components of each FRU.

  If a failure is detected on a hardware component, Junos OS Evolved:

  • Logs the message to give clear indication of failure details, including time stamp, module name, component name, and failure details.

  • Raises or clears alarms, if applicable.

  • Performs local action, such as self-healing and taking the component out of service.

Precision Time Protocol

• Transparent Clock support

  Transparent clocks improve synchronization between the timeTransmitter and timeReceiver clocks and ensure that the timeTransmitter and timeReceiver clocks are not impacted by the effects of packet delay variation.

  • With or without VLAN encapsulation

  • With PTP over IPv4

  • With PTP unicast or multicast

  • On LAG and MC-LAG

  • On all physical, IRB, and aggregated Ethernet interfaces

• IEEE 1588 PTP Ordinary Clock/Boundary Clock Enterprise and media profiles. Includes support for:

  • Enterprise profile using PTP ordinary clock and PTP boundaryclock applications

  • Enterprise profile using PTP over IPv4 multicast transport

  • SMPTE profile, AES67, and AES67+SMPTE combined profiles

  • Media profiles using PTP ordinaryclock and PTP boundary clock applications

  • Media profiles using PTP over IPv4 multicast transport

  [See PTP Profiles.]

• Support for PTP over IRB. QFX5130-48C supports Precision Time Protocol (PTP) over integrated routing and bridging (IRB) interfaces.

  PTP boundary clock (BC) applications often need multiple PTP streams to share a local IP address for broadcast media. These packets are forwarded through Layer2 (L2) switching. Unlike traditional PTP configurations on physical interfaces, no physical interface logical units (IFLs) are created for each PTP physical interface. You can achieve this configuration through integrated routing and bridging (IRB) interfaces.

  [See PTP over IRB for Broadcast Profiles.]

Routing options

• Support for Unified Forwarding Table (UFT).

  [See Understanding the Unified Forwarding Table.]

Routing protocols

• Support for redistribution of IPv4 routes with IPv6 next hop into BGP.

  [See Understanding Redistribution of IPv4 Routes with IPv6 Next Hop into BGP.]

• Support for collect ON_CHANGE BGP RIB telemetry statistics and BGP neighbor telemetry with sharding.

  [See Telemetry Sensor Explorer.]

• Support for maximum reference bandwidth increased to 4 TB for IGP protocols.

  [See reference-bandwidth (Protocols IS-IS).]

  [See reference-bandwidth (Protocols OSPF).]

• Check for AS matches in BGP policy AS paths without regular expressions.

  [See Improve the Performance of AS Path Lookup in BGP Policy.]

• Support for stripping or replacing BGP private AS.

  [See Autonomous Systems for BGP Sessions.]

• BMP local RIB monitoring support for all RIBs with sharding.

  [See BGP Monitoring Protocol].

  [See loc-rib.]

  [See rib-list.]

• Support for bootstrapping route-validation database from a local file.

  [See validation (Origin Validation for BGP).]

Routing policy and firewall filters

• Sharding support for conditional route manager.

  [See Routing Policy Match Conditions].

  [See rib-sharding.]

  [See show policy conditions.]

• Support for fast lookup of origin and neighbor autonomous systems (ASs).

  [See policy-options.]

  [See policy-statement.]

• Firewall filter support on Layer 3 interfaces.

  [See Firewall Filter Match Conditions and Actions.]

• Support for profiles to improve the firewall filter scale.

  [See Planning the Number of Firewall Filters to Create.]

• EVPN-VXLAN firewall filtering and policing.

  [See Firewall Filter Match Conditions and Actions (QFX and EX Series Switches).]

System management

• Secure boot and secure BIOS support.

  [See Secure Boot.]

• CLI-based hash and ECMP resilient hashing support.

  [See enhanced-hash-key.]

  [See ecmp-resilient-hash].

• Support for dynamic load balancing (DLB).

  [See enhanced-hash-key.]

• Support for configuring firewall filters and interfaces programmatically using JET APIs.

  [See Overview of JET APIs.]

Software installation and upgrade

• ZTP support.

  [See Zero Touch Provisioning.]

• Secure zero-touch provisioning—You can use RFC-8572-based secure zero-touch provisioning (SZTP) to bootstrap your remotely located network devices that are in a factory-default state. SZTP enables mutual authentication between the bootstrap server and the network device before the remote network device is accessed for initiating ZTP.To enable mutual authentication, you need a unique digital voucher, which is generated based on the DevID (Digital Device ID or Cryptographic Digital Identity) of the network device. The DevID is embedded inside the Trusted Platform Module (TPM) 2.0 chip on the network device. Juniper Networks issues a digital voucher to customers for each eligible network device.

  You can switch between using SZTP and ZTP on secure platforms. The default behavior on this device is ZTP. To override the default behavior of your secure device, issue the request system zeroize ztp-option secure-enable command.

  [See Secure Zero Touch Provisioning, Generate Secure ZTP Vouchers, and Switching between Secure Zero Touch Provisioning and Zero Touch Provisioning.]

Services applications

• Support for DHCPv4 and DHCPv6 stateless relay.

  [See DHCP Relay Agent.]

• Inband Flow Analyzer (IFA) 2.0 transit node support.

  [See Inband Flow Analyzer (IFA) 2.0 Probe for Real-Time Flow Monitoring.]

VPNs

• Support for EVPN Type 5 routes.

  [See Understanding EVPN Pure Type-5 Routes.]

• Support for assisted replication (AR) integrated with optimized intersubnet multicast (OISM) in an EVPN-VXLAN edge-routed bridging (ERB) fabric.

  [See Assisted Replication Multicast Optimization in EVPN Networks.]

  [See Optimized Inter-Subnet Multicast in EVPN Networks.]

• EVPN-VXLAN support with MAC-VRF routing instances.

  [See EVPN User Guide.]

• Support for EVPN-VXLAN fabric with an IPv6 underlay.

  [See EVPN-VXLAN with an IPv6 Underlay.]

  [See Example: Configure an IPv6 Underlay for Layer 2 VXLAN Gateway Leaf Devices.]

• Support for symmetric IRB with EVPN Type 2 routes.

  [See Symmetric Integrated Routing and Bridging with EVPN Type 2 Routes in EVPN-VXLAN Fabrics.]

  [See irb-symmetric-routing.]

• Support for MLDv1, MLDv2, and MLD snooping with OISM and AR in EVPN-VXLAN fabrics.

  [See Optimized Intersubnet Multicast in EVPN Networks.]

• Support for determining IRB interface state changes based on local and remote connectivity states in EVPN fabrics.

  [See Determine IRB Interface State Changes from Local and Remote Connectivity States in EVPN Fabrics.]

  [See interface-state.]

  [See network-isolation.]

• Overlay and CE-IP ping and traceroute support for EVPN-VXLAN.

  [See Understanding Overlay ping and traceroute Packet Support.]

• Support for blocking asymmetric EVPN Type 5 routes.

  [See EVPN Type 5 Route with VXLAN encapsulation for EVPN-VXLAN.]

  [See ip-prefix-routes.]

• Support for DHCP relay in EVPN-VXLAN.

  [See DHCP Relay Agent over EVPN-VXLAN.]

• Support for coexistence of EVPN Type 2 and Type 5 routes .

  [See EVPN Type 2 and Type 5 Route Coexistence with EVPN-VXLAN.]

• Support for Interconnecting EVPN-VXLAN in a data center to an EVPN-VXLAN control plane in a WAN using a gateway model.

  [See Understanding the MAC Addresses For a Default Virtual Gateway in an EVPN-VXLAN or EVPN-MPLS Overlay Network.]

• Support for OISM in an EVPN-VXLAN fabric.

  [See Optimized Inter-Subnet Multicast in EVPN Networks.]

• Support for service-provider-style interface configuration on EVPN-VXLAN Layer 3 gateways.

  [See Using a Default Layer 3 Gateway to Route Traffic in an EVPN-VXLAN Overlay Network.]

• Overlapping VLAN support in EVPN-VXLAN fabrics on edge-routed bridging (ERB) overlay leaf devices.

  [See Overlapping VLAN Support Using VLAN Translation in EVPN-VXLAN Networks.]

  [See vlan-rewrite.]

CoS

• Support for CoS features on Layer 2 and Layer 3 interfaces. Both IPv4 and IPv6 unicast routing are supported. Other supported CoS features include:

  • Classification and rewrite rules for Differentiated Services code point (DSCP) and IEEE-802.1p.

  • Port scheduling

  • Shared buffer

  • Priority-based flow control (PFC) based on IEEE-802.1p. DSCP-based PFC is required to support Remote Direct Memory Access (RDMA) over converged Ethernet version 2 (RoCEv2).

  • Weighted random early detection (WRED) and explicit congestion notification (ECN)

  • Telemetry support for CoS queue statistics exported using the sensor /junos/system/linecard/qmon-sw/ .

    [See Traffic Management User Guide (QFX Series Switches and EX4600 Switches).]

EVPN

• Support for firewall filtering and policing on an Ethernet VPN–Virtual Extensible LAN (EVPN-VXLAN) network.

  [See Firewall Filter Match Conditions and Actions (QFX and EX Series Switches).]

• Support for sFlow on an EVPN-VXLAN network.

  [See Overview of sFlow Technology.]

• Support for port mirroring and analyzers on an EVPN-VXLAN network.

  [See Port Mirroring and Analyzers.]

Forwarding and sampling

• Support for dynamic load balancing (DLB) and resilient hashing for equal-cost multipath (ECMP) routes. DLB and resilient hashing are not supported on a link aggregation group (LAG).

  [See Dynamic Load Balancing, Use of Resilient Hashing to Minimize Flow Remapping, and ecmp-resilient-hash.]

Interfaces

• QFX5230-64CD has 64 QSFP56-DD ports and two SFP+ ports. The QSFP56-DD ports support the following speeds:

  • 400 Gbps

  • 200 Gbps

  • 100 Gbps

  • 50 Gbps

  • 40 Gbps

  The QSFP ports also support the following speeds (with breakout cables):

  • 50 Gbps

  • 25 Gbps

  • 10 Gbps

  The SFP+ ports support 10-Gbps speed.

  QFX5230-64CD supports the following channelizations:

  • 1x400GbE, 4x100GbE, 2x100GbE, and 2x50GbE on QSFP-DD ports

  • 2x50GbE, 1x50GbE, and 4x25GbE on QSFP28-DD ports

  • 1x40GbE and 4x10GbE on QSFP+ ports

  [See Port Speed on QFX5230-64CD Switches.]

Layer 2 features

• Support for Layer 2 unicast forwarding and VRRP.

  [See Understanding VRRP.]

• Support for IGMP snooping, including:

  • IGMP snooping with IGMPv1, IGMPv2, and IGMPv3

  • IGMP proxy

  • IGMP querier at Layer 2

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

  • Virtual router (VRF-lite) IGMP snooping

  • IGMP snooping with integrated routing and bridging (IRB)

  [See IGMP Snooping Overview, Multicast Overview, and Integrated Routing and Bridging. ]

Layer 3 features

• Support for DHCP stateless relay on IRB interfaces and bridge domains. Support includes DHCPv4 and DHCPv6.

  [See DHCP Relay Agent.]

• Support for Layer 3 unicast forwarding and generic routing encapsulation (GRE) tunneling. We support both IPv4 and IPv6 unicast routing .

  [See Generic Routing Encapsulation (GRE).]

• Support for Layer 3 multicast forwarding includes:

  • PIM first hop router (FHR) rendezvous point (RP) functionality

  • MSDP

  • Make-before-break (MBB) support for multicast receivers on existing Layer 3 aggregated Ethernet (aex) or link aggregation group (LAG) interfaces. Support includes member addition, member deletion, link up, and link down events.

  • PIM source-specific multicast (SSM)

  • PIM sparse mode (SM)

  • PIM dense mode (DM)

  • L3 multicast forwarding on integrated routing and bridging (IRB) interfaces:

    • IPv4 and IPv6 multicast

    • IGMP v1/v2/v3

    • Multicast Listener Discovery (MLD) v1/v2

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

  [See Multicast Routing Protocols and PIM Overview.]

Network management and monitoring

• Support for sFlow.

  [See Overview of sFlow Technology.]

• Support for port mirroring and analyzers. The QFX5230-64CD switches supports a maximum of eight port mirroring sessions.

  [See Understanding Port Mirroring and Analyzers.]

• Select your product in the Hardware Compatibility Tool to view supported transceivers, optical interfaces, and DAC cables for your platform or interface module. We update the HCT and provide the first supported release information when the optic becomes available.

• We support performance monitoring for the QDD-400G-ZR optical transceiver modules. The current and historical performance monitoring metrics are accumulated into 15-minute and 1-day interval bins. You can view the metrics by using the show interfaces transport pm command and can manage optical transport link efficiently.

  See show interfaces transport pm.

Platform and infrastructure

• Platform resiliency support for hardware components of each FRU in the QFX5230-64CD switch. If a failure is detected on a hardware component, Junos OS Evolved:

  • Logs the message to give clear indication of failure details, including time stamp, module name, and component name.
  • Raises and clears alarms, if applicable.
  • Raises SNMP trap.
  • Makes the LED glow to indicate FRU fault, if an LED is present.
  • Performs local actions such as self-healing or taking the component out of service.

• Support to configure firewall filters and interfaces programmatically using the Juniper Extension Toolkit (JET) APIs.

  [See Overview of JET APIs.]

Protection against DDoS attacks

• Supports configuration and installation of policers at the Packet Forwarding Engine (PFE) level for defense from DDoS attacks. By default, DDoS protection is enabled for many protocols on the QFX5230-64CD switches.

  [See Configuring Control Plane DDoS Protection Aggregate or Individual Packet Type Policers, show ddos-protection statistics, and show ddos-protection version.]

Precision Time Protocol (PTP)

• Support for Precision Time Protocol transparent clock.

  [See PTP Transparent Clocks.]

• Support for Precision Time Protocol enterprise and media profiles.

  [See PTP Profiles.]

• Support for configuring Precision Time Protocol (PTP) over integrated routing and bridging (IRB) interfaces on AES67, SMPTE, AES67+SMPTE, and Enterprise PTP profiles.

  [See PTP over IRB for Broadcast Profiles.]

Routing policy and firewall filters

• Firewall filter support on Layer 2 and Layer 3 interfaces.

  [See Firewall Filter Match Conditions and Actions and Configuring Firewall Filters.]

Services applications

• Support for generic routing encapsulation (GRE) features:

  • GRE tunnels over Gigabit Ethernet, LAG, and VLAN

  • Tagged subinterfaces

  • Payload protocol for IPv4 and IPv6

  • Delivery protocol for IPv4

  • Multicast over GRE tunnels

  • Tunnel statistics

  • VRF with GRE

  • Time-to-live (TTL)

  [See Generic Routing Encapsulation (GRE).]

Software installation and upgrade

• Support for secure BIOS and secure boot implementation based on the UEFI 2.4 standard.

  [See Secure Boot.]

• You can dynamically detect the port speed of WAN interfaces and use this information to create ZTP client ports with the same speed. ZTP automatically cycles through the WAN ports until it receives DHCPv6 options 59 and 17 and applicable suboptions to exchange ZTP-related information between itself and the DHCP client.

  See Zero Touch Provisioning Using DHCPv6 Options.

• You can use RFC-8572-based secure zero-touch provisioning (SZTP) to bootstrap your remotely located network devices that are in a factory-default state. SZTP enables mutual authentication between the bootstrap server and the network device before the remote network device is accessed for initiating ZTP.

  To enable mutual authentication, you need a unique digital voucher, which is generated based on the DevID (Digital Device ID or Cryptographic Digital Identity) of the network device. The DevID is embedded inside the Trusted Platform Module (TPM) 2.0 chip on the network device. Juniper Networks issues a digital voucher to customers for each eligible network device.

  You can switch between using SZTP and ZTP on secure platforms. The default behavior on this device is ZTP. To override the default behavior of your secure device, issue the request system zeroize ztp-option secure-enable command.

  See Secure Zero Touch Provisioning, Generate Secure ZTP Vouchers, and Switching between Secure Zero Touch Provisioning and Zero Touch Provisioning.

• The QFX5230-64CD devices support the following firmware upgrade commands:

  • request system firmware upgrade fpc slot 0 bcm-pfe

  • request system firmware upgrade fpc slot 0 dpll

  • request system firmware upgrade fpc slot 0 dpll-cfg

  • request system firmware upgrade fpc slot 0 opticscpld<0|1|2>

  • request system firmware upgrade psm slot <0|1>

  • request system firmware upgrade re bios

  • request system firmware upgrade re fancpld

  • request system firmware upgrade re fpga

  • request system firmware upgrade re i210

  • request system firmware upgrade re ssd <disk1|disk2>

  • request system firmware upgrade re xmcfpga

  [See request system firmware upgrade.]

Chassis

• Support for inbuilt Routing Engine, Control Board (CB), power supply units, fan trays, Flexible PIC Concentrators (FPCs), and PICs.

  [See QFX5240 Switch Hardware Guide].

CoS

• Support for CoS features on Layer 2 and Layer 3 interfaces. Supported CoS features include:

  • IPv4 and IPv6 unicast routing.

  • Classification and rewrite rules (DSCP, IEEE-802.1p)

  • Port scheduling

  • Shared buffer

  • Priority-based flow control (PFC) based on IEEE-802.1p. DSCP-based PFC is required to support Remote Direct Memory Access (RDMA) over converged Ethernet version 2 (RoCEv2).

  • Weighted random early detection (WRED) and explicit congestion notification (ECN)

  • Telemetry support for CoS queue statistics exported using the sensor /junos/system/linecard/qmon-sw/.

  [See Understanding How Class of Service Manages Congestion.]

Forwarding and sampling

• Support for dynamic load balancing (DLB) (for port speeds over 50 Gbps) and resilient hashing for ECMP routes. DLB and resilient hasing are not supported on a link aggregation group (LAG) or when a LAG is one of the egress ECMP members.

  [See Dynamic Load Balancing, Use of Resilient Hashing to Minimize Flow Remapping, and ecmp-resilient-hash.]

Interfaces

• The QFX5240 switches have 64x800GbE OSFP ports on the QFX5240-64OD and 64x800GbE QSFP-DD ports on the QFX5240-64QD. The last two ports (64 and 65) on both the QFX5240 variants are 2x10GbE SFP ports.

  The ports on the QFX5240-64OD and QFX5240-64QD support the following speeds:

  • 1x800 Gbps

  • 2x400 Gbps

  • 4x200 Gbps

  • 8x100 Gbps

  Note:

  On the QFX5240 switches, the runts (under Input errors) and fragment frames (under MAC statistics) counters do not increment in the output of the show interfaces extensive command. These counters are not supported due to a hardware limitation.

  [See Port Speed on QFX5240 Switches.]

Layer 2 features

• Support for Layer 2 unicast forwarding and VRRP.

  [See Understanding VRRP.]

• Support for IGMP snooping includes:

  • IGMP snooping with IGMPv1, IGMPv2, and IGMPv3
  • IGMP proxy
  • IGMP querier at Layer 2
  • Any-source multicast (ASM) and source-specific multicast (SSM) modes
  • Virtual router (VRF-lite) IGMP snooping
  • IGMP snooping with integrated routing and bridging (IRB)

  [See IGMP Snooping Overview, Multicast Overview, and Integrated Routing and Bridging.]

Layer 3 features

• Support for Layer 3 unicast forwarding and generic routing encapsulation (GRE) tunneling. We support both IPv4 and IPv6 unicast routing.

  [See Generic Routing Encapsulation (GRE).]

• Support for Layer 3 multicast forwarding includes:

  • PIM first hop router (FHR) rendezvous point (RP) functionality
  • Multicast Source Discovery Protocol (MSDP)
  • Make-before-break (MBB) support for multicast receivers on existing Layer 3 aggregated Ethernet (aex) or link aggregation group (LAG) interfaces. Support includes member addition, member deletion, link up, and link down events.
  • PIM source-specific multicast (SSM)
  • PIM sparse mode (SM)
  • PIM dense mode (DM)
  • L3 multicast forwarding on integrated routing and bridging (IRB) interfaces:
    • IPv4 and IPv6 multicast
    • IGMP v1/v2/v3
    • Multicast Listener Discovery (MLD) v1/v2
    • Any-source multicast (ASM) and source-specific multicast (SSM) modes

  [See Multicast Routing Protocols and PIM Overview.]

• Support for DHCP stateless relay on IRB interfaces and bridge domains. The switches support DHCPv4 and DHCPv6.

  [See DHCP Relay Agent.]

Network management and monitoring

• Support for sFlow.

  [See Overview of sFlow Technology.]

• Support for analyzers and port mirroring. The QFX5240-64OD and QFX5240-64QD switches support a maximum of seven port mirroring sessions.

  [See Understanding Port Mirroring and Analyzers.]

• Select your product in the Hardware Compatibility Tool to view supported transceivers, optical interfaces, and DAC cables for your platform or interface module. We update the HCT and provide the first supported release information when the optic becomes available.

Platform and infrastructure

• Support to configure firewall filters and interfaces programmatically using the Juniper Extension Toolkit (JET) APIs.

  [See Overview of JET APIs.]

Protection against DDoS attacks

• Supports configuration and installation of policers at the Packet Forwarding Engine level for defense from distributed denial-of-service (DDoS) attacks. By default, DDoS protection is enabled for many protocols on the QFX5240-64OD and QFX5240-64QD switches.

  [See Configuring Control Plane DDoS Protection Aggregate or Individual Packet Type Policers, show ddos-protection statistics, and show ddos-protection version.]

Routing policy and firewall filters

• Firewall filter support on Layer 2 and Layer 3 interfaces.

  [See Firewall Filter Match Conditions and Actions and Configuring Enhanced Egress Firewall Filters.]

Services applications

• Support for generic routing encapsulation (GRE) features:

  • GRE tunnels over Gigabit Ethernet, LAG, and VLAN
  • Tagged subinterfaces
  • Payload protocol for IPv4 and IPv6
  • Delivery protocol for IPv4
  • Multicast over GRE tunnels
  • Tunnel statistics
  • VRF with GRE
  • Time-to-live (TTL)

  [See Generic Routing Encapsulation (GRE).]

Software installation and upgrade

• Support for firmware upgrade commands:

  • request system firmware upgrade re bios

  • request system firmware upgrade re i210

  • request system firmware upgrade re ssd disk1

  • request system firmware upgrade re ssd disk2

  • request system firmware upgrade cb fancpld

  • request system firmware upgrade cb fpga

  • request system firmware upgrade cb port-fpga

  • request system firmware upgrade fpc slot 0 bcm-pfe

  • request system firmware upgrade fpc slot 0 dpll

  [See request system firmware upgrade.]

• Support for USB booting.

  Note:

  On QFX5240 switches, only UEFI boot media (UEFI USB, UEFI NVME, UEFI network, and so on) is supported. You must select USB (UEFI USB) manually from the BIOS menu or use the request node reboot re0 usb command to boot from USB.