Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?



  • New ACX7332 router (ACX Series)—Starting in Junos OS Evolved Release 23.4R1-S1, we introduce the Juniper Networks® ACX7332 Cloud Metro Router, an extended temperature-rated (E-Temp) platform from the ACX7300 series that supports a variety of deployment scenarios. With a compact 3-RU semi-modular form factor, it offers an aggregation solution that gives cloud providers and service providers the performance and scalability needed as networks grow.

    The ACX7332 router provides 1-Gigabit Ethernet (GbE) through 400GbE port flexibility and a throughput of 2.4 Tbps. The router has a fixed FPC with thirty-two 25GbE and eight 100GbE ports, dual Routing Engines, three bays for pluggable interface modules, redundant power supply modules (AC or DC), and four fan trays (two fans per tray).

    The ACX7332 router supports the following pluggable FPCs:

    • ACX7K3-FPC-2CD4C—Two 400GbE and four 100GbE ports

    • ACX7K3-FPC-16Y—Sixteen 50GbE ports

    The ACX7332 router runs Junos OS Evolved and provides several capabilities that include support for the latest protocol and traffic engineering technologies, enhanced security, and precision timing for mobile backhaul applications. These capabilities and features enable you to create converged, virtualized, and automated architectures to address the rapid growth of 5G, IoT, and the cloud.

    Table 1: ACX7332 Feature Support



    Authentication and Access Control

    • 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, PSM, fan tray, input, and output devices.

    Class of service

    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.]


    • 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.]


    Firewall filters


    High availability


    • The ACX7332 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 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.]

    • Support for telemetry interfaces.

    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.

    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.]


    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:


    VT interface-based Layer 3 VPN is not supported. Layer 3 VPN ping is supported only with the vrf-table-label configuration.

    • 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


    Table next hop is not supported.

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


      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.]


    Supports Media Access Control Security (MACsec).

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


    • 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.]


    • 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)

      [See IGMP Snooping Overview.]


    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).


    Protection against DDoS attacks

    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 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.]


    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


    Software installation and upgrade

    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 optics

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