A mix of WiSM2s, 5508, 5520, 8540 (working on getting that down to just
5520s and 8540s) with ~1500 APs total.

-Luke

On Tue, Oct 4, 2016 at 7:25 AM, Lee H Badman <[email protected]> wrote:

> Thanks, Luke. Which WLCs and how many APs?
>
>
> -Lee
>
> ​
> ------------------------------
> *From:* The EDUCAUSE Wireless Issues Constituent Group Listserv <
> [email protected]> on behalf of Luke Jenkins <
> [email protected]>
> *Sent:* Monday, October 3, 2016 8:41 PM
>
> *To:* [email protected]
> *Subject:* Re: [WIRELESS-LAN] Cisco WLC Code 8.2 MR3?
>
> We also helped test the 8.2mr3 release in a limited setting and have
> upgraded to the 8.2.130.0 build campus wide since the release. No issues to
> report. It seems like the 2800/3800 code is finally getting to a good
> place.
>
> -Luke
>
> On Thu, Sep 29, 2016 at 2:32 PM, Lee H Badman <[email protected]> wrote:
>
>> Thanks, Jeff
>>
>>
>>
>> *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* [email protected] *w*
>> its.syr.edu
>>
>> *SYRACUSE UNIVERSITY*
>> syr.edu
>>
>>
>>
>> *From:* The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:
>> [email protected]] *On Behalf Of *Jeffrey D. Sessler
>> *Sent:* Thursday, September 29, 2016 11:15 AM
>> *To:* [email protected]
>> *Subject:* Re: [WIRELESS-LAN] Cisco WLC Code 8.2 MR3?
>>
>>
>>
>> Lee,
>>
>>
>>
>> I’ve been running the beta. Based on fixed items, MR3 is mostly focused
>> on the new AP’s along with fixing a couple of other issues. Our controllers
>> have been running 8.2.121.14 for 12 days. No issues with that build or the
>> previous builds. There was a .15 that I believe became MR3, but the
>> additional fixes were minimal.
>>
>>
>>
>> Jeff
>>
>>
>>
>> *From: *"[email protected]" <
>> [email protected]> on behalf of "[email protected]" <
>> [email protected]>
>> *Reply-To: *"[email protected]" <
>> [email protected]>
>> *Date: *Thursday, September 29, 2016 at 7:35 AM
>> *To: *"[email protected]" <[email protected]
>> E.EDU>
>> *Subject: *[WIRELESS-LAN] Cisco WLC Code 8.2 MR3?
>>
>>
>>
>> Having some issues with 8.2.111.0 and 8.2.121.0  on our 8540 WLCs. The
>> recommended path forward is 8.2. MR3, which was made available yesterday.
>> I’m wondering if anyone on the list was a beta tester for the code? Or if
>> you might be hearing good, bad, or indifferent from your relationships with
>> VARS/partners/Cisco Champions, etc on the new code?
>>
>>
>>
>> Regards,
>>
>>
>>
>> Lee Badman
>>
>>
>>
>> *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* [email protected] *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/.
>>
>>
>
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=
> Luke Jenkins
> Network Engineer
> Weber State University
> ********** 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/.
>
>


-- 
=-=-=-=-=-=-=-=-=-=-=-=
Luke Jenkins
Network Engineer
Weber State University

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

Reply via email to