UK’s trusted IT infrastructure partner since 2003
sales@servnetuk.com
0800 987 4111
Servnet
FinanceToolsConfiguratorGet in Touch
NetApp · FAS2600 series (entry-level hybrid FAS)

FAS2650 end of life

The NetApp FAS2650 is past end of support on third-party data: Park Place Technologies' EOSL library and the eosl.date tracker both give 31 May 2024 as its end-of-service-life or end-of-support date. NetApp's own end-of-availability and end-of-support dates for the FAS2650 are not public, because NetApp keeps them behind a Support Site login. For a 2U hybrid system that carries its drives inside the controller chassis, the options set out below are third-party maintenance and NetApp's documented upgrade routes: an in-chassis head swap or a move to newer controllers.

FAS2650 support dates

Every row names its basis. A third-party tracker date is not the vendor’s own, and “not published” means exactly that.
MilestoneDateBasisSource
NetApp End of Availability (EOA) / End of Support (EOS): vendor record, sign-in required—Not published by the vendorNetApp records EOA and EOS per platform ('EOA and EOS can be viewed from either Hardware Universe or NetApp Support Site: Product Communique'), but not publicly. The rest of the KB is behind sign-in. Re-checked 2026-10-08: hwu.netapp.com/api returned 401 'Unauthorized: Bearer token missing' with requiresLogin true, and the Product Communiqué data service (mysupport.netapp.com/api/support-commns-service) returned a 302 to sign-in. NetApp's own FAS2650 dates are therefore not reproduced here.NetApp KB: How to check End of Support and End of Availability for NetApp products
End of Service Life31 May 2024Third-party trackerThird-party tracker (Park Place Technologies, which absorbed Service Express in January 2026), not NetApp's own publication. The page shows 'May 31, 2024' and no separate EOA/EOL date.Park Place Technologies EOSL library: NetApp FAS 2650
End of Support31 May 2024Third-party trackerListed as 'FAS 2650' under 'No Longer Supported', with release date 'Not Announced' and End of Support '2024-05-31'. This is a separate third-party tracker that agrees with Park Place. Neither is NetApp's own date.eosl.date: NetApp FAS End of Life (EOL) Dates and End of Service Life (EOSL) Dates

Where the FAS2650 stands today

Both dates come from trackers rather than from NetApp. Park Place's FAS 2650 page carries 31 May 2024 alone, without a separate EOA or EOL date, and eosl.date files the 'FAS 2650' under 'No Longer Supported' with the same end-of-support date. NetApp records EOA and EOS per platform in Hardware Universe and in Product Communiqué EOA notices, and a sign-in-only KB holds the FAS2650's maximum supported ONTAP release, so none of those can be quoted here. NetApp's public controller-upgrade documentation does state that the FAS2620, the FAS2650's sibling in the FAS2600 series, and the AFF A200 support no ONTAP version later than 9.11.1. That statement covers those two models only.

NetApp's own position for a specific system needs a NetApp Support Site sign-in. Its KB on checking end of support and end of availability points to Hardware Universe (hwu.netapp.com) and the Product Communiqué EOA notices for platform dates, while contract and warranty status is held against the serial number under SYSTEMS > Contracts and Warranties. NetApp's end-of-support KB also directs owners to BlueXP Digital Advisor for EOS parts information. Other arrays can be looked up in the storage end-of-life checker.

FAS2650: lifecycle on one axis
FAS2650 lifecycle timeline202420252026202720282029Checked 8 Oct 202631 May 2024End of Service Life; Endof SupportNot dated by the vendorNetApp End of Availability (EOA) / End of Support (EOS): vendor record, sign-in required —Not published by the vendor. NetApp records EOA and EOS per platform ('EOA and EOS can beviewed from either Hardware Universe or NetApp Support Site: Product Communique'), but notpublicly. The rest of the KB is behind sign-in. Re-checked 2026-10-08: hwu.netapp.com/apireturned 401 'Unauthorized: Bearer token missing' with requiresLogin true, and the ProductCommuniqué data service (mysupport.netapp.com/api/support-commns-service) returned a 302 tosign-in. NetApp's own FAS2650 dates are therefore not reproduced here.
Dated milestones are placed only where a source gives the date; milestones the vendor has not dated are listed beneath the axis rather than guessed. Blue = vendor-published, amber = third-party tracker, violet = derived from a vendor policy. Checked 8 October 2026.
Finding the date for your own unit

NetApp shows platform EOA/EOS dates only to signed-in users. NetApp KB 'How to check End of Support and End of Availability for NetApp products' (https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/How_to_check_End_of_Support_and_End_of_Availability_for_NetApp_products) says they can be viewed in Hardware Universe (https://hwu.netapp.com) or in the NetApp Support Site Product Communiqué EOA notices (https://mysupport.netapp.com/info/eoa/index.html). Both need a NetApp Support Site login. Your own unit's support contract and warranty go by serial number. Per NetApp KB 'How to check Service Contract and Warranty information on NetApp Support Site' (https://kb.netapp.com/nss/Support_Site/How_to_check_Service_Contract_and_Warranty_information_on_NetApp_Support_Site), log in to the NetApp Support Site, open SYSTEMS > Contracts and Warranties, and search by the system's serial number. NetApp's EOS KB also points to BlueXP Digital Advisor for EOS parts information.

What still works after NetApp support ends

Per NetApp's KB, a system at EOS loses eligibility for case submittal, technical support assistance, AutoSupport notifications and parts replacement. For owners already past that point, the same KB suggests contacting NetApp Sales about 'EOS PVR's if applicable', without giving terms, scope or price; NetApp's Digital Advisor documentation spells PVR out as Product Variance Request. Software is gated separately, since NetApp states that 'Customers can only download software purchased by their company.'

ONTAP releases have a published ladder: full support in years one to three, including patch (P) releases and vulnerability alerts; limited support in years four and five, which keeps technical support, root-cause analysis and downloads but drops P-releases and alerts; and self-service, documentation only, in years six to eight. NetApp adds that 'ONTAP versions that are no longer under limited support do not have available software to download.' What that means for older hardware is an inference rather than NetApp's wording: a platform capped at an older ONTAP release loses that download once its last supported release leaves limited support. The FAS2650's own ceiling is sign-in only, so confirm it first.

  • NetApp says EOS systems are not eligible for case submittal, technical support assistance, AutoSupport notifications or parts replacement. Owners of systems already at EOS are told to contact NetApp Sales about 'EOS PVR's if applicable'. (kb.netapp.com)
  • NetApp software downloads are entitlement-gated: 'Customers can only download software purchased by their company.' (kb.netapp.com)
  • NetApp: 'ONTAP versions that are no longer under limited support do not have available software to download.' The following is an implication, not a NetApp statement: a platform capped at an older ONTAP release loses that download once its last supported release leaves limited support. (kb.netapp.com)
  • ONTAP release support levels. Full support, years 1-3: technical support, root-cause analysis, software downloads, patch (P) releases and vulnerability alerts. Limited support, years 4-5: technical support, root-cause analysis and software downloads, but no P-releases or vulnerability alerts. Self-service support, years 6-8: online documentation only. (docs.netapp.com)

Vendor support you can still buy

  • EOS PVR via NetApp Sales ('if applicable') — NetApp's KB tells owners of systems already at EOS to contact Sales about 'EOS PVR's if applicable'. The KB gives no terms, scope or price. A separate NetApp Digital Advisor KB expands PVR as 'Product Variance Request' (https://kb.netapp.com/data-mgmt/Digital-Advisor-KBs/How_to_handle_AIQDA_risks_after_a_PVR_FEPVR_approval). (kb.netapp.com)

What a maintenance contract needs to cover on the FAS2650

A maintenance contract for a FAS2650 should cover a storage enclosure as well as the controllers. The 2U chassis holds internal drives, and NetApp's field-replaceable units are boot media, caching module, chassis, controller, DIMM, drive, NVMEM battery, power supply and real-time clock battery. The PSUs are redundant and hot-swappable, but cooling is built into each one, and NetApp warns that a delay of more than two minutes in replacing a removed PSU shuts down all controller modules in the chassis. In practice, the replacement should be at the rack before the failed unit is pulled.

Where external capacity is fitted, it is DS212C or DS224C shelves with IOM12 modules, each controller cabled to both IOM A and IOM B of the stack with mini-SAS HD cables, so shelves, IOMs and cables all belong on the asset schedule. Per controller, record e0a/e0b for the cluster interconnect, data on e0c/0c plus any further data ports in use, and the separate wrench management port. Storage and SAN maintenance explains third-party cover for arrays of this kind.

FAS2650: what to tell a maintenance provider
FAS2650 hardware factsNETAPP · FAS2600 SERIES (ENTRY-LEVEL HYBRID FAS)FAS2650Past the vendor’s last date ofsupportRACK SPACE2U per chassis (FAS26xx series)INTERNAL STORAGEHas internal drives (NetApp lists theFAS2620, FAS2650, FAS2720 and FAS2750 assystems with internal drives). NetAppdocuments converting the FAS2650 controllerchassis into a DS224C SAS shelf whenupgrading.EXTERNAL EXPANSIONDS212C or DS224C disk shelves (IOM12). Eachcontroller is cabled to both IOM A and IOMB of the shelf stack with mini-SAS HDcables.NETWORK PORTS (PER CONTROLLER)e0a/e0b cluster interconnect, data on porte0c/0c (required, with further portsavailable if needed), and a separate wrench(management) portPOWER SUPPLIESRedundant and hot-swappable, with coolingbuilt into the PSU. A delay of more thantwo minutes in replacing a removed PSUshuts down all controller modules in thechassis.FIELD-REPLACEABLE UNITSBoot media, caching module, chassis,controller, DIMM, drive, NVMEM battery,power supply, real-time clock battery6 sourced specification facts · checked 8 October 2026
The hardware facts a maintenance quote is priced on, printed in the vendor's own wording from its specification documents (cited in Sources). Nothing on this plate is estimated; facts the vendor does not state are left off rather than filled in.
FAS2650 hardware, from NetApp’s own specification documents
SpecificationDetailSource
Rack space2U per chassis (FAS26xx series)library.netapp.com
Internal storageHas internal drives (NetApp lists the FAS2620, FAS2650, FAS2720 and FAS2750 as systems with internal drives). NetApp documents converting the FAS2650 controller chassis into a DS224C SAS shelf when upgrading.docs.netapp.com
External expansionDS212C or DS224C disk shelves (IOM12). Each controller is cabled to both IOM A and IOM B of the shelf stack with mini-SAS HD cables.library.netapp.com
Network ports (per controller)e0a/e0b cluster interconnect, data on port e0c/0c (required, with further ports available if needed), and a separate wrench (management) portlibrary.netapp.com
Power suppliesRedundant and hot-swappable, with cooling built into the PSU. A delay of more than two minutes in replacing a removed PSU shuts down all controller modules in the chassis.docs.netapp.com
Field-replaceable unitsBoot media, caching module, chassis, controller, DIMM, drive, NVMEM battery, power supply, real-time clock batterydocs.netapp.com

Extend or refresh the FAS2650?

Keeping a FAS2650 on third-party maintenance is reasonable when it serves a stable workload on the ONTAP release it already runs and the need is fault diagnosis and replacement parts rather than new features. Third-party maintenance generally covers exactly that, with parts and engineers past the vendor's own end of support, as what third-party maintenance covers explains. NetApp's entitlement KB adds a caution: it may decline support, even with a valid entitlement or warranty, if 'services have been performed by a person or entity other than NetApp or an authorized NetApp service representative' without a prior agreement with NetApp. That matters if the system might later go back under NetApp support.

The case for refresh rests on software: an ONTAP release past full support gets no further P-releases or vulnerability alerts, and an EOS system cannot raise cases with NetApp. Two NetApp-documented routes reuse existing hardware. An in-chassis head swap to the FAS2750, the next model in the same line, keeps the chassis, though NetApp's KB records a known issue in which the new FAS2750 node halts with 'This platform is not supported in this release' while the partner FAS2650 controller is still in the other slot. Alternatively, NetApp's example upgrade from a FAS2650 to a FAS8300 converts the old controller chassis into a DS224C SAS shelf attached to the new system, keeping the existing drives in service.

  • NetApp's controller-upgrade docs state that the sibling FAS2620 (and the AFF A200) do not support ONTAP versions later than 9.11.1. The FAS2650's own maximum ONTAP release is in a sign-in-only KB, so it is not stated here. (docs.netapp.com)
  • NetApp's KB covers in-chassis controller upgrades (head swaps) from FAS2650 to FAS2750. It also documents a known issue: the FAS2750 node halts with 'This platform is not supported in this release' while the partner FAS2650 controller is still in the other slot of the chassis. (kb.netapp.com)
  • Refresh option that keeps the drives: NetApp gives the example of upgrading a FAS2650 to a FAS8300 by converting the FAS2650 controller chassis into a DS224C SAS shelf and attaching it to the FAS8300. (docs.netapp.com)
  • NetApp may decline support even with a valid entitlement or warranty if 'services have been performed by a person or entity other than NetApp or an authorized NetApp service representative' without a prior agreement with NetApp. This matters if a third-party-maintained system is later returned to NetApp support. (kb.netapp.com)
FAS2650: what came before and what replaces it
FAS2650 product lineageFAS2650Release date not sourcedPast the last date of supportFAS2750 (FAS2700 series)Next model in the same lineNetApp · FAS2600 series (entry-level hybrid FAS)
The successor shown is the next model in the same product line; the vendor notice does not name a direct replacement. No predecessor is shown because none could be sourced.

Keep your FAS2650 covered

Tell us how many you run and when your current cover ends, and we will come back with a like-for-like maintenance quote for that estate. Your model and its support status are attached to the enquiry automatically, so there is nothing to re-type.

NetApp maintenance in detail →

The FAS2650 sits in the FAS2600 series with the FAS2620, and NetApp lists both, along with the FAS2720 and FAS2750, as systems with internal drives. Because NetApp's head-swap guidance runs from the FAS2650 to the FAS2750, the FAS2720 / FAS2750 end of life page is the natural next read. Estates that also run a FAS8200 can turn to the FAS8200 end of life page.

Where the FAS2650 sits against related models
FAS2650: end of support passed 2.4 years ago (31 May 2024, a third-party tracker’s date).20202021202220232024202520262027202820292030FAS2650release not sourcedFAS2720 / FAS2750release not sourcedFAS8200release not sourcedAFF A300release not sourcedTodayFAS2650: end of support passed 2.4 years ago (31 May 2024, a third-party tracker’s date).
Each bar runs from release to the milestone that marks end of support for the model as a whole. Amber bars end on a third-party tracker's date, not the vendor's. A dashed open end means no end date is published — not that support is indefinite. Component and accessory dates (a management controller, a power module) are not treated as the model's.

Look up another model in the storage end-of-life checker, or read what third-party maintenance covers.

Questions people ask about the FAS2650

Is the NetApp FAS2650 end of life?

On third-party data, yes: Park Place Technologies' EOSL library and eosl.date both give 31 May 2024 as the FAS2650's end of service life or end of support. NetApp's own EOA and EOS dates sit in Hardware Universe and the Product Communiqué EOA notices behind a NetApp Support Site login, so they are not reproduced here.

Will NetApp still support my FAS2650?

That depends on NetApp's own end-of-support date for your system, which only signed-in users can see. Per NetApp's KB, systems at EOS are not eligible for case submittal, technical support assistance, AutoSupport notifications or parts replacement, and owners of systems already at EOS are pointed to Sales about 'EOS PVR's if applicable'. Look up your unit's contract by serial number in the Contracts and Warranties area of the Support Site.

Can I still download ONTAP for a FAS2650?

Only with entitlement, because NetApp restricts downloads to software your company purchased. NetApp also says ONTAP versions out of limited support have no software available to download, and the FAS2650's maximum ONTAP release sits in a sign-in-only KB. Check that ceiling before planning around a specific release.

Can a FAS2650 be upgraded to a FAS2750?

NetApp's KB covers in-chassis controller upgrades from the FAS2650 to the FAS2750, the next model in the same line. It also documents a known issue where the FAS2750 node halts with 'This platform is not supported in this release' while the partner FAS2650 controller is still in the other chassis slot.

Can I get third-party maintenance for a FAS2650?

Third-party maintenance generally provides diagnosis, replacement parts and engineers for hardware past vendor end of support, and you can request a quote through the maintenance coverage builder. Include the internal drives, any DS212C or DS224C shelves and the power supplies, since NetApp's two-minute PSU rule makes spares timing part of the cover.

Sources

Every date, rule and specification above was checked against these on 8 October 2026 by an independent verification pass. Vendors revise lifecycle notices; this page is re-checked by 8 January 2027.

  1. NetApp KB: How to check End of Support and End of Availability for NetApp products — kb.netapp.com
  2. Park Place Technologies EOSL library: NetApp FAS 2650 — parkplacetechnologies.com
  3. eosl.date: NetApp FAS End of Life (EOL) Dates and End of Service Life (EOSL) Dates — eosl.date
  4. EOS PVR via NetApp Sales ('if applicable') — kb.netapp.com
  5. kb.netapp.com — kb.netapp.com
  6. kb.netapp.com — kb.netapp.com
  7. docs.netapp.com — docs.netapp.com
  8. library.netapp.com — library.netapp.com
  9. docs.netapp.com — docs.netapp.com
  10. docs.netapp.com — docs.netapp.com
  11. docs.netapp.com — docs.netapp.com
  12. docs.netapp.com — docs.netapp.com
  13. kb.netapp.com — kb.netapp.com
  14. kb.netapp.com — kb.netapp.com

Last reviewed 7 October 2026. Lifecycle dates for the FAS2650 are re-verified against NetApp's own notices at each review; a date a vendor has not published is never filled in.