Hi.
You get some features you loose some features. The biggest change is licensing vs subscription. On the on-prem controller you have permanent licenses on Central you only have subscriptions. You will be able to manage AOS10 only when valid subscription is applied for device. In AOS10 many functions are moved from controller/AP to the cloud and are available when APs have connection to the Central.
Scalability and flexibility of AOS10 is excellent. On the other hand controller based configuration provide more control over low level functions versus AOS10 more let say user friendly approach.
As Dustin already pointed out, without gateway (controller) you will lose tunnel and mixed mode and you need to provide all required vlans to each AP. If you use RADIUS authentication, you will need to register all APs with RADIUS server instead of registering only GW. As you already have controllers, you can migrate them into GWs and have tunnel and RADIUS proxy features back.
Other limitation/recommendation is the number of APs and client. If you approach 500 APs, then go with gateways.
There are many customers using only APs on smaller deployments up to several hundreds of APs without gateways and it's working just fine.
Best, Gorazd
------------------------------
Gorazd Kikelj
MVP Guru 2024
------------------------------
Original Message:
Sent: Sep 26, 2024 04:38 PM
From: dtuen
Subject: Aruba Central and WIfi Access Points (without on prem controllers)
Hello All,
Looking at possibly adding new Aruba AP's but having them connect directly to Aruba Central.
We currently have on prem controllers and want to find out what are the drawbacks of configuring it just for Aruba Central to be managed in the cloud?
Anyone else doing this without on prem controllers?
What features and options would not be available if we do AP direct to Aruba Central?
Any Performance , troubleshooting, upgrade issues to look out for?
Thanks