Hive Manager NG VM forgets hostname afte update - no guest management possible! Urgent help needed!

  • 1
  • Question
  • Updated 6 months ago
The Hive Manager NG VM on our site has been updated to its latest version (11.26.3.5)

After updating when we try to access it as usual via the hostname we assigned the webbrowser is redirected automatically to the IP of the hivemanager.
This triggers a SSL certificate warning in the browser since the certificat is issued for our domain and not for an IP address. Since our AV software blocks access to insecure sites, our guest managers can currently not manage any guest accounts.
At the moment our IT department has to handle all of their requests. The problem may be due to a misconfiguration of the default site of the webserver, how can we access the HM NG VM directly to remedy this? We have no login user credentials for the console for direct access to the HM.
Photo of Tobias Protz

Tobias Protz

  • 61 Posts
  • 11 Reply Likes

Posted 6 months ago

  • 1
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Hi Tobias,

I suspect that you have a problem with your VMware environment rather than with the HMNG VA.

Have you checked that the OVF properties are still configured and being passed to the HMNG VA. These are mentioned in the Quick Start Guide:

https://media.aerohive.com/documents/Aerohive-QuickStart-HiveManagerNG-Virtual-Appliance.pdf

As far as I am aware, running VMs cannot control settings outside of it in host environment.

You need to ensure that VMs are started via vSphere so that the OVF properties are passed in at VM start. If you start the VM via another route, VMware does not persist and pass these in.

Cheers,

Nick
Photo of Tobias Protz

Tobias Protz

  • 61 Posts
  • 11 Reply Likes
Nick, iirc the ovf properties are only set at the first run when you set up Hivemananger NG as a new VM.
In fact, there is no option to set/check these properties afterwards in VSphere.

The problem did not arise with a new install, but with a normal upgrade of the VM via the files provided by Aerohive.
The same procedure was done a few times last year without any problem, but now accessing the machine via its hostname will switch to the ip in the browser address bar immediately, thereby voiding the ssl certificate.
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Hi Tobias,

That is not correct. The OVF properties in expected, normal circumstances do-and-must persist within the VMware hosting environment. They are and must be passed in by vSphere every time the VM is started.

Your hosting environment has become corrupted somehow if these are missing.

I will add some screenshots showing how to manually recreate these properties in a reply to this thread.

Thanks,

Nick
Photo of Tobias Protz

Tobias Protz

  • 61 Posts
  • 11 Reply Likes
Hello Nick,
thanks for the quick reply. The environment hasn't changed, we only applied the update to the Hive Manager and noticed afterwards this strange behaviour. 
It is consistent with a badly configured Apache, seen this on other web servers, therefore my suspicion.
Will investigate further with our Vsphere tech guy.
Photo of Tobias Protz

Tobias Protz

  • 61 Posts
  • 11 Reply Likes
Just checked, the Vm is started via vSphere center, but I cannot find any of the ovf settings mentioned in the guide. The vApp settings for this machine are completely switched off however, so it will get its network settings from the DHCP server.
Could this have something to do with the latest patches from VMWare for the vCenter?
We normally do not deploy pre-configured VMs though, so I have no other VM to check this against.

Edit: just to be sure: I was under the impression that the .ovf settings are only applied on the first startup of the VM when it is initially configured.

Our VM WAS up and running fine, with the correct hostname and everything. It was only after applying the latest update that it started to refer to the IP when trying to access the HMNG via browser instead of keeping the hostname in the address bar.
(Edited)
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Hi,

I am not sure how your VMware hosting environment has become corrupted.

I suggesting investigating this with VMware's support.

Thanks,

Nick
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Hi Tobias,

The expected properties are as follows.

If the OVF Template has gone missing, I suggest recreating the properties manually.

You should stop the HMNG VA, recreate these as below, and then start the HMNG VA again within vSphere.







Regards,

Nick
(Edited)
Photo of Tobias Protz

Tobias Protz

  • 61 Posts
  • 11 Reply Likes
Thanks a lot Nick,
unfortunately vApp support is turned off and has been off all the time on this vCenter.
Therefore our tech is unable to set anything in this submenu. 

Still, in this very same configuration, the VM was working for more than half a year, and through two prior updates. So I am quite surprised that this could suddenly have an impact?

Also, what vSphere version are you running this on? Our menus look quite different from yours, we are on 6.5.0 
I noticed only now that the Hivemanager VM is still on version 8, we are currently deploying machines of much newer versions (the VMware tools on the machine are also always flagged as outdated for this reason). Can we upgrade the machine to newer VM tech (Gen 13) without any problem?
As of now, your machine is still stuck on ESXi level 5.0 which should be from around 2013.

Greetings,
Tobias
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Hi Tobias,

VMware have changed the look and feel of their GUI and moved to a Web-based interface.

These are some screenshots we took from an older version some time ago that I dug up to try and help you as quickly as possible.

However, you should be able to find the same area of configuration, it still applies.

Yes, you should be able to move to a newer hardware generation if you wish to. Please take a backup first, however.

We have always required OVF Properties to be configured for the HMNG VA since day one as the official process in the deployment guide.

I suspect this issue may be related to an upgrade to 6.5 and an incompatibly with our existing OVF template and that version.

Official support for 6.5 is coming with the next release of the HMNG VA.

Is this something that coincides?

It should be possible to recover this by getting the OVF properties recreated.

Regards,

Nick
(Edited)
Photo of Tobias Protz

Tobias Protz

  • 61 Posts
  • 11 Reply Likes
Thanks for all your help Nick, 
I have forwarded everything to our VM tech :)

Hm, our vCenter was always kept up to date, the only thing that "might" coincide is the timing of the upgrade and the Spectre/Meltdown patches that VMware issued.

Will check up on this. If I can pinpoint it 100% to a certain chain of updates I will report back so that other people won't have the same problem.