Is there a way to stop the Automatic update of Aerohive devices?

  • 1
  • Question
  • Updated 4 years ago
Hi

We have many Aerohive devices and each access point has many users, around 800, the access points are constantly trying to update the configuration, user database, etc and this fails more often that not. This seems to cause other problems for us, like the IDM proxies or UAP to stop working. Is there a way to stop these automatic updates and only have them run when we want them to?

Regards
Jordan
Photo of Jordan Hall

Jordan Hall

  • 3 Posts
  • 0 Reply Likes

Posted 4 years ago

  • 1
Photo of Carsten Buchenau

Carsten Buchenau, Champ

  • 356 Posts
  • 117 Reply Likes
I might be missing the point here, but by design Aerohive devices only update their configuration if you trigger that process via Hivemanager. Unless there is configuration option somewhere I am not aware of, to install configuration changes automatically / scheduled... Anyway, as long as you do not change your configuration, there will be no updates. And - unless configured otherwise - the default behaviour is do do incremental updates in most cases, not requiring a reboot and thus normally not causing disruptions (unless you change radio parameters etc).

What puzzles me is your statement of 800 clients per Access Point - maybe I misunderstood and you mean 800 in total? Because the max limit of clients per radio is 100...
Photo of Jordan Hall

Jordan Hall

  • 3 Posts
  • 0 Reply Likes
We have over 800 permanent accounts, which get uploaded to the access points.
You mention as long as the configuration changes, we often have to add users to the system and this is done via the operator login and activated individually. this causes the configuration of the devices to be pretty much constantly considered out of date by hive manager. That is the issue really. I want to stop Hive Manager trying to update these devices.
Photo of Carsten Buchenau

Carsten Buchenau, Champ

  • 356 Posts
  • 117 Reply Likes
Ok, got it. You have a large number of user accounts, all defined via "Manually Created Private PSKĀ Users" local user groups, correct?

The point is that those "permanent accounts", generated by a user manager admin, must be pushed to every AP, otherwise they won't work.

NOTE: I don't know this functionality well enough if this default behaviour of automatic updating can be alternated... someone else has to comment on this.

However - Considering the size of your user db and the frequency of changes being done, you might want to consider changing your concept:
- Switch to automatically generated, temporary accounts - so you use User manager to assign accounts that are generated automatically on each AP due to the creation mechanism you define, and thus no configuration updates are required
- Switch to RADIUS accounts

Ultimately you probably want to switch to Radius. You can use a 3rd party product to manage those accounts, or an Aerohive AP as Radius server with local accounts (and thus only that AP needs to be updated), or Aerohive ID Manager - which is definitely an option you should look at.
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
I am not understanding the perceived problem. What is the issue with HiveManager flagging that the running configuration on an AP differs from that which is configured? You can always look at a diff of the configured to running configuration if you ever need to dill down in to what is different.

Until an upload is performed to the devices, changes you have made to add users, PPSKs etc., will not be applied. The notification is therefore valid.

HiveManager does not perform this upload automatically after a configuration change, you instigate that process.

If you are having issues actually uploading the delta configuration changes because they fail, have you updated to HiveManager and HiveOS 6.2r1?
(Edited)
Photo of Jordan Hall

Jordan Hall

  • 3 Posts
  • 0 Reply Likes
Well that's the thing we aren't triggering the update. Maybe we did before and it's choosing a moment to retry that update. But we almost constantly have devices trying to update. This has pretty much always occurred and I haven't worried about it. But this may be causing us issues and I just wanted to see if there is a way to stop it. We are looking to move to 6.2r1 soon and perhaps that will help. I have found different version of the HM have had varying degrees of success with the delta upgrades in our environment.