Juniper Networks ACX-Series Edge Router Maintenance
side by side.

ACX710 · compact aggregation

ACX710 (1U compact, mobile-backhaul-focused)

ACX5448 · cloud metro

ACX5448 (1U cloud metro, 25/100G aggregation)

ACX7100/7332/7509 · carrier-class aggregation

ACX7100 · ACX7332 · ACX7509 (modular, carrier-class)

Components & optics

Line cards · power supplies · fan trays · routing engines · 1/10/25/100/400G optics · service provider sync (SyncE, TIM)

EOSL status of ACX generations

ACX maintenance is a volume business — typical carrier fleets have 200-2,000+ ACX devices distributed across hundreds of sites (cell sites, MPLS PEs, metro aggregation nodes). At these volumes, Juniper Care terms add up to significant budgets — TPM reduces this to 40-50 percent. For mobile backhaul fleets with ACX710 in 4G/5G cell sites, economics are particularly attractive: 4-hour onsite replacement at cell sites is operationally crucial, and TPM pricing makes this SLA level affordable for many carriers in the first place.

We service ACX with OEM line cards, routing engines, power supplies and optics from our own warehouse. ACX-specific service provider features like TWAMP (Two-Way Active Measurement Protocol), TIM-Sync, SyncE and PTP (IEEE 1588v2) are part of the Junos firmware and continue without licensing — also all MPLS, BGP, segment routing and service provider VPN functions. Code updates to newer Junos versions require an active Juniper contract.

The full OEM-vs-TPM matrix (spare parts, SLA tiers, language, sub-outsourcing, compliance docs, reporting) is the same for every Juniper Networks line — see the Juniper Networks battle card.

BAIT/MaRisk documentation package, DORA Art. 28 contract template, ISO 27001 and GDPR-compliant media handling apply identically to every Juniper Networks line — details on the Juniper Networks battle card.

Same four steps for every Juniper Networks line: inventory → fixed-price quote in 48 h → contract (BAIT/MaRisk/DORA hooks) → hand-over with spare-parts provisioning. Details on the Juniper Networks battle card.

Which ACX models do you service?

Complete ACX family: ACX710 (1U compact for mobile backhaul and small aggregation), ACX5448 (1U cloud metro with 25/100G aggregation), ACX7100, ACX7332, ACX7509 (modular carrier-class for metro aggregation and MPLS edge). Plus older ACX5048/ACX5096 generations (EOSL reached). Including all line cards, routing engines, power supplies and sync modules for service provider features.

What does TPM cost for ACX compared to Juniper Care?

30 to 60 percent savings. For a typical mobile backhaul fleet of 500 ACX710 with 24×7×4 onsite at cell sites, TechCare is roughly 55% below the Juniper Care price. ACX5448 fleets for cloud metro aggregation are similar; ACX7332 fleets are smaller but more expensive to maintain per box. Volume savings make TPM particularly attractive for large carrier fleets.

Do SyncE, PTP and service provider features continue to work?

Yes. SyncE (Synchronous Ethernet), PTP/IEEE 1588v2 (for mobile backhaul time synchronization), TIM-Sync, TWAMP (Two-Way Active Measurement Protocol), MPLS stack including Segment Routing, BGP-LU, all layer 2 and layer 3 VPN functions are part of the Junos firmware and continue to work without licensing. Code updates to newer Junos versions require an active Juniper contract — usually uncritical with stable service provider configurations.

Can you service older ACX5048/ACX5096?

Yes. ACX5048 and ACX5096 (released 2015, EOSL 2023-2024) are still productive in some DACH service provider fleets — typically in metro aggregation roles or older mobile backhaul setups. We stock switches, power supplies and sync modules for these generations. For very old configurations we use certified refurbishing partners from the service provider networking ecosystem.

Which SLA levels do you recommend for ACX?

ACX in cell sites and mobile backhaul: 24×7×4 onsite replacement is standard — mobile service outages have direct end customer impact and SLA penalty risks. For ACX in metro aggregation roles with high redundancy (dual homing, ring topologies), 5×9 NBD can be economical. For carrier-class ACX7332/7509 in MPLS edge roles with tier-1 service: 24×7×4 recommended. Multi-SLA contracts with mix of 24×7×4 (critical sites) and 5×9 NBD (secondary sites) are standard in practice.

How does ACX maintenance differ from MX maintenance?

MX is a carrier backbone platform with modular chassis and MPCs/MICs — more complex hardware architecture, higher maintenance complexity per box. ACX is an edge aggregation platform with more focused form factor — simpler hardware architecture but higher volumes. From a maintenance perspective: MX contracts are 'deep' (few boxes with complex components), ACX contracts are 'wide' (many boxes with standardized components). We cover both use cases with the same service quality.