Aruba WAP Controller recommend advice
Aruba WAP Controller recommend advice
Hi, I'm dealing with a setup of around 150 wireless access points, mostly Aruba 105, 115, and 215 models. They're all properly installed and positioned across the branches—great job! The only issue is that I don’t have the controller server or its configuration. I’m open to suggestions but want some advice from someone who’s worked with these APs before. Most of my experience is with Cisco equipment, so I’m guessing they’d recommend a similar path. I’m considering three options: A) spin something up and handle it myself, B) use Aruba/HP cloud services (essentially IaaS), or C) run each branch independently without central management. There are pros and cons to each, especially regarding brand familiarity and costs. Thanks in advance for any insights or tips!
As a Cisco professional, I recommend swapping all references to generic equipment with actual Cisco products. Depending on how many access points are deployed, you should run standalone units in branch locations. For campuses or sites with dense AP clusters, set up dedicated hardware and handle management locally.
I heard the Cisco employee party line firsthand when I reached out to our business development manager. The CAPEX expenditure didn't seem reasonable at this early phase—those 150 APs span over 12 sites, so it's not a massive volume, but there are still thousands of miles between us and them for easy oversight. One vote was given for standalone mode. Thanks.
This appears to be a risk assessment. You might want to share solutions with management. If you prefer standalone operation, a breakdown could result in a few days of downtime since you’ll need to reach there first. Launching a new control server would require significant investment, but having direct control can reduce downtime considerably. The IaaS option (which could be SaaS) is likely the most costly and offers no advantages over the initial choice. I’d only recommend IaaS if you lack the necessary hardware or expect hardware failure, in which case a complete replacement would be ideal.
We rely on Aruba 7005 devices in our operations, primarily as gateways for managing user logins and authentication at locations such as hotels and restaurants. These devices are not connected to any Aruba APs. By applying firewall licensing, they become a cost-effective solution that meets Hilton StayConnected and Mariott GPNS standards. The alternative option is Nomadix. I know the GUI works adequately, but mastering the CLI is essential. At least its interface improves over the Extreme Networks controller—this one really deserves attention. We never install Aruba APs, so I haven’t used the device for its primary role.
They made the tough choice to invest in the controller for around 9k NZ, with a four-week delivery time. I also need to secure licenses for the WAPs—though I understand they’re not ideal since I already have a proprietary unit running Aruba. I’m considering looking into Fortigate for the rest of the setup. Why should everything be complicated with separate per-WAP licenses? I’d appreciate it if you could clarify this quickly, as I’m waiting four weeks to evaluate whether it’s worth the investment. Just a heads-up: HP staff reading this—worth noting that spending so much without clear justification makes me cautious. But I’m open to your perspective.
You’re referring to an Aruba 7000 series controller, such as the 7005. The last digit indicates how many APs it can manage without extra licenses. In enterprise environments, licensing typically follows this model: the hardware cost covers both the device and its standalone software, while the controller’s price mainly covers its own hardware. This structure is common across major vendors like Ruckus, Extreme, Cisco, and Meraki—though Meraki was acquired by Cisco and adopted similar practices beforehand. The concept is straightforward: the AP price includes the equipment and software in standalone mode, and the controller price reflects only its own hardware. This setup is typical for large-scale deployments.
Edited note: 9000 NZD equates to roughly $6,500 USD. That’s a big purchase—what exactly did you acquire? The 7005 usually costs between $1300 and $1500.
Additional comment: I just rechecked your original message; it clarifies the licensing approach better now. I assumed we were discussing a few APs at a time. Even if you’re not taking over the controller, it makes sense to include the licenses—technically tied to managing a set number of APs rather than each individual unit.
This applies to Ruckus ZoneDirector, such as model ZD1205. I'm not sure it affects Aruba controllers—I might be mistaken.