Environment : This article applies to all Aruba Instant Access Points running Aruba InstantOS 126.96.36.199-188.8.131.52 or higher.
Empirical testing at Aruba has shown that the number of clients on a given channel, not clients per access point, is the dominant predictor of data capacity. This is because closely spaced access points create an interference zone where Wi-Fi transmissions are detected by most access points and clients on the channel, so adding access points merely increases co-channel interference.
While the decision about which access point to choose is normally left to the client, ARM’s infrastructure-controlled load balancing forces the client to a ‘better’ channel using standard association response frames.
The command below helps us to understand the RF neighborhood with neighbor access points, their active channel and associated client count per channel. It also gives an idea if load enforcement is activated on AP which generally depends on below rule:
Current_associated >= Client_Threshold
IAP's send updates (such as client propagation information) in the form of Information Element (IE) within the probe request packets. Once the AP receives the update, it is checked across its own density map to decide if the AP falls with same RF neighborhood or not.
show ap debug spectrum-load-balancing x
(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.