HMOL HM server entry changes from DNS name to non-routable IP address

  • 1
  • Question
  • Updated 2 years ago
We seem to be having an unusual situation occurring with our devices (Switches & AP's) where the HM server entry is getting changed from a DNS name (which works) to a 10.x.x.x IP address.

We use HMOL, so that entry by all accounts should always be a DNS name, not an IP address, and certainly not a 10.x.x.x IP address.

The devices continue to work -- as they should, however they can't be managed once this occurs.

Has anyone else had this happen?  Resolutions?

It's a real (PITA) to have to manually change them back to make them work again.
Photo of Bryan Tetlow

Bryan Tetlow

  • 78 Posts
  • 2 Reply Likes

Posted 2 years ago

  • 1
Photo of Mike Kouri

Mike Kouri, Official Rep

  • 1030 Posts
  • 271 Reply Likes
Bryan,
My guess is that you either have an unexpected local copy of HM6 on your network, or that your DHCP server is offering up options to instruct your HiveOS devices to point to the wrong place for the HM6 server. Take a look at the graphic showing how CAPWAP discovers HM at http://docs.aerohive.com/330000/docs/help/english/6.6r3/hm/full/help.htm#config/APs/capwap.htm?Highl... ; this may help you troubleshoot your problem.
Photo of Bryan Tetlow

Bryan Tetlow

  • 78 Posts
  • 2 Reply Likes
We don't have any "local" HM installations... Only Switches and AP's.

I'm going to have to log a support call it seems....  The info you attached (good info) seems to dead-end back at HMOL servers which we have no control over.

The idea that the 10.x.x.x subnet is getting deposited in the configs is the part that is of concern because with support recently we had a major failure of our configurations at the AH servers and EVERY device had to be touched to repoint them to the DNS named entry....which begs the question, IF it had a DNS name there how did it get changed to an IP address?

If it was HM in-house, then that would be ok, but this is not the case.  Also, the 10 subnet belongs to our internet scopes so should never have gotten there...ever!

The subnet that's getting used however, is not one that we use DHCP for, so it could not be assigned by anything locally.