Hello Folks,
I´m finding a tough time to add an ESXi host.
The FQDN is absolutely fine, the ESXi2 is reachable when I ping.
But the add host is timing out in the vCenter.
I appreciate all your comments and assistance
Note:
1. Both the ESXi 1 & 2 are running in the vmware workstation as I do not have enough network ports in the server. Its a LAB scenario.
2. vCenter is hosted in ESXi1 as VM and I did not have issues adding ESXi1 to vcenter, but when I add ESXi2 am unable to add. It timeout..
Thanks,
I appreciate if someone could throw light on this peculiar problem.
I thoroughly searched for solution, but am unable to find a fix. Please help
Is reverse DNS working?
ping -a 172.16.33.6
Lars
Yep !
vcenter:~ # ping -a 172.16.33.6
PING 172.16.33.6 (172.16.33.6) 56(84) bytes of data.
64 bytes from 172.16.33.6: icmp_seq=1 ttl=63 time=104 ms
64 bytes from 172.16.33.6: icmp_seq=2 ttl=63 time=104 ms
64 bytes from 172.16.33.6: icmp_seq=3 ttl=63 time=103 ms
crazy_xplorer,
As the result of "ping -a" returns the ip address instead of the host name your problems seems to be related to reverse dns not working.
Lars
mumesxi01.vmlab.local is 172.16.32.4. It is already added to vcenter
mumesxi02.vmlab.local is 172.16.33.6 is problem.
When I do nslookup in the vcenter the results here.
vcenter:~ # nslookup 172.16.33.6
Server: 172.16.32.10
Address: 172.16.32.10#53
Non-authoritative answer:
6.33.16.172.in-addr.arpa name = mumesxi02.vmlab.local.
Authoritative answers can be found from:
vcenter:~ # nslookup 172.16.32.4
Server: 172.16.32.10
Address: 172.16.32.10#53
Non-authoritative answer:
4.32.16.172.in-addr.arpa name = mumesxi01.vmlab.local.
Authoritative answers can be found from:
Why you put your vCenter Server on one of your virtualized ESXi?? If you setup VCSA in another VM beside them as a VMware workstation VM, is the problem still existing or not? Can you check it.
You setup the VCSA in a VM inside of a ESXi that is a VM itself, So VCSA's vNIC must be connected to a vSwitch that vSwitch's connected uplinks must be connected to a bridged VMNET in the Workstation host to transfer the network traffics to another ESXi host.
When you try to add the 2nd ESXi check following path in that host:
/var/log/vpxa.log
/var/log/hostd.log
Since it is LAB scenario I tried to connect as shown below
ESXi1 (vCenter) - GNS3 (Ethernetswitch/Router) - ESXi2 (vSWITCH)
I guess the bottom of the problem lies in the GNS3.
It is not capable to carry traffic between vcenter and ESXi2 and timeout. I fixed the problem via adding a virtual router in ESXi 1 & 2.
It is fixed now and am able to add the the ESXi2 host.