Juniper ACX Cloud Metro Routers Dubai
A practical selection guide for service providers, data centers, wholesale networks and large enterprises evaluating the Juniper ACX7000 family for metro access, aggregation, edge and distributed-cloud connectivity in Dubai and the UAE.
Direct answer: what are Juniper ACX Cloud Metro Routers?
Why the ACX7000 family is different from buying a generic edge router
A metro router is rarely selected by forwarding capacity alone. In a real operator network, the platform has to sit at a defined point in the service architecture, terminate a known mix of interfaces, preserve timing where mobile transport requires it, support the chosen routing and service model, fit the physical site, and remain economical as traffic grows. Juniper positions the ACX7000 family specifically around this broader Cloud Metro problem rather than as a single box with a single throughput figure.
The portfolio contains compact fixed routers as well as fixed-plus-modular and modular systems. That matters because a cell-site or street-cabinet access location has very different constraints from a major aggregation node. At the access layer, depth, environmental tolerance, low-speed client density and 100GbE uplinks can dominate the choice. At an aggregation or lean-edge location, the decision can shift toward multiple 100GbE or 400GbE links, higher total system capacity, resilience, routing scale and the ability to grow without replacing the chassis.
For Dubai buyers, the right starting point is therefore not simply “which ACX is fastest?” It is “what role does this node perform, what traffic will it carry on day one, what does the three-to-five-year growth curve look like, and what are the physical and operational constraints?” That framing usually produces a more accurate model shortlist and reduces the risk of paying for capacity or modularity that will never be used.
Five sizing inputs that change the answer
- Network role: access, pre-aggregation, aggregation or lean edge.
- Interface plan: count and speed of 1/10/25/40/50/100/200/400GbE connections.
- Traffic and growth: current load, oversubscription policy and future service expansion.
- Site conditions: rack depth, AC or DC power, airflow, temperature and physical access.
- Service software: routing features, service types, automation, assurance and the required software entitlement.
ACX Cloud Metro model positioning
Juniper currently lists ACX7020, ACX7024, ACX7024X, ACX7100, ACX7332, ACX7348 and ACX7509 within the ACX7000 family documentation. They are not interchangeable. The practical distinction is where they sit in the network, how much capacity they provide, how their ports are distributed, and how much physical or modular expansion is required.
| Platform | Typical position | Published throughput | Representative interface profile | Buyer takeaway |
|---|---|---|---|---|
| ACX7020 | Metro access | 100 Gbps | 4 x 1/10/25GbE plus 16 x 1/10GbE | Compact option for access sites where the required interface mix and aggregate capacity fit the platform. |
| ACX7024 / ACX7024X | Metro access | 360 Gbps | 24 x 1/10/25GbE plus 4 x 100GbE | Dense 1U access choice; ACX7024 and ACX7024X differ in environmental positioning and hardware resources. |
| ACX7100-32C / 48L | High-end aggregation, large enterprise, data center | 4.8 Tbps | 32C: 32 x 100GbE plus 4 x 400GbE; 48L: 48 x 10/25/50GbE plus 6 x 400GbE | Choose based on whether the node needs dense lower-speed aggregation or dense 100GbE connectivity with 400GbE uplinks. |
| ACX7332 / ACX7348 | Metro aggregation | 2.4 Tbps | Fixed 1/10/25GbE and 100GbE ports plus three I/O bays for additional modules | Useful where compact environmental design and selective modular expansion are more important than a fully modular chassis. |
| ACX7509 | High-end aggregation / lean edge | 4.8 Tbps | Modular FPC support spanning 1/10/25/50GbE, 40/100GbE and 200/400GbE profiles | Evaluate when chassis modularity, control/forwarding redundancy and flexible interface combinations are central requirements. |
Published port combinations can include breakout rules and platform-specific restrictions, so the table should be used for initial positioning rather than as a final bill of materials. Exact port-mode combinations, optics and software support should be checked against the intended Junos release and the detailed platform documentation before purchase.
Where ACX7024 and ACX7024X fit
Compact 360 Gbps access
Both platforms provide 360 Gbps system throughput in a compact 1U form factor with 24 multirate 1/10/25GbE SFP28 interfaces and four 100GbE QSFP28 interfaces. That combination is attractive when a site needs many 1/10/25GbE customer, radio or access connections and a smaller number of high-speed uplinks. The short chassis depth is also relevant to constrained locations where a conventional deep data-center rack is not available.
Environmental choice matters
ACX7024 is positioned as the industrial-temperature-rated option, while ACX7024X is positioned for commercial-temperature environments. This distinction should be treated as a deployment requirement, not a naming detail. A buyer placing equipment in a controlled telecom room may have a different requirement from a roadside, cabinet, rooftop or other site with wider thermal exposure. The expected ambient range, ventilation and enclosure design should be documented before the model is finalized.
Timing and mobile transport
Juniper identifies advanced timing as a core use case for the ACX7000 portfolio, and the ACX7024 family includes synchronization interfaces intended for precision timing deployments. For mobile backhaul or fronthaul-related architectures, the requirement should be defined beyond a simple “PTP needed” statement. The engineering team should identify the timing source, boundary or grandmaster design, profile, holdover expectations and how the router participates in the synchronization chain.
When ACX7100 becomes the stronger choice
The ACX7100 line moves the discussion from access density into multi-terabit aggregation. Both ACX7100-32C and ACX7100-48L are published at 4.8 Tbps, but their front-panel orientation is deliberately different. The ACX7100-32C concentrates on 100GbE connectivity with 400GbE ports, while the ACX7100-48L provides a large block of 10/25/50GbE SFP56 ports alongside six 400GbE ports. That difference can materially change cabling, optics cost and migration design.
For example, a network aggregating many 25GbE or 50GbE downstream links into several 400GbE uplinks will naturally look at a different ACX7100 variant than a location built around dense 100GbE interconnection. The important procurement step is to map every planned circuit to a physical port speed and optic type, then test that map against supported breakout modes. A high total port count on paper does not mean every port can run every speed simultaneously.
Site engineering also changes at this level. The ACX7100 chassis is approximately 59.5 cm deep, and Juniper publishes different typical and maximum power figures for the 32C and 48L variants. Optics can add meaningful power and thermal load, especially when long-reach high-power modules are used. Rack depth, front-to-back or reverse airflow requirement, PDU capacity, feed redundancy and the intended transceiver population should therefore be confirmed as part of the hardware design rather than after the router arrives.
ACX7332 and ACX7348: fixed ports plus modular growth
The ACX7332 and ACX7348 occupy an interesting middle ground. Juniper publishes 2.4 Tbps system throughput and a 3U chassis with a set of fixed interfaces plus three I/O bays. ACX7332 provides 32 fixed 1/10/25GbE ports and eight 100GbE ports, while ACX7348 increases the fixed low-speed block to 48 ports while retaining eight 100GbE ports. Optional I/O modules extend the design into additional SFP56 and high-speed QSFP-based connectivity.
This architecture can suit aggregation locations that need more flexibility than a fixed 1U router but do not require the larger chassis approach of ACX7509. It is especially important to specify the I/O-bay population during quotation. Buying only the base chassis without a port-growth plan can create a mismatch between expected and available interfaces.
ACX7509: modular aggregation and lean edge
The ACX7509 is a 5U modular platform published at 4.8 Tbps. Juniper describes it as fully redundant for control and forwarding and supports a mix of port speeds from 1GbE through 400GbE using FPC slots. This makes it relevant when resilience and interface modularity are design requirements rather than optional conveniences.
The trade-off is that the engineering and quotation process becomes more component-driven. A complete design has to account for the chassis, routing engines or control components as applicable, FPC population, power, fan and airflow choices, optics, licenses and spares. The fully configured weight, rack space and power profile are also materially higher than compact access platforms. Buyers should evaluate ACX7509 when those capabilities solve a defined architectural requirement, not simply because it is the largest option in the family.
Software, routing services and automation
ACX7000 platforms run Junos OS Evolved and are designed to participate in Juniper Cloud Metro architectures with Paragon Automation. Juniper also embeds Paragon Active Assurance test-agent capability into the ACX7000 portfolio, allowing the network infrastructure to participate in service-experience measurement rather than relying exclusively on separate probes. Secure zero-touch provisioning and cryptographically bound device identity are part of Juniper’s Cloud Metro security approach.
From a protocol perspective, ACX Cloud Metro platforms are designed for modern IP and service-provider networking. Juniper documentation for the family and individual platforms references technologies including MPLS, segment routing, SRv6, EVPN-VXLAN, telemetry, programmability and network slicing. The exact feature combination that matters to a buyer should be validated against the specific platform, Junos OS Evolved release and software entitlement. A feature being associated with the family does not automatically mean every hardware variant supports every scale, interface combination or deployment mode identically.
Operationally, standardization can be as important as raw performance. A service provider using multiple ACX7000 models across access and aggregation can benefit from a common operating model, but change control still needs platform-specific qualification. Software-release selection, maintenance windows, automation templates, routing-policy consistency and telemetry destinations should be treated as part of the deployment plan. This is particularly relevant in brownfield networks where the new ACX node must interoperate with existing Juniper or third-party routing platforms.
Licensing: confirm entitlement before the hardware order is locked
Capacity-aware licensing
Juniper publishes common ACX software license options using bandwidth-related ordering units such as 10G, 100G and 400G classes. The license requirement should therefore be tied to the planned service capacity and selected platform rather than treated as a generic line item.
Subscription or perpetual
ACX licensing documentation includes subscription terms and perpetual options, with Advanced and Premium families represented in published ordering structures. Support inclusion differs by license form, so commercial comparisons should normalize term length and support coverage.
Feature requirements first
The correct entitlement depends on what the network must actually do. Routing scale, service functions, automation and lifecycle expectations should be written into the requirement before a software SKU is chosen. This prevents under-licensing and unnecessary premium entitlement.
A quotation should identify software separately enough that the buyer can understand what is included with the hardware and what is term-based. It is also sensible to identify renewal responsibility, software support coverage and the commercial impact of expanding activated capacity later. Where a deployment is being phased, a build-as-you-grow licensing approach may align expenditure with service growth, but the operational team should confirm that the chosen activation plan matches commissioning milestones.
Optics, cabling and port-mode planning
Optics are one of the most common causes of an incomplete router quotation. The ACX7000 family supports multiple Ethernet rates and, on selected platforms, high-power coherent ZR or ZR+ transceivers. That does not mean every optic is appropriate for every port or route. The bill of materials needs to reflect fiber type, reach, connector, wavelength plan, breakout requirement, link partner and the exact transceiver qualification for the selected ACX platform.
For short data-center or central-office links, the economics may favor direct attach or short-reach optics. Metro spans can require different optical budgets or coherent technology. A 400GbE port that is intended to break out into lower-speed services also needs the correct cable or optic configuration and a supported port mode. Juniper documentation explicitly advises checking supported configurations because changing one port speed can affect neighboring ports or usable breakout combinations on some hardware.
A good pre-sales worksheet therefore lists each logical connection and its physical implementation. Include source device, destination device, speed, distance, fiber type, redundancy role and desired optic. This makes it easier to identify where a lower-cost optic is sufficient, where a qualified high-power optic is required, and whether the router’s planned port population remains within power and thermal limits.
Dubai deployment considerations
Dubai deployments can range from controlled data halls and carrier facilities to telecom rooms, edge cabinets and distributed sites. The installation environment should be documented before the hardware choice is finalized. Temperature rating, front-to-back airflow, rack depth, available rack units, DC versus AC feeds, grounding, maintenance access and noise limits all influence the practical fit of a router.
Environmental tolerance should never be assumed from the ACX family name. For example, the ACX7024 is positioned for industrial-temperature operation, whereas the ACX7024X is commercial-temperature rated. Larger aggregation systems have different depth, weight and power requirements. A site survey or accurate rack-and-power worksheet can prevent expensive changes during installation.
Power and resilience
Redundancy requirements should be specified as an architecture decision. A router may support redundant power supplies, fans, routing engines or forwarding components, but the value is only realized when the site has independent feeds, correct PDU design and operational procedures that preserve redundancy during maintenance.
Power calculations should include the expected optics population rather than relying only on a chassis figure. High-speed and long-reach modules can materially change consumption and heat output. For critical metro nodes, buyers should also consider spare strategy: which components should be held locally, what replacement target is required, and whether support coverage aligns with the business impact of a failure.
Migration from an existing metro network
Replacing or expanding a metro network is not a simple hardware swap. The target ACX platform must coexist with the current routing, timing, management and service environment during the migration window. Start by documenting the services that terminate on the existing node: Internet uplinks, L2VPN or L3VPN services, mobile transport, wholesale Ethernet, data-center interconnect, management networks and any specialized timing or assurance functions.
Next, map control-plane dependencies. Identify IGP and BGP adjacencies, MPLS or segment-routing behavior, EVPN roles, route-reflector relationships, QoS policy, multicast requirements, authentication, telemetry collectors and automation systems. The purpose is not to reproduce every legacy configuration line for line; it is to ensure that every business service and operational dependency has a target state. A Cloud Metro deployment is an opportunity to simplify architecture, but simplification should be deliberate and tested.
Finally, define the cutover method. Some sites can migrate circuit by circuit, while others require a staged parallel build with temporary interconnection between old and new routers. The selected ACX model needs enough spare interfaces and capacity to support the migration state, not just the final state. This is an important sizing detail that is easily missed when procurement is based only on the end-state topology.
Practical use cases
5G transport
ACX platforms combine packet routing with precision-timing capabilities useful in mobile transport designs. Model selection depends on cell-site density, uplink architecture, timing design and the rate at which 10/25GbE access links aggregate into 100/400GbE transport.
Wholesale Ethernet
Operators carrying services for multiple customers need predictable interface density, service separation, QoS and operational visibility. The ACX7000 family can cover both access-facing and aggregation roles, allowing the design to scale while maintaining a consistent operating model.
Large-enterprise metro
Large organizations linking campuses, data centers and cloud on-ramps may use ACX where service-provider-style routing, high-speed Ethernet and deterministic operations are justified. The business case should be compared with smaller enterprise routing platforms if metro-scale features are not required.
Data-center edge
ACX7100 can be relevant to data-center leaf, spine or edge roles where high port density and 400GbE connectivity align with the architecture. Confirm buffering, routing scale, optics and feature requirements against the exact intended topology rather than treating it as a generic switch replacement.
When another platform should be evaluated
An ACX Cloud Metro router is not automatically the best fit for every network edge. If the requirement is primarily branch security, SD-WAN, application inspection or user VPN termination, an enterprise edge or security platform may be more appropriate. If the requirement is a very small routed site with modest bandwidth and no metro-specific timing or service scale, a smaller router could offer a better cost and operational fit.
Within the ACX family itself, buyers should resist selecting a high-end model solely for future proofing. Oversizing increases acquisition cost, rack, power and optics requirements. Conversely, choosing an access router that is already close to its port or throughput ceiling can force an early replacement. A balanced design should leave realistic growth headroom based on forecast demand, not an arbitrary percentage.
There are also cases where a different ACX variant is the better answer even at the same throughput level. ACX7100-32C and 48L both publish 4.8 Tbps capacity, yet their port orientation is very different. ACX7332 and ACX7348 share a platform concept but provide different fixed low-speed density. The correct comparison is therefore based on the full interface map and physical deployment, not a single performance number.
Buyer questions to settle before requesting a quote
How many interfaces are needed on day one?
Count ports by speed and optic type, not only total ports. Separate customer-facing, access-facing, uplink, management and timing connections. Include migration ports that may be temporary.
What will traffic look like in three years?
Estimate aggregate throughput, peak utilization, service growth and whether uplinks move from 100GbE to 400GbE. Growth should influence both chassis choice and initial optic strategy.
Is precision timing required?
For mobile transport, document the timing architecture and profile. Timing support is a system requirement involving sources, topology and configuration, not merely a checkbox on the router.
What does the site allow?
Confirm usable rack depth and units, airflow direction, AC or DC power, available feeds, ambient conditions, grounding and maintenance clearance. These details can eliminate unsuitable models early.
Which software functions are mandatory?
List required routing, VPN, segment-routing, EVPN, assurance, telemetry and automation functions. Validate platform support and entitlement against the planned software release.
What resilience target applies?
Define whether the site needs redundant power feeds, control components, diverse uplinks, local sparing and a specific restoration target. Architecture and support coverage should match business criticality.
Procurement and quotation guidance for Dubai and UAE projects
A complete ACX quotation should be built from the target architecture rather than from a chassis part number alone. At minimum, the quote needs the exact platform variant, quantity, power option, airflow requirement where selectable, intended optics, breakout cables where required, software entitlement, support coverage and any modular I/O components. If the deployment is redundant, the quote should make clear whether the hardware population supports the intended failure model.
Availability and lead time should be treated as quotation-time variables. Enterprise routing portfolios change over time, and individual hardware, optics, license or support SKUs may have different fulfillment schedules. FourTeck can prepare the request around the required deployment date and identify which items need particular attention. Buyers planning a multi-site rollout should also state whether all sites must ship together or can be phased.
For projects involving installation or migration, include the scope of services in the initial request. Rack-and-stack, fiber patching, configuration, testing, cutover assistance and post-migration validation are different work packages. Defining them early gives both the technical and commercial teams a clearer basis for planning and reduces ambiguity between equipment supply and implementation responsibility.
Deployment journey
Define the role
Place the router in the target topology and identify every service it must carry.
Build the port map
Translate circuits into physical speeds, optic types, breakout needs and redundancy pairs.
Validate the site
Confirm rack space, depth, power, airflow, environment and maintenance access.
Align software
Check required protocols, scale, entitlement, release compatibility and automation integration.
Plan migration
Document staging, testing, coexistence, cutover, rollback and acceptance criteria.
Decision recap
Match access, aggregation or lean-edge role to the platform architecture rather than selecting by brand family alone.
Size both total throughput and the actual distribution of Ethernet speeds needed now and later.
Confirm the required software level, capacity basis, term and support coverage before final pricing.
Validate optics, breakout modes, routing features and interoperability against the intended software release.
Treat power, cooling, rack depth, environment and timing design as procurement inputs, not post-delivery details.
Leave justified headroom and choose modularity only where the forecast shows it will produce value.
What FourTeck needs from the buyer
For an accurate Juniper ACX Cloud Metro quotation, share as much of the following information as is available. An early-stage project does not need every answer, but each confirmed input reduces ambiguity and helps identify the correct hardware and commercial structure.
Frequently asked questions
Are all Juniper ACX Cloud Metro Routers the same capacity?
No. The portfolio ranges from compact access systems such as ACX7020 and the 360 Gbps ACX7024 family to multi-terabit aggregation platforms. Capacity, port mix and chassis architecture vary significantly, so the model must be selected for the intended role.
Does ACX7000 support 400GbE?
Yes, selected ACX7000 platforms support 400GbE interfaces. The exact number of ports, breakout options and supported optics depend on the model. ACX7100, ACX7300-series platforms and ACX7509 provide different approaches to high-speed connectivity.
Can ACX7024 be used for outdoor or harsh environments?
ACX7024 is positioned as an industrial-temperature-rated platform, but the complete installation environment still needs validation. Enclosure design, airflow, humidity, power, dust exposure and site standards can affect suitability. ACX7024X has a different commercial-temperature positioning.
Are transceivers included with an ACX router?
Optics should be treated as separate design and quotation items unless the commercial offer explicitly states otherwise. The required transceivers depend on speed, reach, fiber, wavelength plan, link partner and supported port mode.
Do ACX platforms require software licenses?
Juniper publishes ACX software entitlements in multiple capacity and feature tiers, with subscription and perpetual structures. The commercial requirement should be confirmed for the selected platform, intended features and support term even where the device does not technically require a license key to boot.
Which ACX model is best for Dubai?
There is no single best model for the city. A controlled data-center aggregation node may justify ACX7100 or ACX7509, while a compact access location may fit ACX7024. The correct choice depends on topology, ports, traffic, timing, site conditions, software and resilience requirements.
Build the right Juniper ACX Cloud Metro configuration for your Dubai network
Share your network role, expected capacity, port map, optics, power environment and software requirements. FourTeck can help turn those inputs into a technically aligned ACX model shortlist and a quotation-ready configuration without assuming that the largest platform is automatically the right one.