client balancing has it been fixed

[AxL1971]

I recall last year there was some issue with client balancing on the AP and recommendation was to disable it.

I am aware the latest firmware has this resolved, has anyone enabled client balancing and what is the experience like.

[Mloraditch]

There was a bug with client balancing where certain SSID slots wouldn't work when enabled. That was fixed. There may have been other issues, but I'm not specifically aware of any.

[PhilipDAth]

The biggest issue with client load balancing is client support.  The way it works (simplified) is it sends the client a disconnection message.  The client then needs to try and connect to a different AP.

Some clients don't handle this well.  Some just simply disconnect and do nothing.

Computers tend to do this fine.  IoT devices don't tend to handle it that well.  Mobile devices and tablets have variable support.

[Networking101]

I believe this issue has not been fixed yet, Last week support recommended that we disable this feature. Its always good to enable and disable based on your experience and results.

[sinelnyyk]

Hi @AxL1971, @Networking101,

There was a bug in MR 30.7 where client balancing was rejecting clients from connecting to particular SSIDs. This is resolved in MR 30.7.1+ firmware versions, and we didn't have reiterations of this bug.

With this said, it is still recommended to keep Client Balancing disabled due to often client compatibility issues. If client doesn't support 802.11k, you can see something like "client was rejected by the AP" or "reason.code == 17" in the logs, which doesn't necessarily mean that that the AP is malfunctioning, but can just be compatibility issue. This behavior is explained quite well in this KB.