+49 6430 9227117
JUNIPER ACX · TPM FOR EDGE ROUTING

Juniper ACX Series Maintenance — vendor-independent service for edge routing

We service Juniper ACX edge routers after factory warranty and Juniper Care — vendor-independent, with OEM line cards, routing engines, power supplies and optics, SLA up to 24×7×4. Complete family: ACX710 (compact aggregation), ACX5448 (cloud metro), ACX7100/7332/7509 (carrier-class aggregation). 30 to 60 percent below Juniper Care, up to 70 percent on EOSL generations.

Which ACX models we service

ACX platforms are Juniper's edge and aggregation router family for service provider use cases — mobile backhaul (4G/5G), MPLS edge, metro Ethernet, cloud metro aggregation. Unlike the MX series, ACX platforms are optimized for higher volumes (hundreds to thousands of devices per carrier network), with more compact form factors and service-provider-specific features like TWAMP, TIM-Sync and SyncE.

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)

Why TPM maintenance for Juniper ACX

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.

30–60 %
Savings vs. Juniper Care
Volume SLA
Service provider fleets with 100-2,000+ devices
Cell-Site
4h onsite replacement at mobile backhaul sites
Sync features
SyncE, PTP, TIM stay functionally active

Generations timeline & TPM coverage

Per hardware generation: vendor phase (slate) and TechCare coverage window (teal) up to ~5 years post-OEM EOSL.

EOSL status of ACX generations

ACX generations follow a 7-9 year Juniper lifecycle. Early ACX5048/ACX5096 (predecessors of current generation) have largely reached EOSL. ACX710, ACX5448, ACX7100 family are current.

Model family Released OEM support ends TPM status
ACX5048 / ACX5096 (Vorgänger) 2015 2023–2024 Recommended
ACX710 2019 2027–2028 Supported
ACX5448 2020 ca. 2027+ Supported
ACX7100 / ACX7332 / ACX7509 2021+ ca. 2028+ Supported

As of 2026. EOSL data based on official vendor roadmaps and subject to change. Binding case-by-case information available on request.

What we deliver

OEM original parts

Our warehouse stocks OEM original components, including for end-of-life generations.

Onsite engineer

German-speaking technicians throughout DACH, 4-hour response time guaranteed.

Flexible SLA per system

Parts Only, 5×9 NBD or 24×7×4 — freely combinable by location and criticality.

Multi-vendor contract

One contract for Juniper and all other vendors. No more individual contracts.

EOSL tracking & reporting

Monthly SLA reports, asset overview, automatic EOSL notifications.

Junos & software stay

Junos OS, Mist Cloud subscription and all Juniper software licenses independent.

FAQ on ACX-Series maintenance

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: Juniper Care 200,000-300,000 EUR/year, TechCare 90,000-140,000 EUR. ACX5448 fleet for cloud metro aggregation correspondingly, ACX7332 fleet smaller but higher in absolute terms 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.
Can we have ACX and other Juniper lines (EX, QFX, MX, SRX) in the same contract?
Yes. Multi-class contracts are our strength — ACX as edge aggregation and mobile backhaul, MX as carrier backbone, QFX as data center fabric, EX as campus switching, SRX as security gateway, plus Mist as wireless — all in one contract, one point of contact, one SLA report set. For service provider customers with combined fleets, this is the standard configuration.
How fast do we get a quote?
Within 48 hours after receipt of your inventory list with model, generation, device count, site distribution (cell sites, metro, data center) and desired SLA tiers.
Service performance

Real actuals Q1 2026 — straight from our ITIL ticketing.

99,2 %
Tickets resolved within agreed response time
2,4 h
Avg. first response on 4h SLA tier
88 %
First-time fix on initial dispatch
97 %
Spare part on site within 4 h, DACH depots
More from Juniper

Other Juniper models and service