<?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 It will only reboot the new in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/will-adding-a-new-ap-to-existing-ap-group-cause-all-ap-s-in/m-p/2560376#M131973</link>
    <description>&lt;P&gt;It will only reboot the new added AP not the entire existing AP group.&lt;/P&gt;</description>
    <pubDate>Fri, 20 Feb 2015 01:52:17 GMT</pubDate>
    <dc:creator>Abhishek Abhishek</dc:creator>
    <dc:date>2015-02-20T01:52:17Z</dc:date>
    <item>
      <title>Will adding a new AP to existing AP Group cause all AP's in group to reboot?</title>
      <link>https://community.cisco.com/t5/wireless/will-adding-a-new-ap-to-existing-ap-group-cause-all-ap-s-in/m-p/2560374#M131971</link>
      <description>&lt;P&gt;Hi Guys&lt;/P&gt;&lt;P&gt;Looking to deploy a new AP to vWLC controller, want to make sure I dont effect any users.. will adding a new AP to existing AP group cause all the AP's in group to reboot or only the new AP being added.&lt;/P&gt;&lt;P&gt;Kind Regards&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 09:13:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/will-adding-a-new-ap-to-existing-ap-group-cause-all-ap-s-in/m-p/2560374#M131971</guid>
      <dc:creator>Mohamed Hamid</dc:creator>
      <dc:date>2021-07-05T09:13:40Z</dc:date>
    </item>
    <item>
      <title>Only the new access-point</title>
      <link>https://community.cisco.com/t5/wireless/will-adding-a-new-ap-to-existing-ap-group-cause-all-ap-s-in/m-p/2560375#M131972</link>
      <description>&lt;P&gt;Only the new access-point will be restarted.&lt;BR /&gt;&lt;BR /&gt;Before you add the access-point to the correct group, the access-point by default will be placed in the default-group where WLAN ID 1 - 16 will be available with all the WLANs in the native VLAN of the access-point. Only this could give some impact if a client is nearby the new access-point and will roam to it. Don't forget to push the correct VLAN ID's with a FlexConnect group or just configure them static on the AP itself.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jan 2015 22:10:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/will-adding-a-new-ap-to-existing-ap-group-cause-all-ap-s-in/m-p/2560375#M131972</guid>
      <dc:creator>Freerk Terpstra</dc:creator>
      <dc:date>2015-01-07T22:10:33Z</dc:date>
    </item>
    <item>
      <title>It will only reboot the new</title>
      <link>https://community.cisco.com/t5/wireless/will-adding-a-new-ap-to-existing-ap-group-cause-all-ap-s-in/m-p/2560376#M131973</link>
      <description>&lt;P&gt;It will only reboot the new added AP not the entire existing AP group.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Feb 2015 01:52:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/will-adding-a-new-ap-to-existing-ap-group-cause-all-ap-s-in/m-p/2560376#M131973</guid>
      <dc:creator>Abhishek Abhishek</dc:creator>
      <dc:date>2015-02-20T01:52:17Z</dc:date>
    </item>
    <item>
      <title>It will not reboot the whole</title>
      <link>https://community.cisco.com/t5/wireless/will-adding-a-new-ap-to-existing-ap-group-cause-all-ap-s-in/m-p/2560377#M131974</link>
      <description>&lt;P&gt;It will not reboot the whole group when you edit/add AP in the group.&lt;/P&gt;&lt;P&gt;Correclty AP reboots only if there is a change to its 'AP mode' , 'AP Group' or 'HREAP Group'.&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 May 2015 22:48:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/will-adding-a-new-ap-to-existing-ap-group-cause-all-ap-s-in/m-p/2560377#M131974</guid>
      <dc:creator>sobhardw</dc:creator>
      <dc:date>2015-05-27T22:48:43Z</dc:date>
    </item>
  </channel>
</rss>

