Hi, I have a cluster of 3 ESXi 4.0 hosts, I'm using vCenter 4 to manage them.
My issue is when I reboot a host, the status is esx.host.com (Not Responding) for about 20 minutes, however if is restart vCenter service that fixes it straight away.
Anyone else had this issue?
A delay of 10-15 min could be normal.
The status return normal ONLY if you restart VC?
Do you meet minimum requirement for VC Server?
I have 2 clusters one with six ESX 3.5 hosts and the other with the three ESXi 4.0 hosts
vCenter is a VM still running on the ESX3.5 cluster (2 vCPUs 3 GB memory)
I have rebooted ESX hosts in the past it never took so long it came back up within 60secs. I have tried rebooting these ESXi 4 hosts several times with the same problem, I never gave it the chance to recover on its own cause I thought it wouldn't so that when I tried restarting the vCenter service to see if that resolved it and it did.
In the last week I have noticed a few issues with vCenter, storage views doesn't work anymore now.. error stating "Storage service in not initilized"
In fact, you should look again to DNS resolution.
I had a situation, when I could ping all the machines (Esx1, Esx2, vCenterServer), but nslookup wan't successful.
When I resolved problem with my DNS (actually a routing problem) only then it was ok.
So - recheck that Esx host and vCenter have ability to nslookup FQDN each other.
I am having a similar issue in my POC environment. The only difference is that my systems (Dell 6850s) take 30+ minutes before coming back online.
I have verified that it isn't a name resolution issue.