Used AP's possibly available

  • 1
  • Question
  • Updated 2 years ago

It has come time to remove Aerohive equipment from our campus. It is unfortunate, but required for the direction we are headed. There were many things that were amazing about this equipment, but there were some challenges that we just could not overcome. That said, I know our organization would be much happier knowing that the equipment went to someone who could use it, than going to electronics recovery or worse yet, the landfill.

We are a small private hospital who would love to see this equipment go to another small healthcare organization or the educational system. Preferably somewhere in our region, which is the Northwest.

If you would have use for any AP330's, AP350's, or AP170's, please throw a reply up here and I can submit your request/need to our Accounting department for approval. If you haven't looked into buying used gear, there is a transfer fee, and then all of the license and support fees that go with it. I am sure your account manager/VAR rep can help you through this.

Thanks!


Photo of Mike Smith

Mike Smith

  • 13 Posts
  • 1 Reply Like
  • hopeful

Posted 2 years ago

  • 1
Photo of Tim De Meyer

Tim De Meyer

  • 10 Posts
  • 1 Reply Like
Sadly I live and work in the wrong part of our globe :)  Otherwise I would be extremely interested...
Photo of mr bee

mr bee

  • 77 Posts
  • 0 Reply Likes
I am very interested in the why's of removing the AeroHive's, could you tell me more ?
Photo of Bill W.

Bill W.

  • 222 Posts
  • 35 Reply Likes
I know this doesn't help you, but it may help others.  To address the first issue, you can use the supplemental cli to make the changes to all your APs very easily.  This is for HM 6.6 versions.
  1. Create your CLI Supplement by navigating to Configuration->Advanced Configuration->Common Objects->CLI Supplement
  2. The command to enter is: interface wifi 1 radio channel exclude 165
  3. Modify your network policy to use the CLI Supplement by going to Configuration->Network Policies->network policy name->Additional Settings->Edit->Service Settings->Supplemental CLI and then selecting the CLI Supplement that you created
  4. Save the changes to your policy
  5. Push a full configuration change to your APs.
You could also do the same thing to set a reboot schedule for the APs, such as every day or once a week.  Instead of just having the single line in the supplemental cli, you would just add a second line with the reboot schedule command.  That could have potentially resolved the second issue you were seeing.

Sorry to hear that you will be leaving Aerohive, but I can understand the ease of having a single vendor for support.
Photo of Mike Smith

Mike Smith

  • 13 Posts
  • 1 Reply Like

Thanks for the reply Bill, especially on behalf of other existing customers. We did end up implementing the CLI supplement workaround and it did address the issue, but only after the decision was already made to change. It was a sore subject for many years before that.

However, I find the reboot suggestion to be completely outside of the realm of what is reasonable for a product that is identified as an Enterprise solution. Can you imagine Cisco, Juniper, Adtran, or some other major hardware vendor presenting this as a "solution"? This is a temporary workaround at best. Nobody on the Aerohive support team was interested in determining WHY it happened, let alone really understanding what the issue actually was, which was the part that was completely unacceptable to us. Rebooting an AP because it does odd things is not a resolution.

Many things I do like about Aerohive, it is just a little young.

Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Hi Mike,

We would only usually recommend a periodic reboot as a shorter term workaround for issues of this nature while the root cause is identified, not as a longer term solution.

Was the support case escalated to the Tier 3 support team? Do you know if a CFD was filed?

Thanks,

Nick
(Edited)
Photo of Bill W.

Bill W.

  • 222 Posts
  • 35 Reply Likes
Mike, actually I can imagine a very large, major hardware vendor presenting a reboot as a solution.  Years ago we had an Extreme Networks Black Diamond chassis that required a reboot every few months like clockwork.  And I remember there was another bug in some of the other Extreme switches that required a reboot at just under a year or so.  Otherwise it would reboot on its own.  And speaking of Cisco, there is bug in the 3602 APs that require they be rebooted to rejoin the WLC because they will intermittently disjoin from the WLC.

So even the "big boys" have problems that will require a reboot every so often.

Having to reboot network equipment all the time is not ideal, but I do like the idea that everything is then "fresh".  And as I'm also responsible for a plethora of Windows servers, I'm used to monthly reboots of network equipment.
Photo of mr bee

mr bee

  • 77 Posts
  • 0 Reply Likes
Mike, thanks a lot for sharing your experiences ! Some years ago we struggled with similar issues on 7920 and 7921 Cisco phones. Finally we removed the phones :-)
Photo of Crowdie

Crowdie, Champ

  • 972 Posts
  • 272 Reply Likes
Mike,

Interesting read.  Having deployed Aerohive in a number of private hospitals here are my thoughts:

The AP330 is an extremely robust access point.  It is not the best performing but you can just configure and leave it.

The Cisco 7925G is a very average phone.  It looks like the Cisco engineers listened too much to the sale team when they were looking for a replacement for the 7921.  I found the Ascom handsets outperformed the 7925G.

The Aerohive 6.4r1 to 6.5r3 firmware images had huge problems.  We experienced random disconnects, extremely poor roaming, radios stopping transmitting, low throughput, etc.  During this period I was having to defend Aerohive on an almost daily basis and I suspect that by the end the local Aerohive System Engineer was going to remove me from his Christmas card mailing list :-) The 6.5r4 firmware resolved these issues but if it had arrived a week or two later there may not have been Aerohive wireless networks left at the customers to upgrade.  Since the release of the 6.5r4 firmware we are not experienced any further issues.

Have you thought of donating or selling very cheaply the Aerohive equipment to a charity that works with disadvantaged or disabled children?  We have worked with a number of church and charity groups that operate in this area and it hugely rewarding.
Photo of mr bee

mr bee

  • 77 Posts
  • 0 Reply Likes
Crowdie, I know the feeling of defending AeroHive :-) We had also a lot of issues with 6.4r1 till 6.5r3. For now 6.5r4 seems stable, let's hope it stays like this because we have a big deployment and rolling out takes a lot of time to get processed.
Photo of Crowdie

Crowdie, Champ

  • 972 Posts
  • 272 Reply Likes
We have 6.5r4 running across some big deployments and it has been very stable.  We rolled it out under urgency to a number of affected sites and they have remained stable.
Photo of mr bee

mr bee

  • 77 Posts
  • 0 Reply Likes
Same here, no random issues for the moment :-)
Photo of Webster Alfonso

Webster Alfonso

  • 3 Posts
  • 0 Reply Likes
Mike

I work for a university and would be interested in your AP's if still available.

Webster
Photo of Mike Smith

Mike Smith

  • 13 Posts
  • 1 Reply Like

OK, so this is the deal. It was not my intent to open up a discussion about defending Aerohive or not. I am not attacking Aerohive. The platform has its limits, so does every platform. A few of the issues that we had, we were given "resolutions" that are not adequate for an "Enterprise" platform. We tested alternate phones, including Ascom, and had the same results. We have had expert after expert from partners and Aerohive make refinements to our configuration that did make it better, but did not resolve our particular issues.

To say that Ascom handsets outperform Cisco means nothing with out specifics. Arbitrary positive statements do not make compelling cases to purchase new hardware. 7925 phones are not "n" capable, and Ascom handsets are. That is useful information. Ultimately it did not change our experience.

Many sites have 7925's with Cisco RF, and are very happy. Other sites have Aerohive RF and are very happy. FOR US, we are making the move to a platform that has displayed that it can deliver what we need, and fill in the gaps that Aerohive is not addressing at the time that we needed it. I am not accusing Aerohive of anything, I am just stating the facts from our decision making process.

I think Aerohive is good hardware, or I would just go ahead and send it to the rubbish heap and not try to get it to someone that could use it.

Please limit any further comments to suggestions for relocating the equipment. There are a few already in the thread, and I appreciate that. I will let you know more as we work through vacating the equipment, which happens at the end of next week. If you have made a request or recommendation, I will connect back with you individually. Any and all suggestions for relocation are great. I was just trying to provide preferences for which organizations we are hoping to benefit.

Thanks!

Photo of Peter Pham

Peter Pham

  • 0 Posts
  • 0 Reply Likes
Hi Mike,

We've just migrated to Aerohive over at Edmonds Community College over in the NW. I'm interested in knowing cost but really wishing for a donation. 


Thanks!
Photo of Mike Smith

Mike Smith

  • 13 Posts
  • 1 Reply Like

Thank you all for your replies. I would like to take the conversation with any interested parties outside of this forum, so as to not clutter it all up. If you are interested in receiving AP's, would you please email me directly with the following information:

  • Name
  • Organization

  • Desired number of AP's

  • Desired AP models (we have 330's, 350's, and 170's)



mike.smith@grh.org


Thanks!