Environment : This article applies to all Aruba Instant Access Points running Aruba InstantOS 126.96.36.199-188.8.131.52 or higher.
Spectrum Load Balancing (SLB) divides APs in a cluster into several logical virtual RF neighborhood domains and these AP's in the same RF neighborhood share the same clients. For example, in the below figure, there are 15 Instant APs in a cluster. Take AP1, AP2 and AP3, each of them has a different virtual RF neighborhood
The virtual RF neighborhoods are automatically created via ARM scanning, client density updates and neighbor exchanges.
This ensures that APs that are far away from the clients perspective do not belong to the virtual RF neighborhood, to avoid redirecting clients to a far away AP that is on a lightly loaded channel.
APs in the virtual RF neighborhood participate in client load balancing using association responses to direct clients towards APs on less loaded channels.
IAP's send updates which includes density map, working channel, and current associated clients count in that radio (sum of all vaps) in the form of Information Element (IE) within the probe request packets. Once the AP receives the update, it lists all the density maps in the database, and compare to my own density map. If the two density maps are 75%+ match, (which is controlled by "SLB Matching Interval" configuration parameter) the neighbor is in my virtual RF neighborhood.
APs continously monitor the client associations and client count threshold on its own channel and if it hits condition (Current_associated >= Client_Threshold), load enforcement kicks in and clients starts associating to channels of other APs that have less client count.
(Where, x stands for radio: 0 or 1. 0 is for 5.GHz and 1 is for 2.4GHz)
AP's with "VR" flag, are valid and in the same RF Neighborhood domain.
- Whereas, AP's with "V" flag are valid but not in the same RF domain as the Instant AP that we are running the command on.
- APs with "S" flag, indicates that they are on the same channel.
- "Recved_Seconds" is the amount of the seconds before the update was received from neighbor AP of same RF neighborhood.
|Note: The entry in the SLB neighbor table is aged out, if no entry from the neighbor AP is received in 5 mins (or) 300 seconds.