Wireless Access

Contributor I

Bandwidth Contracts per AP-Group in a clusterd setup

Can anyone explain to me how bandwidth contracts in the controller work?

For example what happens when I create a bandwidth contract of 50Mb on a per AP group basis and have two clients in the same role connected to the same controller within the cluster.
I assume each user will get 25Mb.


But what happens if those two users have a different role within the controller. Or if those users are connected to a different controller within the cluster.


Do the same rules still apply?

Guru Elite

Re: Bandwidth Contracts per AP-Group in a clusterd setup

I honestly don't think that ap-group bandwidth contracts were modified to account for clustering, so your results would be unpredictable.

*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Remote Access Point Solution Guide
ArubaOS Consolidated Release Notes
ArubaOS 8 ViA VPN Solution Guide

Re: Bandwidth Contracts per AP-Group in a clusterd setup

Colin is right, there is no consideration of cluster - if the group (or user-role) is configured for a 50Mbps shaper, and there are 2 users, each on a separate controller, then each can have 50Mbps of throughput.


A shaper contract, whether applied to a role or a single user, allocates its buffer depth depending on the rate configured. The smaller the shape rate the smaller the buffer. There is no ordering or precedence applied per user, ergo if there is a single 50Mbps shaper applied to a role then all users on that controller in that role will have at it on a first come first served basis. It would not necessarily result in 50/50 splitting, e.g. if one client already had a heavy transfer running and the second client started up, it would have to fight to get through.


As such, group based shaping can be quite unfair, and is often detrimental to real time traffic as there is no fancy stuff done when deciding what packets to drop when the buffer is full.


Routers and dedicated packet shapers of course offer a wider selection of shaper algorithms that increase fairness, improve QOS and implement minimum guaranteed rate etc., but the controller unfortunately does not have such capabilities.


Final comment, please be aware of bug AOS-191579 which causes auth crashes on S-UAC when ap-group bandwidth contracts are configured. It's just recently fixed in and, and any 8.6.0.x.  If you're not on 8.6 or one of the fixed builds, you should probably move to role based in the interim.

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