OEM End-of-Support Jargon Decoded: EOSL, LDoS & More

Why the jargon matters: the support cliff

Somewhere in your estate there is a server, switch or storage array approaching a date after which its maker will no longer support it. Log a fault after that date and there is no engineer to dispatch, no spare part to ship, and no fix to download. Support does not taper off gently — it stops. That is the support cliff, and every hardware vendor has its own name for the edge of it.

The problem for a UK IT manager or procurement lead is that the words are deliberately inconsistent. One vendor's datasheet says 'End of Support Life', another's says 'Last Date of Support', a third talks about 'Sustaining Support', and two of them do not publish a model date at all — they bury it inside a per-unit entitlement record. Miss the distinction and you can budget a refresh for the wrong year, or assume a box is covered when its contract quietly lapsed months ago.

This article is a neutral glossary. It decodes what each major OEM actually means by 'end of support', explains why the terminology differs, and shows you how to find the real date for your own equipment. If you have already decided you need to act and want the commercial angle, our sister page on when OEM support ends and what it costs covers renewals and alternatives; here we stay on the terminology and the how-to.

The three milestones every vendor has (even when they name them differently)

Under all the branding, hardware support follows the same shape across vendors. There is a moment the product stops being sold, a stretch where it is still fully supported, and a final date after which support ends. The vendors agree on the shape and disagree on the vocabulary.

First comes end-of-sale (sometimes end-of-life, end-of-marketing or 'product withdrawn'). This means you can no longer buy the kit new. It does not mean support has ended — support usually continues for years afterwards, which is exactly where the confusion starts. 'End of life' sounds terminal but is often the least urgent milestone.

Then comes the support window, during which the OEM offers its paid maintenance programmes — HPE Tech Care, Dell ProSupport, Cisco SmartNet Total Care and the rest. Finally comes the true cliff: the last date the vendor will honour a support contract at all. This is the date that governs your risk, and it is the one hidden behind the most varied jargon.

• •End-of-sale / product withdrawn: you can no longer buy it new — a warning shot, not the cliff.
• •Support window: the years the OEM sells maintenance for the product (the tiered programmes below).
• •The true cliff: the final date the OEM will service the product — call it EOSL, LDoS, Sustaining Support or a per-serial expiry depending on the badge on the box.

HPE: End of Support Life (EOSL) and Tech Care tiers

HPE is the vendor that gives the cliff its most widely borrowed name. HPE's term for the final date is End of Support Life, almost always abbreviated to EOSL. After a product's EOSL, HPE will no longer sell or renew support on it — no contract, no spares guarantee, no fixes. Because HPE publishes these dates fairly openly, 'EOSL' has become the generic shorthand many people (and third-party providers) use for any vendor's end of support, even when that vendor calls it something else.

During the supported years, HPE sells maintenance under HPE Tech Care Service, which replaced the older Foundation Care and Pointnext branding. Tech Care comes in three tiers: Basic (business-hours cover with next-business-day on-site response), Essential (24x7 cover with 4-hour on-site response) and Critical (24x7 with a 6-hour call-to-repair commitment). If your paperwork still mentions Foundation Care or Pointnext, it predates the current naming.

Once a ProLiant, Alletra or networking box passes HPE EOSL, your options narrow to refresh or independent support; our HPE Tech Care alternative page explains how post-EOSL HPE hardware can stay under cover. Note that Juniper became part of HPE in 2025, so some Juniper support may increasingly sit under HPE processes over time.

Cisco: End-of-Sale, then LDoS — the date that actually bites

Cisco publishes a formal end-of-life bulletin for each product with a chain of dated milestones, and it is easy to fixate on the wrong one. The milestone people notice first is End-of-Sale (EoS) — the last day you can order the product. But EoS is not the cliff. The date that matters is the Last Date of Support (LDoS): the final day Cisco will provide any support, including hardware RMA and TAC assistance, for that product.

Between EoS and LDoS, Cisco typically continues support (often for around five years for hardware), which is why a switch marked 'end-of-life' on a datasheet can still be fully serviceable for years. Read the bulletin to the bottom and use the LDoS row — that is your true expiry.

During the supported period Cisco hardware cover is bought as SmartNet Total Care (SNTC), which handles hardware replacement and TAC access. Software entitlement is a separate matter, licensed through SWSS or DNA subscriptions — so it is entirely possible to have valid hardware RMA cover while your software support has lapsed, or vice versa. After LDoS, independent support is the route to keeping the hardware serviceable; see our Cisco SmartNet alternative and the Cisco third-party maintenance overview.

Oracle: Premier, then Extended, then Sustaining Support

Oracle uses a completely different model, governed by its Lifetime Support Policy, which runs a product through three named, sequential phases rather than to a single hard date. This applies to Oracle's systems hardware — SPARC servers, Exadata, the ZFS Storage Appliance and legacy Sun kit — under Oracle Premier Support for Systems.

The phases are Premier Support (the full, current support period), then Extended Support (continued support, often at a premium and for a limited window), and finally Sustaining Support. Sustaining Support is the phrase to watch: while Oracle will still take your call under Sustaining Support, it provides no new fixes, no new updates and no new certifications. In practice, a product in Sustaining Support has already gone over the meaningful cliff — you get help with existing material, not new engineering.

So when an Oracle account manager says a system is 'still supported', ask which phase. Premier is healthy; Extended is a countdown; Sustaining means the fixes have stopped. For hardware break-fix on Oracle systems that have aged out or where you want off the Oracle renewal cycle, see our Oracle support alternative.

Dell and Lenovo: there is no model date — it is per unit

Here is the distinction that catches the most people out. Dell and Lenovo do not, as a rule, publish a single model-wide end-of-support date you can look up the way you can for a Cisco switch. Support is tied to the individual unit, so the right question is never 'when does the R750 go end of support?' — it is 'when does *this* R750, service tag ABC1234, go end of support?'

Dell attaches entitlement to each machine's service tag. Dell ProSupport is sold in tiers — Basic Hardware Service, ProSupport, and ProSupport Plus (which adds predictive failure analytics via SupportAssist) — and each unit carries its own contract with its own expiry. Two identical servers bought twelve months apart can therefore fall off support twelve months apart. Dell does not publish a blanket model EOSL, so a lookup by service tag is the only reliable answer; our Dell ProSupport alternative page covers what happens when that entitlement runs out.

Lenovo works the same way, publishing end-of-service per serial number. Lenovo Premier Support runs in Foundation, Essential and Advanced tiers (with a Premier Support Plus option), and firmware and XClarity management updates flow through a Lenovo entitlement. Because the date lives against the serial, an accurate inventory of serial numbers is the prerequisite to knowing your exposure — see the Lenovo Premier Support alternative for the post-expiry picture.

IBM, NetApp and Juniper: withdrawal notices and separate software entitlement

The remaining major vendors add their own wrinkles. IBM sells hardware maintenance through ServicePac and Maintenance Agreements; a Warranty Service Upgrade lifts the base entitlement, with response options such as On-Site next-business-day or On-Site 24x7x4. The thing to watch with IBM is that it withdraws support on older machine types fairly aggressively — support is retired by machine type, so track IBM's withdrawal-from-support notices for your specific type and model. Our IBM hardware maintenance alternative covers kit that has been withdrawn.

NetApp sells hardware and support under SupportEdge, across tiers from Standard and Premium to the AI-enabled Advisor and Expert levels. Crucially, ONTAP and Element software updates are not bundled with hardware cover — they require a separate NetApp software entitlement. So a NetApp array can be under hardware support while its right to new software releases has expired, or the reverse. The NetApp SupportEdge alternative page addresses the hardware side once controllers age out.

Juniper hardware is covered by Juniper Care (J-Care) in Core, Next Day and Same Day tiers, with Juniper Care Plus adding proactive and managed service; Junos software entitlement is, again, separate. As noted above, Juniper became part of HPE in 2025, so watch for its lifecycle and support processes converging with HPE's over time. For end-of-support Juniper hardware, see the Juniper Care alternative.

How to find YOUR kit's real end-of-support date

Terminology aside, the practical job is to pin down the actual date for each box you own. The method depends on whether your vendor publishes by model or by unit.

For vendors that publish a model-wide date — chiefly Cisco, and to a hedged degree HPE — start from the model's official end-of-life bulletin or support-lifecycle page and read down to the final row: Cisco's Last Date of Support, HPE's End of Support Life. For vendors that publish per unit — Dell by service tag, Lenovo by serial number — you cannot answer the question from the model name at all; you must feed the specific service tag or serial into the vendor's warranty-and-entitlement lookup. Oracle systems are checked by support phase in the Lifetime Support Policy documentation for that product line.

To speed up a fleet-wide first pass across mixed vendors, our free server and network EOSL checker and storage end-of-life checker hold curated, source-cited dates for common flagship models — and, importantly, they are honest about the gaps: where Dell and Lenovo tie support to the unit rather than the model, the tools say so instead of inventing a date. Treat any tool as a starting point and confirm the binding date against the vendor's own entitlement record for your exact service tag or serial before you rely on it commercially.

• •Cisco: read the model's End-of-Life bulletin down to the Last Date of Support (LDoS) row.
• •HPE: check the product's End of Support Life (EOSL) in the HPE Support Center / product lifecycle pages.
• •Dell: look up the specific service tag in Dell's warranty & entitlement tool — there is no model-wide date.
• •Lenovo: look up the specific serial number for its end-of-service — again, per unit, not per model.
• •Oracle: identify which Lifetime Support phase the system is in — Premier, Extended or Sustaining.
• •Cross-check a mixed fleet with the free server/network and storage EOSL checkers, then verify the binding date with the OEM.

What to do when you hit the cliff: refresh or extend on TPM

Once you know a box's real end-of-support date, the decision is straightforward in shape: refresh the hardware, or keep it running under independent support. The honest tie-breaker is whether your risk is hardware or software.

Third-party maintenance (TPM) — independent post-warranty and post-EOSL support — can keep serviceable hardware under cover for years past the OEM cliff, and at an indicative 50-70% less than OEM support net prices (a band Gartner cited in its 2019 Market Guide for third-party hardware maintenance; treat it as indicative, not a promised per-device figure). That makes TPM a strong fit for stable, well-understood kit where the value is spare parts and on-site break-fix, letting you defer a costly refresh. Our TPM savings calculator and hub lets you estimate the saving against your own current renewal spend.

But be clear about the limit, because it is the whole point of understanding the jargon. TPM covers hardware break-fix, spare parts, on-site engineering and continued cover past OEM end-of-support. It does not supply the OEM's software updates, firmware or security patches — those still require the OEM's software entitlement. So if the exposure is an unpatchable security or compliance risk in the software or firmware, the honest answer is a refresh, not a maintenance contract. If the exposure is purely 'the vendor won't ship a spare disk any more', TPM is exactly the tool. For the fuller comparison see TPM vs OEM support and what third-party maintenance is, or start at the hardware maintenance hub.