New AP won't show in Manager even after manual config (led is white and gets proper capwap server ip

  • 1
  • Question
  • Updated 4 years ago
  • Answered
I have 8 new AP 121 and after entering the hivemanager settings (online manager) and ip settings etc. I get and IP from the CAPWAP server (outside) the AP led is white but does not show up in the manager at all. I have plenty licenses left.
Photo of M. Boekholt

M. Boekholt

  • 9 Posts
  • 1 Reply Like
  • frustrated

Posted 4 years ago

  • 1
Photo of BJ

BJ, Champ

  • 374 Posts
  • 45 Reply Likes
I would contact the reseller or support, it seems the serial numbers are not associated with you HMOL account.

Photo of Crowdie

Crowdie, Champ

  • 972 Posts
  • 272 Reply Likes
For anybody having issues connecting an access point to a HMOL I hope the following is useful to you.

In your HMOL:

  • Click on the "Monitor" menu
  • Click on the "All Devices" option in the left hand pane
  • Click on the "Device Inventory...." button
  • Select "Add/Import" from the drop down menu
  • Enter the serial number of your access point
  • Click on the "Add" button
You should now see a dialog box saying your access point has been successfully added.  If the dialog box mentions that the serial number is assigned to another HMOL then you need to contact your reseller as your access point has been assigned to an incorrect HMOL.

What you have just done is advise the Aerohive Redirector cloud component where to redirect the access point if it attempts to connect to the Aerohive cloud service without a valid VHM configured.

If you have successfully assigned your access point to your HMOL and the access point does not have a configuration on it then just connect it to an Internet source and wait a few minutes until it is configured automatically for your HMOL.

What happens here is the Aerohive HiveOS firmware has attempted to connect to the Aerohive cloud service as it has no configuration and has not been able to communicate with an on-premise HiveManager.  If the access point is able to communicate with the Aerohive cloud service and the Aerohive Redirector has a valid entry for the serial number of the access point the Aerohive Redirector will send two commands to the access point advising it how to connect to the VHM.  If you have a console connection to the access point you will, after a few minutes, suddenly see two commands added to the access point's configuration.

However, if you can't wait you can manually configure your access point to connect to the HMOL using the same two CLI commands that the Aerohive Redirector would use:

capwap client server name
capwap client vhm-name yyyyyyyyyy

Where is the hostname of the server housing your VHM and vhm-name yyyyyyyyyy is the name of your VHM.

If you are not sure what these should be SSH into an access point that is working and execute a show capwap client command.

I have had issues moving an access point from one HMOL to another and in this case you need to factory reset the access point and then try to connect it to the new HMOL.

To test if your access point has connectivity to the HMOL use the CLI command capwap ping where is the hostname of the server housing your VHM.
Photo of M. Boekholt

M. Boekholt

  • 9 Posts
  • 1 Reply Like

Thanks you for your info (both). It runed out to be registred on the wrong Hivemanger like suspected a litle by both of you.

I cleared my  config (because I already used the manual capwap configuration, so I did not see it come up with the wrong name.

I contacted the reseller and hopefully Aerohive can fix this fast for us.

Anyway, thank you again for all the info and I will post a final comment when it works out.