Migrating from HMOL to on-premise

  • 1
  • Question
  • Updated 2 years ago
I have a customer who would like to migrate an existing HMOL account to an on-premise appliance (vm).  Is there a guide or any other form of documentation available that depicts the procedure for this? 
Photo of Josh Grzelakowski

Josh Grzelakowski

  • 11 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 1
Photo of Karthik Krishnaswamy

Karthik Krishnaswamy

  • 13 Posts
  • 4 Reply Likes
HM NG VA is available. Same Entitlement key can be used between HMOL and NG. Here's the migration document: http://www.aerohive.com/330000/docs/guides/Aerohive_HiveManagerNG-Migration.pdf

AM-HMNG-VA: Zero currency SKU needs to be purchased.
Photo of Josh Grzelakowski

Josh Grzelakowski

  • 11 Posts
  • 0 Reply Likes
Thanks for providing that.  Is there a guide that doesn't involve NG?  The customer won't get going to that right away.
Photo of Brian Powers

Brian Powers, Champ

  • 391 Posts
  • 91 Reply Likes
What type of guide are you looking for?  As there isint a ton involved in this.  

Once the VM image is spun up and working, it needs licenses, and configuration and lastly the devices need pointed to it.  

Customer should be able to backup their HMOL account/configuration.

On the VM HM, you should be able to restore the above backup file to retain all the exact configuration.

Lastly on the HMOL side of things, you should be able to select all of the gear and modify it, and under the Credentials section, you can alter the primary/backup HM.  Put in the new IP of the VM HM and push that out.  That should change the gears CAPWAP server IP.  The gear will come in as unconfigured.  Apply the configuration to the gear (should all be identical), and push out.  Reboot most likely needs to happen since its technically a new HM/Network Policy.  Once gear comes back up, things should be working as intended.

The above is a real rough draft, but I believe it should cover everything needed to move gear...  
Photo of Bill W.

Bill W.

  • 222 Posts
  • 35 Reply Likes

Make sure that you have all your settings documented before you attempt your migration.  Because not every setting gets migrated.  The majority of your stuff gets migrated, but there will still be a few things that do not.  You will need to go back in and double-check everything.  And your database size will need to be under 1 GB.  I'm in the middle of migrating my on-prem HM to a new, beefier VM and have discovered some of these issues.