Campus & Wi-Fi network refresh: plan your move off end-of-support Aruba gear
If your campus runs Aruba AOS-S switches (2530/2930F/2930M) or Wi-Fi 5/6 access points, you are likely past or nearing end of software support — which means no firmware fixes, growing security exposure, and devices that can't keep up with PoE-hungry endpoints. A planned refresh to Aruba CX switching, Wi-Fi 6E/7, and cloud-managed Aruba Central lets you modernize on your timeline instead of reacting to a failure. Use the planner below to scope your refresh, then request a TAA-compliant quote through GSA, SAP/FAR channels, or a cooperative SLED contract.
Signs it’s time to refresh
- Your Aruba AOS-S switches (2530, 2930F, 2930M) have hit end of software updates or end of support, so no more firmware or security patches
- Older Aruba CX models (e.g. 6200/6300 first-gen deployments) are nearing end-of-support milestones and dropping off current AOS-CX trains
- Wi-Fi 5 (802.11ac) or early Wi-Fi 6 APs can't handle today's device density, high-bandwidth video, or 6 GHz clients
- Switches are running out of PoE budget as you add Wi-Fi 6E/7 APs, IP cameras, badge readers, and PoE lighting that need 802.3bt (PoE++)
- You're still managing the campus box-by-box via CLI or AirWave instead of cloud-based Aruba Central with Marvis AIOps
- Uplinks are stuck at 1G/10G and bottlenecking aggregation as access switches move to multi-gig (2.5G/5G) for Wi-Fi 7
- An audit, cyber-insurance requirement, or zero-trust/dynamic-segmentation initiative demands hardware that still receives security updates
Your refresh planning checklist
Work these in order, or send us where you are and we’ll build the plan with you.
- 1
Inventory every switch and AP with its lifecycle date
Pull a full list of access/aggregation switches and APs by model and serial, then map each to its end-of-sale and end-of-support date. This tells you what's already unsupported versus what you can phase later.
- 2
Map PoE and multi-gig demand at the edge
Count current and planned PoE devices (APs, cameras, phones, sensors) and total their wattage against each switch's PoE budget. Flag where you need 802.3bt (PoE++) and 2.5G/5G access ports for Wi-Fi 6E/7.
- 3
Run a wireless coverage and capacity check
Review AP placement, client density, and whether you need 6 GHz coverage. A predictive or on-site survey shows how many Wi-Fi 6E/7 APs you actually need versus a one-for-one swap.
- 4
Decide your management model: Aruba Central vs. on-prem
Choose cloud-managed Aruba Central (with Marvis AIOps) or controller/on-prem management based on your security posture and air-gap requirements. This drives licensing and subscription scope.
- 5
Standardize on CX and a target AOS-CX/AP firmware
Pick your go-forward CX switch families (e.g. 6200/6300/6400 class) and Wi-Fi 7 AP models so spares, configs, and firmware stay consistent across buildings.
- 6
Plan segmentation, configs, and a migration path
Document VLANs, ACLs, and any move to dynamic segmentation/zero-trust, then plan AOS-S to AOS-CX config conversion. Decide stack/VSX redundancy and cutover order building by building.
- 7
Choose the buying path and lock the budget
Confirm GSA, SAP/FAR channels, GPC, or a cooperative purchasing vehicle, then build a phased PO that fits your fiscal year. Include licenses, subscriptions, optics/cabling, and install services in the number.
A typical refresh timeline
Discovery & assessment (weeks 1-3)
Inventory switches and APs, capture lifecycle dates, and run a PoE/multi-gig and wireless capacity review. Output: a prioritized list of what's unsupported now versus phaseable.
Design & quote (weeks 3-5)
Finalize the CX switching and Wi-Fi 6E/7 design, management model, licensing, and segmentation plan. Uniqcli returns a TAA-compliant quote on your chosen contract vehicle.
Procurement (weeks 5-9)
Place the order via GPC, SAP, FAR, GPC, or co-op contract. Stage gear, pre-stage Aruba Central, and validate firmware and configs in a lab/pilot closet.
Phased migration (weeks 9-16+)
Cut over building by building or closet by closet during maintenance windows, converting AOS-S configs to AOS-CX and validating PoE, Wi-Fi, and segmentation as you go.
Optimization & handoff (ongoing)
Tune Wi-Fi with Marvis, confirm monitoring/alerting, document the new standard, and set lifecycle reminders so the next refresh is planned, not reactive.
Why run the refresh with Uniqcli
Authorized HPE Aruba partner, TAA-compliant
We quote and deliver genuine HPE Aruba switching and Wi-Fi with TAA-compliant sourcing — important for federal, DoD, and SLED buyers with country-of-origin requirements.
Every major buying path
Purchase through GSA, SAP/FAR channels, or GPC for federal, and cooperative purchasing vehicles for SLED — so your refresh fits the contract and fiscal year you already use.
Refresh-planning help, not just a price list
We help you read lifecycle dates, size PoE and multi-gig, plan the AOS-S to AOS-CX migration, and phase the spend so a campus refresh stays on schedule and on budget.
Full bill of materials in one quote
Switches, Wi-Fi 6E/7 APs, Aruba Central licensing, optics, cabling, and services land on a single quote — no surprise add-ons mid-project.
Solutions to refresh into
Refresh planning — FAQs
My Aruba 2930F switches still work — why refresh now?
"Still working" and "still supported" are different. Once AOS-S models like the 2930F reach end of software updates and end of support, they stop receiving security patches and firmware fixes, and TAC help becomes limited. That's a compliance and risk problem even when the hardware runs fine, and it's why most teams plan the move to CX before a failure forces it.
What's the difference between AOS-S and AOS-CX?
AOS-S is the older switch OS on ProVision/2530/2930-class hardware; AOS-CX is the modern, database-driven OS on the Aruba CX line. CX adds better automation, programmability, VSX redundancy, and tighter Aruba Central integration. Configs don't port over one-to-one, so a refresh includes converting and validating your VLANs, ACLs, and segmentation.
Do I need Wi-Fi 7, or is Wi-Fi 6E enough?
It depends on density and roadmap. Wi-Fi 6E adds the clean 6 GHz band and is plenty for many campuses today; Wi-Fi 7 adds higher throughput and lower latency for high-density and future client mixes. Many sites deploy 6E now in lighter areas and Wi-Fi 7 where density and bandwidth are highest. We size this against your client counts and PoE/uplink capacity.
Will Wi-Fi 6E/7 APs blow my PoE budget?
They can. Higher-end 6E/7 APs often want 802.3bt (PoE++), and adding cameras, sensors, and PoE lighting compounds the draw. Part of the planner is totaling watt demand per closet against each switch's PoE budget so you right-size CX switches with enough PoE++ instead of discovering a shortfall mid-cutover.
Can SLED buyers purchase through a cooperative contract?
Yes. State, local, and education buyers can acquire HPE Aruba refresh gear through cooperative purchasing vehicles, which streamlines procurement versus a full bid. Federal buyers can use GSA, SAP/FAR channels, or GPC. We'll quote on whichever vehicle you already hold.
Do I have to replace everything at once?
No. Most campus refreshes are phased — typically worst-first by lifecycle date or building by building during maintenance windows. We help you sequence cutovers so unsupported gear goes first while the rest is budgeted across fiscal years.
Build your HPE bill of materials.
Send us the requirement, the project, or an existing quote to beat. We come back with a validated, TAA-compliant HPE configuration and a real price, often below list.
connect [at] getuniqcli.com · Chicago, IL