Juniper Networks SRX Security Gateways 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
- SRX300 / SRX340 / SRX345 (Branch NGFW) · EOSL 2022-12-01
- SRX1500 / SRX4100 / SRX4200 (Mid-Market NGFW) · EOSL 2021-06-15
- SRX5400 / SRX5600 / SRX5800 (High-End Chassis NGFW) · EOSL 2027-09-15
- SRX380 / SRX1600 / SRX4300 / SRX4700 (aktuelle Plattform) · EOSL 2030-12-31
Which SRX models we service
- SRX300 series · branch
- SRX300 · SRX320 · SRX340 · SRX345 · SRX380
- SRX1500/4100/4200/4600 · mid/enterprise
- SRX1500 · SRX4100 · SRX4200 · SRX4600
- SRX5400/5600/5800 · carrier-class
- SRX5400 · SRX5600 · SRX5800
- Components & modules
- SPCs (Services Processing Cards) · IOCs (I/O Cards) · NPCs (Network Processing Cards) · routing engines · power supplies · fan trays
EOSL status of SRX generations
| Generation | Released | End of vendor support | TechCare TPM |
|---|---|---|---|
| SRX300 / SRX320 / SRX340 / SRX345 | 2017 | 2025–2026 | Supported |
| SRX380 | 2019 | 2027–2028 | Supported |
| SRX1500 | 2016 | 2024–2025 | Recommended |
| SRX4100 / SRX4200 | 2017 | 2025–2026 | Supported |
| SRX4600 | 2019 | 2027–2028 | Supported |
| SRX5400 / SRX5600 / SRX5800 | 2009 (mit Roadmap-Refreshes bis heute) | ca. 2027+ | Supported |
Why TPM maintenance for Juniper SRX
SRX hardware maintenance must be considered separately from SRX software subscription. Junos OS, IDP/AppSecure, UTM, Sky ATP/Advanced Threat Prevention, all security subscription functions are software licenses — they continue independently of hardware maintenance. What TPM replaces is the hardware layer: SPCs, IOCs, routing engines, power supplies, fan trays. With fully populated SRX5600/5800 with multiple SPCs and IOCs, Juniper Care quickly becomes a major annual budget item — TPM reduces this to 35-50 percent.
We service SRX with OEM SPCs (Services Processing Cards for crypto/stateful inspection acceleration), IOCs (I/O cards), NPCs (Network Processing Cards), routing engines and power supplies. For branch SRX300 series, maintenance use cases are simpler (standalone boxes, often as HA pair), for carrier SRX5800 more complex (modular chassis with redundant components). We cover both use cases with the same 24×7×4 onsite response time.
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 SRX-Series maintenance
- Which SRX models do you service?
- Complete SRX family: SRX300/320/340/345/380 (branch, standalone and HA pair), SRX1500 (mid-enterprise, most common configuration in DACH), SRX4100/4200/4600 (enterprise, NGFW with high throughput) and SRX5400/5600/5800 (carrier-class with modular chassis and multi-SPC architecture). Including all SPCs, IOCs, NPCs, routing engines and power supplies.
- What does TPM cost for SRX compared to Juniper Care?
- 30 to 60 percent savings. For an SRX1500 HA pair with 24×7×4, TechCare is roughly 55% below the Juniper price; for the SRX4600 also roughly 55%, and for an SRX5800 with full population roughly 55–60% below Juniper Care. The SRX300 series is significantly cheaper in absolute terms.
- What happens to security subscriptions like IDP, ATP and AppSecure?
- All security subscriptions are software licenses independent of hardware maintenance. Junos OS, IDP (Intrusion Detection/Prevention), AppSecure (Application Identification), UTM (Anti-Virus, Anti-Spam, Web Filtering, Content Filtering), Sky ATP / Advanced Threat Prevention — all continue via your existing subscription with Juniper. TPM replaces only hardware maintenance. Code updates and threat intelligence feeds stay active.
- Can you service SRX1500 approaching EOSL?
- Yes. SRX1500 (released 2016, EOSL from 2024-2025) is one of the most common SRX configurations in DACH mid-enterprise environments. We stock switches, SPCs, IOCs and power supplies. Junos OS on SRX1500 continues to work — code updates to newer Junos versions require an active Juniper contract. Usually uncritical with stable firewall configurations.
- Which SLA levels do you recommend for SRX?
- SRX as central NGFW or internet gateway: 24×7×4 with German-speaking onsite engineer is standard — outage affects internet connectivity or inter-site connectivity. For SRX in HA pair setups (active-passive or active-active), one box can fail without service outage — 5×9 NBD saves budget. SRX300 series in branch office sites: typically 5×9 NBD sufficient because branch outage tolerable.
- What about SSG / NetScreen legacy fleets?
- SSG and NetScreen platforms have been EOSL for over 10 years — Juniper retired the line in 2010-2012 in favor of the SRX series. If you still have SSG/NetScreen in use, that's a rare constellation requiring individual review. For small fleets (1-3 devices) we can supply spare parts from refurbishing pools, but typical recommendation is refresh to SRX300 series.