<?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 Creating Mobility Groups with 4402 in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/creating-mobility-groups-with-4402/m-p/2359092#M36360</link>
    <description>&lt;P&gt;I'm looking to place three production 4402 controllers into the same mobility group.&amp;nbsp; There are currently no mobility groups.&amp;nbsp; My question is, will this affect clients somehow when I add the controllers to the same group?&amp;nbsp; I'm pretty sure not, but I just wanted to make sure.&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jul 2021 06:51:31 GMT</pubDate>
    <dc:creator>kevinyamada</dc:creator>
    <dc:date>2021-07-05T06:51:31Z</dc:date>
    <item>
      <title>Creating Mobility Groups with 4402</title>
      <link>https://community.cisco.com/t5/wireless/creating-mobility-groups-with-4402/m-p/2359092#M36360</link>
      <description>&lt;P&gt;I'm looking to place three production 4402 controllers into the same mobility group.&amp;nbsp; There are currently no mobility groups.&amp;nbsp; My question is, will this affect clients somehow when I add the controllers to the same group?&amp;nbsp; I'm pretty sure not, but I just wanted to make sure.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 06:51:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/creating-mobility-groups-with-4402/m-p/2359092#M36360</guid>
      <dc:creator>kevinyamada</dc:creator>
      <dc:date>2021-07-05T06:51:31Z</dc:date>
    </item>
    <item>
      <title>Creating Mobility Groups with 4402</title>
      <link>https://community.cisco.com/t5/wireless/creating-mobility-groups-with-4402/m-p/2359093#M36361</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, you're right, it'll not harm the client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#Mobility group is useful for smooth Roaming, Anchoring and AP fallback. WLC reboot is not required to add/configure Mobility.&lt;/P&gt;&lt;P&gt;#If you've similar wlan configured on all these 3 WLCs and clients were trying to do roaming, it probably doing failover roaming with dhcp delays. Since it is already harming those client, feel free to configure Mobility.&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;#If the APs on those 4402s shares the RF then be sure to configure similar RF groups to avoid each APs idetifying themselves as Rogues.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Dec 2013 21:06:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/creating-mobility-groups-with-4402/m-p/2359093#M36361</guid>
      <dc:creator>Saravanan Lakshmanan</dc:creator>
      <dc:date>2013-12-27T21:06:51Z</dc:date>
    </item>
    <item>
      <title>Creating Mobility Groups with 4402</title>
      <link>https://community.cisco.com/t5/wireless/creating-mobility-groups-with-4402/m-p/2359094#M36362</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Awesome.&amp;nbsp; Thanks for the help!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Dec 2013 21:59:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/creating-mobility-groups-with-4402/m-p/2359094#M36362</guid>
      <dc:creator>kevinyamada</dc:creator>
      <dc:date>2013-12-27T21:59:50Z</dc:date>
    </item>
  </channel>
</rss>

