27 cases won’t necessarily translate into hundreds of other sites hitting the bug. I just finished the 1st academic semester and have had zero tickets for wireless. Were users running into this bug and not reporting it, or are there specific circumstances that trigger it that aren’t happening in my environment? If this was wide-spread, I’d have expected a quick MR6 .1 release.
MR7 is not released yet, and I’ve not seen the open beta either, so it stands to reason that TAC isn’t going to recommend it unless there is good cause. As for being chummy – it’s more about being engaged with your vendors support network. TAC is just one of many avenues and having a professional relationship with your local support SE as well as the BU is just plain good business. Jeff From: "wireless-lan@listserv.educause.edu" <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> on behalf of "lhbad...@syr.edu" <lhbad...@syr.edu> Reply-To: "wireless-lan@listserv.educause.edu" <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> Date: Wednesday, December 20, 2017 at 9:15 AM To: "wireless-lan@listserv.educause.edu" <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> Subject: Re: [WIRELESS-LAN] Another Cisco WLC Code Thread I understand the words. And am speaking in the context that 8.2.166 is what’s listed as recommended. Not sure why you’d have to be chummy with the BU to get better information. My point is that 27 reported open cases equals likely hundreds of sites more hitting the issue without realizing it. Ideally, a customer wouldn’t have to hit a known bug and have customers impacted before being able to negate that bug. If MR7 fixes it before it happens, now is the time to install it, while we’re on break, as opposed to late in January when suddenly business operations get impacted. The messaging is uncomfortable to say the least. Lee Badman | Network Architect Certified Wireless Network Expert (#200) 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<mailto:lhbad...@syr.edu> w its.syr.edu SYRACUSE UNIVERSITY syr.edu From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Jeffrey D. Sessler Sent: Wednesday, December 20, 2017 11:41 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Another Cisco WLC Code Thread Well, 8.2 MR7 interim with that fix has been available since early September, but there are several newer builds including the Dec 18th 8.2.167.2 that include it and other fixes and new features. Those first early builds were likely restricted i.e. if you aren’t hitting the bug then why risk installing very early interim code? Again, hit up your local SE or BU contacts and it’s easy to get access to the interim code, but don’t install it unless you’re hitting the identified bugs. That’s the point of verification by TAC. Jeff From: "wireless-lan@listserv.educause.edu<mailto:wireless-lan@listserv.educause.edu>" <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU<mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>> on behalf of "lhbad...@syr.edu<mailto:lhbad...@syr.edu>" <lhbad...@syr.edu<mailto:lhbad...@syr.edu>> Reply-To: "wireless-lan@listserv.educause.edu<mailto:wireless-lan@listserv.educause.edu>" <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU<mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>> Date: Wednesday, December 20, 2017 at 5:09 AM To: "wireless-lan@listserv.educause.edu<mailto:wireless-lan@listserv.educause.edu>" <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU<mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>> Subject: Re: [WIRELESS-LAN] Another Cisco WLC Code Thread Thanks, Yahya. Now here’s an axe-grinding moment for me: from Cisco’s list of recommended code versions, 8.2.166.0 is the version to go with. Easy enough- yes? No. Look at the note regarding the x800 AP-related bug CSCve57121 Client when auto-connects to SSID unable to reach gateway after a few secs It’s a nasty one, with 27 reported cases. The fix is to get MR7- but you seemingly have to prove that you’re hitting the bug before you can get it. So… the culture here on the vendor side: * Recommend a code version- to upgrade large environments, there will be downtime required and coordinated after testing of this code, as normal. * Leave an extremely disruptive bug out there for people to hit * Make them prove that the bug is actually being hit before they can get the fix code * Meanwhile, potentially thousands of clients are being impacted and can’t use the WLAN * Make the fix code available after a TAC case has been opened * Back to step one- scheduling a code upgrade and re-disrupting the environment So why isn’t MR7 the recommended code to begin with? Lee Badman | Network Architect Certified Wireless Network Expert (#200) 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<mailto:lhbad...@syr.edu> w its.syr.edu SYRACUSE UNIVERSITY syr.edu From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Yahya M. Jaber Sent: Wednesday, December 20, 2017 12:06 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU<mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> Subject: Re: [WIRELESS-LAN] Another Cisco WLC Code Thread Hi, This is what Cisco Says, https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/200046-tac-recommended-aireos.html#anc6 HTH Yahya Jaber. Sr. Wireless Engineer IT Network & Communications – Engineering Building 14, Level 3, Rm 308-WS07 KAUST 23955-6900 Thuwal, KSA Email yahya.ja...@kaust.edu.sa<mailto:yahya.ja...@kaust.edu.sa> Office +966 (0) 12 8081237 Mobile +966 (0) 558697555 On Call Rotation Mobile: +966 54 470 1177 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Britton Anderson Sent: Tuesday, December 19, 2017 11:43 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU<mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> Subject: [WIRELESS-LAN] Another Cisco WLC Code Thread Happy Holidays, Like many others I'm sure, I've been studying all of the email threads from this list to see if anyone has settled on any of the current code releases on their controllers. With all of the bugs disabling several AP models, we have been holding off our code upgrade and wireless migration. I have a plan to move about half of our wireless APs off of a pair of WiSM2s to our new 8540's next week. We've had the 8540's up since the summer running on 8.4.100.0 seemingly without many issues. It's been pretty stable but there has only been about 80 APs on it for our Fall semester. That code release is now deferred and we've looked at going up to 8.5.110.0 which released just a few days ago. Release notes list the open caveats, and there are several that still impact the 3500/3600/3700 lines pretty hard. 8.6.101.0 released a day after, and its even more grim. Has anyone found anything stable? We have a pretty wide deployment of APs, but most of them are 3500/3600/3700s with a fleet of 702W/1810W in residences. We simply don't have the manpower to run around and console into APs that lose their marbles, and our time slot to move forward is narrowing by the day. And more importantly, I would like to sleep better over the holidays, like we all would I'm sure. Thanks for the input, Britton Britton Anderson<mailto:blanders...@alaska.edu> | Lead Network Communications Specialist | University of Alaska<http://www.alaska.edu/oit> | 907.450.8250 ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss. ________________________________ This message and its contents including attachments are intended solely for the original recipient. If you are not the intended recipient or have received this message in error, please notify me immediately and delete this message from your computer system. Any unauthorized use or distribution is prohibited. Please consider the environment before printing this email. ********** 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. ********** 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. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss.
