<?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 Roaming between WLCs and Mobility Groups in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/roaming-between-wlcs-and-mobility-groups/m-p/5304878#M284520</link>
    <description>&lt;P&gt;Hello, everyone.&lt;/P&gt;
&lt;P&gt;I need some clarification regarding roaming. My book says that:&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;If two controllers are assigned to &lt;STRONG&gt;different mobility groups&lt;/STRONG&gt;, clients &lt;STRONG&gt;can still roam&lt;/STRONG&gt; between them, but the roam is not very efficient. &lt;STRONG&gt;Credentials are not cached and shared&lt;/STRONG&gt;, so clients must go through a full authentication during the roam.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;My other book states that&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Client roaming can occur between controllers that are in different mobility groups &lt;STRONG&gt;as long as the controllers are in the same mobility domain&lt;/STRONG&gt;. If a client moves from one controller to another in a different mobility domain (that is, to a controller that is not known by the controller that the client leaves), the client has to reauthenticate, reassociate, and get new IP address information.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;Please, how exactly does seamless roaming happen? I feel like the explanations of these two books conflict a bit. Do the two WLCs need to be part of the same mobility group in order for credentials to be cached, etc? Or do they just have to be a part of the same mobility domain, or how is it please?&lt;/P&gt;
&lt;P&gt;Thank you&lt;BR /&gt;David&lt;/P&gt;</description>
    <pubDate>Wed, 02 Jul 2025 13:45:13 GMT</pubDate>
    <dc:creator>Mitrixsen</dc:creator>
    <dc:date>2025-07-02T13:45:13Z</dc:date>
    <item>
      <title>Roaming between WLCs and Mobility Groups</title>
      <link>https://community.cisco.com/t5/wireless/roaming-between-wlcs-and-mobility-groups/m-p/5304878#M284520</link>
      <description>&lt;P&gt;Hello, everyone.&lt;/P&gt;
&lt;P&gt;I need some clarification regarding roaming. My book says that:&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;If two controllers are assigned to &lt;STRONG&gt;different mobility groups&lt;/STRONG&gt;, clients &lt;STRONG&gt;can still roam&lt;/STRONG&gt; between them, but the roam is not very efficient. &lt;STRONG&gt;Credentials are not cached and shared&lt;/STRONG&gt;, so clients must go through a full authentication during the roam.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;My other book states that&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Client roaming can occur between controllers that are in different mobility groups &lt;STRONG&gt;as long as the controllers are in the same mobility domain&lt;/STRONG&gt;. If a client moves from one controller to another in a different mobility domain (that is, to a controller that is not known by the controller that the client leaves), the client has to reauthenticate, reassociate, and get new IP address information.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;Please, how exactly does seamless roaming happen? I feel like the explanations of these two books conflict a bit. Do the two WLCs need to be part of the same mobility group in order for credentials to be cached, etc? Or do they just have to be a part of the same mobility domain, or how is it please?&lt;/P&gt;
&lt;P&gt;Thank you&lt;BR /&gt;David&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jul 2025 13:45:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/roaming-between-wlcs-and-mobility-groups/m-p/5304878#M284520</guid>
      <dc:creator>Mitrixsen</dc:creator>
      <dc:date>2025-07-02T13:45:13Z</dc:date>
    </item>
    <item>
      <title>Re: Roaming between WLCs and Mobility Groups</title>
      <link>https://community.cisco.com/t5/wireless/roaming-between-wlcs-and-mobility-groups/m-p/5305023#M284530</link>
      <description>&lt;P&gt;Depends on the OS of the controllers.&amp;nbsp; But I'd say:&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Controllers must share the same SSID-related config.&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;Controllers must be in the same mobility group &amp;amp; mobility domain.&amp;nbsp;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Depends on the firmware version on the controller(s) but they can be different.&amp;nbsp; However, it is best for them to be the same firmware so they can share the same bugs and share the same cause of the crash.&amp;nbsp; There will be some Bug IDs where the Workround recommends not to use Mobility Group because this adds special "tax" to the uncontrollable and untameable WNCD process (9800-40/-80, 9800M, 9800H1/H2).&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Mobility Group is fine if the WLC is the 9800-L because there is only one WNCD instance.&amp;nbsp; Any controller with multiple WNCD instance will face issues.&amp;nbsp; That's a guarantee.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jul 2025 22:04:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/roaming-between-wlcs-and-mobility-groups/m-p/5305023#M284530</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2025-07-02T22:04:01Z</dc:date>
    </item>
    <item>
      <title>Re: Roaming between WLCs and Mobility Groups</title>
      <link>https://community.cisco.com/t5/wireless/roaming-between-wlcs-and-mobility-groups/m-p/5305066#M284535</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/326026"&gt;@Leo Laohoo&lt;/a&gt;&amp;nbsp;isn’t that mobility group bug you’re referring to specifically for a group that is formed between a 9800 WLC and an AireOS-based WLC? Or do I have that mixed up with something else?&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jul 2025 03:44:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/roaming-between-wlcs-and-mobility-groups/m-p/5305066#M284535</guid>
      <dc:creator>eglinsky2012</dc:creator>
      <dc:date>2025-07-03T03:44:58Z</dc:date>
    </item>
    <item>
      <title>Re: Roaming between WLCs and Mobility Groups</title>
      <link>https://community.cisco.com/t5/wireless/roaming-between-wlcs-and-mobility-groups/m-p/5305089#M284538</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/314036"&gt;@eglinsky2012&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;isn’t that mobility group bug you’re referring to specifically for a group that is formed between a 9800 WLC and an AireOS-based WLC? Or do I have that mixed up with something else?&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Nope.&amp;nbsp; There are a few (two, if I remembered correctly) that I've read and impacts IOS-XE only.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jul 2025 05:36:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/roaming-between-wlcs-and-mobility-groups/m-p/5305089#M284538</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2025-07-03T05:36:29Z</dc:date>
    </item>
  </channel>
</rss>

