Moving AP's between VHMs....

  • 1
  • Question
  • Updated 5 years ago
  • Answered
We recently just purchased 79 of the 121 units and I have a need to break two of them into a separate VHM. Is there a suggested way for me to do this myself?
Photo of Brandon Dayberry

Brandon Dayberry

  • 4 Posts
  • 0 Reply Likes

Posted 5 years ago

  • 1
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2487 Posts
  • 449 Reply Likes
Can you not just set up a different Hive if you're using Enterprise mode?
Photo of Jeff Haydel

Jeff Haydel

  • 6 Posts
  • 4 Reply Likes
If you are using HM on-prem then you can simply setup a new VHM and then SSH into each AP and use the command 'capwap client vhm VHM_NAME' to push the device to the new client.

I'm certain there is another way, but I've found that way to be the most efficient.

If you are using HMOL then you will need to contact support to get access to another VHM. Once you have the second VHM you will possibly need to change the capwap server name as well as Aerohive runs our services on a pool of servers. The command to do that is 'capwap client serve name SERVER_NAME' . I think this SERVER_NAME can be a DNS name like or an IP addresses like .

Hope that helps,

Jeff H
Photo of Andrew Garcia

Andrew Garcia, Official Rep

  • 368 Posts
  • 119 Reply Likes
If you have an on-premise HiveManager, you can also assign the APs to the new VHM from the GUI. If you log in using a super admin account, there will be a Reassign button in the Monitor > All Devices window (if using 5.x).
Photo of Brian Powers

Brian Powers, Champ

  • 391 Posts
  • 91 Reply Likes
If i'm not mistaken, Andrew is only partially correct. You can move them between VHMs within the GUI, but only if it hasnt been assigned to a VHM yet and doesnt have a policy applied. For example, you have VHM ID 1 and 2 and the default (new devices pool) pool that devices go to prior to assignment. You cannot move a device from VMH ID 1 to VHM ID 2 via the GUI (You get this error, "Aerohive device "Device Name" cannot be reassigned to another VHM because it is already a managed device.").

You can however go from the default pool to either VHM ID 1 or 2. And the easiest way I've come across on getting a device out of a VHM, is just to remove it and it'll pop back into your HM after a time period and you can reassign it from there.

Also bear in mind you will need to divide up your licenses between your VHMs. As it also will not let you assign devices to a VHM if that instance doesnt have enough licenses to support the quantity of devices you are assigning to it.