<?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: AP's disassociate during WLC upgrade in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874313#M45835</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Give the pruning a shot. Although my 40+ only allow the wireless vlans and we still had this issue. Also, we did notice some move to the secondary while most did not. They came right back up on the primary. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I suspect this is the norm and unless you pay extra close attention to the ap while upgrading you may not even notice this going on... &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Jan 2012 15:05:08 GMT</pubDate>
    <dc:creator>George Stefanick</dc:creator>
    <dc:date>2012-01-17T15:05:08Z</dc:date>
    <item>
      <title>AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874301#M45823</link>
      <description>&lt;P&gt;I'm upgrading (6) WiSM 1's(12 controllers) from 7.0.98 to 7.0.116.&amp;nbsp; I've completed 3 controllers total so far, and on every one of them, the AP's disassociate during the upgrade process.&amp;nbsp; This happens when "&lt;EM&gt;Writing &lt;/EM&gt;new &lt;EM&gt;APIB &lt;/EM&gt;to flash disk"...&amp;nbsp; How am I supposed to predownload the image to the AP's if they keep disassociating?&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I started a continuous ping to the 3rd upgraded controller before starting the upgrade process.&amp;nbsp; Ping times were normal, &amp;lt;1ms, in the beginning... then spiked to 30-40ms in the final stages of the upgrade, which is when the AP's disassociated.&amp;nbsp; Coincidence or cause?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;P&gt;Tony&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 04:23:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874301#M45823</guid>
      <dc:creator>Tony Davis</dc:creator>
      <dc:date>2021-07-04T04:23:48Z</dc:date>
    </item>
    <item>
      <title>AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874302#M45824</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That doesn't seem right.... I haven't upgraded a WiSM in a while, but on the stand-alone WLC, you do not have the AP's disassociate from the WLC during the upload process.&amp;nbsp; Might want to see what others say or just open a TAC case.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 13:56:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874302#M45824</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2012-01-17T13:56:20Z</dc:date>
    </item>
    <item>
      <title>AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874303#M45825</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually, the pings rise starting with "Executing backup script", continue through RTOS to flash, &lt;/P&gt;&lt;P&gt;AP's started disassociating during the apib install&lt;/P&gt;&lt;P&gt;dropped more during the "fini script"&lt;/P&gt;&lt;P&gt;All are completely disassociated by the end of the upgrade&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 14:05:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874303#M45825</guid>
      <dc:creator>Tony Davis</dc:creator>
      <dc:date>2012-01-17T14:05:38Z</dc:date>
    </item>
    <item>
      <title>AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874304#M45826</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Log from WLC GUI........&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:30:37:a6:c9:3b:00&amp;nbsp; Cause=Heartbeat Timeout Status:NA&lt;/P&gt;&lt;P&gt;AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:30:37:a6:c9:3b:00&amp;nbsp; Cause=Heartbeat Timeout Status:NA&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have messages like this for every AP&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 14:08:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874304#M45826</guid>
      <dc:creator>Tony Davis</dc:creator>
      <dc:date>2012-01-17T14:08:33Z</dc:date>
    </item>
    <item>
      <title>Re: AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874305#M45827</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would open a TAC case… maybe there is a bug id for that, I just don’t know.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 14:09:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874305#M45827</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2012-01-17T14:09:36Z</dc:date>
    </item>
    <item>
      <title>AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874306#M45828</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I can confirm this. I have a ton of WLCs I just updated and during the unpacking the aps would do the same thing on my 4400 and WISMs. Although I didnt notice it on the 5508s. I suspect the controller processor is under load and misses a few of the control plane packets.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How this became apparent for me is because of my WCS email alerts. I got blasted with ap dissociations. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 14:11:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874306#M45828</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2012-01-17T14:11:29Z</dc:date>
    </item>
    <item>
      <title>Re: AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874307#M45829</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;that a actually makes sense as that's the time the WLC is getting busy and pings could be delayed as its 'scavenger' traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But they should stay associated until you reboot. Now there were some issues In earlier code where odd issues, AP rebooting, WLC pushing the code that was downloaded, before the WLC reboots.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Out of curiosity, are you pruning the non-wireless v,an from the WiSM port channel?  Did you set a syslog for the AP?  Excess broadcast traffic could cause an issue like this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support iPad App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 14:12:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874307#M45829</guid>
      <dc:creator>Stephen Rodriguez</dc:creator>
      <dc:date>2012-01-17T14:12:24Z</dc:date>
    </item>
    <item>
      <title>AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874308#M45830</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Tony,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My issue was when the WLCs took the code. Once the code was on the WLCs the APs stay associated. Are you say when you push the image they are dropping ? Ive heard of this as well. A guy commented on twitter about this a few weeks ago. That I havent seen for myself. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 14:23:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874308#M45830</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2012-01-17T14:23:12Z</dc:date>
    </item>
    <item>
      <title>Re: AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874309#M45831</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is during the code download &lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;to&lt;/STRONG&gt;&lt;/SPAN&gt; the controller.&amp;nbsp; The AP's disassociate before I get a chance to push the image to the AP's...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 14:31:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874309#M45831</guid>
      <dc:creator>Tony Davis</dc:creator>
      <dc:date>2012-01-17T14:31:52Z</dc:date>
    </item>
    <item>
      <title>Re: AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874310#M45832</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok, thats what I seen as well. But once the aps come back (like 2 seconds later) they stay on, or atleast they did with all of mine. After the WLC takes the new code and is done unpacking you then do the predownload. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will mentioned I had an issue with 7.0.98.0 and predownloading to the aps. But it wasnt related to what you mentioned. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 14:41:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874310#M45832</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2012-01-17T14:41:37Z</dc:date>
    </item>
    <item>
      <title>Re: AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874311#M45833</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We do not prune any VLANs on the port channels for the WiSM's...&amp;nbsp; It is apparent that the controller is "busy", but what is making the AP's heartbeat timer expire?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 14:43:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874311#M45833</guid>
      <dc:creator>Tony Davis</dc:creator>
      <dc:date>2012-01-17T14:43:11Z</dc:date>
    </item>
    <item>
      <title>Re: AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874312#M45834</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;because the wl. Is too busy processing other information and does not reply to the heartbeat from the AP. I bet of you looked at the secondary WLC you would see the ap moved when the heartbeat failed to its primary. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you try pruning the non-wireless vlan and setting a syslog for the ap so they aren't broadcasting, before you upgrade the next WLC and see if they remain stable on their primary?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steve &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 14:54:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874312#M45834</guid>
      <dc:creator>Stephen Rodriguez</dc:creator>
      <dc:date>2012-01-17T14:54:07Z</dc:date>
    </item>
    <item>
      <title>Re: AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874313#M45835</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Give the pruning a shot. Although my 40+ only allow the wireless vlans and we still had this issue. Also, we did notice some move to the secondary while most did not. They came right back up on the primary. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I suspect this is the norm and unless you pay extra close attention to the ap while upgrading you may not even notice this going on... &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 15:05:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874313#M45835</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2012-01-17T15:05:08Z</dc:date>
    </item>
    <item>
      <title>Re: AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874314#M45836</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;These 6509 chassis are dedicated to wireless vlans.&amp;nbsp; The only VLAN that is allowed through those etherchannels that's NOT wireless is the management VLAN.&amp;nbsp; I seriously doubt that it is congesting anything. All other VLANs are wireless related.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 15:19:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874314#M45836</guid>
      <dc:creator>Tony Davis</dc:creator>
      <dc:date>2012-01-17T15:19:24Z</dc:date>
    </item>
    <item>
      <title>Re: AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874315#M45837</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what if I disable the heartbeat timer during the upgrade?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 15:27:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874315#M45837</guid>
      <dc:creator>Tony Davis</dc:creator>
      <dc:date>2012-01-17T15:27:22Z</dc:date>
    </item>
    <item>
      <title>Re: AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874316#M45838</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;don't disable it but you could extend by maybe 5 seconds. Just remember to put it back when you're done upgrading. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 15:43:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874316#M45838</guid>
      <dc:creator>Stephen Rodriguez</dc:creator>
      <dc:date>2012-01-17T15:43:47Z</dc:date>
    </item>
    <item>
      <title>Re: AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874317#M45839</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Tony&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You mentioned this happens during the wlc  upgrade. What does this have to do with the predownload. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 15:45:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874317#M45839</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2012-01-17T15:45:56Z</dc:date>
    </item>
    <item>
      <title>Re: AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874318#M45840</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If the AP's keep moving to another controller while I'm upgrading the current controller, then I'll never have the opporunity to predownload the image to the AP, which is the whole point of this new feature.&amp;nbsp; This results in a longer downtime because when the AP moves to a controller that has been upgraded, it has to download a new image and then reboot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Consider the following scenario:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;C1 has 40 AP's, running 7.0.98&lt;/P&gt;&lt;P&gt;C2 has 30 AP's, running 7.0.98&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Upgrade software on C1 to 7.0.116, AP's move to C2 before having chance to predownload image to AP's&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;C1 has 0 AP's, running 7.0.116&lt;/P&gt;&lt;P&gt;C2 has 70 AP's, running 7.0.98&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Upgrade C2 to 7.0.116, AP's disassociate and join C1, now has to download image(couldn't predownload) and reload&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is that more clear?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 16:17:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874318#M45840</guid>
      <dc:creator>Tony Davis</dc:creator>
      <dc:date>2012-01-17T16:17:01Z</dc:date>
    </item>
    <item>
      <title>Re: AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874319#M45841</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you don't reboot the WLC until all are upgraded, it shouldn't be a problem.&amp;nbsp; Even if the AP move, they hit a WLC with the code they are running and won't download by default.&amp;nbsp; Then once all WLC are upgraded you can run the pre-download command, wait for that to finish, then do rolling reboots, or wait till 2am and reboot them all.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All depends on what you can do inside your organization WRT the rebooting of the individual WLC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 16:22:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874319#M45841</guid>
      <dc:creator>Stephen Rodriguez</dc:creator>
      <dc:date>2012-01-17T16:22:49Z</dc:date>
    </item>
    <item>
      <title>Re: AP's disassociate during WLC upgrade</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874320#M45842</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Tony,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Its very clear, but thats not the advisable process. You will have a mess on your hands for sure. I have 40 WLCs and the upgrade process is just that a process. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. You upgrade the WLCs&lt;/P&gt;&lt;P&gt;2. After upgrade you then push the code to the AP &lt;EDIT&gt;&lt;/EDIT&gt;&lt;/P&gt;&lt;P&gt;3. You then swap the code on the aps to primary &lt;/P&gt;&lt;P&gt;4. Then you reboot all controllers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thats why you are having problems. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I blogged about this process. This may help you better understand the process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small active_link" href="http://www.my80211.com/cisco-wlc-cli-commands/2011/2/20/wlc-predownload-the-image-to-the-access-points-from-the-cont.html"&gt;http://www.my80211.com/cisco-wlc-cli-commands/2011/2/20/wlc-predownload-the-image-to-the-access-points-from-the-cont.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EDIT&gt; I need my morning coffee&lt;/EDIT&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 16:29:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-disassociate-during-wlc-upgrade/m-p/1874320#M45842</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2012-01-17T16:29:14Z</dc:date>
    </item>
  </channel>
</rss>

