<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Client roaming between APs at high traffic load cause 3 second gap in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5219643#M277368</link>
    <description>&lt;P&gt;After a couple of weeks with extensive testing with hundreds of AP roaming events at high uplink load (30Mbit/s), we found that the problem is gone after upgrading to WLC version 17.15.1.&lt;/P&gt;</description>
    <pubDate>Mon, 04 Nov 2024 12:24:14 GMT</pubDate>
    <dc:creator>Anders Hedlund</dc:creator>
    <dc:date>2024-11-04T12:24:14Z</dc:date>
    <item>
      <title>Client roaming between APs at high traffic load cause 3 second gap</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5073606#M270428</link>
      <description>&lt;P&gt;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).&lt;BR /&gt;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.&lt;BR /&gt;We have activated Radio Active Traces in the WLC and gets the response included below.&lt;BR /&gt;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).&lt;BR /&gt;We have tested roaming between them with low load and this does not happen then.&lt;BR /&gt;We are on WLC 9800-L version 17.13.1 (but we had the issue on the 17.9.4A also).&lt;BR /&gt;The AP version/models are:&lt;BR /&gt;17.13.0.107, C9124AXE-E&lt;BR /&gt;17.13.0.107, C9124AXE-B&lt;BR /&gt;17.13.0.107, C9120AXE-E&lt;BR /&gt;This is the reported issue in the debugTrace:&lt;BR /&gt;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&lt;BR /&gt;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)&lt;BR /&gt;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|&lt;/P&gt;&lt;P&gt;And in the analysis tool, we get:&lt;BR /&gt;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&lt;BR /&gt;Has anyone seen this? Any ideas how we can debug this further to better find a solution or work-around?&lt;BR /&gt;/Anders&lt;/P&gt;</description>
      <pubDate>Fri, 19 Apr 2024 09:37:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5073606#M270428</guid>
      <dc:creator>Anders Hedlund</dc:creator>
      <dc:date>2024-04-19T09:37:52Z</dc:date>
    </item>
    <item>
      <title>Re: Client roaming between APs at high traffic load cause 3 second gap</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5073655#M270431</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; You can feed Radio Active traces&amp;nbsp;&amp;nbsp;into :&amp;nbsp;&lt;A href="https://cway.cisco.com/wireless-debug-analyzer/" target="_blank"&gt;Wireless Debug Analyzer&lt;/A&gt;&amp;nbsp;for high level analysis&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Outputs from&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/217738-monitor-catalyst-9800-kpis-key-performa.html#anc5" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/217738-monitor-catalyst-9800-kpis-key-performa.html#anc5&lt;/A&gt;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;can also be useful&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;- You may try to tweak e.g. parameters related to fast roaming (802.11k,...)&lt;BR /&gt;&amp;nbsp; &amp;nbsp;-&amp;nbsp; I can assume that the mining environment is very challenging for wireless ; has sufficient site survey been done ?&lt;BR /&gt;&amp;nbsp; &amp;nbsp;- Check if wireless drivers of the camera's are up to date , and or can be updated or else&amp;nbsp; , look at new revisions of the&lt;BR /&gt;&amp;nbsp; &amp;nbsp;camera models with other firmware if applicable ,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; Also&amp;nbsp;&lt;SPAN&gt;have a checkup of the WLC 9800-L configuration with the CLI command&amp;nbsp;&lt;/SPAN&gt;&lt;FONT color="#008000"&gt;&lt;STRONG&gt;show tech wireless&lt;/STRONG&gt;&lt;/FONT&gt;&lt;SPAN&gt;&amp;nbsp;and feed the output to :&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://cway.cisco.com/wireless-config-analyzer/" target="_blank" rel="nofollow noopener noreferrer"&gt;Wireless Config Analyzer&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; M.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Apr 2024 10:53:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5073655#M270431</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2024-04-19T10:53:17Z</dc:date>
    </item>
    <item>
      <title>Re: Client roaming between APs at high traffic load cause 3 second gap</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5073691#M270434</link>
      <description>&lt;P&gt;CSCwi49862&lt;/P&gt;</description>
      <pubDate>Fri, 19 Apr 2024 11:31:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5073691#M270434</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2024-04-19T11:31:36Z</dc:date>
    </item>
    <item>
      <title>Re: Client roaming between APs at high traffic load cause 3 second gap</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5073710#M270438</link>
      <description>&lt;P&gt;&lt;BR /&gt;&amp;nbsp;-&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/326026"&gt;@Leo Laohoo&lt;/a&gt;&amp;nbsp;Leo , do you have shared and or allowed content availability for this bug because I get :&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;FONT color="#FF6600"&gt;&lt;STRONG&gt; &amp;nbsp;This bug is not available for viewing at this time&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Apr 2024 11:53:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5073710#M270438</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2024-04-19T11:53:19Z</dc:date>
    </item>
    <item>
      <title>Re: Client roaming between APs at high traffic load cause 3 second gap</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5073748#M270439</link>
      <description>&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://imgur.com/pKY4D6t" target="_blank"&gt;https://imgur.com/pKY4D6t&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Apr 2024 12:20:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5073748#M270439</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2024-04-19T12:20:25Z</dc:date>
    </item>
    <item>
      <title>Re: Client roaming between APs at high traffic load cause 3 second gap</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5073861#M270451</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1453932"&gt;@Anders Hedlund&lt;/a&gt;&amp;nbsp;have you tested 17.12 train?&lt;/P&gt;
&lt;P&gt;Cisco only recommends 17.13 for deployments that need new features introduced in that code, but TC will tell you to move to recommended 17.9.5 or 17.12.2 (17.12.3 in few weeks)&lt;/P&gt;</description>
      <pubDate>Fri, 19 Apr 2024 14:04:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5073861#M270451</guid>
      <dc:creator>JPavonM</dc:creator>
      <dc:date>2024-04-19T14:04:46Z</dc:date>
    </item>
    <item>
      <title>Re: Client roaming between APs at high traffic load cause 3 second gap</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5074536#M270497</link>
      <description>&lt;P&gt;17.12.3 has been out since 21 March 2024 and 17.14.1 was released last week, 13 April 2024.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-12/release-notes/rn-17-12-9800.html" target="_self"&gt;Release Notes for Cisco Catalyst 9800 Series Wireless Controller, Cisco IOS XE Dublin 17.12.x&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-14/release-notes/rn-17-14-9800.html" target="_self"&gt;Release Notes for Cisco Catalyst 9800 Series Wireless Controller, Cisco IOS XE 17.14.x&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 21 Apr 2024 00:05:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5074536#M270497</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2024-04-21T00:05:56Z</dc:date>
    </item>
    <item>
      <title>Re: Client roaming between APs at high traffic load cause 3 second gap</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5074537#M270498</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1453932"&gt;@Anders Hedlund&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Since the APs are in a vehicle, are the APs powered OFF when the vehicle is not in use?&lt;/P&gt;</description>
      <pubDate>Sun, 21 Apr 2024 00:08:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5074537#M270498</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2024-04-21T00:08:14Z</dc:date>
    </item>
    <item>
      <title>Re: Client roaming between APs at high traffic load cause 3 second gap</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5075537#M270573</link>
      <description>&lt;P&gt;Thanks Marce, yes, we have gone through the usual troubleshooting processes, what makes it tricky is that it's so tight correlated to the traffic load. We have tested adding a UDP packet generator (then skipping the cameras, so only the safety mechanism and the UDP packets) and if we set it to like 30Mbit/s UDP packets can clearly see the problem, but not if we switch it off or have less load).&lt;/P&gt;</description>
      <pubDate>Mon, 22 Apr 2024 21:43:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5075537#M270573</guid>
      <dc:creator>Anders Hedlund</dc:creator>
      <dc:date>2024-04-22T21:43:55Z</dc:date>
    </item>
    <item>
      <title>Re: Client roaming between APs at high traffic load cause 3 second gap</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5075540#M270574</link>
      <description>&lt;P&gt;Now this was interesting, thanks, we might have some contact that can dig this one out for us (it has some security classification).&lt;/P&gt;</description>
      <pubDate>Mon, 22 Apr 2024 21:46:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5075540#M270574</guid>
      <dc:creator>Anders Hedlund</dc:creator>
      <dc:date>2024-04-22T21:46:14Z</dc:date>
    </item>
    <item>
      <title>Re: Client roaming between APs at high traffic load cause 3 second gap</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5075544#M270575</link>
      <description>&lt;P&gt;Yes, we have to use 17.13, we have many many AP model 9124, and we need 17.13 to be able to run then in indoor-mode enabling non-DFS channel usage (we can not use DFS channels in our setup, it causes too long communucation gaps so the machines will make a safety stop).&lt;/P&gt;</description>
      <pubDate>Mon, 22 Apr 2024 21:51:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5075544#M270575</guid>
      <dc:creator>Anders Hedlund</dc:creator>
      <dc:date>2024-04-22T21:51:34Z</dc:date>
    </item>
    <item>
      <title>Re: Client roaming between APs at high traffic load cause 3 second gap</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5075547#M270576</link>
      <description>&lt;P&gt;We don't have the APs on the vehicles, sorry for not beeing clear about this. On the vehicles we have MOXA 4131A clients.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Apr 2024 21:55:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5075547#M270576</guid>
      <dc:creator>Anders Hedlund</dc:creator>
      <dc:date>2024-04-22T21:55:47Z</dc:date>
    </item>
    <item>
      <title>Re: Client roaming between APs at high traffic load cause 3 second gap</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5075569#M270580</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1453932"&gt;@Anders Hedlund&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;SPAN&gt;We don't have the APs on the vehicles, sorry for not beeing clear about this. On the vehicles we have MOXA 4131A clients.&lt;/SPAN&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Good.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Reboot the APs and see if the roaming has improved.&amp;nbsp; If it has, &lt;STRONG&gt;consider the possibility of rebooting the APs daily&lt;/STRONG&gt; -- Read between the lines.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Apr 2024 22:57:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5075569#M270580</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2024-04-22T22:57:25Z</dc:date>
    </item>
    <item>
      <title>Re: Client roaming between APs at high traffic load cause 3 second gap</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5199326#M276013</link>
      <description>&lt;P&gt;I dont have access to this one, is there any update? Is there a fix?&lt;/P&gt;</description>
      <pubDate>Thu, 26 Sep 2024 11:10:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5199326#M276013</guid>
      <dc:creator>PierreWallin4026</dc:creator>
      <dc:date>2024-09-26T11:10:02Z</dc:date>
    </item>
    <item>
      <title>Re: Client roaming between APs at high traffic load cause 3 second gap</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5199347#M276015</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I dont have access to this one, is there any update? Is there a fix?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Sep 2024 11:53:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5199347#M276015</guid>
      <dc:creator>PierreWallin4026</dc:creator>
      <dc:date>2024-09-26T11:53:10Z</dc:date>
    </item>
    <item>
      <title>Re: Client roaming between APs at high traffic load cause 3 second gap</title>
      <link>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5219643#M277368</link>
      <description>&lt;P&gt;After a couple of weeks with extensive testing with hundreds of AP roaming events at high uplink load (30Mbit/s), we found that the problem is gone after upgrading to WLC version 17.15.1.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Nov 2024 12:24:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-roaming-between-aps-at-high-traffic-load-cause-3-second/m-p/5219643#M277368</guid>
      <dc:creator>Anders Hedlund</dc:creator>
      <dc:date>2024-11-04T12:24:14Z</dc:date>
    </item>
  </channel>
</rss>

