<?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 8.0 Change in AP Controller HA behavior? in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/8-0-change-in-ap-controller-ha-behavior/m-p/2906045#M56158</link>
    <description>&lt;P&gt;Has anything changed recently with the way APs react to changing HA Primary/Secondary/Tertiary controllers? Previously I was running 7.6.100.0, and when I would make changes to AP HA settings (either on the WLC or Prime), the APs would move and join the new primary controller in 2-5 minutes or so. Now it seems like they aren't automatically moving at all without a reboot. Is there something i'm missing to get an AP to go move to another controller without requiring a reboot?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jul 2021 12:02:30 GMT</pubDate>
    <dc:creator>cmonks119</dc:creator>
    <dc:date>2021-07-05T12:02:30Z</dc:date>
    <item>
      <title>8.0 Change in AP Controller HA behavior?</title>
      <link>https://community.cisco.com/t5/wireless/8-0-change-in-ap-controller-ha-behavior/m-p/2906045#M56158</link>
      <description>&lt;P&gt;Has anything changed recently with the way APs react to changing HA Primary/Secondary/Tertiary controllers? Previously I was running 7.6.100.0, and when I would make changes to AP HA settings (either on the WLC or Prime), the APs would move and join the new primary controller in 2-5 minutes or so. Now it seems like they aren't automatically moving at all without a reboot. Is there something i'm missing to get an AP to go move to another controller without requiring a reboot?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 12:02:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/8-0-change-in-ap-controller-ha-behavior/m-p/2906045#M56158</guid>
      <dc:creator>cmonks119</dc:creator>
      <dc:date>2021-07-05T12:02:30Z</dc:date>
    </item>
    <item>
      <title>I think you're talking about</title>
      <link>https://community.cisco.com/t5/wireless/8-0-change-in-ap-controller-ha-behavior/m-p/2906046#M56159</link>
      <description>&lt;P&gt;I think you're talking about AP SSO. Check WLC high availability SSO.&lt;/P&gt;
&lt;P&gt;It is working as a cluster (1 WLC is active and the other one is passive). In this setup, AP and users sessions are kept and no AP reboot and/or client disconnection.&lt;/P&gt;
&lt;P&gt;SSO works with some WLC (e.q.: 2504 not supporting this feature, 5508 yes)&lt;/P&gt;</description>
      <pubDate>Wed, 11 May 2016 15:56:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/8-0-change-in-ap-controller-ha-behavior/m-p/2906046#M56159</guid>
      <dc:creator>Francesco Molino</dc:creator>
      <dc:date>2016-05-11T15:56:01Z</dc:date>
    </item>
    <item>
      <title>Yes i'm familiar with AP SSO,</title>
      <link>https://community.cisco.com/t5/wireless/8-0-change-in-ap-controller-ha-behavior/m-p/2906047#M56160</link>
      <description>&lt;P&gt;Yes i'm familiar with AP SSO, i'm talking about manually moving an AP from one Standalone WLC (or HA Pair) to another. Not a fail-over scenario, but just moving for maintenance, etc.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 May 2016 16:08:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/8-0-change-in-ap-controller-ha-behavior/m-p/2906047#M56160</guid>
      <dc:creator>cmonks119</dc:creator>
      <dc:date>2016-05-11T16:08:26Z</dc:date>
    </item>
    <item>
      <title>Ok. I get your point now.</title>
      <link>https://community.cisco.com/t5/wireless/8-0-change-in-ap-controller-ha-behavior/m-p/2906048#M56161</link>
      <description>&lt;P&gt;Ok. I get your point now. Since I'm doing wireless, I've ever seen AP rebooting to do all discovery and join process (complete process including reboot is around 3 minutes) while they need to mount their tunnel with new WLC.&lt;/P&gt;
&lt;P&gt;Are your sure that during your 5 minutes with version 7.6, AP was not reloading?&lt;/P&gt;</description>
      <pubDate>Wed, 11 May 2016 18:42:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/8-0-change-in-ap-controller-ha-behavior/m-p/2906048#M56161</guid>
      <dc:creator>Francesco Molino</dc:creator>
      <dc:date>2016-05-11T18:42:40Z</dc:date>
    </item>
    <item>
      <title>Yes, the APs would move to</title>
      <link>https://community.cisco.com/t5/wireless/8-0-change-in-ap-controller-ha-behavior/m-p/2906049#M56162</link>
      <description>&lt;P&gt;Yes, the APs would move to the new WLC just by changing the primary WLC HA setting a couple minutes later. They did not reboot, just re-associated to the new WLC. I'm finding that with 8.0 now I have to manually reset the AP and it will joint the new WLC after rebooting..&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 12 May 2016 04:10:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/8-0-change-in-ap-controller-ha-behavior/m-p/2906049#M56162</guid>
      <dc:creator>cmonks119</dc:creator>
      <dc:date>2016-05-12T04:10:49Z</dc:date>
    </item>
    <item>
      <title>Anyone? How do you guys</title>
      <link>https://community.cisco.com/t5/wireless/8-0-change-in-ap-controller-ha-behavior/m-p/2906050#M56163</link>
      <description>&lt;P&gt;Anyone? How do you guys gracefully move APs from one controller to another? This new behavior is a real pain having to reboot each AP to move them.. I'd really like to know if this is by design or some kind of bug.&lt;/P&gt;</description>
      <pubDate>Wed, 25 May 2016 03:33:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/8-0-change-in-ap-controller-ha-behavior/m-p/2906050#M56163</guid>
      <dc:creator>cmonks119</dc:creator>
      <dc:date>2016-05-25T03:33:27Z</dc:date>
    </item>
  </channel>
</rss>

