How does the controllerless Wi-Fi environment scale?

  • 1
  • Question
  • Updated 4 years ago
  • Answered
Photo of Mike Jordan

Mike Jordan

  • 5 Posts
  • 1 Reply Like

Posted 4 years ago

  • 1
Photo of Travis Kaufman

Travis Kaufman, Champ

  • 113 Posts
  • 30 Reply Likes
How does it not?  Controller at each location = $$$$   Cloud Management, Auto-Provision Policies, Network Policy per Location etc... Scales much easier than a typical controller wifi environment 
Photo of David Coleman

David Coleman, Official Rep

  • 209 Posts
  • 164 Reply Likes
I shut-down my company 5 years ago and came to work to Aerohive because I saw that a "distubuted architecture" without a controller was the best way to scale and the future of WLAN architecture in my opinion.  Scalability is the best thing about a distributed architecture. As you grow in one location or in many locations you just add access points as needed.
Photo of David Coleman

David Coleman, Official Rep

  • 209 Posts
  • 164 Reply Likes
No need for redundant controllers. No need to deploy controllers at each location. No need to install 24 different feature licenses.  Just add access points and other mobility edge devices as you grow. 
Photo of David Coleman

David Coleman, Official Rep

  • 209 Posts
  • 164 Reply Likes
Distributed Architecture = SCALABILITY
Photo of Travis Kaufman

Travis Kaufman, Champ

  • 113 Posts
  • 30 Reply Likes
Cost effectiveness helps it scale in the CFO's eyes 
Photo of Mike Jordan

Mike Jordan

  • 5 Posts
  • 1 Reply Like
I am a strong proponent against controller based networks; especially in mesh networks. An AP sending a request for the shortest path back makes no sense. By that time, the least cost route has most likely changed. Not to mention the overhead...
Photo of Mike Jordan

Mike Jordan

  • 5 Posts
  • 1 Reply Like
BTW, I wasn't questioning the ability, I was attempting to become educated on the solution. It's new to me.
Photo of Mike Jordan

Mike Jordan

  • 5 Posts
  • 1 Reply Like
The Cloud Based solution
Photo of Mike Jordan

Mike Jordan

  • 5 Posts
  • 1 Reply Like
I had the luxury of avoiding a controller base architecture until a few years ago.
(Edited)
Photo of Travis Kaufman

Travis Kaufman, Champ

  • 113 Posts
  • 30 Reply Likes
Understood - as a Network Admin. You can create network policies per location.  Auto-Provisioning per policy can greatly reduce configuration time for the network admin.  Buy an AP, send it to New York Location, when its connected to the network, it configures, updates and is ready to go in minuets. 
Photo of GeoffEvans

GeoffEvans

  • 11 Posts
  • 1 Reply Like
Made our deployments very easy with auto-pro
Photo of Eddie Klaczko

Eddie Klaczko

  • 28 Posts
  • 5 Reply Likes
This is the way I understand it.  Aerohive's AP's communicate with their close neighbor APs to make many of the decisions for RF, roaming etc.  that would be the responsibility of a controller in other solutions. 

Now one AP communicating with 6 to 10 other APs is scalable.  Now asking a single controller to do the same for 50, 100, 500, 1000 APs and you will be limited at some point by that controller.