Wireless Access

Reply
Contributor I
Posts: 90
Registered: ‎08-03-2009

Limitations of multiple AP-Groups.

We have a scenario where in we are forced to use many AP-groups, AP-groups Per building , Per floor , and it is a large scale installation.

 

Scenario is like this : 3services under one SSID , using rule derivations for seperating services in to different vlan/subnet, 

one single service has multiple vlan/subnet depending on the floor number. Subneting cannot be changed as it designed as common standard for both wired and wirelss.

 

So we are planning to use floor-wise AP-groups to get multiple subnets per floor.aps in the respective floor will be under that AP-goup.

 

Is there any limitations with the design , interms of ARM functionality, Roaming , Scalability etc.. ??

 

I know it will be difficult to manage though..

 

 

 

MVP
Posts: 500
Registered: ‎04-03-2007

Re: Limitations of multiple AP-Groups.

If users on the same 1of3 service will derive different vlan as they traverse floors, you should look into mobileIP or realize that users will "re-IP" as they associate above/below the floor their on. Client devices are generally stupid and it's not uncommon for a device to roam upstairs/downstairs. If this breaks your security model, you may need to rethink things. If you're doing this for security, have your SE arrange a call with Goldman Sach's, as they (used to?) have a pretty intricate setup that may be comparable.
==========
Ryan Holland, ACDX #1 ACMX #1
The Ohio State University
Guru Elite
Posts: 21,029
Registered: ‎03-29-2007

Re: Limitations of multiple AP-Groups.

[ Edited ]

wifiabcd wrote:

We have a scenario where in we are forced to use many AP-groups, AP-groups Per building , Per floor , and it is a large scale installation.

 

Scenario is like this : 3services under one SSID , using rule derivations for seperating services in to different vlan/subnet, 

one single service has multiple vlan/subnet depending on the floor number. Subneting cannot be changed as it designed as common standard for both wired and wirelss.

 

So we are planning to use floor-wise AP-groups to get multiple subnets per floor.aps in the respective floor will be under that AP-goup.

 

Is there any limitations with the design , interms of ARM functionality, Roaming , Scalability etc.. ??

 

I know it will be difficult to manage though..

 

 

 


First think about what access your clients need to what applications.  If the applications are centralized, clients merely need an ip address to get whatever they need done.  We have a few institutions where there is fiber everywhere and they have a single /16 network servicing all their clients (we are dropping broadcast and multicast), so that all wlan users just simply get an ip address in the same range, but have access to all their applications.

 

Your WLAN could be as simple as all traffic tunneled back to a single controller.   All clients getting the same ip address range, that would allow them to access their applications.  You would need only a single profile in your infrastructure to accomplish this.  First get the access portion squared away.  Many people think that they need a wlan subnet for each building or floor, but nothing is further from the truth.  The subnets assigned to those floors just end up getting wasted when not enough people show up in the floors or in the buildings.  If you have a single VLAN or pool that all WLAN users pull from, it is shared more effectively.

 

Please let us know if you have any further questions about this, because we are very passionate about getting users a good start to their wireless networks.  I strongly suggest you speak to your local Aruba SE so that your planning gets off on the right foot.

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
Showing results for 
Search instead for 
Did you mean: