Troubleshooting the non-connection problem during terminal roaming

Troubleshooting the non-connection problem during terminal roaming

 Centralized forwarding networking without encryption. When a site reports that a terminal is roaming under the AP, the connection will be disconnected, and it cannot be reconnected without manual intervention. After air interface packet capture, it can be seen that after the terminal roams, it initiates an auth request to the new AP at the first time, and continues to try to initiate an assoc request to the AP when no AP auth response is obtained, the AP rejects and replies to deauth, and opens the deauth message Analysis, the reason is "Dauthentication Reason Code: 6 Class 2 frame received from non-authenticated station” refers to receiving a Class 2 message from an unauthenticated terminal; then the terminal initiates an association request to another new SSID. So the problem turns to troubleshooting why the AC does not reply to the auth request initiated by the terminal. First check the link, because the terminal has a time requirement for the AP to reply to auth. If the time is too long, the terminal will think it is timed out. After counting the wired delays of all APs on site, it is found that a large number of APs have problems with large delays, so the root cause of the problem is found. After checking the cable on site, the problem disappeared.

Solution:

The large delay of the wired link causes the wireless controller to reply auth slowly, which eventually leads to problems. Adjust the wired link to ensure that the wired delay is within 10ms.