Should automatic roaming be disabled in high-density deployments to avoid issues?

  • 1
  • Question
  • Updated 5 years ago
  • Answered
I have nearly 400 AP's in my site. I would say it is a 'hi-density' wifi deployment because it has been deployed with location tracking planned for the future.

AP's are divided into four management subnets. Same corporate ssid but users get IP address from subnet related to their management domain.

All AP's are in the same Hive. My question is as follows:

1. Should automatic roaming be disabled in such high-density deployments to avoid issues?



Note: This topic was created from a reply on the Aerohive Cooperative Control Features topic.
Photo of mag007


  • 24 Posts
  • 1 Reply Like

Posted 5 years ago

  • 1
Photo of Tash Hepting

Tash Hepting

  • 55 Posts
  • 29 Reply Likes

I'm not entirely sure what you mean by "automatic roaming". If you are refering to the automatic L3 tunneling, it is fine to leave this enabled in a high density deployment.

If you haven't already looked at out High-Density Wi-Fi Configuration and Deployment Guide, you should take a look at it for tips on optimizing your high-density deployment. Here's a link to it:
Photo of Crowdie

Crowdie, Champ

  • 958 Posts
  • 269 Reply Likes
We have approximately 600 access points in a high density deployment at an academic facility with each main building having unique subnets. Without layer three roaming when staff and students moved between buildings they would change IP address and this would interrupt any streaming video, voice call, etc.

Mag, if your users can roam from an access point in one subnet to an access point in a different subnet you need layer three roaming enabled - unless your users don't have an issue changing IP address.