I need to setup a wireless network with one SSID and around 3000 clients. The topology will be bridged@controller.
I found this example in a internet document that sums it all nicely:
"Company A decides to follow its desktop subnet model and use a single subnet per floor for the WLAN. This setup introduces complications because now the roaming domains are restricted to a floor, not the entire building as before. With the new subnet model in place, application persistence when roaming across floors is lost. The application most impacted is Company A's wireless VoIP devices. As users move between the floors (and subnets) on their wireless phones, they drop their calls when they roam. Figure 5-8 illustrates this scenario. In this figure, an 802.11 VoIP phone is connected to a wired VoIP phone. As the user roams from AP1 on Subnet 10 to AP2 on Subnet 20, the session drops because the roaming user is now on a different subnet.”
"The scenario described for Company A is common. Many applications require persistent connections and drop their sessions as a result of inter-VLAN roaming. To provide session persistence, you need a mechanism to allow a station to maintain the same Layer 3 address while roaming throughout a multi-VLAN network. Mobile IP provides such a mechanism, and it is the standards-based, vendor-interoperable solution to Layer 3 roaming for WLANs.”
That's when they introduce the Mobile IP standard.
Since we are planning for 3000 clients I would never consider a single network to service them. I was planning to create several /24 IP networks, and assign them to the same SSID, distributed by AP groups (geographically close).
Is this the right approach?
Will the controller apply the described mechanism of mobility?