Hello,
I'm struggling adding a ESXi host back to my vCenter. The setup is a bit "exotic" but worked for months.
I've have my home lab and one single host I rent on the Internet for "disaster recovery".
All my hosts are (were) connected to the same vCenter (so all required ports are opened for that) - I'm not opening a discussion about the design.
After an Internet provider's problem, I was not able to reconnect the host, so I removed it from inventory to tried to add it back, but I wasn't able to.
vCenter and hosts are patched to the very last 6.7 version (VC: 15807714 and hosts: 15160138)
This is what I see from the vCenter, the task fails at 80% after the usual wizard (I can see all VMs during the wizard):
Ad this is what I see on the host:
What I've already tried so far :
* Rebooted my Internet box - Don't laugh, the provider is not rulled out from the issue. I had several strange things with it like not being to access the web console of the spoken host from home, but able to access it from my mobile!
* Removed the vpxuser from command line : the warning disappear during the process
* Rolled back a self signed certificate from the host, but after the wizard, it replaces it automatically by one from the VCMA (which is OK)
None of the above helped to get any further.
What I need first is to know where I need to search further something that can be relevant for me or for anyone that would like to help... Thanks in advance !
at first i would check vpxa.log and hostd.log
then try to restart management agents. if vm are running check that autostart on the host is disabled
at first i would check vpxa.log and hostd.log
then try to restart management agents. if vm are running check that autostart on the host is disabled
Hi,
After the provider issue, haven't they added Firewall?
ARomeo
AlessandroRomeo68 well even if I would not be surprised, it is not the case, it just a basic router with NAT. I'm forwarding all the ports on my own to get a proper management.
berndweyand restart of the agents worked ! Thanks a lot. But now you have to explain me why it worked when several reboots of the host didnt... :smileylaugh:
I can't believe such a simple thing helped, I'm ashamed (but still confused)
now i have the problem that i cant explain this. but restarting the agents is a common tasks for resolving problems since over 10 years.
but thee main thing is that it worked 🙂
berndweyand yep, I'll try that first the next time for sure BEFORE shuting down all VMs and restarting the host !!! :smileylaugh:
In that case, it was absolutelly not an issue to do so but we should write that down somewhere: restarting the host is not helping the same as restarting the agent.