In our case we do "Mobility" by using VLAN pooling (layer 2 roaming).
So our VLANs are defined on all controllers
(and terminated on our Routers). The limit of 8096 still persists,
unless we use a different size subnet per VLAN
(/23, /22 etc...)
If one decides to terminate a VLAN on a specific controller only, IP-
Mobility needs to be enabled for roaming purposes.
Code release 3.4 will change all this by introducing the concept of
VLAN names (more than one pool!!!)
(to be tested)
Philippe
Univ. of TN
On May 28, 2009, at 1:12 PM, Brooks, Stan wrote:
Actually, the VLANs are assigned to a particular controller, so your
limit (using /24 - 8096) is per controller. If you need more, go
with /23 subnets. Any way you cut it, it’s a lot of users per VAP
or per Controller.
We’ve been using VLAN pooling for something like 3 or 4 years now
and it’s been freaking AWESOME for scaling our wireless network.
The MAC hashing for load balancing clients wireless clients had been
great. It may not give a perfect user distribution across the
pooled VLANs but it gets very close.
Aruba’s layer 3 roaming (mobility) works with the VLAN pooling to
truly make a decent scalable wireless solution. After hearing about
different wireless deployments with a /20 subnet or larger just to
handle roaming, I shudder at the thought of NOT having VLAN pooling
an mobility.
>>-> Stan Brooks - CWNA/CWSP
Emory University
University Technology Services
404.727.0226
AIM/Y!/Twitter: WLANstan
MSN: wlans...@hotmail.com
GoogleTalk: wlans...@gmail.com
From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
] On Behalf Of Philippe Hanset
Sent: Thursday, May 28, 2009 12:56 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] ARuba VLAN pooling
If my memory serves me well, there is
a capacity caveat to Aruba's VLAN pooling at the moment:
(might change in a future code release)
1 SSID = 1 VAP = 1 Pool = Max 32 VLANs
So if you use /24, a maximum of 8096 ((256 - 3(gateway, network,
broadcast)) * 32) users is the limit for one SSID.
Not too many places have to worry about exceeding this number,
but it's good to keep in mind!
Philippe
Univ. of TN
On May 28, 2009, at 12:34 PM, Garrett Harmon wrote:
We've also loved vlan pooling, and the distribution of clients
across the /24's is excellent. As we start to see our vlans becoming
highly utilized, we simply add another /24 to the pool and slowly
the distribution evens out again, current users are not affected
until they disconnect and reconnect at which point they'll likely
receive a new vlan assignment, while new users immediately get
hashed into the new algorithm.
Garrett Harmon
Network Engineer
Office of Information Technology
The Ohio State University
614.292.2122 (o)
614.747.5539 (c)
On May 28, 2009, at 11:45 AM, Michael Dickson wrote:
We find that Vlan Pooling does a really good job at "balancing" the
users across our 24 client vlans. We have eighteen client vlans on
our main SSID and I'm impressed with the even distribution this
feature offers.
If you have multiple local controllers make sure that the client
vlans are properly configured on each controller for both L2 and L3.
This will ensure that the clients can roam across "controller
boundaries" with the same IP address.
Also, we found it helpful to size each client vlan/subnet the same
(again we use /24 subnets)
Hope this helps.
Mike
*******************************
Michael Dickson
Network Analyst
University of Massachusetts
Network Systems and Services
********************************
Ken Connell wrote:
Assuming you you have multiple client side vlans already configured
on your controller, you assign those vlans to the vap (currently
your only specifying one vlan, just comma seperate and add
another ). Now when a user associates, there is hash done on the
client mac address and they are placed in a vlan based on the output
of the hash.
That mac will always hash out the same, and they will therefore
always be put into the same vlan.
Just be careful if you have any static clients or use reserved DHCP,
cause once you add another vlan to the pool, they'll more than
likely hash out to a diff vlan and therefore require a diff IP of
course....
We've been using that since it was available and have no complaints.
Ken Connell
Intermediate Network Engineer
Computer & Communication Services
Ryerson University
350 Victoria St
RM AB50
Toronto, Ont
M5B 2K3
416-979-5000 x6709
------------------------------------------------------------------------
*From*: Jason Appah
*Date*: Thu, 28 May 2009 08:16:07 -0700
*To*: <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>
*Subject*: [WIRELESS-LAN] ARuba VLAN pooling
What is this VLAN pooling? How does it work? **********
Participation and subscription information for this EDUCAUSE
Constituent Group discussion list can be found at http://www.educause.edu/groups/
.
**********
Participation and subscription information for this EDUCAUSE
Constituent Group discussion list can be found at http://www.educause.edu/groups/
.
--
BEGIN-ANTISPAM-VOTING-LINKS
------------------------------------------------------
Teach CanIt if this mail (ID 879804209) is spam:
Spam: https://antispam.osu.edu/b.php?c=s&i=879804209&m=307de3940232
Not spam: https://antispam.osu.edu/b.php?c=n&i=879804209&m=307de3940232
Forget vote: https://antispam.osu.edu/b.php?c=f&i=879804209&m=307de3940232
------------------------------------------------------
END-ANTISPAM-VOTING-LINKS
********** Participation and subscription information for this
EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/
.
********** Participation and subscription information for this
EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/
.
This e-mail message (including any attachments) is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination,
distribution
or copying of this message (including any attachments) is strictly
prohibited.
If you have received this message in error, please contact
the sender by reply e-mail message and destroy all copies of the
original message (including attachments).
********** Participation and subscription information for this
EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/
.
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/groups/.
