<?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: Delayed roaming in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3924124#M166262</link>
    <description>&lt;P&gt;Hello Mauro, try to identify if the issue is on the client-side or the AP side.&lt;/P&gt;
&lt;P&gt;From the WLC we should be able to see the new reassociation request from the client to the new AP, the authentication (PSK or 802.1x) and the 4-way handshake. to get that information run a debug on the WLC to track one client and wait until the issue happens again so we should be able to see if the WLC is receiving all that information. Follow the steps in the guide below to accomplish that task:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/213258-collect-debugs-from-wireless-lan-control.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/213258-collect-debugs-from-wireless-lan-control.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Once the desired event has occurred and you were able to debug it, you need to read the logs. You can use the guides in the links below to know how to read the debugs:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/aironet-1200-series/100260-wlc-debug-client.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/aironet-1200-series/100260-wlc-debug-client.html&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://mrncciew.com/2014/10/15/wlc-client-debug-part-1/" target="_blank"&gt;https://mrncciew.com/2014/10/15/wlc-client-debug-part-1/&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://mrncciew.com/2014/10/17/wlc-client-debug-part-2/" target="_blank"&gt;https://mrncciew.com/2014/10/17/wlc-client-debug-part-2/&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://mrncciew.com/2019/06/03/wlc-client-debug-part-3/" target="_blank"&gt;https://mrncciew.com/2019/06/03/wlc-client-debug-part-3/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Or you can use the online debug reader with a Cisco ID at&amp;nbsp;&lt;A href="https://cway.cisco.com/tools/WirelessDebugAnalyzer/" target="_blank"&gt;https://cway.cisco.com/tools/WirelessDebugAnalyzer/&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;From the client you should be able to see the client looking for another AP when the signal is weak, a new connection request for the new AP, the authentication and the 4-way handshake, you can look at that by running tracest on the laptop. Take a look at the video in the link below, start watching the video from minute 22:00 for checking how to run tracest and how to read them:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.youtube.com/watch?v=vYbtiY3bnTM&amp;amp;t=640s" target="_blank"&gt;https://www.youtube.com/watch?v=vYbtiY3bnTM&amp;amp;t=640s&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;before doing all the stuff above make sure that your WLC is running a recommended code listed in this link: &lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/200046-tac-recommended-aireos.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/200046-tac-recommended-aireos.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;And that your wireless client is running the latest wireless driver code. Look for that information on the CMD using netsh WLAN show driver command, look at this link as a reference of what you should see: &lt;A href="https://www.solvetic.com/tutoriales/article/4168-comando-netsh-gestionar-conexion-red-wifi-windows/" target="_blank"&gt;https://www.solvetic.com/tutoriales/article/4168-comando-netsh-gestionar-conexion-red-wifi-windows/&lt;/A&gt; finally look at the driver provider web page whats the latest code for your NIC.&lt;/P&gt;</description>
    <pubDate>Fri, 13 Sep 2019 18:14:01 GMT</pubDate>
    <dc:creator>jonathga</dc:creator>
    <dc:date>2019-09-13T18:14:01Z</dc:date>
    <item>
      <title>Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3727500#M166229</link>
      <description>&lt;P&gt;I have inherited a 5 year old WLAN deployment&amp;nbsp;where clients have never successfully roamed. There is a 10 - 20 second delay when moving between AP.&amp;nbsp;During this break the wifi icon disappears from devices and connectivity is lost. We have a mix&amp;nbsp;of iOS, Android, SurfacePro and the odd laptop on the network and all encounter the same issue. I do not see any disassociation&amp;nbsp;events in the debug when this happens.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Where do I troubleshoot from here to track down the root cause? have attached a debug log&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;5508 (8.2.151.0) controller and mix of 3502 &amp;amp; 3602 AP. Dual 2.4/5Ghz&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 16:19:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3727500#M166229</guid>
      <dc:creator>Pako1</dc:creator>
      <dc:date>2021-07-05T16:19:19Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3727783#M166230</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I have a similar question. We are running two WLC 5508 controllers with software release 8.3 in a HA configuration and Cisco 2802E 802.11ac Wave 2 access points.&lt;/P&gt;
&lt;P&gt;All access points placed in the same building are attached to the same controller so that Intra-Controller-Roaming does not occur when moving in the building.&lt;/P&gt;
&lt;P&gt;However, we sometimes observe that clients (mostly Windows notebooks with Intel 8265 wireless NIC) stay too long connected to the same AP, whereas they should already have moved to another access point that is closer.&lt;/P&gt;
&lt;P&gt;We never have configured anything special regarding to roaming. However, is there something we can do in order to increase the roaming time to make sure clients roam to a closer AP more quickly?&lt;/P&gt;
&lt;P&gt;Thanks&lt;BR /&gt;Michael&lt;/P&gt;</description>
      <pubDate>Thu, 18 Oct 2018 11:38:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3727783#M166230</guid>
      <dc:creator>michaelbs</dc:creator>
      <dc:date>2018-10-18T11:38:54Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3727861#M166231</link>
      <description>&lt;P&gt;First I would go to 8.2.170.0 code &amp;amp; see if behavior remain as it is.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;Rasika&lt;/P&gt;
&lt;P&gt;*** Pls rate all useful responses ***&lt;/P&gt;</description>
      <pubDate>Thu, 18 Oct 2018 13:18:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3727861#M166231</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2018-10-18T13:18:07Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3727878#M166232</link>
      <description>What is the roaming sensitivity configured in the wlan driver? &lt;BR /&gt;And is the driver more or less up to date?&lt;BR /&gt;Don't forget, the client decides when it wants to roam.</description>
      <pubDate>Thu, 18 Oct 2018 13:27:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3727878#M166232</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2018-10-18T13:27:17Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728228#M166233</link>
      <description>&lt;P&gt;The WLC/Aps&amp;nbsp; has been through many version over the years and none have made a difference.Is there a reason for you thinking upgrading to that version will resolve this?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So if the clients are sticking to previous AP, how can I validate that is indeed what is happening? On the iphones it appears disconnected but debug shows a reassociation not disconnection/association.&amp;nbsp;Is a 20-30 second (sometimes minute) delay normal in these cases?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;How can I tune the system to make the clients more likely to decide to roam faster instead of hanging on to an AP that it cant communicate with. Can I adjust rssi so signal strength between AP is lower?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Oct 2018 01:07:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728228#M166233</guid>
      <dc:creator>Pako1</dc:creator>
      <dc:date>2018-10-19T01:07:37Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728354#M166234</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Is there a reason for you thinking upgrading to that version will resolve this?&lt;/STRONG&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;No point spending lot of time in troubleshooting, if current code you running have known issues. As of today 8.2.170.0 is the recommended code in 8.2 train. So let's do that first &amp;amp; then spend time on troubleshooting if issues is there.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Is a 20-30 second (sometimes minute) delay normal in these cases?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;It is not normal taking that long to roam.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Pls give more information about how your WLAN is configured (WPA2-PSK or WPA2-Enterprise, what encryption methods, etc), is any fast roaming methods configured (like FT)&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;HTH&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Rasika&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Oct 2018 02:46:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728354#M166234</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2018-10-19T02:46:40Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728412#M166235</link>
      <description>If you have a dense enough coverage, you can lower the signal strength of the APs and also increase the minimum speed (disable rates 1, 2, ... and leave 18 as the minimum enabled).&lt;BR /&gt;</description>
      <pubDate>Fri, 19 Oct 2018 06:10:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728412#M166235</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2018-10-19T06:10:59Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728430#M166236</link>
      <description>&lt;P&gt;After Reading the following blog post about sticky MacOS wireless clients:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;A href="https://framebyframewifi.net/2017/08/20/macos-wi-fi-roaming/" target="_blank"&gt;https://framebyframewifi.net/2017/08/20/macos-wi-fi-roaming/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have enabled Optimized Roaming in our environment:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &lt;A href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-1/configuration-guide/b_cg81/b_cg81_chapter_010001110.pdf" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-1/configuration-guide/b_cg81/b_cg81_chapter_010001110.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm curious about whether this will help! Will let you know in a few days.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Oct 2018 06:52:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728430#M166236</guid>
      <dc:creator>michaelbs</dc:creator>
      <dc:date>2018-10-19T06:52:54Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728437#M166237</link>
      <description>From the Optimized Roaming manual: "This feature disassociates clients based on the RSSI of the client data packets and data rate."&lt;BR /&gt;Because of this, latency sensitive applications will have outages, also most older drivers don't understand what's happening and will cause an up to 1 minute outage. Also it can sometimes take a few minutes until a client can connect, because it tries and retries to connect to an "not optimal" AP, but always gets denied.&lt;BR /&gt;Use it with caution!</description>
      <pubDate>Fri, 19 Oct 2018 07:03:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728437#M166237</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2018-10-19T07:03:58Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728459#M166238</link>
      <description>&lt;P&gt;Thanks. We will test and observe this. Fortunately, all our laptops are quite new and therefore have new chips and wireless drivers install. It it causes issues, we will disable it.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Oct 2018 07:50:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728459#M166238</guid>
      <dc:creator>michaelbs</dc:creator>
      <dc:date>2018-10-19T07:50:55Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728539#M166239</link>
      <description>&lt;P&gt;Lower data rates are blocked. Density is pretty high in some sites so could be backed off. sh run attached&lt;/P&gt;</description>
      <pubDate>Fri, 19 Oct 2018 11:18:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728539#M166239</guid>
      <dc:creator>Pako1</dc:creator>
      <dc:date>2018-10-19T11:18:38Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728550#M166240</link>
      <description>Not fully. On 802.11a is 12M still enabled, although that is fairly ok and I wouldn't change it at the moment. &lt;BR /&gt;&lt;BR /&gt;If I read the config correct, you "only" have 20 MHz channels on 5 GHz, right? &lt;BR /&gt;That actually means your clients will not see an improved throughput on 5 GHz compared to 2.4 GHz. If your channel plan allows, enable also 40 MHz channels, that can double the throughput and will "look more interesting" for the clients to attach to, even at a slightly lower signal strength. &lt;BR /&gt;Check on the Home Tab of the WLC how the channel load on 5 GHz is during a normal day. If all the APs are &amp;lt; 10%, then you can probably savely enable 40 MHz. But don't forget to check it again after you've made the change.&lt;BR /&gt;</description>
      <pubDate>Fri, 19 Oct 2018 11:37:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728550#M166240</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2018-10-19T11:37:06Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728555#M166241</link>
      <description>&lt;P&gt;I have enabled and tested Optimized Roaming and it seems that it is indeed makes roaming faster. I just tested with a new Windows 10 laptop with Intel 8265 and wandered through the building. Each time I crossed another AP the client quickly associated with the AP.&lt;/P&gt;
&lt;P&gt;Should be enable CleanAir in order to make things more smooth? We currently have CleanAir completely disabled, however, all 2802E access points are capable of this.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Oct 2018 12:07:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728555#M166241</guid>
      <dc:creator>michaelbs</dc:creator>
      <dc:date>2018-10-19T12:07:23Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728562#M166242</link>
      <description>If you use RRM, DFS, and so on, yes it would benefit from using CleanAir.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 19 Oct 2018 12:16:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728562#M166242</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2018-10-19T12:16:08Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728571#M166243</link>
      <description>&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Oct 2018 12:39:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728571#M166243</guid>
      <dc:creator>michaelbs</dc:creator>
      <dc:date>2018-10-19T12:39:44Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728599#M166244</link>
      <description>&lt;P&gt;The Corp SSID is 5Ghz only. Guest was previously 2.4 only. The drop happened roaming on both these as well as the dual. Happens to all devices on all sites which led me to think it maybe a config problem&lt;/P&gt;</description>
      <pubDate>Fri, 19 Oct 2018 13:00:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728599#M166244</guid>
      <dc:creator>Pako1</dc:creator>
      <dc:date>2018-10-19T13:00:01Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728634#M166245</link>
      <description>It could also be a Radius or SSID security settings issue. But now it sounds like it's working okey'isch?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 19 Oct 2018 13:44:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728634#M166245</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2018-10-19T13:44:08Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728638#M166246</link>
      <description>Same for me, since like always with Cisco APs. Not sure why though, but the 802.11n models showed it really strong. Now the newer 2802 which are 802.11ac based, less so.&lt;BR /&gt;&lt;BR /&gt;There were models in the past, which had one more simultaneous stream in the upload direction (or was it antenna?), for those it was normal.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 19 Oct 2018 13:46:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728638#M166246</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2018-10-19T13:46:08Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728656#M166247</link>
      <description>&lt;P&gt;Thanks. Seems to be kind of normal then I guess as there a multiple threads out there discussing this. Its not an issue that causes problems in real life however since data rates are high enough for most workloads in our environment these days.&lt;/P&gt;
&lt;P&gt;btw - just updated the driver of a Intel wireless NIC from mid 2017 to mid 2018 and data rates nearly doubled on that client. It is unbelivable that the driver on the client device always have that much impact.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Oct 2018 14:13:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728656#M166247</guid>
      <dc:creator>michaelbs</dc:creator>
      <dc:date>2018-10-19T14:13:07Z</dc:date>
    </item>
    <item>
      <title>Re: Delayed roaming</title>
      <link>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728668#M166248</link>
      <description>The client device is the main factor and Intel has a history of really bad drivers. So I'm not surprised at all actually &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;Btw. If you update the Wi-Fi driver for Intel Wi-Fi devices, don't forget to also upgrade the Bluetooth driver (separate download).&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 19 Oct 2018 14:24:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/delayed-roaming/m-p/3728668#M166248</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2018-10-19T14:24:08Z</dc:date>
    </item>
  </channel>
</rss>

