NetApp AFF A220 End of Life: Status and Dates

NetApp AFF A220 support dates

Every row names its basis. A third-party tracker date is not the vendor’s own, and “not published” means exactly that.
Milestone	Date	Basis	Source
End of Availability (NetApp: 'no longer available for purchase, but are still supported')	—	Vendor-publishedNetApp states the EOA status but this page gives no date. The dated notice is on the NetApp Support Site EOA pages, which need a sign-in.	NetApp docs: End of availability for ONTAP hardware systems
End of Life, Park Place wording ('Affa220 Flash Array' row only), from the Park Place Technologies EOSL library	4 October 2021	Third-party trackerThird-party tracker, not NetApp. The page says 'End of Life October 4, 2021'. Park Place's 'Affa220C 2-CTRL' page gives no End of Life date.	Park Place Technologies: Affa220 Flash Array End of Service Life Date
End of Service Life (Affa220 Flash Array and Affa220C 2-CTRL), from the Park Place Technologies EOSL library	30 November 2026	Third-party trackerThird-party tracker. The /eosl/netapp/affa220c/ page gives the same date. Park Place and Service Express count as one source.	Park Place Technologies: Affa220 Flash Array End of Service Life Date
End of Support (AFF A220), from the eosl.date tracker	30 November 2026	Third-party trackerThird-party tracker. 'Not Announced' sits in its Release Date column. The table has no EOL column.	eosl.date: NetApp AFF End of Life (EOL) Dates and EOSL Dates

Where the NetApp AFF A220 stands today

Park Place carries the A220 on two pages, 'Affa220 Flash Array' and 'Affa220C 2-CTRL', and both give 30 November 2026 as End of Service Life; eosl.date shows the same date as End of Support. Service Express is not treated as a second, independent source alongside Park Place. A separate Park Place field, 'End of Life', reads 4 October 2021 on the 'Affa220 Flash Array' page and is missing from the 2-CTRL page. That is Park Place's wording and should not be read as NetApp's end-of-availability date: NetApp states the EOA status publicly but puts the dated notice on Support Site pages that need a sign-in.

NetApp publishes EOA and EOS dates per platform or component, and its KBs point to Hardware Universe or the Support Site's Product Communique for them. On 8 October 2026 Hardware Universe and the EOA Platforms page both redirected to a NetApp sign-in; signed-in customers can read the A220's EOS date there. If the question is one array's own contract or warranty, NetApp's answer is a non-technical support case. Confirming the date matters because NetApp's EOA policy ends a platform's Patch/Fix period, the window in which Service Updates are delivered, at its EOS date, so vendor software updates should not be relied on beyond whatever date NetApp confirms.

NetApp AFF A220: lifecycle on one axis

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 publishes EOA and EOS dates per platform or component. Its EOA policy KB (https://kb.netapp.com/cs/lcm/Why_does_the_latest_software_release_not_support_my_hardware_or_platform) says the dates 'can be found in Hardware Universe'. The public summary of NetApp's KB (https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/How_to_check_End_of_Support_and_End_of_Availability_for_NetApp_products) points to Hardware Universe or the NetApp Support Site Product Communique. On 8 Oct 2026, Hardware Universe (https://hwu.netapp.com) and the EOA Platforms page (https://mysupport.netapp.com/info/eoa/df_eoa_category_page.html?category=Platforms) both redirected to a NetApp sign-in. Signed-in customers can read the A220 EOS date there. For a specific system's contract or warranty, the public part of NetApp's KB (https://kb.netapp.com/cs/lcm/How_to_find_contract_details_such_as_warranties) says to 'open a non-technical case'.

What still works after NetApp support ends

Before EOS, NetApp's guidance is to 'Contact Account Team/Sales representative to arrange a technology refresh prior to the part EOS date.' After it, NetApp's KB says the system is not eligible for case submittal, technical support assistance, AutoSupport notifications or parts replacement. AutoSupport messages stop generating cases once the entitlement has expired, and NetApp adds that case creation resumes within 24 hours of a renewal. An alternative to NetApp SupportEdge sets out how independent cover compares.

Under NetApp's End of Availability Policy, which NetApp calls 'applicable to all NetApp hardware', new ONTAP Feature Releases support a platform for two years after its EOA date, and Service Updates (P-releases, 'which include security fixes') continue for Feature Releases that already support it, a Patch/Fix period that 'ends at the End of Support (EOS) date, typically 5 years after the EOA date'. Each ONTAP release also runs on its own clock: under NetApp's definitions, Limited Support brings no Service Updates of any form, and Self-Service Support is the period 'where NetApp does not provide support'.

NetApp's End of Availability Policy ('applicable to all NetApp hardware'): for ONTAP hardware, new ONTAP Feature Releases support a platform for 2 years after its EOA date. Service Updates (P-releases, 'which include security fixes') then continue for Feature Releases that already support it. That Patch/Fix period 'ends at the End of Support (EOS) date, typically 5 years after the EOA date'. (kb.netapp.com)
NetApp: 'EOS systems will not be eligible for:' case submittal, technical support assistance, AutoSupport notifications and parts replacement. (kb.netapp.com)
NetApp version-support definitions: Limited Support provides no 'Service Updates (including any form of software update)'. Self-Service Support is the period 'where NetApp does not provide support'. (kb.netapp.com)
AutoSupport messages 'WILL NOT generate cases' once support entitlement has expired. 'Once renewed, case creation will automatically resume within 24 hours.' (kb.netapp.com)

What a maintenance contract needs to cover on the NetApp AFF A220

Host connectivity on an A220 depends on how it was ordered. NetApp's installation instructions describe two configurations: a unified build, cabled from ports e0c/0c and e0d/0d, or e0e/0e and e0f/0f, with 10 GbE or optical cables, including to FC host network switches; and an Ethernet build, cabled with CAT6 RJ-45 from e0c and e0e, or e0d and e0f, to the data network switches. NetApp's KB likewise says A220 systems were 'ordered with a choice of mezzanine modules', and its title distinguishes RJ45 and CNA versions, so confirm which is fitted before spares are listed in a contract.

The rest of the parts picture is a 2U chassis (NetApp's lifting warning is 25 kg or more) with onboard drives, controller modules that are each reached through a wrench port combining e0M and the BMC, and redundant, hot-swappable, auto-ranging power supplies; NetApp notes that 'You do not have to shut down the controller to replace a PSU.' Where capacity was added, NetApp's instructions show external DS224C drive shelves with IOM12 modules on mini-SAS HD cables, so shelves, IOMs and cables should be scheduled as well.

NetApp AFF A220: what to tell a maintenance provider

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.

NetApp AFF A220 hardware, from NetApp’s own specification documents
Specification	Detail	Source
Form factor	Rack space '2U per chassis'. Lifting hazard ≥ 25 kg (≥ 56 lbs.).	docs.netapp.com
Host connectivity	Order-dependent, two configurations. Unified: ports e0c/0c and e0d/0d, or e0e/0e and e0f/0f, cabled with 10 GbE or optical cables, including to FC host network switches. Ethernet: CAT6 RJ-45 cables from ports e0c and e0e, or e0d and e0f, to the data network switches.	docs.netapp.com
Management controller	BMC, reached through the 'wrench port (e0M + BMC)' on each controller module	docs.netapp.com
External expansion	NetApp's installation instructions show external DS224C drive shelves (IOM12 modules) cabled with mini-SAS HD cables	docs.netapp.com
Internal storage	Onboard drives. For a controller upgrade, each AFF A220 node can be converted nondisruptively into a DS224C drive shelf attached to the replacement nodes.	docs.netapp.com
Power supplies	Redundant, hot-swappable, auto-ranging. NetApp: 'You do not have to shut down the controller to replace a PSU.'	docs.netapp.com

Extend or refresh the NetApp AFF A220?

Until NetApp's EOS date the A220 is still a NetApp-supported system; after it, third-party maintenance is one way to keep the hardware covered. Such cover generally means fault diagnosis, replacement parts and engineers once the vendor has stepped back, which suits an A220 serving a stable workload where hardware failure, not software currency, is the main risk. What third-party maintenance covers sets out the scope, and a quote for the exact configuration can be requested through the maintenance coverage builder.

NetApp documents a refresh route for this model: a nondisruptive upgrade in which each AFF A220 node is converted into a DS224C drive shelf and connected to the replacement nodes, moving the onboard storage across. The next model in the same line is the AFF A250. Because NetApp ends a platform's Service Updates at its EOS date, an array that needs them for longer is a candidate for planning that move before the trackers' 30 November 2026 date rather than after it.

Both trackers give 30 Nov 2026 as EOS, weeks away, but NetApp's own date is behind a sign-in. Under NetApp's EOA policy, a platform's Patch/Fix (Service Update) period ends at its EOS date, so confirm NetApp's EOS before relying on vendor software updates beyond it. (kb.netapp.com)
Refresh path: NetApp documents a nondisruptive upgrade that converts each AFF A220 node into a DS224C shelf and connects it to the replacement nodes, moving the onboard storage. (docs.netapp.com)
NetApp's guidance for systems before EOS: 'Contact Account Team/Sales representative to arrange a technology refresh prior to the part EOS date.' (kb.netapp.com)
AFF A220 systems were 'ordered with a choice of mezzanine modules' (NetApp's KB title: RJ45 or CNA versions). Check which one is fitted before ordering spares. (kb.netapp.com)

NetApp AFF A220: what came before and what replaces it

The successor shown is the next model in the same product line; the vendor notice does not name a direct replacement.

Keep your NetApp AFF A220 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 →

NetApp's KB on identifying RJ45 and CNA versions covers the AFF A220 together with the AFF C190 and FAS27xx series systems, and FAS2700 series end of life covers the FAS27xx models' own dates. By product-line order the AFF A200 came before the A220, and the AFF A250 is the next model in the same line; neither placement comes from a NetApp statement.

Where the NetApp AFF A220 sits against related models

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 NetApp AFF A220

Is the NetApp AFF A220 end of life?

It is end of availability: NetApp lists the A220 among systems that are 'no longer available for purchase, but are still supported'. Third-party trackers Park Place Technologies and eosl.date give 30 November 2026 as the end of NetApp support, but NetApp's own EOS date needs a Support Site sign-in to read.

When does NetApp stop supporting the AFF A220?

NetApp's own date is in Hardware Universe and on the Support Site's EOA Platforms page, both of which redirected to a NetApp sign-in when checked on 8 October 2026. Two third-party trackers give 30 November 2026. Under NetApp's EOA policy, Service Updates for a platform end at its EOS date, so confirm NetApp's date before planning around vendor updates.

Do all AFF A220 systems have the same host connectivity?

No. NetApp says A220 systems were 'ordered with a choice of mezzanine modules', and its KB distinguishes RJ45 and CNA versions. NetApp's installation instructions describe a unified configuration cabled with 10 GbE or optical cables, including to FC host network switches, and an Ethernet configuration cabled with CAT6 RJ-45, so check which is fitted before ordering spares.

What is the upgrade path from an AFF A220?

NetApp documents a nondisruptive controller upgrade that converts each A220 node into a DS224C drive shelf attached to the replacement nodes, moving the onboard storage to them. The AFF A250 is the next model in the same line, a placement inferred rather than stated by NetApp.

Should third-party maintenance for an AFF A220 be arranged before EOS?

A third-party contract can pick up where NetApp's ends, typically covering diagnosis, parts and engineers, and a quote can be requested for a specific A220. Because NetApp says EOS systems lose eligibility for parts replacement and technical support assistance, it is worth arranging before NetApp's EOS date arrives.

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.

NetApp docs: End of availability for ONTAP hardware systems — docs.netapp.com
Park Place Technologies: Affa220 Flash Array End of Service Life Date — parkplacetechnologies.com
eosl.date: NetApp AFF End of Life (EOL) Dates and EOSL Dates — eosl.date
kb.netapp.com — kb.netapp.com
kb.netapp.com — kb.netapp.com
kb.netapp.com — kb.netapp.com
kb.netapp.com — kb.netapp.com
docs.netapp.com — docs.netapp.com
docs.netapp.com — docs.netapp.com
docs.netapp.com — docs.netapp.com
kb.netapp.com — kb.netapp.com
docs.netapp.com — docs.netapp.com

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