VLAN Pooling Behavior

  • 1
  • Question
  • Updated 2 weeks ago
I have 3 vlan pools created.  Two of them contain 2 vlans and the other contains 4 vlans.  The 2 vlan pools work like I expect with it placing clients in each vlan.  The 4 vlan pool is only placing clients into the first two vlans.  I am only in a testing phase right now and when I look in the first two vlans I'm typically seeing 10-15 addresses used.  Will the SZ not dip into the other vlans until It's getting closer to capacity on the first two?
Photo of John Westlund

John Westlund

  • 26 Posts
  • 2 Reply Likes

Posted 2 weeks ago

  • 1
Photo of Phil Coverdale

Phil Coverdale, Principal Technical Support Engineer

  • 26 Posts
  • 15 Reply Likes
Hi John,

Ruckus VLAN pooling uses the MAC address of the client device against a fixed algorithm.

This ensures that the client device will be assigned to the same VLAN from any AP in a given network which is essential for seamless roaming.
Using this method, it is not possible to guarantee an exactly even balance between the VLAN pools as would be when using 'round robin' or 'assign least used VLAN' pooling methods. Both of these methods would introduce roaming issues as a client may be assigned a different VLAN on an AP they have roamed to leaving the device without valid IP information until it is disconnected and reconnected.
 
With this in mind, it is strongly advised to create IP address pools within each VLAN that are considerably bigger than the even share that would be expected. Best practice dictates that each pool should have enough IP address to handle ALL of the devices in each pool to guarantee that any single pool cannot be exhausted.
 
The VLAN pool assigned is based on the last octet of the client device's MAC address. This value is divided by the number of available pools. The remainder of this calculation decides which pool the device will be assigned to.

Regards,

Phil.