EOL Tracking

Vendor EOL guides · Aruba (HPE)

Aruba end-of-life dates: the HPE lifecycle, decoded

By Nico De Muynck · Updated July 19, 2026

Quick answer

HPE Aruba Networking runs a clear, published lifecycle: End of Sale → End of New Features → End of Service Life. Support typically continues for about five years after End of Sale, then End of Service Life (EOSL) ends all patches, TAC and hardware replacement. Dates are published per product on the HPE Networking Support portal.

Aruba's lifecycle milestones

  • End of Sale (EOS) — the product can no longer be ordered from HPE. Units already deployed keep their support for now, but this is the latest reasonable moment to start planning a refresh.
  • End of New Features (ENF) — software development for new capabilities stops. You still get fixes, but the platform no longer moves forward.
  • End of Service Life (EOSL) — the hard stop. All HPE Aruba software and hardware support terminates: no patches, no TAC support, no replacement parts through standard channels.

Note the terminology overlap with the wider industry — Aruba's “End of Sale” abbreviates to EOS, which elsewhere means “End of Support.” If you mix vendors, our EOL vs EOS vs EOSL glossary keeps the acronyms straight.

The five-year window is your planning runway

The roughly five years of support after End of Sale is generous — but it's exactly what lulls teams into forgetting. A switch bought near its End of Sale date can be at EOSL far sooner than its age suggests, because the clock started at the product's end-of-sale, not your purchase date. The gap that bites is End of New Features: the platform stops advancing while still “supported,” so security posture and capability quietly fall behind years before EOSL formally arrives.

How to find your exact dates

1. The HPE Networking Support portal. HPE publishes lifecycle notices per product with End of Sale, End of New Features and End of Service Life dates.

2. Check by SKU, not just model family. Dates can vary by SKU, so confirm against the product-specific notice rather than relying only on third-party EOL databases.

3. Record EOSL per device. Map each switch and access point to its End of Service Life date and watch it — the support clock, not the hardware's health, decides when it must go.

A note on the HPE / Aruba overlap

Aruba is HPE's networking arm, so its lifecycle policy sits alongside the broader HPE hardware approach. If you also run HPE servers, the HPE ProLiant EOL guide covers the generation-based server side — both funnel through HPE's support portal, and both reward tracking the support date rather than the purchase age.

Look each device up once. Never again.

Record your Aruba End of Service Life dates in EOL Tracking and get warned months before support runs out — by email, Slack or Teams.

Start free — up to 5 assets

No credit card · CSV import for whole fleets