Hardware

• Supports two Routing Engines, one Control Board, one Forwarding Engine Board (FEB), one fixed FPC, and three removable FPCs chassis supports:

  • Platform FEB and FPC FRU presence and power-up.

  • Infrastructure databases and services.

  • Power management.

  • Environment monitoring and cooling.

  • System LED behavior.

• Platform resiliency support for device chassis, RCB, FEB, and input/output card (IOC).

• Support for telemetry interfaces.

• Support for classification and rewrite rules of all types (Inet-Prec/DSCP/DSCP-v6/IEEE-802.1p/IEEE-802.1ad) at the logical interface level. Supports logical interfaces classification and rewrite rules for MPLS, VPLS, Layer 3 VPN, Layer 2 circuit, CCC, IRB, and EVPN. [See Classifiers and Rewrite Rules at the Global, Physical, and Logical Interface Levels Overview.]

• Support for port shaping and scheduling with eight VoQ queues per port and two scheduling priority levels (strict-high and low). Supports multiple strict-high priority queues (RR scheduling), multiple low-priority queues (WFQ scheduling), low latency queues (LLQ), and default deep buffers. [See Schedulers Overview for ACX Series Routers and Shared and Dedicated Buffer Memory Pools on ACX Series Routers .]

Dynamic Host Configuration Protocol

• DHCP server and DHCP relay configuration for IPv4 and IPv6 services.

  [See DHCP Overview.]

• DHCP relay deployment of EVPN over MPLS, which includes:

  • Edge-routed bridging (ERB)—Edge model where DHCP clients are connected and relayed in network leaf devices. The spine PEs do not perform DHCP relay functions, and the routers support transit spine functionality running protocols such as BGP for integrated routing and bridging (IRB).

• The following functionalities:

  • EVPN over MPLS Ethernet-LAN

  • DHCPv4 and DHCPv6 relay options

  • Stateless forward-only mode for DHCP relay over VPN

  • Anycast IP address with IRB for a relay source

  • Client VRFs only

• DHCPv4 and DHCPv6 relay agent support for MC-LAG. DHCP relay agent support includes:

  • DHCPv4 and DHCPv6 stateless forward-only option on Layer 3 static interfaces over MC-LAG.

  • DHCPv4 and DHCPv6 stateless forward-only option on IRB interfaces over MC-LAG.

  • DHCPv4 and DHCPv6 forward-snooped-clients on dual-stack configurations.

  [See DHCP Relay Agent and Enabling and Disabling DHCP Snooped Packets Support for DHCP Relay Agent.]

  [See DHCP Relay Agent in EVPN-MPLS Network.]

EVPN

• Support for the following EVPN-MPLS features on MAC-VRF instances:

  • L2 flooding for broadcast, unknown unicast, and multicast (BUM) traffic

  • Split-horizon between core interfaces

  • Data plane and control plane MAC learning and aging, and static MAC

  • MAC movement and MAC mobility on control plane only

  • MAC limiting and MAC learning

  • Input and output VLAN maps using normalization on user-to-network interfaces (UNIs)

  • Aggregated Ethernet interfaces used for UNIs and network node interfaces (NNIs)

  • Physical interfaces for VLAN tagging, stacked VLAN tagging, flexible VLAN tagging, and extended VLAN bridges using EVPN-MPLS as a service

  • Ethernet bridge mode for logical UNIs

  • VLAN ID lists, native VLAN ID supported logical UNIs, and priority-tagged logical interfaces

  • Underlay networks with ECMP and Fast Reroute (FRR)

  • Control-word support for EVPN

  • EVPN Proxy Address Resolution Protocol (ARP) and ARP suppression

  • EVPN-ELAN over segment routing

    [See EVPN Feature Guide.]

• Virtual private wire service (VPWS) with EVPN signaling mechanisms and flexible cross-connect support.

  [See Overview of VPWS with EVPN Signaling Mechanisms.]

• EVPN E-LAN active-active multihoming with EVPN aliasing support for ESI LAG.

  [See Example: Configuring EVPN Active-Active Multihoming.]

• All-active multihoming redundancy in both Ethernet VPN–virtual private wire service (EVPN-VPWS) and EVPN-VPWS with flexible cross-connect.

  [See Overview of Flexible Cross-Connect Support on VPWS with EVPN.]

• EVPN VPWS multihoming all-active forsegment routing over MPLS

  [See Overview of VPWS with EVPN Signaling Mechanisms.]

• Entropy and flow label for EVPN-ELAN

  [See Configuring Entropy Labels.]

• Support for the following EVPN-MPLS features:

  • IRB with IPv4 and IPv6 addresses

  • IRB virtual gateway

  • IRB anycast gateway

  • IRB with static mac

  • EVPN asymmetric Type 2 and symmetric Type 5 routes

  • EVPN E-LAN over BGP-LU

  • EVPN proxy ARP and ARP suppression, and NDP and NDP suppression

  • EVPN routing policies

  • Ingress virtual machine traffic optimization (VMTO)

  [See EVPN with IRB Solution Overview, Anycast Gateways, Symmetric Integrated Routing and Bridging with EVPN Type 2 Routes, Understanding EVPN Pure Type 5 Routes, EVPN Proxy ARP and ARP Suppression, and Proxy NDP and NDP Suppression, Ingress Virtual Machine Traffic Optimization, and Routing policies for EVPN.]

• Support for the following EVPN-VPWS features:

  • EVPN-VPWS FXC VLAN unaware service

  • EVPN-VPWS FXC VLAN aware service

  • EVPN-VPWS over segment routing

  • Single homing and all active multihoming support

  • Flow-aware transport (FAT) pseudowire labels

  • Entropy labels

  [See Overview of VPWS with EVPN Signaling Mechanisms.]

Firewall filters

• Support for firewall filters and policers. You can configure firewall filters with packet match conditions for the bridge domain, IPv4, IPv6, CCC, and MPLS families. In addition to packet match conditions, the count, discard, log, syslog, and policer actions are supported.

  [See Standard Firewall Filter Match Conditions and Actions on ACX Series Routers Overview.]

• Filter-based forwarding (FBF).

  [See Filter-Based Forwarding Overview.]

• Firewall filter protocols: MPLS, CCC, virtual private LAN service (VPLS), and ANY.

  [See Firewall Filters Overview, Filter-Based Forwarding Overview, Understanding Filter-Based Forwarding to a Specific Outgoing Interface or Destination IP Address, and Guidelines for gRPC and gNMI Services.]

High availability

• VRRP for IPv4 and IPv6. [See VRRP and VRRP for IPv6 Overview.]

• BFD over label-switched paths (LSPs) or RSVP-based LSPs in a centralized mode.

  [See Bidirectional Forwarding Detection (BFD) for MPLS.]

• High availability on these routers are supported at the hardware level. Graceful routing engine switchover is not supported in this release.

• Support for loop-free alternate (LFA) routes for OSPF and IS-IS. LFA enables IP fast-reroute capability for OSPF and IS-IS.

  [See Loop-Free Alternate Routes for OSPF Overview and Understanding Loop-Free Alternate Routes for IS-IS.]

• BFD-triggered fast reroute for unicast next hops.

  [See Bidirectional Forwarding Detection (BFD) for MPLS, session-id-change-limiter-indirect, and no-bfd-triggered-local-repair.]

Interfaces

• The ACX7348 router provides 1GbE through 400GbE port flexibility and a throughput of 2.4 Tbps.

  [See Port Speed.]

• Support for 6xQSFPDD and 16xSFP56 FPC line cards. The 6xQSFPDD FPC Line Card has two QSFPDD ports (Port 0 and 2) and four QSFP ports (Port 1, 3, 4 and 5). The 16xSFP56 FPC line card has 16 SFP56 ports (Port 0 to 15). Slot 1 and 2 supports 10-Gbps, 25-Gbps, and 50-Gbps speeds. Slot 3 supports 1-Gbps, 10-Gbps, and 25-Gbps speeds.

  [See Port Speed.]

• Support for 802.1X authentication on Layer 2 and Layer 3 interfaces.

  [See 802.1X Authentication on Layer 2 Interfaces.]

• Support for LACP link protection. We support 1:1 and N:N link protection.

  [See link-protection.]

• Resiliency support for ASIC error and CM infra. Resiliency only supports logging and detection and not action.

• Features supported for unnumbered interfaces:

  • Bidirectional Forwarding Detection (BFD)

  • BGP labeled unicast

  • Ethernet VPN virtual private wire service (EVPN-VPWS)

  • IS-IS protocol adjacency

  • Label Distribution Protocol (LDP)

  • Layer 2 VPN and Layer 2 circuit

  • Layer 3 VPN

  • Qualified next hop

  • RSVP-TE

  • Static subnet route

  • Source Packet Routing in Networking (SPRING) over OSPFv2

  • SPRING-TE

  • Segment routing with MPLS

  • Static LSP

  • Source Packet Routing in Networking (SPRING) over OSPFv2

  • SPRING-TE

  • Segment routing with MPLS

  • Static LSP

  [See Configure unnumbered Interfaces.]

Junos Telemetry Interface (JTI)

• Logical subinterface and Packet Forwarding Engine drop, pipe, and line-card counter sensor support for JTI.

  [See Junos YANG Data Model Explorer.]

Layer 2 features

• Ethernet ring protection switching (ERPS) with G.8032 version 2.

  [See Understanding Ethernet Ring Protection Switching Functionality .]

• Support for the following advanced Layer 2 (L2) features:

  • 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

• • MAC learning, ageing, and limiting

  • Single-learning domain per bridge domain

  • Ethernet service types:

    • E-Line with these 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

  • ethernet-bridge

• Q-in-Q tunneling

[See Understanding Layer 2 Bridge Domains and Q-in-Q Tunneling.]

• Disable local switching in bridge domains.

  [See Configuring MAC Address Flooding and Learning for VPLS.]

• Layer 2 protocol tunneling (L2PT) to send L2 protocol data units (PDUs) across the network and deliver them to devices that are not part of the local broadcast domain.

• Storm control.

  [See Understanding Storm Control.]

• Rapid Spanning Tree Protocol (RSTP), Multiple Spanning Tree Protocol (MSTP), and VLAN Spanning Tree Protocol (VSTP).

  [See Spanning-Tree Protocol Overview.]

• MAC move limit and multiple trunk ports, virtual private LAN service (VPLS), and EVPN networks.

  [See Understanding MAC Limiting and MAC Move Limiting.]

• Layer 2 Control Protocol (L2CP) BPDUs are transparently forwarded in hardware unless a specific protocol is configured on the incoming interface. This feature helps you to configure and enable L2PT.

• VLAN sensor support.

  [See Telemetry Sensor Explorer.]

  [See Understanding Layer 2 Bridge Domains on ACX Series and Q-in-Q Tunneling on ACX Series, Bridging and VLANs, and Configuring MAC Address Flooding and Learning for VPLS .]

• Multichassis link aggregation groups (MC-LAGs). The following Layer 2 features are available on MC-LAGs:

  • Layer 2 bridging for active-active and active-standby modes

  • Layer 2 unicast with and without IGMP snooping

  • Layer 3 unicast with and without IGMP snooping

  • Layer 2 multicast with and without IGMP or MLD snooping•

  • Layer 3 multicast with and without IGMP or MLD snooping

  [See Understanding Multichassis Link Aggregation Groups.]

Layer 2 VPN

• Support for VPLS. The router supports a single VLAN for each virtual switch routing instance type. Junos OS Evolved does not support the family vpls option. To configure VPLS, configure the instance-type virtual-switch statement at the [edit routing-instances routing-instance-name] hierarchy level. If you configure normalized VLANs, either by not configuring VLAN IDs or by including the vlan-id none statement, then you must include the service-type single statement at the [edit routing-instances routing-instance-name protocol vpls] hierarchy level.

  [See Introduction to Configuring VPLS.]

• Support for control word and load-balancing capabilities using entropy and flow-aware transport of pseudowires (FAT) flow labels, across LDP-signaled pseudowires for virtual private LAN service (VPLS).

  [See control-word , Configuring Entropy Labels, and FAT Flow Labels Overview.]

• Support for redundant pseudowires for virtual private LAN service (VPLS). The router supports VPLS with LDP hot-standby, cold-standby model, and without BFD or CFM trigger.

  [See Redundant Pseudowires for Layer 2 Circuits and VPLS.]

• IRB support for VPLS.

  [See Configuring VPLS and Integrated Routing and Bridging.]

• Layer 2 VPN and L2 circuit support:

  • L2 circuit—Targeted LDP signaling pseudowires and interoperability between different types of supported attachment circuit for L2 circuit

  • L2 VPN circuit—BGP signaling

• MPLS fast reroute (FRR) on IGP, circuit attachment types (port, VLAN, and Q-in-Q tunneling), control word, pseudowire circuit on aggregated Ethernet interfaces, indirect next hops and composite next hops, pipe and uniform mode time-to-live (TTL), Tag Protocol Identifiers (TPIDs), and VLAN map on pop, push, or swap.

  [See Understanding Layer 2 VPNs and Understanding Layer 2 VPNs and Configuring Interfaces for Layer 2 Circuits.]

• Flow-aware transport for pseudowires (FAT) label and entropy label support for Layer 2 circuit and Layer 2 VPN.

  [See Configuring Entropy Labels, and FAT Flow Labels Overview.]

Layer 3 features

• Support for the following Layer 3 features:

  • IP forwarding and exception packet handling

  • IEEE 802.1Q (VLAN trunk) on IRB interfaces

  • Address Resolution Protocol (ARP), neighbor discovery, unicast reverse-path forwarding, and ECMP

  • LPM and fragmentation handling, ICMP redirect handling, VLAN tagging modes, neighbor solicitation, and Interface-based routing

  • Longest prefix match

  • Exception packets handling

  • VLAN tagging modes

  • Integrated routing and bridging (IRB)

  • IPv4 and IPv6

The router also supports interior gateway protocols such as OSPF, IS-IS, RIP, and ECMP for IPv4 and IPv6. [See Configure ICMP Features, Enabling VLAN Tagging, Neighbor solicitation, Understanding Unicast RPF (Routers), OSPF Overview, IS-IS Overview, and RIP User Guide.]

Layer 3 VPN

Support for the following Layer 3 VPN features:

• IP-VPN services:

  • Instance-type –virtual routing and forwarding (VRF) and virtual-router

  • All control plane configuration options

• • Per-prefix and per-table label signaling

  • Layer 3 VPN support with ECMP

  • BGP polices support for different Layer 3 VPN use cases (for example, full mesh VPN, hub-spoke VPN, management VPN, and leaking routes)

  • Layer 3 VPN with vrt-table-label mode

  • Layer 3 VPN with chained composite mode

• Import or export of routes across local VRF and global VRF

• Inter-autonomous system (inter-AS) options A, B, and C

  Note:

  Inter-AS option B can be deployed in hierarchical network design within a single IGP AS.

• PE to CE routing protocols—Static, eBGP, IS-IS, OSPF, and RIP

• IPv6 Provider Edge (6PE)/IPv6 VPN routing over MPLS (6VPE) with PE-CE routing-static and PE-CE BGPv6

[See Layer 3 VPNs User Guide for Routing Devices.]

MACsec

Supports Media Access Control Security (MACsec).

[See Understanding Media Access control Security (MACsec).]

MPLS

• Support for the following MPLS features:

  • IP/MPLS infrastructure feature set for the L3 VPN service

  • Basic BGP control plane features such as LDP-DOD, CSPF, and single-area CSPF

  • MPLS label stack

  • MPLS protections:

    • Fast reroute (FRR) and 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 includes refresh reduction

  • Label Distribution Protocol (LDP) LSP over IPv4

  • RSVP 1:1

  • RSVP-Traffic Engineering (RSVP-TE)

  • LDP over RSVP

  • Inter-autonomous system LSP intra-area LSP

  • [See MPLS Applications User Guide.]

• Support for MPLS LSP statistics and RSVP-TE auto-bandwidth features. Support includes:

  • MPLS LSP statistics for the following LSP types:

    • LDP-signaled LSPs

    • RSVP-signaled LSPs

    • Static LSPs

    • Bypass LSPs

    • Container LSPs

  • RSVP-TE auto-bandwidth

[See LSP Overview, LDP Overview, RSVP Overview, and Configuring Optimized Auto-bandwidth Adjustments for MPLS LSPs.]

Multicast

• Support for multicast snooping in a VPLS for the following protocols:

  • IGMPv1, IGMPv2, and IGMPv3 snooping in VPLS

  • MLDv1 and MLDv2 snooping in VPLS

  • IGMP and MLD snooping in VPLS with integrated routing and bridging (IRB)

  • Protocol Independent Multicast support over VPLS with IRB

  [See Multicast Snooping for VPLS.]

• Support for Layer 2 multicast-related features, including IGMP and MLD snooping. You can configure IGMP snooping with IGMPv1, IGMPv2, and IGMPv3, which includes support for:

  • IGMP snooping in bridge domains

  • IGMP snooping with integrated routing and bridging (IRB) configured in bridge domains

  • MLD snooping in bridge domains

  • MLD snooping with IRB configured in bridge domains

  [See IGMP Snooping Overview and Understanding MLD Snooping.]

• Support for IPv4 multicast for Layer 3. You can configure IGMP snooping with IGMPv2 and IGMPv3, which includes support for the following:

  • Anycast RP

  • IGMP filter

  • IGMP querier

  • Protocol Independent Multicast source-specific multicast (PIM SSM)

  • PIM sparse mode (PIM SM)

  Note:

  In this Junos OS Evolved release, the ACX7348 router doesn't support IPv6 multicast or L3 multicast protocols (such as IGMP, MLD, or PIM) over IPv4 and IPv6 IRB interfaces.

  [See IGMP Snooping Overview.]

• Support for BGP MVPN. BGP over MPLS MVPN (also known as "next generation," or "NG," MVPN) running on multipoint LDP provider tunnels, where BGP MVPN is the intra-AS and PIM-SM and multipoint LDP point-to-multipoint (P2MP) tunnels is the data plane.

  [See Multiprotocol BGP MVPNs Overview.]

• Multicast with IGMP or MLD snooping within VLANs for EVPN-MPLS.

  [See Overview of Multicast Forwarding with IGMP or MLD Snooping in an EVPN-MPLS Environment.]

Network management and monitoring

• Support for port mirroring with analyzers and encapsulated remote Switch Port Analyzer (ERSPAN).

  [See Port Mirroring and Analyzers.]

• Support for SNMP.

Operations, Administration, and Maintenance

• Support for OAM. You can configure connectivity fault management (CFM), BFD, and the ITU-T Y.1731 standard for Ethernet service OAM. You can also configure the following features of link-fault management (LFM):

  • Discovery

  • Link monitoring

  • Remote fault detection

  [See ITU-T Y.1731 Ethernet Service OAM Overview and Introduction to OAM Link Fault Management (LFM).]

• Support for IEEE 802.1ag OAM CFM.

• Support for IEEE Standard 802.3ah and 802.1ag for OAM CFM down and up maintenance association end points (MEPs) over virtual private LAN service (VPLS).

• Support for IEEE Standard 802.3ah and 802.1ag for OAM CFM up MEPs over EVPN.

  [See IEEE 802.3ah OAM Link-Fault Management Overview and IEEE 802.1ag OAM Connectivity Fault Management Overview.]

• Support for CFM and performance monitoring (Y.1731) protocols over Ethernet interfaces for bridge and inet services.

  [See Ethernet OAM Connectivity Fault Management.]

• Support for native Y.1731 operational state sensors to provide statistics such as frame loss ratio, frame delay, frame delay variation, and availability for Y.1731 performance monitoring.

Protection against DDoS attacks

• Support for control plane distributed denial of service (DDoS) protection.

  [See Control Plane Distributed Denial-of-Service (DDoS) Protection Overview.]

Routing protocols

• Layer 3 and routing protocols IPv4, IPv6, BGP, IS-IS and ARP streaming sensor support using gRPC services.

• Support for unicast reverse path forwarding (unicast RPF):

  • Support for loose and strict mode

  • Support for IPv4 and IPv6

  [See Understanding Unicast RPF (Routers).]

• Support for BGP flow specification (BGP flowspec).

  • The following match conditions are not supported:

    • Fragment for IPv6

    • Packet length

    • Port

    • Source and destination prefix with offset

• The following actions are not supported:

  • Community

  • Next-term

  • Routing instance

  • Sample

  • Traffic marking

  [See Understanding BGP Flow Routes for Traffic Filtering.]

• Support for configuring interface groups in BGP flowspec filters.

  [See Understanding BGP Flow Routes for Traffic Filtering and Configuring BGP Flow Specification Action Redirect to IP to Filter DDoS Traffic.]

• BGP PIC edge support for inet and MPLS VPNs. The following features are not supported:

  • Session-based repair

  • BGP PIC over LDP over RSVP tunnel

  • BGP PIC over SR-MPLS

  • BGP PIC with RSVP

  • BGP-LU with PIC

  • BGP PIC edge protection for Layer 2 services

  • Protection with multilink failure

  [See Configuring BGP PIC Edge for MPLS Layer 3 VPNs and Use Case for BGP PIC for Inet.]

• Support for entropy label for LDP, RSVP, L3VPN, and BGP-LU.

  [See Entropy label support for BGP Labeled Unicast (BGP-LU) and Configuring Entropy Labels.]

• Support for BGP transport address family or BGP Classful Transport (BGP-CT) includes:

  • Service mapping over colored transport tunnels (RSVP, IS-IS flexible algorithm) to transport classes and map service routes over an intended transport class. The transport tunnels can span multiple domains (ASs or IGP areas).

  • Network slicing and interoperability between network domains.

  • IPv6 and segment routing–traffic engineered (SR-TE) color-only support.

  • IPv6 and BGP service routes with a color-only mapping community.

  • Enhanced transport-class configuration to provide precise resolution.

  [See use-transport-class.]

Services Applications

• RFC 2544-based benchmarking tests. Support for Layer 2 reflection (bridge, L2CKT, L2VPN, EVPN-VPWS, EVPN-FXC, EVPN-MPLS, and VPLS), with family ccc or family ethernet-switching and for Layer 3 reflection (IPv4, L3VPN) with family inet. RFC 2544 tests are performed to measure and demonstrate the service-level agreement (SLA) parameters before activation of the service. The tests measure throughput, latency, frame loss rate, and back-to-back frames.

  [See RFC 2544-Based Benchmarking Tests for ACX Routers Overview.]

• 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. TWAMP is often used to check compliance with service-level agreements. The support for this service is limited to the following features:

  • IPv4 and IPv6 source and target addresses for clients, control connections, 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 software (the Routing Engine or the Packet Forwarding Engine) or the hardware

  • Error reporting through system log messages only

  • Unauthenticated mode only

  [See Understand Two-Way Active Measurement Protocol.]

• Support for sFlow monitoring (ingress).

  [See sFlow Monitoring Technology and Understanding How to Use sFlow Technology for Network Monitoring.]

• Inline active flow monitoring support for IPFIX and v9 export formats. We support ingress and egress sampling of IPv4 and IPv6 traffic on aggregated Ethernet and IRB interfaces and interfaces mapped to non-default VRFs, for both the IPFIX and version 9 export formats. You can configure up to four IPv4 collectors for inline active flow monitoring.

  See Understand Inline Active Flow Monitoring.

Source Packet Routing in Networking (SPRING) or segment routing

• Support for the following segment routing features:

  • Segment routing global block (SRGB) for OSPF, IS-IS, and fast reroute.

  • Metro Ethernet services over segment routing infrastructure

  • Segment routing services: L3VPN, IPv6 VPN Provider Edge (6VPE) , IPv6 Provider Edge (6PE), L2VPN, L2 circuit, and BGP-VPLS

  • Static segment routing (node segment, prefix segment, adjacency, and anycast segments) for OSPF and IS-IS

  • Topology-independent loop-free alternate (TI-LFA) with segment routing for OSPF and IS-IS

• Unnumbered interfaces support for segment routing with OSPF

• Support for IPv6 L3VPN over IPv6 SR-TE and IPv6 underlay

• Support for flexible algorithm in OSPF and IS-IS for segment routing traffic

• Interoperability of segment routing with LDP

• SPRING support for SR-TE

• Support for BGP link-state distribution with SPRING extensions

  [See Understanding Topology-Independent Loop-Free Alternate with Segment Routing for IS-IS, Understanding Source Packet Routing in Networking (SPRING), Understanding Adjacency Segments, Anycast Segments, and Configurable SRGB in SPRING, Configure Unnumbered Interfaces, Understanding Static Segment Routing LSP in MPLS Networks, Link-State Distribution Using BGP Overview, Understanding OSPF Flexible Algorithm for Segment RoutingHow to Configure Flexible Algorithms in IS-IS for Segment Routing Traffic Engineering, and Mapping Client and Server for Segment Routing to LDP Interoperability.]

• Support for SRv6 network programming in BGP and IS-IS.

  [See Understanding SRv6 Network Programming and Layer 3 Services over SRv6 in BGP and How to Enable SRv6 Network Programming in IS-IS Networks.]

• Support for OAM ping and traceroute for Segment Routing for IPv6 (SRv6) network programming.

  [See ITU-T Y.1731 Ethernet Service OAM Overview and How to Enable SRv6 Network Programming in IS-IS Networks.]

• Support for SRv6 flexible algorithms in traffic engineering database (TED) and BGP Link State (BGP-LS)

  [See How to Configure Flexible Algorithms in IS-IS for Segment Routing Traffic Engineering and BGP Link-State Extensions for Source Packet Routing in Networking (SPRING).]

• SRv6 support for static SR-TE policy.

  [See Understanding SR-TE Policy for SRv6 Tunnel.]

• Support for SRv6 micro-SIDs in IS-IS transport. You can compress multiple SRv6 addresses into a single IPv6 address (micro-SID). For use cases that need to include more than six SRv6 SIDs, micro-SIDs can help in compressing multiple IPv6 addresses.

  [See How to Enable SRv6 Network Programming in IS-IS Networks.]

Software installation and upgrade

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

  [See Software Installation and Upgrade Guide.]

• Zero-touch provisioning (ZTP) support for WAN interfaces and DHCPv6 options.

  [See Zero Touch Provisioning.]

• Secure Zero Touch Provisioning.

  [See Secure Zero Touch Provisioning.]

System management

• Support for an alternate partition for device recovery. You can use an alternate partition called /altconfig to recover the device when the /config partition gets corrupted. In certain scenarios, the /config partition (which holds the last four committed configuration files along with the rescue configuration) gets corrupted during resets or power cycles. The /altconfig partition (which holds the juniper.conf.gz and rescue.conf.gz files) is used by the management daemon (mgd) to recover the device when the /config partition is corrupted. This is a boot-time feature and is enabled by default.

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.

  The ACX7348 router 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

  [See enable-extended-ql-tlv, Ethernet Synchronization Message Channel Overview, 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.]

• Synchronous Ethernet over LAG with Ethernet Synchronization Message Channel (ESMC).

  [See Synchronous Ethernet and Ethernet Synchronization Message Channel (ESMC).]

• SNMP MIB support for the Synchronous Ethernet timing feature.

  [See Configuring SNMP Trap Groups and Enterprise-Specific MIBs for Junos OS Evolved.]

• Support for G.8275.1 telecom profile, Precision Time Protocol over Ethernet (PTPoE) encapsulation, and hybrid mode. [See Precision Time Protocol Overview and Understanding Hybrid Mode.]

• PTP G.8275.1 support over Link Aggregation Group (LAG)

  [See G.8275.1 Telecom Profile.]

Support for optics

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

• Logical interfaces support classification and rewrite rules for MPLS, VPLS, L3VPN, L2CKT, CCC, IRB, and EVPN. [See Classifiers and Rewrite Rules at the Global, Physical, and Logical Interface Levels Overview.]

• Support for deep buffering of oversubscribed traffic and absorbs network bursts. [See Shared and Dedicated Buffer Memory Pools on ACX Series Routers .]

• Hierarchical Class of Service (CoS) support for Layer 3 VPN, Layer 2 VPN, Layer 2 Circuit, VPLS, and EVPN services. [See Hierarchical Class of Service in ACX Series Routers.]

• Support for multiple classifier rules on interfaces. [See Understanding Applying CoS Classifiers and Rewrite Rules to Interfaces.]

EVPN

• Support for the following EVPN features:

  • EVPN-ETREE

  • VLAN-aware bundle service in EVPN-MPLS

  • EVPN Active/Standby Multi-homing with LACP based functionality

  • MC-LAG in active-standby mode in an EVPN configuration without configuration of an ICCP or ICL interface

  • Configure lacp-oos-on-ndf statement at the [edit interfaces interface name esi df-election-granularity per-esi] hierarchy

  [See Understanding VLAN-Aware Bundle and VLAN-Based Service for EVPN and df-election-granularity.]

Firewall filters

• Firewall filter protocols (MPLS, CCC, VPLS, and ANY). [See Firewall Filters Overview.]

• Supports the following firewall filter actions to configure filter-based forwarding or policy based forwarding:

  • next-ip firewall filter action for IPv4 address

  • next-ip6 firewall filter action for IPv6 address

  • next-interface firewall filter action for an interface

  [See Filter-Based Forwarding Overview and Understanding Filter-Based Forwarding to a Specific Outgoing Interface or Destination IP Address.]

• IPv4 and IPv6 filter support for SRv6. [See Firewall Filter Match Conditions and Actions (ACX Series Routers).]

High availability

• BFD-triggered fast reroute for unicast next hops. [See Bidirectional Forwarding Detection (BFD) for MPLS, session-id-change-limiter-indirect, and no-bfd-triggered-local-repair.]

• IPv6 link-local address support for TWAMP Light [edit services monitoring twamp client control-connection connection-name] hierarchy level. [See Configure TWAMP on ACX.]

• Packet Forwarding Engine timestamping for Two-Way Active Measurement Protocol (TWAMP) IPv6 test probes. [See offload-type.]

• VRRP for IPv4 and IPv6. [See VRRP and VRRP for IPv6 Overview.]

• Support for the following Bidirectional Forwarding Detection (BFD) features:

  • BFD for IPv4 and IPv6 routes

  • Single-hop BFD in inline mode with an interval range of 4 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

  • Configure BFD over label-switched paths (LSPs) or RSVP-based LSPs in a centralized mode

  [See Bidirectional Forwarding Detection (BFD) for MPLS.]

• Support for loop-free alternate (LFA) routes for OSPF and IS-IS. LFA enables IP fast-reroute capability for OSPF and IS-IS.

  [See Loop-Free Alternate Routes for OSPF Overview and Understanding Loop-Free Alternate Routes for IS-IS.]

• Bidirectional Forwarding Detection (BFD) for virtual circuit connection verification (VCCV) for Layer 2 Circuits. [See Configuring BFD for VCCV for Layer 2 Circuits.]

Interfaces

• Support for unnumbered interfaces:

  • Bidirectional Forwarding Detection (BFD)

  • BGP labeled unicast

  • Ethernet VPN virtual private wire service (EVPN-VPWS)

  • IS-IS protocol adjacency

  • Label Distribution Protocol (LDP)

  • Layer 2 VPN and Layer 2 circuit

  • Layer 3 VPN

  • Qualified next hop

  • RSVP-TE

  • Static subnet route

  • Source Packet Routing in Networking (SPRING) over OSPFv2

  • SPRING-TE

  • Segment routing with MPLS

  • Static LSP

  [See Configure unnumbered Interfaces.]

Junos Telemetry Interface (JTI)

• RPM and TWAMP statistics sensor support for Junos Telemetry Interface (JTI). [See Telemetry Sensor Explorer.]

• Junos Telemetry Interface provides Packet Forwarding Engine sensor support for firewall filter stats. To generate periodic streaming of statistics, use the resource path /junos/system/linecard/firewall/ in a gRPC or gNMI subscription. JTI provides periodic streaming and ON_CHANGE support for interface queue statistics. The resource path is /junos/system/linecard/interface/queue/. [See Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface).]

• Layer 3 routing and protocols statistics for JTI. [See Telemetry Sensor Explorer.]

Layer 2 features

• Advanced Layer 2 features:

  • 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

  • MAC learning, ageing, and limiting

  • Single-learning domain per bridge domain

  • Ethernet service types (E-Line, E-LAN, E-Access, E-Transit, LLDP, LACP, IRB interfaces).

• 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, ethernet-bridge)

• Q-in-Q tunneling

• Disable local switching in bridge domains.

  [See Configuring MAC Address Flooding and Learning for VPLS.]

• Layer 2 protocol tunneling (L2PT) to send L2 protocol data units (PDUs) across the network and deliver them to devices that are not part of the local broadcast domain.

• Storm control.

  [See Understanding Storm Control.]

• Rapid Spanning Tree Protocol (RSTP), Multiple Spanning Tree Protocol (MSTP), and VLAN Spanning Tree Protocol (VSTP).

  [See Spanning-Tree Protocol Overview.]

• MAC move limit, virtual private LAN service (VPLS), and EVPN networks.

  [See Understanding MAC Limiting and MAC Move Limiting.]

• Layer 2 Control Protocol (L2CP) BPDUs are transparently forwarded in hardware unless a specific protocol is configured on the incoming interface. This feature helps you to configure and enable L2PT.

Layer 3 features

• Support for the following Layer 3 features:

  • IP forwarding and exception packet handling

  • IEEE 802.1Q (VLAN trunk) on IRB interfaces

  • Address Resolution Protocol (ARP), neighbor discovery, unicast reverse-path forwarding, and ECMP

  • LPM and fragmentation handling, ICMP redirect handling, VLAN tagging modes, neighbor solicitation, and Interface-based routing

  • Longest prefix match

  • Exception packets handling

  • VLAN tagging modes

  • Integrated routing and bridging (IRB)

  • IPv4 and IPv6

  The router also supports interior gateway protocols such as OSPF, IS-IS, RIP, and ECMP for IPv4 and IPv6. [See Configure ICMP Features, Enabling VLAN Tagging, Neighbor solicitation, Understanding Unicast RPF (Routers), OSPF Overview, IS-IS Overview, and RIP User Guide.]

Operations, Administration, and Maintenance

• Support for OAM. You can configure connectivity fault management (CFM), BFD, and the ITU-T Y.1731 standard for Ethernet service OAM. You can also configure the following features of link-fault management (LFM):

  • Discovery

  • Link monitoring

  • Remote fault detection

  [See ITU-T Y.1731 Ethernet Service OAM Overview and Introduction to OAM Link Fault Management (LFM).]

• Support for IEEE 802.1ag OAM CFM.

• Support for IEEE Standard 802.3ah and 802.1ag for OAM CFM down and up maintenance association end points (MEPs) over virtual private LAN service (VPLS).

• Support for IEEE Standard 802.3ah and 802.1ag for OAM CFM up MEPs over EVPN.

  [See IEEE 802.3ah OAM Link-Fault Management Overview and IEEE 802.1ag OAM Connectivity Fault Management Overview.]

• Support for CFM and performance monitoring (Y.1731) protocols over Ethernet interfaces for bridge and inet services.

  [See Ethernet OAM Connectivity Fault Management.]

• Support for native Y.1731 operational state sensors to provide statistics such as frame loss ratio, frame delay, frame delay variation, and availability for Y.1731 performance monitoring.

Platform and Infrastructure

• 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, communicating errors through LEDs, self-healing, and taking components out of service.

  [See show system errors active.]

Protection against DDoS attacks

• Support for distributed denial of service (DDoS) protection, which is enabled by default.

  [See Control Plane Distributed Denial-of-Service (DDoS) Protection Overview.]

Routing protocols

• Support for forwarding information base (FIB) compression. Using FIB compression, multiple routes with the same forwarding behavior are compressed into a single route. This helps to limit the number of forwarding entries stored in the hardware. FIB compression is enabled by default. You can store a larger number of IPv4 and IPv6 routes after FIB compression.

  Support for new MDB profiles to replace old MDB profiles, that replaces older profiles for lean-edge, cloud metro, carrier-ethernet and Border Network Gateways (BNGs). IPv6 multicast source specific multicast (SSM) is supported on all MDB profiles. The MDB resource for routes can now be used by either global or VRF routing tables and can be scaled to maximum per-profile capacity.

  Use the command set system packet-forwarding-options hw-db-profile cloud-metro to configure the cloud-metro profile.

  [See hw-db-profile.]

• Layer 3 and routing protocols IPv4, IPv6, BGP, IS-IS and ARP streaming sensor support using gRPC services.

• Support for unicast reverse path forwarding (unicast RPF):

  • Support for loose and strict mode

  • Support for IPv4 and IPv6

  [See Understanding Unicast RPF (Routers).]

• Support for BGP flow specification (BGP flowspec).

  • The following match conditions are not supported:

    • Fragment for IPv6

    • Packet length

    • Port

    • Source and destination prefix with offset

• The following actions are not supported:

  • Community

  • Next-term

  • Routing instance

  • Sample

  • Traffic marking

  [See Understanding BGP Flow Routes for Traffic Filtering.]

• Support for configuring interface groups in BGP flowspec filters.

  [See Understanding BGP Flow Routes for Traffic Filtering and Configuring BGP Flow Specification Action Redirect to IP to Filter DDoS Traffic.]

• Unicast reverse path forwarding (unicast RPF) support for IPv4 and IPv6. [See Understanding Unicast RPF (Routers).]

Services Applications

• RFC 2544 benchmarking test reflector support for Layer 2 services (Layer 2 bridge, Layer 2 circuit, Layer 2 VPN, EVPN-VPWS, EVPN-FXC, EVPN-MPLS, and VPLS) and Layer 3 services. [See RFC 2544-Based Benchmarking Tests for ACX Routers Overview.]

• RFC 2544-based benchmarking tests for the Layer 3 reflector function that supports family inet and IPv4 source and destination addresses.

• RFC 2544 generation for the following services:

  • Layer 3 VPN

  • Basic layer 3 routing

• RFC 5357 Two-Way Active Measurement Protocol (TWAMP) monitoring service. 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 features:

  • IPv4 and IPv6 source and target addresses for clients, control connections, 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 software (the Routing Engine or the Packet Forwarding Engine) or the hardware

  • Error reporting through system log messages only

  • Unauthenticated mode only

  Refer to the offload-type inline-timestamping option of the test-session statement. [See test-session (Junos OS Evolved).]

  [See Understand Two-Way Active Measurement Protocol.]

• Inline active flow monitoring support for IPFIX and v9 export formats. We support ingress and egress sampling of IPv4 and IPv6 traffic on aggregated Ethernet and IRB interfaces and interfaces mapped to non-default VRFs, for both the IPFIX and version 9 export formats. You can configure up to four IPv4 collectors for inline active flow monitoring.

  See Understand Inline Active Flow Monitoring.

• Real-time Performance Monitoring (RPM) IPv6 source and target address support. [See source-address (RPM) and target.]

Support for optics

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