Juniper Networks MX-Series Router Maintenance
side by side.
TechCare TPM vs. Juniper Care / Care Plus. Cost range, EOSL advantages, migration path and DACH compliance at a glance — for IT leadership and procurement.
Cost comparison
Example Juniper EX4300-48P with 4-year Juniper Care 24×7×4: TechCare TPM roughly 36–54% below the OEM price.
Active EOSL lines
- MX240 / MX480 / MX960 (Mid/High-End Edge) · EOSL 2026-06-30
- MX204 / MX10003 / MX10008 / MX10016 (aktuelle Edge) · EOSL 2030-06-30
- MX5 / MX10 / MX40 / MX80 (legacy Compact) · EOSL 2022-12-31
Which MX models we service
- MX204/MX240/MX480/MX960 · mid/high-end
- MX204 (compact) · MX240 · MX480 · MX960
- MX2008/MX2010/MX2020 · carrier backbone
- MX2008 · MX2010 · MX2020
- MX10003/MX10008/MX10016 · Universal Chassis
- MX10003 · MX10008 · MX10016
- MPCs, MICs & components
- MPC1E/2E/3E/4E/5E/7E/8E/9E · MIC1/2/3/6 · routing engines (RE-S/RE-X/RE-MX2K) · switch fabric boards · power supplies · 1/10/40/100/400G optics
EOSL status of MX generations
| Generation | Released | End of vendor support | TechCare TPM |
|---|---|---|---|
| MX240 / MX480 (early generations) | 2008–2010 | 2020–2022 | Recommended |
| MX960 (early generations) | 2009–2011 | 2021–2023 | Recommended |
| MX204 | 2017 | 2025–2026 | Supported |
| MX2008 / MX2010 / MX2020 | 2013–2015 | 2025–2027 | Supported |
| MX10003 / MX10008 / MX10016 | 2018+ | ca. 2028+ | Supported |
Why TPM maintenance for Juniper MX
MX-Series maintenance is the highest lever in the Juniper maintenance portfolio. Juniper Care for a fully populated MX2020 with 16 MPCs, redundant routing engines and 8 power supplies is one of the largest annual budget items — and MX2020/MX10016 are not uncommon in carrier and large enterprise WAN backbones. TPM reduces these maintenance terms to 35-50 percent without limiting MPC or MIC functionality — Junos on MX continues to work without licensing, all MPLS, BGP, OSPF, IS-IS and VPN functions stay active.
We service MX with OEM MPCs, MICs, routing engines, switch fabric boards, power supplies and optics from our own warehouse. We stock MX-specific components for all generations — MPC1E to MPC9E, MIC1 to MIC6, RE-S to RE-MX2K. For very old MPC1/MPC2 modules (early MX240/480/960 from 2008-2010), some components have become rare — we use certified refurbishing partners from the carrier networking ecosystem.
OEM vs. TechCare — where the switch pays off
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.
Stays with Juniper Networks
- Junos software licenses
- Mist Cloud subscription
- Juniper TAC software tickets
Moves to TechCare
- Hardware defects (memory, disk, PSU, mainboard, modules)
- 24×7×4 on-site SLA with German-speaking field service
- Spare-parts logistics DACH + global hub network
- Fixed-price contract in 48 h, one inventory — one contract
DACH compliance by design.
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.
Migration path from first contact to hand-over.
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.
FAQ on MX-Series maintenance
- Which MX models do you service?
- Complete MX family: MX204 (compact 1U edge), MX240, MX480, MX960 (classic mid/high-end), MX2008, MX2010, MX2020 (carrier backbone) and MX10003, MX10008, MX10016 (Universal Chassis). Including all MPCs (MPC1E to MPC9E), MICs (MIC1 to MIC6), routing engines (RE-S, RE-X, RE-MX2K), switch fabric boards and power supplies.
- What does TPM cost for MX compared to Juniper Care?
- 30 to 60 percent savings. For an MX480 with 4 MPCs, redundant routing engines and 24×7×4, TechCare is roughly 55% below the Juniper price; for an MX2020 with full population also roughly 55% below Juniper Care. The MX10008 shows a similar ratio. For EOSL MX240/480 we see up to 70 percent — Juniper often no longer offers renewal.
- Can you service older EOSL MX240/480/960?
- Yes, a focus area of our Juniper business. MX240/480 (2008-2010, EOSL 2020-2022) and early MX960 (2009-2011, EOSL 2021-2023) are still productive in DACH carrier and enterprise WAN backbones. We stock MPCs, MICs, routing engines and power supplies for these generations. For very old MPC1/MPC2 modules we use certified refurbishing partners from the carrier networking ecosystem.
- Do MPLS, BGP and VPN functions continue to work without a Juniper contract?
- Yes. Junos on MX continues to work without licensing — MPLS stack (LDP, RSVP-TE, Segment Routing), BGP (eBGP, iBGP, BGP-LU, BGP-EVPN), OSPF/IS-IS, all layer 2 and layer 3 VPN functions (VPLS, EVPN-VXLAN, L2VPN, L3VPN), MPLS Fast Reroute, BFD and all carrier-class features stay functionally active. Code updates to newer Junos versions require an active Juniper contract.
- Which SLA levels do you recommend for MX?
- MX as carrier backbone or primary WAN edge: 24×7×4 with German-speaking onsite engineer is standard — an outage affects entire carrier backbones or multi-site WANs. MX204 as edge router in branch sites can be sufficiently covered with 5×9 NBD depending on redundancy concept. For MX2020/MX10016 in carrier core roles with high redundancy (active-active or N+1), 5×9 NBD can be economical — single component failures are absorbed by the backup path.
- What about Juniper Paragon Active Assurance?
- Paragon Active Assurance (service assurance platform for MX service provider workflows) is a software subscription independent of hardware maintenance. Customers actively using Paragon should keep the subscription with Juniper — hardware maintenance runs in parallel via TPM. Paragon probes and service monitoring stay functionally active.