i'am working on an cluster/host preparation.
on the nsx manager console i proofed the connectivity between nsx mgr and host via "debug connection <hostname>", which is fine.
i'm also able to reach nsx-manager from the esxi through hostname and fqdn.
there is no firewall in between.
but preparation does not go throuth.
i already downloaded the vxlan.zip and installed the 3 vib's manually on the host (dvfilter, vsip, vxlan)
when i have a look in the nsx managers log bundle i see this error:
VIB module for agent is not installed on host <hostname> (_VCNS_159_Cluster_VMware Network Fabri)
is someone else having the same issue or an idea what i should look for ?
i really appreciate your help !
Encountered a similar error. Check the /var/log/esxupdate.log on the affected hosts. If you see a message about MetadataDownloadError (<urlopen error [Errno -2] Name or service not known>), check to see if the vCenter Server managed address is set correctly.
Log into the vCenter Server (Web Client), browse to the vCenter Server in the Inventory List.
Go to Manage/Settings/General and expand Runtime settings. Verify that vCenter Server managed address is set correctly.
I made that correction in my environment, disconnected/reconnected the problematic ESXi host from the cluster (not sure if that was necessary), then retried the Host Preparation.
At that point Host Preparation was successful.
Hope this helps.
Agree with Blair. Many people forget about the vCenter Managed address in the Runtime settings. Some of the VMware products require this setting.
I have the same problem then i try to add DNS Record for NSX Manager and ESXi host. After add DNS Record it's work for me.
Points to Blair. I performed the NSX Component Installation via the Web Client and two out of three hosts installed the VIB correctly. After much troubleshooting I added the Managed IP Address to vCenter Runtime Settings per this thread and the third host finally succeeded.
Verified that the vCenter Server managed address is set correctly.
This did not work for me. My resolution was to Uninstall Update Manager, and re-install Update Manager.
This fixed my issue... just in case others run into this issue.
Worked for me. Thank you very much.
In my case I did not have to unregister and register the host