HPE Aruba Networking gateways and controllers (hardware) End of Life (EOL) Dates & Support Timeline

HPE Aruba Networking gateways and controllers (hardware) lifecycle status — the real story

HPE Aruba Networking gateways and controllers are the WAN and WLAN edge hardware of the Aruba line: the 7000 and 9000 series branch gateways, the 7200 series campus gateways and mobility controllers, the Mobility Conductor hardware appliances, the EdgeConnect SD-WAN gateways (formerly Silver Peak) and the HPE Comware MSR routers. Cycles on this page are SKUs, each labelled with Aruba's own description. Every date comes from HPE Aruba Networking's own Product End of Life notifications on the HPE Networking Support Portal (networkingsupport.hpe.com/notification/product-eol, public, no sign-in). Each notice lists its SKUs with their own End of Sale and End of Support dates, which can differ from the notice headline, so cycles are SKUs and carry the SKU's own dates. The notices were read twice on 2026-10-18: the portal's notification data and the same query run inside the portal page in the built-in browser (all 1,121 SKU rows identical), and the notice list as the page renders it (every rendered row matched day for day), by tools/aruba-eol.mjs, which refuses to write on any difference. The verifier re-reads the notification data at every build.

Field mapping: support is the SKU's End of Sale date; eol is the SKU's End of Support date, the day printed (the data appends clock times such as 05:00 or 12:00 AM, which the page does not show). A SKU with no End of Support date is not listed rather than given a guessed day, and Aruba's placeholder date of December 31, 2099 is never served. Licences, subscriptions, software, support services and accessories (mounts, power supplies, fans, transceivers, cables, antennas, injectors, spares) are not modelled. Aruba prints no launch date, so releaseDate is empty. Current models without an end-of-sale notice are not listed; their absence is not a statement that they are supported indefinitely.

HPE Aruba Networking gateways and controllers (hardware) release and support pattern

Of the 172 release lines tracked, 6 are past end of life and 166 are still within support. The next scheduled end of life is JM250A on December 31, 2026 — 72 days from this build. The longest-supported line currently published is JZ878A, to December 31, 2032.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

What does HPE Aruba Networking gateways and controllers (hardware) end of life mean for your organization?

When a version of HPE Aruba Networking gateways and controllers (hardware) reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.

Organizations running EOL HPE Aruba Networking gateways and controllers (hardware) should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when HPE Aruba Networking gateways and controllers (hardware) reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

Extended Support Options

If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your HPE Aruba Networking gateways and controllers (hardware) version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.

Related Products