<?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: Seamless Roaming within same Controller in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/seamless-roaming-within-same-controller/m-p/3374031#M146929</link>
    <description>&lt;P&gt;If you configure any fast roaming mechanisms (CCKM/OKC/802.11r/etc), then that to work , you have to configure FlexConnect Group. Then only those key chaching will distribute among APs within that flexconnect group.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;See below&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-1/Enterprise-Mobility-8-1-Design-Guide/Enterprise_Mobility_8-1_Deployment_Guide/ch7_HREA.html" target="_self"&gt;https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-1/Enterprise-Mobility-8-1-Design-Guide/Enterprise_Mobility_8-1_Deployment_Guide/ch7_HREA.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;"&lt;/P&gt;
&lt;UL&gt;
&lt;LI class="pBu1_Bullet1"&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;EM&gt;FlexConnect Groups are required for CCKM/OKC fast roaming to work with FlexConnect access points. Fast roaming is achieved by caching a derivative of the master key from a full EAP authentication so that a simple and secure key exchange can occur when a wireless client roams to a different access point. This feature prevents the need to perform a full RADIUS EAP authentication as the client roams from one access point to another. The FlexConnect access points need to obtain the CCKM/OKC cache information for all the clients that might associate so they can process it quickly instead of sending it back to the controller. If, for example, you have a controller with 300 access points and 100 clients that might associate, sending the CCKM/OKC cache for all 100 clients is not practical. If you create a FlexConnect Group comprising a limited number of access points (for example, you create a group for four access points in a remote office), the clients roam only among those four access points, and the CCKM/OKC cache is distributed among those four access points only when the clients associate to one of them.&lt;/EM&gt;&lt;/FONT&gt;"&lt;/LI&gt;
&lt;/UL&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, 26 Apr 2018 20:09:52 GMT</pubDate>
    <dc:creator>Rasika Nayanajith</dc:creator>
    <dc:date>2018-04-26T20:09:52Z</dc:date>
    <item>
      <title>Seamless Roaming within same Controller</title>
      <link>https://community.cisco.com/t5/wireless/seamless-roaming-within-same-controller/m-p/3373948#M146928</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have a regional controller serving multiple sites where access points are in local switching mode,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;what happens if the client roams from AP1 to AP2 with no flex-connect groups are configured, is it a seamless roaming? noting that AP1 and AP2 are both managed by the same regional WLC&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 15:34:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/seamless-roaming-within-same-controller/m-p/3373948#M146928</guid>
      <dc:creator>mina_raouf</dc:creator>
      <dc:date>2021-07-05T15:34:22Z</dc:date>
    </item>
    <item>
      <title>Re: Seamless Roaming within same Controller</title>
      <link>https://community.cisco.com/t5/wireless/seamless-roaming-within-same-controller/m-p/3374031#M146929</link>
      <description>&lt;P&gt;If you configure any fast roaming mechanisms (CCKM/OKC/802.11r/etc), then that to work , you have to configure FlexConnect Group. Then only those key chaching will distribute among APs within that flexconnect group.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;See below&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-1/Enterprise-Mobility-8-1-Design-Guide/Enterprise_Mobility_8-1_Deployment_Guide/ch7_HREA.html" target="_self"&gt;https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-1/Enterprise-Mobility-8-1-Design-Guide/Enterprise_Mobility_8-1_Deployment_Guide/ch7_HREA.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;"&lt;/P&gt;
&lt;UL&gt;
&lt;LI class="pBu1_Bullet1"&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;EM&gt;FlexConnect Groups are required for CCKM/OKC fast roaming to work with FlexConnect access points. Fast roaming is achieved by caching a derivative of the master key from a full EAP authentication so that a simple and secure key exchange can occur when a wireless client roams to a different access point. This feature prevents the need to perform a full RADIUS EAP authentication as the client roams from one access point to another. The FlexConnect access points need to obtain the CCKM/OKC cache information for all the clients that might associate so they can process it quickly instead of sending it back to the controller. If, for example, you have a controller with 300 access points and 100 clients that might associate, sending the CCKM/OKC cache for all 100 clients is not practical. If you create a FlexConnect Group comprising a limited number of access points (for example, you create a group for four access points in a remote office), the clients roam only among those four access points, and the CCKM/OKC cache is distributed among those four access points only when the clients associate to one of them.&lt;/EM&gt;&lt;/FONT&gt;"&lt;/LI&gt;
&lt;/UL&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, 26 Apr 2018 20:09:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/seamless-roaming-within-same-controller/m-p/3374031#M146929</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2018-04-26T20:09:52Z</dc:date>
    </item>
  </channel>
</rss>

