When hardware reaches end of OEM support, the manufacturer stops supplying replacement parts, closes technical support cases and will not renew the maintenance contract. The kit keeps running. What ends is the vendor’s obligation to fix it. You then have four choices: refresh, buy extended cover while the OEM still sells it, move to third-party maintenance, or carry the risk uninsured.
Most teams meet this date as a line in a renewal quote rather than as a decision. By then the options have narrowed. This article sets out the milestones in the order they actually arrive, what stops at each one, the four routes open to you, and the questions to settle before the date lands rather than after.
Need engineers on site in the UK, Europe or further afield?
Throne Solutions provides on-site IT field engineers across 60+ countries. Tell us your sites and the kind of cover you need, and we will come back with options and a quote.
The milestones, in the order they arrive
Vendors use different names for the same sequence, and the names matter because support entitlements hang off them. Cisco’s published End-of-Life Policy is a useful reference because the dates are defined rather than implied.
- End-of-life notification. The date the vendor makes the schedule public.
Cisco states that an end-of-sale notice typically comes six months before the end-of-sale date
itself. - End of sale (EOS). In Cisco’s words, “the Product is no longer offered for
sale after this date.” Park Place Technologies describes the equivalent announcement as the point
at which “the OEM is no longer producing or selling the particular piece of equipment.” - Last customer ship. Cisco sets this three months after the hardware
end-of-sale date. - Last day of support (LDOS). Cisco defines it as “the last date to receive
support as entitled by active service contracts.” After this, there is no contract to renew.
Between EOS and LDOS, entitlement erodes in stages rather than all at once. Under Cisco’s policy, routine hardware failure analysis runs for one year from end-of-sale; TAC support runs for five years from the hardware end-of-sale date; and replacement parts are available for five years from end-of-sale under the RMA process. Park Place Technologies puts the same pattern more bluntly: an end-of-life announcement “generally starts a 5-year phase-out of the equipment.”
Two timing rules catch people out. Cisco allows a customer to add a new hardware or application software support contract “for up to one (1) year from the EOS date,” and only if that contract ends no later than LDOS. Renewals are permitted on the same condition. So the window to buy cover closes well before support itself does — if you let the attachment period lapse, you cannot simply buy back in later.
What actually stops
End of support is not a kill switch. Your switches keep switching and your arrays keep serving. What you lose is specific:
- Parts. Park Place notes that after end of service life, “parts may not be
readily available from the OEM, since production has stopped.” This is usually the binding
constraint, not the engineering. - Vendor maintenance. At end of service life the OEM “no longer sells, provides
operating system updates for, or renews support agreements on the hardware.” - Firmware and security patches. Once development stops, fixes stop. Anything
found after that date stays unpatched on that platform, which is the part your auditors and your
cyber insurer will ask about. - The escalation path. No contract means no case number and no vendor engineer
at 2am.
Note what does not stop: your obligation to keep the service up. If the equipment sits behind a customer-facing SLA, the end of OEM support changes nothing about what you owe your own customers. That gap between obligation and entitlement is the real exposure.
The four options
1. Refresh the hardware
The vendor’s preferred answer, and sometimes the right one — particularly where the platform is genuinely slower, hungrier or incompatible with where you are going. The cost is rarely the box: it is the project around it. Budget for the migration, the overlap period, the rack-and-stack, and the disposal of what comes out. If the estate is spread across sites, the limiting factor is engineer availability at each address, not procurement.
2. Buy extended OEM cover while you still can
Where the vendor offers a post-EOS extension and the attachment window is still open, this is the lowest-friction route. Two cautions: the quote usually rises, and the clock is fixed. Cisco’s policy caps any new or renewed contract at the last day of support, so extended cover buys you time, not an open-ended arrangement. Check the LDOS date before you accept a three-year renewal that cannot legally run three years.
3. Move to third-party maintenance
An independent maintainer takes on the hardware the OEM has walked away from, usually with parts held in stock and engineers trained on the platform. Park Place Technologies notes that at end of service life “third-party hardware maintenance is traditionally available for your hardware,” and that where an OEM agreement is still on offer “it can often be very expensive.” This route keeps working kit in service past the vendor’s calendar and is the standard answer for stable, well-understood platforms that still do their job. Our
third-party maintenance and
hardware maintenance pages set out how the cover is structured, and whether it is the right call against staying with the vendor is a decision worth making platform by platform.
4. Run it uncovered
Sometimes defensible: a non-critical platform, a short remaining life, a cold spare on the shelf. It stops being defensible the moment nobody has written down which systems are in this state and what the plan is when one fails. Uncovered by decision is a strategy. Uncovered by drift is an incident waiting for a date.
What to settle before the date lands
- Build the list. Serial number, platform, site, EOS date, LDOS date, current
contract end. Most estates do not have this in one place, and the exercise alone usually finds kit
nobody knew was still in production. - Tier it by consequence, not by age. What breaks downstream if this box stops?
That answer, not the purchase date, decides which option each item gets. Our guide to
SLA-based IT support covers how to
tier an estate by business impact. - Check the parts question per platform. Secondary-market availability varies
enormously between a mainstream switch and a niche controller. Ask any prospective maintainer
where the spares for your specific models are held and how they reach each site. - Confirm the compliance position. If a framework or an insurer requires
supported, patchable systems, that is a constraint on the decision rather than an input to it. - Plan the exit. Whatever comes out needs collecting, wiping and documenting.
IT asset disposal is part of the refresh
project, not an afterthought. - Fix the coverage gaps first. If the estate includes countries where you have
no engineers, sort delivery before you sort contracts. We cover that in
global field services.
Planning cover for a new contract or region?
Send us the countries, sites and service level you need. It takes two minutes, and there is no obligation.
Frequently asked questions
What does end of OEM support mean?
It means the manufacturer no longer has an obligation to fix the equipment. Park Place Technologies describes end of service life as the point at which the OEM “no longer sells, provides operating system updates for, or renews support agreements on the hardware.” The equipment itself keeps working; the vendor’s responsibility for it ends.
Does hardware stop working at end of life?
No. End of life and end of service life are commercial and contractual milestones, not technical ones. Nothing in the equipment changes on the date. What changes is parts availability, patching and your route to escalation.
How long after end of sale does support last?
It depends on the vendor and the product class. Under Cisco’s published policy, hardware TAC support runs five years from the hardware end-of-sale date and replacement parts are available for five years from end-of-sale under the RMA process, while routine failure analysis runs for one year. Park Place Technologies describes an end-of-life announcement as generally starting a five-year phase-out. Always read the specific product’s own bulletin — the dates are published per platform.
Can I still buy a support contract after end of sale?
For a limited period. Cisco permits a new hardware or application software support contract “for up to one (1) year from the EOS date,” and only where that contract ends no later than the last day of support. Once that attachment window closes, the OEM route is gone and the realistic options are third-party maintenance or replacement.
Is third-party maintenance safe for end-of-life hardware?
It is the normal route for it. Park Place Technologies notes that third-party hardware maintenance is traditionally available once a platform reaches end of service life. What varies between providers is parts depth for your specific models, engineer coverage at your specific sites, and how the response commitment is written. Judge a maintainer on those three, in writing.
What happens to firmware and security patches?
They stop when development stops. A third-party maintainer can keep hardware running and replace failed components, but no independent provider can issue the vendor’s firmware. Where a platform must stay patched for compliance reasons, that points towards replacement rather than extended maintenance.
Should we refresh or extend?
Refresh where the platform no longer fits the workload, where compliance demands a patchable system, or where parts for your models are genuinely scarce. Extend where the equipment still does its job, the spares position is sound, and the money is better spent elsewhere. The honest answer is usually different for different tiers of the same estate.
Hardware support after the OEM walks away
Throne Solutions provides on-site IT field engineering and hardware support across the UK and Europe, with coverage in 60+ countries. If you have an estate approaching end of OEM support — or already past it — we can cover the platforms the vendor has dropped, attend the sites your own team cannot reach, and handle the rollout and disposal if you decide to refresh instead. See
hardware break-fix and
data centre support for how the on-site element works.
Send your platform list, the sites involved and the dates you are working to, and you will get a quote against the real estate rather than a standard rate card.
Email: info@thronesolutions.com
Tell us what needs covering ·
IT consulting and field engineering ·
Rollouts and migrations
