RE: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Ron Mirabile]

Hi Britton,

I have been looking into the same issue as we are going to 8540’s and need to 
support 1815W’s.  We are running 8.2.166 on our production and after talking 
with TAC, it appears 8.5 train is the recommended for those needing the new 
features and new AP support.  8.5.110.0 fixes a few major bugs however I was 
told today that there is a new maintenance release for 8.5 coming out by end of 
January that may be worth the wait.

Specific codes recommended by TAC inside each code train can be seen at: 
https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/200046-tac-recommended-aireos.html#anc9.
 This bulletin is constantly updating depending on the monitoring and release 
of new codes.

Hope that helps.  I would be interested in knowing how your 8.5.110 experience 
works out.

Cheers!
-Ron


Ron Mirabile
r...@uoregon.edu
Network and Telecom Services
Network Engineer – Wireless
[cid:image005.png@01D09A22.022FFF90]



From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Britton Anderson
Sent: Tuesday, December 19, 2017 12:43 PM
To: 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 |

 Lead Network Communications Specialist |

 University of Alaska |

 907.450.8250


** 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.

Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Joachim Tingvold]

On 20 Dec 2017, at 5:06, Jeffrey D. Sessler wrote:
[…] I have three releases to choose from, or four if I wanted to run 
8.6 beta! ;-)


FYI; 8.6 was released on CCO 6 days ago (14th).

--
Joachim

**
Participation and subscription information for this EDUCAUSE Constituent Group 
discussion list can be found at http://www.educause.edu/discuss.

Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Britton Anderson]

Thanks everyone for the discussion -- I think this thread somewhat proves
the state that AirOS is in right now, for better or worse. Our deployment
on 8.4.100.0 has been stable on our 8540's and the deferral notice for DFS
issues can be remedied by disabling DFS channels if we have to. We will
figure out a migration plan internally and probably take a few more baby
steps to take care of any road blocks as we hit them.

If anybody else is planning on taking a plunge with one of these new code
releases, chime in as you go if you see any issues.

Otherwise I hope everyone has a good holiday and Happy New Year!

Take care,
Britton



Britton Anderson  |  Lead Network Communications
Specialist |  University of Alaska <http://www.alaska.edu/oit> |
 907.450.8250

On Wed, Dec 20, 2017 at 8:45 AM, Lee H Badman  wrote:

> All right then, the last word is yours.
>
>
>
> Happy Holidays.
>
>
>
> *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 <(315)%20443-3003>  * f* 315.443.4325 <(315)%20443-4325>
> *e* 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 12:34 PM
>
> *To:* WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
> *Subject:* Re: [WIRELESS-LAN] Another Cisco WLC Code Thread
>
>
>
> 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"  EDUCAUSE.EDU> on behalf of "lhbad...@syr.edu" 
> *Reply-To: *"wireless-lan@listserv.educause.edu"  EDUCAUSE.EDU>
> *Date: *Wednesday, December 20, 2017 at 9:15 AM
> *To: *"wireless-lan@listserv.educause.edu"  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 <(315)%20443-3003>  * f* 315.443.4325 <(315)%20443-4325>
> *e* 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

RE: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Lee H Badman]

All right then, the last word is yours.

Happy Holidays.

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 12:34 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

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<mailto:wireless-lan@listserv.educause.edu>" 
mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>> 
on behalf of "lhbad...@syr.edu<mailto:lhbad...@syr.edu>" 
mailto:lhbad...@syr.edu>>
Reply-To: 
"wireless-lan@listserv.educause.edu<mailto:wireless-lan@listserv.educause.edu>" 
mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>>
Date: Wednesday, December 20, 2017 at 9:15 AM
To: 
"wireless-lan@listserv.educause.edu<mailto:wireless-lan@listserv.educause.edu>" 
mailto: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<mailto: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>" 
mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>> 
on behalf of "lhbad...@syr.edu<mailto:lhbad...@syr.edu>" 
mailto:lhbad...@syr.edu>>
Reply-To: 
"wireless-lan@listserv.educause.edu<mailto: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>" 
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

Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Jeffrey D. Sessler]

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"  
on behalf of "lhbad...@syr.edu" 
Reply-To: "wireless-lan@listserv.educause.edu" 

Date: Wednesday, December 20, 2017 at 9:15 AM
To: "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>" 
mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>> 
on behalf of "lhbad...@syr.edu<mailto:lhbad...@syr.edu>" 
mailto:lhbad...@syr.edu>>
Reply-To: 
"wireless-lan@listserv.educause.edu<mailto: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>" 
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 Lis

RE: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Lee H Badman]

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>" 
mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>> 
on behalf of "lhbad...@syr.edu<mailto:lhbad...@syr.edu>" 
mailto:lhbad...@syr.edu>>
Reply-To: 
"wireless-lan@listserv.educause.edu<mailto: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>" 
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 ma

Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Jeffrey D. Sessler]

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"  
on behalf of "lhbad...@syr.edu" 
Reply-To: "wireless-lan@listserv.educause.edu" 

Date: Wednesday, December 20, 2017 at 5:09 AM
To: "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
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 

Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Joseph Bernard]

I'm told that one of the pair will spontaneously lose the ability to tag 
traffic.

Thanks,
Joseph B.

Sent from my iPhone

On Dec 19, 2017, at 8:44 PM, Alan D Wang 
mailto:aw...@binghamton.edu>> wrote:

What problems have you been seeing with HA and was this in 8.3 and/or 8.5?

On Tue, Dec 19, 2017 at 7:34 PM, Joseph Bernard 
mailto:j...@clemson.edu>> wrote:
To expand, we instantly had issues with 8.5.105.0.  We haven't tried 8.5.110.0 
yet, but I'm sure our wireless team is looking for anything better.  They have 
little hope of ever getting HA working.

Thanks,
Joseph B.

Sent from my iPhone

On Dec 19, 2017, at 3:48 PM, Joseph Bernard 
mailto:j...@clemson.edu>> wrote:

Don’t move off 8.4.100.0 if you can help it.

Thanks,
Joseph B.


From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>> 
on behalf of Britton Anderson 
mailto:blanders...@alaska.edu>>
Reply-To: The EDUCAUSE Wireless Issues Constituent Group Listserv 
mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>>
Date: Tuesday, December 19, 2017 at 3: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 |

 Lead Network Communications Specialist |

 University of 
Alaska
 |

 907.450.8250


** 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.



--
Alan Wang
Network Analyst
Binghamton University
aw...@binghamton.edu

** 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.

RE: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Lee H Badman]

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
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.

RE: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Yahya M. Jaber]

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
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
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 |

 Lead Network Communications Specialist |

 University of Alaska |

 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.

Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Jeffrey D. Sessler]

Mike,

The 1815w, as far as I’m aware, is also supported on 8.4 – but your point is 
well taken. The M and T models are 8.5-only, forcing one’s hand.

I actually liked the support matrix with the x800 series, where they were 
supported from 8.2 on beyond. This is where having a relationship with the BU 
can help here i.e. getting NDA knowledge and testing of new products, and then 
pushing back on decisions where support is only in the bleeding-edge controller 
code. I’ve suggested that the BU support newer WAPs, even if in a diminished 
feature capacity, on older code e.g. support 3800 series on 8.1, but they work 
like a fixed dual-radio 3700 AP – allowing the customer to get current-gen WAPs 
but on ultra-stable controller code.

All of that said, I believe that 8.5 is the new 8.2. I recall being told it’s 
the primary platform for new hardware and gets all the bug fix attention, with 
back/forward ports to the other versions. It will likely be the new stable and 
will have a longer life than other builds, especially given it’s the last to 
support the 5508 controllers.

But this also goes back to the “not every customer is the same” statement. I’m 
deploying only x800 series including in my residential-halls, so from my 
perspective, I have three releases to choose from, or four if I wanted to run 
8.6 beta! ;-)

Jeff


From: "wireless-lan@listserv.educause.edu"  
on behalf of "m...@mpking.com" 
Reply-To: "wireless-lan@listserv.educause.edu" 

Date: Tuesday, December 19, 2017 at 7:13 PM
To: "wireless-lan@listserv.educause.edu" 
Subject: Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

Jeff,   I'm semi-seriously picking a fight over this statement.

I get what you mean about cutting edge. They are choosing the bleeding edge.   
But how can you reconcile that with if you want to the new access point we're 
selling, you have to run X?   IE, Cisco still recommends on it's website 
8.3.133.0 as the release you should run, but the 1815w (Which went First 
Customer Ship on December 5th, 2016) REQUIRES 8.5.x.  Is it bleeding edge, when 
the product has been out for over 1 year?

We all know Cisco (and other vendors) give these products the shortest shelf 
life they can reasonable get away with.  And Cisco usually prices new models at 
the same price as the old model (usually), so why would you buy the 3700 
series, when the 3800 is out, and we all know the EOS for the 3700 will 
probably hit fairly soon.  So buying old AP's is not helping you in the long 
run.  (I used the 3800 cause I know that model, I have no idea what the 1815w 
is targeted to replace)

Mike

On Tue, Dec 19, 2017 at 9:27 PM, Jeffrey D. Sessler 
mailto:j...@scrippscollege.edu>> wrote:
Discussions like this just reinforce the notion that no one-customer is the 
same as another. Folks like myself have been rock solid where others seem to 
excite every little bug. There are also customers who want to push the cutting 
edge with code version and feature-set, but are not well-resourced to support 
it and/or have the expectation that it should be as stable as general 
deployment code.

The important part is to make sure you have a great relationship with your 
local wireless SE’s as well as the Wireless BU. I can’t say enough good things 
about the folks in the BU, especially the engineering teams, who I’ve 
interfaced with over the years.

Jeff
** 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.

Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Mike King]

Jeff,   I'm semi-seriously picking a fight over this statement.

I get what you mean about cutting edge. They are choosing the bleeding
edge.   But how can you reconcile that with if you want to the new access
point we're selling, you have to run X?   IE, Cisco still recommends on
it's website 8.3.133.0 as the release you should run, but the 1815w (Which
went First Customer Ship on December 5th, 2016) REQUIRES 8.5.x.  Is it
bleeding edge, when the product has been out for over 1 year?

We all know Cisco (and other vendors) give these products the shortest
shelf life they can reasonable get away with.  And Cisco usually prices new
models at the same price as the old model (usually), so why would you buy
the 3700 series, when the 3800 is out, and we all know the EOS for the 3700
will probably hit fairly soon.  So buying old AP's is not helping you in
the long run.  (I used the 3800 cause I know that model, I have no idea
what the 1815w is targeted to replace)

Mike

On Tue, Dec 19, 2017 at 9:27 PM, Jeffrey D. Sessler  wrote:

> Discussions like this just reinforce the notion that no one-customer is
> the same as another. Folks like myself have been rock solid where others
> seem to excite every little bug. There are also customers who want to push
> the cutting edge with code version and feature-set, but are not
> well-resourced to support it and/or have the expectation that it should be
> as stable as general deployment code.
>
>
>
> The important part is to make sure you have a great relationship with your
> local wireless SE’s as well as the Wireless BU. I can’t say enough good
> things about the folks in the BU, especially the engineering teams, who
> I’ve interfaced with over the years.
>
>
>
> Jeff
>

**
Participation and subscription information for this EDUCAUSE Constituent Group 
discussion list can be found at http://www.educause.edu/discuss.

Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Jeffrey D. Sessler]

Discussions like this just reinforce the notion that no one-customer is the 
same as another. Folks like myself have been rock solid where others seem to 
excite every little bug. There are also customers who want to push the cutting 
edge with code version and feature-set, but are not well-resourced to support 
it and/or have the expectation that it should be as stable as general 
deployment code.

The important part is to make sure you have a great relationship with your 
local wireless SE’s as well as the Wireless BU. I can’t say enough good things 
about the folks in the BU, especially the engineering teams, who I’ve 
interfaced with over the years.

Jeff

From: "wireless-lan@listserv.educause.edu"  
on behalf of "lhbad...@syr.edu" 
Reply-To: "wireless-lan@listserv.educause.edu" 

Date: Tuesday, December 19, 2017 at 4:50 PM
To: "wireless-lan@listserv.educause.edu" 
Subject: Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

I really hope someone from Cisco's Wireless BU monitors these conversations. It 
just never seems to improve for very long. Whereas you have no faith in HA, 
we've written off AVC.

But hey, Fastlane!

-Original Message-
From: Joseph Bernard [j...@clemson.edu]
Received: Tuesday, 19 Dec 2017, 19:35
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU [WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU]
Subject: Re: [WIRELESS-LAN] Another Cisco WLC Code Thread
To expand, we instantly had issues with 8.5.105.0.  We haven't tried 8.5.110.0 
yet, but I'm sure our wireless team is looking for anything better.  They have 
little hope of ever getting HA working.

Thanks,
Joseph B.

Sent from my iPhone

On Dec 19, 2017, at 3:48 PM, Joseph Bernard 
mailto:j...@clemson.edu>> wrote:
Don’t move off 8.4.100.0 if you can help it.

Thanks,
Joseph B.


From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>> 
on behalf of Britton Anderson 
mailto:blanders...@alaska.edu>>
Reply-To: The EDUCAUSE Wireless Issues Constituent Group Listserv 
mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>>
Date: Tuesday, December 19, 2017 at 3:43 PM
To: 
"WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU<mailto: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<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.alaska.edu_oit&d=DwMFaQ&c=Ngd-ta5yRYsqeUsEDgxhcqsYYY1Xs5ogLxWPA_2Wlc4&r=4Pt1z80PQIvvfw2j1-oSIA&m=6um6HYVcrWqTXe-bRNajqykdk7nntQSv0E2YAP5F6gM&s=ypsFwmiKTApHMaF7izMuBHHNMFuDnqRFKYEb-4Jv0Xc&e=>
 |

 907.450.8250


** Participation and subscription information for this EDUCAUSE 
Constituent Group discussion list can be found at 
http://www.educause.edu/discuss<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.educause.edu_discuss&d=DwMFaQ&c=Ngd-ta5yRYsqeUsEDgxhcqsYYY1Xs5ogLxWPA_2Wlc4&r=4Pt1z80PQIvvfw2j1-oSIA&m=6um6HYVcrWqTXe-bRNajqykdk7nntQSv0E2YAP5F6gM&s=fRWbdLe7Az6QE8CoJiwW7fu6r6pUjO4urKFQFF4TvjE&e=>.
** Participation and subscription information for this EDUCAUSE 
Constituent Group discussion list can be found at 
http://www.educause.edu/discuss<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.educause.edu_discuss&d=DwMGaQ&c=Ngd-ta5yRYsqeUsEDgxhcqsYYY1Xs5ogLxWPA_2Wlc4&r=4Pt1z80PQIvvfw2j1-oSIA&m=u0H0PUNLXiy1a3cR-fDPfH27LqBuQ9bdvaomzbhs

Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Alan D Wang]

What problems have you been seeing with HA and was this in 8.3 and/or 8.5?

On Tue, Dec 19, 2017 at 7:34 PM, Joseph Bernard  wrote:

> To expand, we instantly had issues with 8.5.105.0.  We haven't tried
> 8.5.110.0 yet, but I'm sure our wireless team is looking for anything
> better.  They have little hope of ever getting HA working.
>
> Thanks,
> Joseph B.
>
> Sent from my iPhone
>
> On Dec 19, 2017, at 3:48 PM, Joseph Bernard  wrote:
>
> Don’t move off 8.4.100.0 if you can help it.
>
>
>
> Thanks,
>
> Joseph B.
>
>
>
>
>
> *From: *The EDUCAUSE Wireless Issues Constituent Group Listserv <
> WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> on behalf of Britton Anderson <
> blanders...@alaska.edu>
> *Reply-To: *The EDUCAUSE Wireless Issues Constituent Group Listserv <
> WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>
> *Date: *Tuesday, December 19, 2017 at 3:43 PM
> *To: *"WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU"  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  |
>
>  Lead Network Communications Specialist |
>
>  University of Alaska
> 
>  |
>
>  907.450.8250 <(907)%20450-8250>
>
>
>
> ** 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.
>
>


-- 
Alan Wang
Network Analyst
Binghamton University
aw...@binghamton.edu

**
Participation and subscription information for this EDUCAUSE Constituent Group 
discussion list can be found at http://www.educause.edu/discuss.

RE: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Lee H Badman]

I really hope someone from Cisco's Wireless BU monitors these conversations. It 
just never seems to improve for very long. Whereas you have no faith in HA, 
we've written off AVC.

But hey, Fastlane!

-Original Message-
From: Joseph Bernard [j...@clemson.edu]
Received: Tuesday, 19 Dec 2017, 19:35
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU [WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU]
Subject: Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

To expand, we instantly had issues with 8.5.105.0.  We haven't tried 8.5.110.0 
yet, but I'm sure our wireless team is looking for anything better.  They have 
little hope of ever getting HA working.

Thanks,
Joseph B.

Sent from my iPhone

On Dec 19, 2017, at 3:48 PM, Joseph Bernard 
mailto:j...@clemson.edu>> wrote:

Don’t move off 8.4.100.0 if you can help it.

Thanks,
Joseph B.


From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>> 
on behalf of Britton Anderson 
mailto:blanders...@alaska.edu>>
Reply-To: The EDUCAUSE Wireless Issues Constituent Group Listserv 
mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>>
Date: Tuesday, December 19, 2017 at 3:43 PM
To: 
"WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU<mailto: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<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.alaska.edu_oit&d=DwMFaQ&c=Ngd-ta5yRYsqeUsEDgxhcqsYYY1Xs5ogLxWPA_2Wlc4&r=4Pt1z80PQIvvfw2j1-oSIA&m=6um6HYVcrWqTXe-bRNajqykdk7nntQSv0E2YAP5F6gM&s=ypsFwmiKTApHMaF7izMuBHHNMFuDnqRFKYEb-4Jv0Xc&e=>
 |

 907.450.8250


** Participation and subscription information for this EDUCAUSE 
Constituent Group discussion list can be found at 
http://www.educause.edu/discuss<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.educause.edu_discuss&d=DwMFaQ&c=Ngd-ta5yRYsqeUsEDgxhcqsYYY1Xs5ogLxWPA_2Wlc4&r=4Pt1z80PQIvvfw2j1-oSIA&m=6um6HYVcrWqTXe-bRNajqykdk7nntQSv0E2YAP5F6gM&s=fRWbdLe7Az6QE8CoJiwW7fu6r6pUjO4urKFQFF4TvjE&e=>.
** Participation and subscription information for this EDUCAUSE 
Constituent Group discussion list can be found at 
http://www.educause.edu/discuss<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.educause.edu_discuss&d=DwMGaQ&c=Ngd-ta5yRYsqeUsEDgxhcqsYYY1Xs5ogLxWPA_2Wlc4&r=4Pt1z80PQIvvfw2j1-oSIA&m=u0H0PUNLXiy1a3cR-fDPfH27LqBuQ9bdvaomzbhsJVQ&s=rch_RPRvVcJNvJLqVTwHSmz8Q1zg0nQhfEn8XCg60Dc&e=>.

** 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.

Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Joseph Bernard]

To expand, we instantly had issues with 8.5.105.0.  We haven't tried 8.5.110.0 
yet, but I'm sure our wireless team is looking for anything better.  They have 
little hope of ever getting HA working.

Thanks,
Joseph B.

Sent from my iPhone

On Dec 19, 2017, at 3:48 PM, Joseph Bernard 
mailto:j...@clemson.edu>> wrote:

Don’t move off 8.4.100.0 if you can help it.

Thanks,
Joseph B.


From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>> 
on behalf of Britton Anderson 
mailto:blanders...@alaska.edu>>
Reply-To: The EDUCAUSE Wireless Issues Constituent Group Listserv 
mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>>
Date: Tuesday, December 19, 2017 at 3: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 |

 Lead Network Communications Specialist |

 University of 
Alaska
 |

 907.450.8250


** 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.

Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Curtis K. Larsen]

We're also on 8.3.133 with 8540's and 3500,3600,3700,3800, and some 1810's.  
Things are pretty good and stable and have been for a while.  I guess it must 
be time to start testing 8.5 in the lab and a few remote sites.

Thanks,

Curtis


From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
 on behalf of Jess Walczak 

Sent: Tuesday, December 19, 2017 4:34 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

We've been very fortunate with no issues observed while running 8.3.133.0 on 
pairs of 8540's, 8510's, and 5508's, that run 1142, 2702, 2802, 1562, and 702w. 
 Now that we are testing the 1815w out, we've had to run 8.5.105.0 on a lone 
5508 and I upgraded it to 8.5.110.0 just last night without issue.

Thanks!--JW

On Dec 19, 2017 3:42 PM, "Entwistle, Bruce" 
mailto:bruce_entwis...@redlands.edu>> wrote:
Is sounds like we have a similar assortment of APs and we have been running 
8.2.160.0 for the current semester and it seems stable.

Bruce Entwistle
Network Manager
University of Redlands


From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU<mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>]
 On Behalf Of Britton Anderson
Sent: Tuesday, December 19, 2017 12: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.
** 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.

Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Jess Walczak]

We've been very fortunate with no issues observed while running 8.3.133.0
on pairs of 8540's, 8510's, and 5508's, that run 1142, 2702, 2802, 1562,
and 702w.  Now that we are testing the 1815w out, we've had to run
8.5.105.0 on a lone 5508 and I upgraded it to 8.5.110.0 just last night
without issue.

Thanks!--JW

On Dec 19, 2017 3:42 PM, "Entwistle, Bruce" 
wrote:

> Is sounds like we have a similar assortment of APs and we have been
> running 8.2.160.0 for the current semester and it seems stable.
>
>
>
> Bruce Entwistle
>
> Network Manager
>
> University of Redlands
>
>
>
>
>
> *From:* The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:
> WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] *On Behalf Of *Britton Anderson
> *Sent:* Tuesday, December 19, 2017 12:43 PM
> *To:* 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  |
>
>  Lead Network Communications Specialist |
>
>  University of Alaska  |
>
>  907.450.8250 <(907)%20450-8250>
>
>
>
> ** 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.

RE: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Entwistle, Bruce]

Is sounds like we have a similar assortment of APs and we have been running 
8.2.160.0 for the current semester and it seems stable.

Bruce Entwistle
Network Manager
University of Redlands


From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Britton Anderson
Sent: Tuesday, December 19, 2017 12:43 PM
To: 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 |

 Lead Network Communications Specialist |

 University of Alaska |

 907.450.8250


** 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.

Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Joachim Tingvold]

On 19 Dec 2017, at 21:46, Alan D Wang wrote:
We have been running 8.3.133.0 on several pairs of 5520s and 8540s 
without

an issue.


We're running 8.3.133.0 on our 5520s and 8540s as well. We're running 
almost 3700s exclusively (about ~7k of them), with a few old models 
soon-to-be-replaced (mix of 1142s, 2600s, 3500s and 3600s). It's been 
running rock solid for us.


We've hit bug CSCve70752, which is confirmed to be present in all 
flavors of 8.3MR3. Causes outdated information in Prime, due to 
incomplete snmpwalks on the WLCs. Confirmed to be fixed in 8.3MR4 
(scheduled to be released mid-January). I've asked if the bug is present 
in 8.5/8.6, and if it is, ETA on the fix for those.


We're also having some troubles with AP802s (within 891 ISRs), that has 
been extremely unstable after moving them off our WiSM2s (running 
8.0.140.0), and onto our 5520s/8540s. Moving them back does not help, so 
the culprit seems to be something that is upgraded, but never 
downgraded. We're still working with TAC on this one (6 months, still 
going strong), where the latest status is that we've shipped some of the 
faulty units to a lab in Netherlands for further analysis.


Probably going for 8.6 very soon, as we're starting to buy 3800s, and we 
need the dot1x supplicant support (that was added in 8.6). Not really 
looking forward to it, for two reasons (so far);


 1) AP802s are not supported after 8.5… (inside 891 ISRs; they are 
still for sale, and no EoL/EoS announcement is done… good job, Cisco 
(-: ).


 2) Upgrading 1700/2700/3700s to 8.5 (or any release after 8.5) 
requires downloading the software twice from the WLC (due to the 
filename being renamed). Pre-download will only work for the first of 
the two downloads. Since only 1k APs can pre-download at the same time 
(on 5520/8520s at least), you'll get a queue for any AP above 1k (we 
have 8540s with 3.5k+ APs), causing our downtime window to go from the 
usual ~400s for software upgrades, to 30-60 minutes or more. YAY!


--
Joachim

**
Participation and subscription information for this EDUCAUSE Constituent Group 
discussion list can be found at http://www.educause.edu/discuss.

Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Joseph Bernard]

Don’t move off 8.4.100.0 if you can help it.

Thanks,
Joseph B.


From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
 on behalf of Britton Anderson 

Reply-To: The EDUCAUSE Wireless Issues Constituent Group Listserv 

Date: Tuesday, December 19, 2017 at 3:43 PM
To: "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 |

 Lead Network Communications Specialist |

 University of 
Alaska
 |

 907.450.8250


** 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.

Re: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Alan D Wang]

Britton,
We have been running 8.3.133.0 on several pairs of 5520s and 8540s without
an issue. Our AP mix is 2602/3602, 2702/3702, 2802, and 1810w.
We haven't ran into any APs yet that have hit the flash bug.


On Dec 19, 2017 3:43 PM, "Britton Anderson"  wrote:

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  |  Lead Network Communications
Specialist |  University of Alaska  |
907.450.8250 <(907)%20450-8250>
** 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.

RE: [WIRELESS-LAN] Another Cisco WLC Code Thread

[Lee H Badman]

I believe 8.2.166.0 is the *most* overall stable right now, but also curious if 
I have that wrong given how fluid this topic is.

Lee Badman

-Original Message-
From: Britton Anderson [blanders...@alaska.edu]
Received: Tuesday, 19 Dec 2017, 15:43
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU [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 |Lead Network 
Communications Specialist |University of 
Alaska |   907.450.8250

** 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.