At AirHeads it was described this way: Code is loaded on one WLC, WLC is rebooted and running new code. Client match is used to encourage clients to leave APs on a selected channel. All APs on that selected channel are elected for update and moved to the WLC with the new code. Moved APs get new code, reboot, come back into service. APs running new code are eligible for taking on new clients and client match should start moving clients to the new code APs. Lather, rinse, repeat until all channels have been rotated through. Once the WLC is unloaded, it gets new code and is rebooted.
So, not really 'hitless' as advertised, but yes- far better than taking them all out at once. Assuming of course that client match successfully behaves. ;-) -Sam On Thu, Jun 8, 2017 at 3:38 PM, Joachim Tingvold <joac...@tingvold.com> wrote: > On 8 Jun 2017, at 19:11, Sweetser, Frank E wrote: > >> […] and from there I'm really looking forward to seeing how well the live >> upgrades work! >> > > Hi, > > Do you know how that works in detail? All I can find is the sales > mumbo-jumbo that over-promises (as usual); "[…] allows customers to upgrade > their wireless network in real time without any impact to user > connectivity. Upgrade process is simplified, no maintenance downtime […]". > > Looking at the installation manual of 8.1.0, it doesn't say how it's done, > but I managed to find a "dumbed down" non-official explanation that went > something along the lines of "[…] move all APs to secondary controller, > then upgrade the primary controller. After primary is upgraded, APs are > gradually upgraded/moved to the primary controller (i.e. not all at once). > Once all APs is upgraded, the secondary controller is upgraded, and then > the redundancy is restored". > > How are those APs selected? Just random order? If so, that doesn't really > mean "no downtime" or "no impact on users", as you could risk neighboring > APs to be upgraded at the same time, causing smaller or larger blindspots. > Of course it sounds better than to "take it all down", but, yeah, not > really ISSU… > > -- > Joachim > > > ********** > Participation and subscription information for this EDUCAUSE Constituent > Group discussion list can be found at http://www.educause.edu/discuss. > ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss.
