We are operating our vehicles remotely in the underground mines over Wi-Fi, the data load from the machine is constant around 30Mbit/s (yes, six to eight HD-cameras).
When switching between APs we have noticed that we sometimes get a transmission gap of around 3 seconds, causing the safety mechanism on the trucks to stop the machine.
We have activated Radio Active Traces in the WLC and gets the response included below.
We have more than 150 access points, and this happens between a few of them, most of them never has this problem, but on a few one it happens, we have tried changed the cables and also the access points (we even switched model).
We have tested roaming between them with low load and this does not happen then.
We are on WLC 9800-L version 17.13.1 (but we had the issue on the 17.9.4A also).
The AP version/models are:
17.13.0.107, C9124AXE-E
17.13.0.107, C9124AXE-B
17.13.0.107, C9120AXE-E
This is the reported issue in the debugTrace:
2024/04/04 04:07:20.696836577 {wncd_x_R0-0}{1}: [client-orch-sm] [18090]: (info): MAC: 0090.e89c.47bd Deleting the client, reason: 286, CO_CLIENT_DELETE_REASON_MN_AP_DRIVER_EVENT_CLASS3_RECV, Client state S_CO_RUN
2024/04/04 04:07:20.697072661 {wncd_x_R0-0}{1}: [errmsg] [18090]: (debug): %CLIENT_ORCH_LOG-7-CLIENT_MOVED_TO_DELETE_STATE: R0/0: wncd: Username (null), MAC: 0090.e89c.47bd, IP 10.88.19.154 disconnected from AP (G1N-AP-S-356-1) with SSID (Voysys-AX)
2024/04/04 04:07:20.697082437 {wncd_x_R0-0}{1}: [client-orch-sm] [18090]: (note): MAC: 0090.e89c.47bd Client delete initiated. Reason: CO_CLIENT_DELETE_REASON_MN_AP_DRIVER_EVENT_CLASS3_RECV, details: , fsm-state transition 2c|2d|2e|15|1a|1b|2c|37|46|48|4a|4c|51|60|62|83|86|8e|15|1a|1b|2c|37|46|48|4a|4c|51|60|62|83|ab|
And in the analysis tool, we get:
Controller initiated client deletion with code: CO_CLIENT_DELETE_REASON_MN_AP_DRIVER_EVENT_CLASS3_RECV. Explanation: AP triggered delete, as client sent class 3 frame (data, power save, some management) from non-authenticated client, may happen occasionally on connection recovery. Actions: Nothing required, unless this is happening frequently. This may need RA trace and OTA capture
Has anyone seen this? Any ideas how we can debug this further to better find a solution or work-around?
/Anders
