Moving AP121 to managed - formerly attached, HM Classic won't pick up

  • 1
  • Question
  • Updated 3 months ago
AP121 - was online on another subnet - moved to new subnet, not being picked up by HM.  Plenty of licenses, not that issue.  AP picked up new DHCP reservation.  Can SSH to device but our Hive uname/password is not accepted and neither is the default.  Added device to Unmanaged Devices using MAC and what will be it's Profile, restarted AP via PoE from switch - still not showing up in HM.  We will reset to defaults when we get to it, just wondering if there is another way to make it talk to the mother ship.
Photo of Chris Kelly

Chris Kelly

  • 8 Posts
  • 0 Reply Likes

Posted 3 months ago

  • 1
Photo of Terence Fleming ThinkWireless

Terence Fleming ThinkWireless, Champ

  • 79 Posts
  • 27 Reply Likes
Most likely issue is a firewall blocking traffic between the new subnet and the management system

But it is often really hard to persuade whoever is managing your firewalls that this is the issue.

Ask If they can see traffic traversing the firewall, and whether anything is being dropped

If they cannot help you need to talk to the AP and find out what is going on

SO you need to SSH to the AP either across the network or through the console port (there isnt one on the AP121 if I recall)

If it rejects your Device management password then you will be forced to reset the APin order to get access

With an SSH session running, press the reset button for five seconds - this will give you confirmation that you are in fact resetting, not just rebooting the access point

When it comes alive again, then you should be able to log in with admin/aerohive

Your key CLI command is 
capwap ping redirector.aerohive.com

If this fails you have your smoking gun that capwap (UDP 12222) is blocked

Then you can go back to the people running the firewall with a "Please explain"

show run will show you the running configuration (should initially be blank)

After the AP has connected to redirector.aerohive.com the show run command will tell you which Hive Manager the AP thinks it belongs to
Photo of Chris Kelly

Chris Kelly

  • 8 Posts
  • 0 Reply Likes
We don't have firewalls between subnets and I manage the entire network here so that takes that part out.  All APs have a direct shot to the HM, no interference.

Resolution - reset AP, wait....nothing....reset again.  AP starts rebooting every 2 minutes.  Noted that AP light never went out, as indicated in the hardware reference guide.  Let it reboot about 5 times, never connected to HM.  In between next reboots, it finally takes default Aerohive uname/pw.  Cleared config "_clear config all", rebooted.  PS - checked the capwap config once I got in, it was correct and could see the HM address - just would not talk to it.  After restart, it finally checked in with HM using it's default hostname.  Sent config update - Fail.  Sent firmware update - worked (was already on current release, but anyway).  Sent config update - Fail.  Sent full config update and restart - Done.  45 minutes start to finish. 

NOTE FWIW - we have over 200 APs installed of several types and I have noticed that generally, out-of-box is not a problem.  Moving one AP from Here to There, about half the time Funny Things happen Everywhere - like this particular move.
Photo of Terence Fleming ThinkWireless

Terence Fleming ThinkWireless, Champ

  • 79 Posts
  • 27 Reply Likes
Hmm, sounds a bit sick.  The AP has two firmware images, and also carries the current configuration and a backup one.

Is it possible that one of the firmware images has become corrupted?
Photo of BJ

BJ, Champ

  • 374 Posts
  • 45 Reply Likes
If you can still ssh to it, perform:
"reset config bootstrap" then "reset config"

Please update with the results.