My academic environment is running 5.3-158. Things seen stable.

My ResNet environment moved to 6.x to combat the occasional ap reboot, gain 
AP832/822 support as well as the wildcard cert support and the OS 
identification feature. No config loss on the upgrades. ResNet tech staff not 
reporting troubles on 6.1-1-23 so far.  99% AP1020 on MC4200.

Josh

Sent from my Android


"Garza, Veronica" <[email protected]> wrote:

We went to 6.1 due to AP reboots and recommendations from our SE. However,  
this caused more issues for us. We had no issues with the configuration after 
the upgrade.

We had to revert to 5.3.158 due to various issue on 6.1 and lost some of our 
configurations. Currently we are stable at 5.3.158.


-------- Original message --------
From: Gonzalo Cervantes
Date:04/24/2014 5:53 PM (GMT-05:00)
To: [email protected]
Subject: Re: [WIRELESS-LAN] Meru upgrade to SD 6.1


Also, what was the motivating factor to upgrade to 6.1?

Thanks,
Gonzalo

---
Gonzalo Cervantes
Associate Director Network Services
Barnard College, Columbia University
[email protected]<mailto:[email protected]>
212-854-8795
barnard.edu/bcit<http://barnard.edu/bcit>

<<sent from mobile device>>

On Apr 24, 2014 5:07 PM, "Gonzalo Cervantes" 
<[email protected]<mailto:[email protected]>> wrote:
Thanks Josh and Veronica for the feedback.
Josh, I also looked over the release notes and seen what you pointed out. We 
have three 4200s that will need to jump to 5.1-93 before we can jump to 6.1-x-x 
(whatever release is Heartbleed patched). How has your experience been on 6.1?
A follow question for both...did you find that parts of your configuration were 
not migrated properly (e.g radio settings) into the new code?
Thanks,
Gonzalo

---

Gonzalo Cervantes

Associate Director Network Services


Barnard College, Columbia University

[email protected]<mailto:[email protected]>

212-854-8795<tel:212-854-8795>

barnard.edu/bcit<http://barnard.edu/bcit>


On Thu, Apr 24, 2014 at 1:55 PM, Garza, Veronica 
<[email protected]<mailto:[email protected]>> wrote:
We have over 900 AP320/320i in our environment with three MC4200s. We had 
5.3-132 and upgraded to 5.3-153. We experienced AP reboots and SE recommended 
upgrade to 6.1-03. We experienced many issues with AP reboots, station 
disconnects, DHCP issues, and framed-ip-address … this occurred early April. We 
then learned of Heartbleed on 6.1-03.

We downgraded to 5.3-158 which resolved the issues.

--Veronica


From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:[email protected]<mailto:[email protected]>]
 On Behalf Of Heller, Josh
Sent: Thursday, April 24, 2014 1:43 PM
To: 
[email protected]<mailto:[email protected]>

Subject: Re: [WIRELESS-LAN] Meru upgrade to SD 6.1

Gonzalo,

Meru SD 6.1-0-3 is affected by the Heartbleed bug.  Please upgrade only to 
6.1-1-23 or higher which is available by request.  6.1-1-23 also contains 
combined AP images for support for legacy AP311s which AP 6.1-0-3 does not 
have. So, I would advise against 6.1-0-3.
We were using 5.3-x builds before upgrading to 6.1-1-23, so be sure you get 
clarification from your local SE (or tech support) to find out if you need to 
upgrade to 5.3-x  before arriving at 6.1-x-x.  The 6.1-0-3 Release notes, page 
8, indicate that you should be OK going directly  from 5.1-x to 6.1-x-x, but 
please double check.

Additionally, version 6.x is not supported on legacy controllers. (MC4100 for 
example)  So be sure you are running current model controllers. (3200,4200, 
5000, 6000 etc)

If you use EzRF for reporting and other features, you will need to upgrade that 
server as well.

Hope that helps,

Josh @ KU


Josh Heller
Sr. Network Analyst
Office of Information Technology
Kutztown University
610.683.4930<tel:610.683.4930>




From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:[email protected]] On Behalf Of Lee H Badman
Sent: Thursday, April 24, 2014 12:39 PM
To: 
[email protected]<mailto:[email protected]>
Subject: Re: [WIRELESS-LAN] Meru upgrade to SD 6.1

Dialogue around any vendor’s stuff is helpful and interesting, please don’t 
feel compelled to go off-list unless you get indo NDA/sensitive topics. :)

-Lee Badman

From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:[email protected]] On Behalf Of Gonzalo Cervantes
Sent: Thursday, April 24, 2014 12:33 PM
To: 
[email protected]<mailto:[email protected]>
Subject: [WIRELESS-LAN] Meru upgrade to SD 6.1

Hi All,
Reaching out to all the Meru folks in the group.
Meru is encouraging us to upgrade to the "Go-To-Release" code SD 6.1-0-3. We 
are on SD 5.1-82 with a large deployment of AP 311 and AP320 (about 600 in 
total). The current code has been the most stable of the all the codes we've 
had but it's been two years since an upgrade.
There are no must have enhancements in the code that will help our operation 
but there are other features like device fingerprinting and a spectrum manager 
tool that would be nice to have.
My questions...
Has anyone currently upgraded to SD 6.1 with AP311 and AP320 in their 
environment and what has been your experience with it?
What was your upgrade process? Did you have to go through an upgrade path to 
get to 6.1? Any testing?

I know the group may not be Meru heavy so we can take this off-list to cut down 
on the chatter.

Thank you all in advance.

Thanks,

Gonzalo

---

Gonzalo Cervantes

Associate Director Network Services


Barnard College, Columbia University

[email protected]<mailto:[email protected]>

212-854-8795<tel:212-854-8795>
barnard.edu/bcit<http://barnard.edu/bcit>
********** 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/.

Reply via email to