How to troublshoot connection to Online Hivemanager

  • 1
  • Question
  • Updated 2 years ago
I have 9 AP230 AP's which will not connect to online Hivemanager. It started when the server local DNS server went down and the DNS settings were changed to that of the router. I was able to connect to each individual AP and change the DNS to the router, rebooted the AP and they reconnected. However 2 weeks later I checked and they DNS settings had reverted to the local DNS server (which was disabled) and they no longer were connected. 

This time when I changed the DNS settings back to the router IP they still would not connect, even after a reboot. I connected to CLi on an AP and checked the Hivemanager settings, they were correct, tried to ping the HMoL address, couldn't. I re-enabled the DNS on the local server, changed DNS IP on the AP and was able to ping the HMoL address, however, still not connecting. 

What else can I do to troubleshoot the connectivity from the AP to HMoL?

Thanks
Photo of Nathan Kaa

Nathan Kaa

  • 4 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 1
Photo of Mike Z

Mike Z

  • 8 Posts
  • 2 Reply Likes
You can verify DNS is working by going to the CLI of the AP and trying something simple like ping www.google.com 

Regarding HMOL connection, you'll want to see what your capwap status is via "show capwap client" and look for what's in the RUN state (should say "Connected securely to the CAPWAP server", though you can also make sure that you have your HiveManager Primary name with the proper server (same as you see when you log onto the HMOL portal).  Also note your CAPWAP transport mode, whether it's TCP/UDP/12222, or HTTP on TCP.  You can force HTTP if you want via "capwap client transport http"

You can try "capwap ping <your hmol primary name>" to validate that DNS is resolving and that you can reach the HMOL.

You can also try "exec _test tcp-service host <your hmol primary IP> port 22" and "exec _test tcp-service host <your hmol primary IP> port 80" to validate L4 connectivity.

Also remember that you can run "no capwap client enable" followed by "capwap client enable" to restart the capwap process on-demand.

Hopefully something in all that points to what the issue is.  Also remember that CLI changes will get overwritten by HMOL upon next config push, so make sure to update the proper settings in HMOL.  CLI should ideally be used for non-pushed details (like some capwap settings) or testing.
Photo of Nathan Kaa

Nathan Kaa

  • 4 Posts
  • 0 Reply Likes
Thanks for the reply Mike. Once I had the DNS settings working I had to run the "no capwap client enable" "capwap client enable" to the the AP's to communicate, yay! I just assumed that rebooting the AP would do the same thing.