Diagnosis

1	The problem persists for long periods, but not all the time or everywhere
2	Ongoing issue of Unable to connect to telnet service
3	Roam failed events during that time

Note that in this scenario the administrator has already determined Wi-Fi coverage aspects don’t contribute to the problem.

Select one of the

Roam failed

events. The following screen shows a

Roam Completed

message with an AP at a relative time of

0.0

indicating the device was connected in that area prior to the problem.

86 seconds later, when the device moves to a different area, the message

Reassoc Failed

indicates the device failed to connect to the new AP. The specific message

(Association denied because AP is unable to handle additional associated stations. Assoc status code received is 17.)

indicates that the AP reached its limit of associated clients of any kind, using a standard 802.11 reason code to convey its denial to the device.

Scroll down in this screen to

RAW OUTPUT

to observe the specific AP information.

Exit this

Roam failed

instance and open another one. Scroll down to observe

RAW OUTPUT

parameters, noting this instance shows a different AP than the previous one.

Repeat this with a few more

Roam failed

instances. Multiple APs in the same area respond to the device with the same denial reason code, supporting the conclusion that this area of the deployment is reaching the maximum capacity of allowed connected devices. This is most likely due to user mobility dynamics in which many users congregate in specific areas at specific times.