HiveOS/HiveManager 6.6r1 released!

  • 5
  • Article
  • Updated 2 years ago
  • (Edited)

Folks,

I have two related announcements. We released HiveOS and HiveManager version 6.6r1 this week. Links to the New Features Guide and the Release Notes are below. However, unless you need the new features or cannot wait for the bug-fixes introduced in this release, I am changing from my past behavior and advising that you hold off and not necessarily upgrade to this version of HiveOS immediately



We have all heard the phrase “one size fits all”. That’s a fallacy, one size fits one, and all others get at best a poor fit. That’s true for hardware and software as much as for clothing. We have polled many of our customers (and I thank those of you who were chosen and who responded), and at the risk of oversimplifying things, you essentially are in one of two camps. One set prefers to set-and-forget their wireless infrastructure, you just want it to work and don’t think you need many if any new features beyond what we’ve already delivered. The other set actively manages your wireless infrastructure on a daily or other periodic basis, and many of you submit requests for new features to help you manage un-met needs. Rather than continue to force the ever-growing and ever-diverging Aerohive customer base into the “one size fits all” mentality, Aerohive is adopting a new release strategy that may be familiar to many of you from other long-established vendors. 


We are embracing the concept of a “golden” release train and a “feature” release train. The basic idea is that going forward when/if you find and report a bug to us (or we find one during our own internal testing), we will check in the fixes to BOTH the “golden” release train AND the then-current “feature” release train. In the past we would usually only check in bug-fixes to what would now be considered the next “feature” release, forcing you to accept new features (and potentially new bugs) in order to get a fix for the problem that was bothering you. The goal now is to have one release train with a known and fixed feature-set that becomes increasingly stable over time, and another release train where we can introduce new features and capabilities, but also will occasionally (and unintentionally) introduce new bugs. 

HiveOS 6.6r1 is the first of our new “feature” releases. In the next several weeks and months we will release HiveOS versions 6.5r2, 6.5r3, and further maintenance releases in the “golden” release train. 

For those of you who have been long-term Aerohive customers, one of the most obvious changes you’ll notice is that where previously we would “fly the bee” to indicate the availability of every new feature release, now we will only do that for selected releases. These will typically be in the golden release train. The original intent for “flying the bee” was to inform all customers of a release to which we believe most customers will want to upgrade. 

We will not fly the bee for HiveOS and HiveManager 6.6r1, even though it is available for you now. We will wait until the 6.5r3 release is available and will fly the bee at that time. 

HiveManager version 6.6 will manage HiveOS devices running version 6.6, version 6.5, or earlier, including mixed versions of HiveOS. 

HiveManager-NG does not (yet) support HiveOS 6.6. That is planned for later this summer, in a subsequent maintenance release to HiveOS 6.6.

Please do not interpret all of this as indicating I or anyone at Aerohive considers HiveOS 6.6r1 to be in any way unsuitable for your adoption. I have been running alpha and beta code in my own home and work environments for weeks. I would have allowed it to be commercially released if it had not met my and Aerohive’s quality goals. 

Obviously, if our Technical Support organization suggests you use a specific version of HiveOS then their advice should be followed instead of my generic comments, because Tech Support will take into account the specifics of your environment, your particular problem(s), etc. 

Mike Kouri

Product Manager, Aerohive


http://www.aerohive.com/330000/docs/help/english/documentation/HOS-HM_6.6r1_NewFeatures_330183-01.pdf

http://www.aerohive.com/330000/docs/help/english/documentation/HOS-HM_6.6r1_ReleaseNotes330182-01.pdf


Photo of Mike Kouri

Mike Kouri, Official Rep

  • 1030 Posts
  • 271 Reply Likes
  • pleased and proud

Posted 3 years ago

  • 5
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Great news. Thanks for the in-depth explanation! :)

One aspect that isn't yet clear to me...

Is there a plan to get the EOS AP320/AP340s, AP110s and AP120s running 6.5rX, which would presumably give them compatibility with HM-NG if so?
(Edited)
Photo of Mike Kouri

Mike Kouri, Official Rep

  • 1030 Posts
  • 271 Reply Likes
Yes, our intention for the 6.5rX branch of releases is to support all Aerohive devices (except the very oldest, AP20 and AP28) to bring it up to a quality level where it can be the recommended-by-support release for all platforms, and to add necessary changes so that HiveManager-NG can manage these platforms. 
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Awesome! :)

Nick makes an repeated, impassioned plea for you all to consider back porting the RADIUS behaviour from 6.6r1 to 6.5rX so that it's consistent. ;) :P

Right, time to go and and chase LAN3 to see if there's a fix coming for HOS-2767​. I'm currently in the dark on that one. :)
(Edited)
Photo of Mike Kouri

Mike Kouri, Official Rep

  • 1030 Posts
  • 271 Reply Likes
Nick,
We hear you. We're working on it. And by the way, my records indicate HOS-2767 is still open and unresolved in 6.6r1, sorry.
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Yeah, I know that it's not resolved in 6.6r1 due primarily due to it being discovered by me far too late in the release cycle. Definitely no apology needed, nothing remotely unreasonable about that!
(Edited)
Photo of Leo Bistmans

Leo Bistmans

  • 1 Post
  • 1 Reply Like
CFD-848 "Clients connecting to an AP230 were sometimes unable to obtain a DHCP address."
Got angry end-user this morning.   Contemplating return to 6.1r6a.   Anyone with likewise symptoms out there ;-) ?
Photo of Arison Mercado

Arison Mercado

  • 113 Posts
  • 8 Reply Likes
I've recently joined the  6.6r1 firmware club and now I'm getting this DHCP issue on our internal network in each building. When this issue occurred did you experienced it on version 6.6r1 and revert back to 6.1r to fix it?
Photo of Jeroen van Ingen

Jeroen van Ingen

  • 4 Posts
  • 0 Reply Likes
Just found this thread while reading up on the forum. Great decision to have a stable and a feature branch in parallel, indeed it will do justice to both approaches of network management.

I'm in the "active management" camp myself; I do more in the LAN area (HP and Cisco) than with wireless, but it's the same there: being proactive and considering new features has the downside that you're also one of the first users to encounter new bugs. That's a tradeoff that you make for having earlier access to new features and technology.

Offering a separate stable/"golden" branch will better cater the needs of the other camp. To me this also indicates a new level of maturity for Aerohive as a networking vendor.
Photo of cabrower

cabrower

  • 13 Posts
  • 2 Reply Likes
Has the 6.6r1 OS been pulled for the AP 330s?
Photo of Carsten Buchenau

Carsten Buchenau, Champ

  • 356 Posts
  • 117 Reply Likes
Check this conversation:
https://community.aerohive.com/aerohive/topics/latest-firmware-6-6-for-ap330-not-available-anymore

HiveOS 6.5r4 is currently your best choice for all 802.11n platforms.