The most searched Aruba end of life question has an answer almost nobody publishes correctly: the 2930F has no announced end of sale at all. Below is every date HPE has actually published, read per part number from the bulletins rather than the summary list, plus the three families where the honest answer is that no date exists yet.
Start here if you are checking a 2930F, 2930M or 5400R. As of August 12, 2026 none of them appear anywhere in HPE's end of life database, and HPE's own current warranty reference still lists every one of those part numbers with status Active. There is no end of sale date to plan against. Anyone quoting you one is guessing. What is announced and close: J9777A (2530 8G) and JL356A (2540 24G PoE+) both lose support on October 31, 2026, about ten weeks away.
HPE publishes these dates one bulletin per product family, and the index you land on first is not the same as the table inside. This page reads the bulletins. Where a part number inside a family carries a different date from its siblings, and that happens constantly in this lineup, the part number is listed on its own. Dates verified against HPE's published end of life notices as of August 12, 2026.
Comparing against Cisco? See the companion tables: Cisco switch end of life dates → and Cisco and Meraki access point dates →
| Product | End of sale | End of support | Status today | Worth knowing |
|---|---|---|---|---|
| Switches with no announced end of sale | ||||
| 2930F Series (JL253A–JL265A, JL557A–JL561A, JL692A) | Not announced | Not announced | Current | Status "Active" in HPE's current warranty reference |
| 2930M Series (JL319A–JL324A, R0M67A, R0M68A) | Not announced | Not announced | Current | Status "Active" in HPE's current warranty reference |
| 5400R zl2 / 5406R / 5412R (J9821A, J9822A) | Not announced | Not announced | Current | Different chassis generation from the older ProCurve 5400zl |
| Switches with announced dates | ||||
| J9777A: 2530 8G | Oct 31, 2021 | Oct 31, 2026 | 10 weeks left | Six months earlier than the 8G PoE+ model beside it |
| J9772A, J9775A: 2530 48G and 48G PoE+ | Jan 31, 2022 | Jan 31, 2027 | 5 months left | Bulletin at revision 4, dates corrected April 2026 |
| J9773A, J9776A: 2530 24G and 24G PoE+ | Mar 31, 2022 | Mar 31, 2027 | 7 months left | Two months later than the 48-port models |
| J9774A: 2530 8G PoE+ | May 8, 2022 | Apr 30, 2027 | 8 months left | HPE publishes no SKU-level support date here; this is the bulletin value |
| 2530 Fast Ethernet 10/100 (J9778A–J9783A, JL070A) | Oct 31, 2023 | Oct 31, 2028 | Supported to 2028 | The slower switch outlives the Gigabit one by up to two years |
| JL356A: 2540 24G PoE+ | Oct 31, 2021 | Oct 31, 2026 | 10 weeks left | Three months earlier than the rest of the 2540 family |
| JL354A, JL355A, JL357A: 2540 Series | Jan 31, 2022 | Jan 31, 2027 | 5 months left | HPE's index row understates this as Oct 31, 2026 |
| 3810M Series (JL071A–JL076A, JL428A–JL430A) | Jan 31, 2025 | Jan 31, 2030 | Supported to 2030 | Most recent announced switch in the lineup |
| 2920 family (J9726A–J9729A, J9836A) | 2018 – 2019 | Jun 2023 – Apr 2024 | Unsupported | J9728A specifically ended Dec 31, 2023 |
| Campus access points | ||||
| AP-315 / IAP-315 (310 Series) | Dec 31, 2023 | Dec 31, 2028 | Supported to 2028 | Index row says Jul 31, 2027; only the AP-314 stayed there |
| AP-305 / IAP-305 (300 Series) | Jul 31, 2022 | Jul 31, 2027 | 11 months left | Last supported release ArubaOS 8.10, 10.4 |
| AP-325 / IAP-325 (320 Series) | Jul 31, 2022 | Jul 31, 2027 | 11 months left | Central-managed JW327ACM ends Oct 31, 2026 instead |
| AP-335 / IAP-335 (330 Series) | Jul 31, 2022 | Jul 31, 2027 | 11 months left | Central-managed JW825ACM ends Oct 31, 2026 instead |
| AP-345 / IAP-345 (340 Series) | Dec 31, 2022 | Dec 31, 2027 | 16 months left | Last supported release ArubaOS 8.10, 10.4 |
| AP-365 (360 Series outdoor) | Dec 31, 2024 | Dec 31, 2029 | Supported to 2029 | Outlives every gateway except the 2030 group |
| IAP-205 / AP-205 (200 Series) | May 2, 2018 | Apr 30, 2023 | Unsupported | Capped at ArubaOS 8.10 |
| IAP-225 / AP-225 (220 Series) | Feb 2, 2018 | Jan 31, 2023 | Unsupported | Capped at ArubaOS 8.10 |
| AP-514 / AP-515 (510 Series) | Not announced | Not announced | Current | Absent from all 205 published EOL bulletins |
| Gateways and mobility controllers | ||||
| 7024 Branch Controller | Apr 30, 2022 | Apr 30, 2027 | 8 months left | Dates differ across the regional and TAA variants |
| 7005 / 7008 Branch Controllers | Apr 30, 2023 | Apr 30, 2028 | Supported to 2028 | Dies before an AP-365 does |
| 7205 Controller | Nov 30, 2024 | Nov 30, 2029 | Supported to 2029 | n/a |
| 7280 Controller | Dec 31, 2024 | Dec 31, 2029 | Supported to 2029 | n/a |
| 7010 / 7030 / 7210 / 7220 / 7240XM | Jan 31, 2025 | Jan 31, 2030 | Supported to 2030 | One date wiped out most of the controller line |
"Limited Lifetime Warranty" means five years after the switch stops being sold. This is the single most expensive misunderstanding in the Aruba estate. HPE's Warranty and Support Summary caps it in writing, footnotes 7 and 11, at five years from the end of sale date, and the per-SKU quick reference writes it as "LLTW EOS + 5-Years". Every announced product above follows that rule to the day, with no exceptions. Customers who bought a 2530, 2920, 3810M or 5400R on the strength of the lifetime badge believe they are covered indefinitely. What they actually have is TAC and RMA rights that expired five years after the model left the price list, on a switch that is still happily passing traffic.
The 2530 is two different products with opposite timelines. The Gigabit 2530s lose support between October 2026 and April 2027. The slower 10/100 Fast Ethernet 2530s run all the way to October 31, 2028. The cheaper, older-spec switch outlives the faster one by up to two years. Quoting "the 2530" a single date is wrong in one direction or the other, and inside the Gigabit family the 48-port models end two months before the 24-port models. Price per part number, never per series.
HPE's list view understates the real date, so open the bulletin. The index shows "Original" end of sale and support dates, which are frequently earlier than the current per-SKU dates inside. The 2540 index row says support ends October 31, 2026; the bulletin shows JL357A running to January 31, 2027. The 310 Series index row says July 31, 2027; the AP-315 specifically was extended to December 31, 2028, and only the AP-314 stayed behind. HPE actively revises these, the 2530 bulletins are both at revision 4 as of April 2026, and the revision note says the end of sale date was corrected.
Central-managed part numbers expire up to two years early. Same physical radio, different lifecycle. JW813ACM, the Central-managed AP-315, loses support December 31, 2026 against December 31, 2028 for the standard SKU. JW327ACM and JW825ACM both end October 31, 2026 against July 31, 2027. If your estate was bought through a Central bundle, check the "CM" suffix before you trust any date on this page.
The last day HPE takes orders. The hardware keeps working and keeps support, but you can no longer buy matching units. Expansions and spares now come from a shrinking secondary market at unpredictable prices.
The end of the line: no TAC cases, no RMA replacements, no engineering help. Exactly five years after end of sale across every announced product in this lineup. This is the date that matters.
Not a date, a firmware ceiling. HPE names the highest software train a model will ever run. It is the wall you hit first, and it is invisible in any date-based plan.
HPE does not publish one for this lineup. Its records carry announcement, end of sale, end of support and the firmware ceiling, and nothing else. Any specific Aruba software-maintenance date you have been quoted was invented somewhere downstream.
HPE caps the 320, 330 and 340 Series at ArubaOS 8.10 and 10.4, and the 200 and 220 Series at 8.10. Upgrade a gateway past that train and those access points silently drop out of the cluster. The 2027 support date is not what stops you, the software is, and it stops you sooner.
PCI DSS 4.0, HIPAA security reviews and cyber insurance questionnaires all ask whether components are vendor-supported. "No" turns into findings, exceptions to document, and in some renewals, higher premiums or declined claims.
No RMA means a failed switch is a dead switch. You scavenge the secondary market for matching part numbers, and with a lineup this fragmented by SKU, matching is harder than it sounds. Each swap costs hours.
This is the detail that should change your quote. If HPE is migrating you off these switches onto the CX line, the 6200, 6300, 6400, 8300 or 8400, footnote 12 of the same Warranty and Support Summary caps software updates at one year after end of sale and vulnerability fixes at three years, even though hardware support still runs the familiar five. The old switch gave you five years of everything. The new one gives you five years of hardware and one year of software. Ask for that in writing before you sign, because it is not what the five-year number implies.
The gateway can die before the access points. A 7024 loses support April 30, 2027 and a 7005 or 7008 on April 30, 2028. The APs they manage outlive them: AP-345 to December 2027, AP-315 to December 2028, AP-365 all the way to December 2029. A site running AP-365s on a 7005 pair has nineteen months of orphaned access points. Only the 7010, 7030, 7210, 7220, 7240XM and 7280 outlast the AP fleet.
The part numbers outlived three company names. J9772A, J9728A and J9821A describe the same physical hardware under HP ProCurve, then Aruba, then HPE Aruba Networking. The JL-prefix numbers are Aruba-era and have no ProCurve equivalent. This matters when you are searching for spares or reading an old asset register: the same switch appears under three brands and none of the dates change.
Lead times eat your runway. Between quote cycles, supply queues and install scheduling, a mid-size refresh takes one to two quarters end to end. Ten weeks on a J9777A is already tight. We cover this in network hardware lead times →
Or stop owning the refresh cycle entirely. Network as a Service replaces bought hardware with a managed subscription: the provider supplies and installs current switches, access points and management, monitors it, and refreshes hardware when it ages out. End of life dates become the provider's problem, and so does the part-number archaeology. One monthly price covers hardware, licences and operations. See what NaaS is → or estimate the monthly cost →
Support ends October 31, 2026. That is ten weeks. Too short to run a full procurement, long enough to get a bridge in place: price third-party support now and plan the replacement for next quarter rather than scrambling.
Between five and eight months, depending on your exact part number. Pull the asset register and check each one against the table above, because two switches that look identical in a rack can be four months apart.
Nothing announced. You are not on a clock, and you should be sceptical of anyone telling you otherwise. Worth a re-check before you commit to a long refresh timeline, because this is where an announcement would land first.
Support ends July 31, 2027, so about eleven months. But check for the "CM" suffix: Central-managed variants of the same radio end October 31, 2026, nine months earlier, and nothing about the hardware tells you which you have.
Your real deadline is the gateway's, not the AP's. The 7024 goes April 2027 and the 7005/7008 April 2028, both potentially before the access points hanging off them. Scope the gateway and the APs as one project.
Export the inventory from Central or AirWave and check the part numbers, not the model names, against the table above. Fifteen minutes tells you whether you have a to-do item or a fire drill. We can do this with you at no cost.
An independent advisor can map your part numbers against refresh and NaaS options, with real quotes from multiple providers. No vendor pitch, no cost, no obligation.