HiveManager 6.0r2a stops responding after "Upload and Activate Configuration"

  • 1
  • Question
  • Updated 5 years ago
  • Answered
Hello,
I've upgraded HiveManager from version 5.1r3 to 6.0r2a. Upgrade was successful but after that when I "Upload and Activate Configuration" to all access points at once, it stops responding or becomes terribly slow. I can "Upload and Acticate Configuration" only for one or two access points at once without being affected by HM slowness. Only thing I can do then is to connect by SSH and reboot HM.

There was no such issue in 5.1r3. Do you know how I can overcome this problem?

HiveManager 6.0r2a
110 access points (330, 321, 350, 170)
3GB memory

I checked memory and storage usage, disk I/O rate, system load average - everything is ok.
There are no logs about that in System Log.
Photo of Marek Szymonski

Marek Szymonski

  • 44 Posts
  • 4 Reply Likes

Posted 5 years ago

  • 1
Photo of Crowdie

Crowdie, Champ

  • 972 Posts
  • 272 Reply Likes
I had issues with two AP170 access points when I upgraded one site from 5.1r5 to 6.0r2. To get the new 6.0r2 configuration onto the AP170 access points I had to factory default them and them apply the 6.0r2 configuration.

I didn't experience this issue with the AP121, AP141 and AP330 access points.
Photo of Marek Szymonski

Marek Szymonski

  • 44 Posts
  • 4 Reply Likes
My all access points already have HiveOS 6.0r2a.
Photo of Crowdie

Crowdie, Champ

  • 972 Posts
  • 272 Reply Likes
If you attempt a "complete upload" to a single access point does it complete?

A "complete upload" uses SCP to copy the configuration to the access point. If you use a "delta upload" then the changes are "pushed" through the CAPWAP tunnel.
Photo of Marek Szymonski

Marek Szymonski

  • 44 Posts
  • 4 Reply Likes
Yes, it completes. Problem is in number of access points I want to upload at once. I offten add local users to access points and I need upload them to devices. If I select all access points and then "Upload and Activate Configuration" web interface of HM stops responding.
Photo of Crowdie

Crowdie, Champ

  • 972 Posts
  • 272 Reply Likes
I have a case open with Aerohive Support with a similar problem. One of my sites uses permanent PPSKs for managed devices and if we try to activate more than three or four at the same time it takes so long to complete the update process and respond that the browser times out.
Photo of Marek Szymonski

Marek Szymonski

  • 44 Posts
  • 4 Reply Likes
Yes, this is it.
Photo of Crowdie

Crowdie, Champ

  • 972 Posts
  • 272 Reply Likes
The issue appears to be that the PPSK activation process is a serial function so is extremely inefficient. The amount of time taken to activate PPSK x is longer than the amount of time taken to activate PPSK x-1, which is longer than the amount of time taken to activate PPSK x-2 and so on. Hence the total time required to activate PPSKs grows geometrically as you add additional PPSKs.
Photo of Mike Kouri

Mike Kouri, Official Rep

  • 1030 Posts
  • 271 Reply Likes
Crowdie,
You've correctly described an issue we've identified with the way we distribute PPSKs among the members of the hive. We do have intentions to change the slow PPSK activations from one by one to multiple activations at the same time, in an upcoming release. Sorry, but since it has not yet been committed into a specific release I cannot comment on a timeframe, other than "as soon as I can ".
Photo of Crowdie

Crowdie, Champ

  • 972 Posts
  • 272 Reply Likes
Do we have even an indicative resolution date for this issue? I had a lead that would work well with permanent PPSKs but I cannot recommend Aerohive until the issue is resolved.
Photo of Mike Kouri

Mike Kouri, Official Rep

  • 1030 Posts
  • 271 Reply Likes
Crowdie,
The PPSK activation issue should be fixed in 6.1r1, due for release in about a week.
Photo of Marek Szymonski

Marek Szymonski

  • 44 Posts
  • 4 Reply Likes
That's bad it was "improved" in v. 6.0r2a bacause it worked pretty well in v. 5.1r3.
Photo of Crowdie

Crowdie, Champ

  • 972 Posts
  • 272 Reply Likes
The site where I have this issue is running 5.1r5.

As I am now aware of the issue I haven't used this design at any other sites so I can't comment on the performance under 6.0r2 or 6.0r2a but as Aerohive Support have not advised me to upgrade the HiveManager I suspect the issue hasn't been resolved.
Photo of marco

marco

  • 8 Posts
  • 0 Reply Likes
I have the same problem with AP 121 to pass from 5.1r3 to 6.0r2...
Photo of Marek Szymonski

Marek Szymonski

  • 44 Posts
  • 4 Reply Likes
Thaks to Aerohive technician this case is solved. I was adviced to increase maximum startup memory. My was set to 512. And I increased it to 1024. After that problem is gone. HM is running very fast.
Below is an instruction how to change it.

• SSH into HiveManager
• Choose Advanced Product Configuration
• Choose Configure VM Params
• Choose Display VM Params

If this is less then 1024 then change it.

Instructions for increasing the Java VM memory allocation start size:
• SSH into HiveManager
• Choose Advanced Product Configuration
• Choose Configure VM Params
• Choose Change VM Params
• Enter "1024" (for 1GB)
• Go up to the root menu
• Reboot HM Appliance
Photo of Amanda

Amanda

  • 396 Posts
  • 25 Reply Likes
Thanks for sharing your outcome, and the details Marek. I am glad it all worked out!

Amanda
Photo of marco

marco

  • 8 Posts
  • 0 Reply Likes
Unfortunately I have the same problem again with the use of the ID manager (with PPSK) and startup memory to 1024 ... increase it still can create problems?