We run 8.3 on some new 8540s. We moved to 8.3 to resolve a DFS issue in 8.2 (CSCuy45955 - AP stops xmitting beacons after some # of DFS events). This is fairly silent btw, look for a dearth of 5G clients and/or cleanair being down.
I'm not on the daily battlefield of wireless support so much anymore, but hearing a new 8.3 bug is: '..seen a problem in the past few weeks where sometimes when an AP power cycles the primary image becomes corrupted (premature end of mzip file on boot), AP switches to the backup image, connects to controller, sees that it has the "correct" version in its backup, and boots the bad file again. Infinite loop. The only fix is by renaming the backup image via it's console' As complexity/features continue to increase, no vendor's images will ever be bug free. I was wondering if there might be an advantage in having modular AireOS code. That'd not be without issues either, but bug fixes might possibly come more quickly and allow more time before migrating to the next major release. The biggest downside of that, as seen on the ASR side, is that many modular patches still require a reboot - but on an AP(s) that would not be as big of an issue. On a side note, over the last year/two there seems a behavior on part of the TAC pushing back for us to 'lab' problems. In our view, once we've pretty clearly identified an issue exists, it's a TAC/developer issue to further ferret out and resolve. That adds time and pain to the service impact of the bug. On Wed, Sep 7, 2016 at 7:52 AM, Osborne, Bruce W (Network Services) < bosbo...@liberty.edu> wrote: > …Or better vendor support. > > > > We always check with our vendor support people before jumping on an > upgrade. Sometimes they recommend waiting due to new buigs. > > > > We find vendor support generally better informed than peer user support. > > > > *Bruce Osborne* > > *Wireless Engineer* > > *IT Network Operations - Wireless* > > *(434) 592-4229 <%28434%29%20592-4229>* > > > > *LIBERTY UNIVERSITY* > > *Training Champions for Christ since 1971* > > > > *From:* Lee H Badman [mailto:lhbad...@syr.edu] > *Sent:* Tuesday, September 6, 2016 3:52 PM > *Subject:* Re: Cisco 8540s, and 8.3.102 Code > > > > Wow. Thanks, Brandon. You need a program to keep up with all of the bugs… > > > > > > *From:* The EDUCAUSE Wireless Issues Constituent Group Listserv [ > mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU > <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>] *On Behalf Of *Case, Brandon J > *Sent:* Tuesday, September 06, 2016 3:42 PM > *To:* WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU > *Subject:* Re: [WIRELESS-LAN] Cisco 8540s, and 8.3.102 Code > > > > We deployed our first 8540s running 8.3.102 and ended up running into > CSCva98592. Basically caused both HA peers to crash and reboot > simultaneously. Also had problems re-pairing them after bringing the > secondary out of maintenance state. We were advised to back down to > 8.2.121.9 which is an engineering special that we had to request. Been > stable on that for about 2 weeks now. 8540 pair has about 250 APs and peaks > around 1300 clients right now. We are not running AVC though. > > > > -Brandon > > > > *From:* The EDUCAUSE Wireless Issues Constituent Group Listserv [ > mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU > <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>] *On Behalf Of *Lee H Badman > *Sent:* Tuesday, September 6, 2016 3:31 PM > *To:* WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU > *Subject:* [WIRELESS-LAN] Cisco 8540s, and 8.3.102 Code > > > > Sigh… we continue to have WLC performance issues seemingly related to AVC, > even after upgrading to 8.2.121. TAC has mentioned 8.3.102 as having AVC > fixes, but I don’t see anything after looking at release notes. Anyone > using 8.3.102. or heard any rumblings that are of concern? > > > > > > > > *Lee Badman* | Network Architect (CWDP, CWNA, CWSP, Mobility+) > > Information Technology Services > 206 Machinery Hall > 120 Smith Drive > Syracuse, New York 13244 > > *t* 315.443.3003 * f* 315.443.4325 *e* lhbad...@syr.edu *w* its.syr.edu > > > *SYRACUSE UNIVERSITY *syr.edu > > > > > > > > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at http://www.educause.edu/ > groups/. > > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at http://www.educause.edu/ > groups/. > > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at http://www.educause.edu/ > groups/. > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at http://www.educause.edu/ > groups/. > > -- Garry Peirce Network Architect Networkmaine, University of Maine System US:IT 207-561-3539 ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
