JUNIPER SRX · TPM FOR SECURITY GATEWAYS

Juniper SRX Series Maintenance — vendor-independent service from branch to carrier-class

We service Juniper SRX security gateways after factory warranty and Juniper Care — vendor-independent, with OEM SPCs, IOCs, routing engines and power supplies, SLA up to 24×7×4. Complete family: SRX300/320/340/345/380 (branch), SRX1500/4100/4200/4600 (mid/enterprise), SRX5400/5600/5800 (carrier-class). 30 to 60 percent below Juniper Care, up to 70 percent on EOSL models.

Quote in 48 h Calculate savings

Which SRX models we service

SRX platforms cover the entire security gateway spectrum — from small branch office firewalls (SRX300) to carrier-class multi-service gateways (SRX5800 with thousands of concurrent sessions). Three model classes: branch SRX300 series, mid/enterprise SRX1500-4600 and carrier SRX5400/5600/5800 with modular chassis architecture.

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

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 drives five to six-figure maintenance amounts per year — 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.

30–60 %

Savings vs. Juniper Care

Software stays

Junos, IDP, ATP subscription independent

48 h

Fixed-price quote after receipt of your inventory

4 h

Onsite response time with 24×7×4 SLA

Generations timeline & TPM coverage

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

2009

2013

2017

2021

2025

2029

2033

Today · 2026

SRX300 / SRX320 / SRX340 / SRX345
2017–2026
TPM until2031+
Supported
SRX380
2019–2028
TPM until2033+
Supported
SRX1500
2016–2025
TPM until2030+
Recommended
SRX4100 / SRX4200
2017–2026
TPM until2031+
Supported
SRX4600
2019–2028
TPM until2033+
Supported
SRX5400 / SRX5600 / SRX5800
2009–2027
TPM until2032+
Supported

EOSL status of SRX generations

SRX generations follow a 7-9 year Juniper lifecycle. Early SRX300 models are approaching EOSL, SRX1500/4100 are current, SRX5400/5600/5800 have a long roadmap.

Model family	Released	OEM support ends	TPM status
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

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.

Comparison

TechCare vs. Juniper Networks SRX Security Gateways

Concrete SLA tiers, OEM comparison, coverage details and source footnotes — on a print-friendly page.

Open 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. An SRX1500 HA pair with 24×7×4 costs 4,000 to 6,500 EUR/year with Juniper, 1,700 to 3,000 EUR with TechCare. SRX4600 correspondingly 8,000-12,000 EUR Juniper Care, 3,500-5,500 EUR TechCare. SRX5800 with full population 60,000-90,000 EUR Juniper Care, 25,000-40,000 EUR with TechCare. SRX300 series 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.

Can we have SRX and other Juniper lines (EX, QFX, MX) in the same contract?

Yes. Multi-class contracts are our strength — SRX as security gateway, EX as campus switching, QFX as data center fabric, MX as WAN edge, plus Mist and ACX — all in one contract, one point of contact, one SLA report set. Plus all other vendors (Palo Alto, Fortinet, Check Point, etc.) in the same construct.

How fast do we get a quote?

Within 48 hours after receipt of your inventory list with model, generation, HA pair configuration and serial number.

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