Skip to content
Buying basics

Buying End-of-Life Hardware: Keeping Legacy Systems Running

What EOL and end-of-support notices mean, how to find replacement part numbers, and how to source spares for legacy servers, storage and switches.

Updated 4 min readBy the NorthernITShop team

End-of-life (EOL) hardware is equipment the manufacturer no longer sells, and eventually no longer supports. It can still run reliably for years, but you need a plan for spares, firmware and replacement part numbers before parts become hard to find.

The lifecycle stages

Manufacturers use different names, but most follow the same sequence. Cisco's terms are widely used as a reference:

Stage What it means
End-of-life announcement The manufacturer publishes the dates below for a product.
End of sale Last date to order the product new from the manufacturer.
Last ship date Last date the manufacturer ships it.
End of software maintenance No more bug fixes or feature updates.
End of vulnerability/security support No more security fixes.
Last date of support (LDoS) No more hardware support or replacement parts from the manufacturer.

Other brands use similar milestones. HPE refers to end of life and end of service life. Dell and Lenovo publish end-of-life and end-of-service dates for their platforms. Check the manufacturer's own notice for the exact dates for your model.

What changes at each stage

  • After end of sale: new systems are no longer available from the manufacturer, but spare parts usually are. Distribution stock runs down.
  • After software maintenance ends: you keep the last firmware and software release. Plan any final updates before this date.
  • After last date of support: OEM support contracts end. Spare parts come from third-party maintenance providers and the secondary market.

Is it safe to keep EOL hardware?

It depends on the system's role.

Good candidates to keep running:

  • Stable workloads that do not need new features.
  • Systems inside isolated networks, or behind other security layers.
  • Lab, test, archive and disaster recovery systems.
  • Systems with application dependencies that make migration expensive.

Candidates to replace sooner:

  • Internet-facing devices that need security updates, such as edge switches and firewalls.
  • Systems that must meet compliance rules requiring vendor support.
  • Systems where a single failure would cause a long outage and spares are scarce.

Replacement and superseded part numbers

Spare parts often change part number during a product's life. The manufacturer retires the original number and lists a replacement, usually because a component supplier changed or a firmware revision was needed.

  • The superseded number is the old one. The replacement number is the new one.
  • A replacement usually works in the same system, but sometimes needs a minimum firmware level. Check the manufacturer's notes.
  • Some replacements are newer, larger or faster parts. For example, a higher-capacity drive replacing a discontinued one.

Product pages on this site list superseded and replacement numbers where we have them, with links both ways. Search any number you have, old or new. See server part numbers explained.

Sourcing spares

Know what you run

Build an inventory of each EOL system: model, serial number, part numbers of drives, memory, power supplies, fans and controllers, and firmware levels. Management tools such as HPE iLO, Dell iDRAC and Lenovo XClarity can export much of this.

Buy spares before you need them

The secondary market for a platform is strongest in the years after end of sale, while decommissioned systems are plentiful. Supply thins over time. Common failure parts to keep on the shelf:

  • Hard drives and SSDs, with the right carriers
  • Power supplies
  • Fans
  • Memory modules matching installed part numbers
  • RAID controller cache batteries or capacitor modules
  • Switch power supplies and fan trays

Use donor systems

For very old platforms, a complete used server or switch of the same model can be a cost-effective source of many spares at once.

Match conditions to the part

Refurbished and used parts are often the only source for EOL platforms. Choose the condition by wear risk: low-wear parts such as memory and processors carry less risk than drives and fans. See new vs refurbished vs used.

Firmware considerations

  • Record firmware levels for every system before support ends.
  • Download and keep the final firmware and drivers while they are still available, within the terms of your entitlement.
  • When you fit a spare, check that its firmware is compatible with the system. Replacement drives and controllers may arrive with a different firmware level.

Third-party maintenance

After OEM support ends, third-party maintenance can provide replacement parts and support for failed hardware. It covers hardware only, not OEM firmware or software updates. See our maintenance service.

Planning the exit

Even if a system can run for years, plan its replacement. A short plan covers:

  1. Which workloads move, and to what.
  2. When the move happens, based on risk and budget.
  3. How retired hardware is handled, including data sanitization. See our ITAD service.

Checklist for an EOL spares request

  1. System model and generation.
  2. Part numbers from the labels: option, spare, FRU or OEM. Send all of them.
  3. Quantity, including shelf spares.
  4. Acceptable conditions: new, refurbished or used.
  5. Firmware requirements, if any.
  6. How soon you need the parts.

Browse servers, server components and storage drives, or send hard-to-find numbers through Source a Part. For a full list, send an RFQ.

All guides →
  • How to write an RFQ or BOM for servers, drives, memory and networking parts - part numbers, quantities, conditions, dates, country and Incoterms.

    5 min readRead guide

  • What new, refurbished and used mean for servers, drives, memory and switches, and how to weigh price, warranty, lead time and risk for each workload.

    4 min readRead guide

  • How HPE option and spare numbers, Lenovo option and FRU numbers, Dell part numbers and Cisco PIDs work, and where to find them on a part label.

    5 min readRead guide