I ran into a similar issue with a remote-site ESX 4.1 server connecting to vCenter Server 5.0. The host was pinging, ports 902 and 903 were open and our vCenter server was able to get the host t...
See more...
I ran into a similar issue with a remote-site ESX 4.1 server connecting to vCenter Server 5.0. The host was pinging, ports 902 and 903 were open and our vCenter server was able to get the host to connect for short periods of time, but after about 90 seconds the host would go back to a disconnected state. I was not aware that there was any heartbeat related traffic going across the SSH protocol (port 22) but when comparing this host to another that was not experiencing the issue, the only thing that was not identical was: # esxcfg-firewall -q sshClient Service sshClient is blocked. I followed that up with: [root@localhost ~]# esxcfg-firewall -e sshClient [root@localhost ~]# esxcfg-firewall -q sshClient Service sshClient is enabled. Suddenly the vCenter instance for the host reconnected and has stayed stable and connected ever since.
