I am building out a new ESX cluster and I was using this also as a testbed to upgrade from 3.5 to vsphere. However I am running into an issue that about a minute after a add a host to virtual center (currently 4 but also happened with 2.5) the host does not respond. I have tried this with a 3.5 u5 ESX server as well as a 4.0 u1 server. The ESX server is up and running normally, and I can disconnect and reconnect the server through virtualcenter and it comes back fine.
I have checked the defacto name resolution and firewall ports and everything is able to talk to each other, and virtualcenter even makes the initial connection. I have restarted hostd and mgmt, removed ssl certificates, cleared IE ssl state, and verified the managed server IP in vcenter but this still fails. I finally found the following error in the hostd.log but can't find out what it means. The results seem like it is never fully getting the system information and times out, causing the ESX server to disconnect:
Task Created : haTask--vim.SessionManager.updateMessage-158860894
Task Completed : haTask--vim.SessionManager.updateMessage-158860894
Task Created : haTask-ha-host-vim.HostSystem.updateManagementServerIp-158860895
Task Completed : haTask-ha-host-vim.HostSystem.updateManagementServerIp-158860895
Task Created : haTask-ha-compute-res-vim.ComputeResource.reconfigureEx-158860896
Updated local swap datastore policy: false
Task Completed : haTask-ha-compute-res-vim.ComputeResource.reconfigureEx-158860896
Event 47 : User vpxuser@127.0.0.1 logged in
Task Created : haTask--vim.AuthorizationManager.setEntityPermissions-158860898
Task Completed : haTask--vim.AuthorizationManager.setEntityPermissions-158860898
Event 48 : User vpxuser logged out
Event 49 : User vpxuser@127.0.0.1 logged in
Event 50 : User vpxuser logged out
Hw info file: /etc/vmware/hostd/hwInfo.xml
Task Created : haTask--vim.SessionManager.updateMessage-158860903
Task Completed : haTask--vim.SessionManager.updateMessage-158860903
Task Created : haTask-ha-host-vim.HostSystem.updateManagementServerIp-158860904
Task Completed : haTask-ha-host-vim.HostSystem.updateManagementServerIp-158860904
Task Created : haTask-ha-host-vim.HostSystem.acquireCimServicesTicket-158860905
Task Completed : haTask-ha-host-vim.HostSystem.acquireCimServicesTicket-158860905
GetPropertyProvider failed for session[52bb821a-c547-553d-c891-e77ff8acfc56]523b4db6-bf57-ee7c-1527-9d19269e82c4
GetPropertyProvider failed for haTask--vim.AgentManager.upgrade-158860714
GetPropertyProvider failed for haTask-ha-root-pool-vim.ResourcePool.updateConfig-158860461
GetPropertyProvider failed for haTask--vim.AuthorizationManager.setEntityPermissions-158860459
GetPropertyProvider failed for haTask-ha-host-vim.HostSystem.updateManagementServerIp-158860465
GetPropertyProvider failed for haTask--vim.SessionManager.updateMessage-158860464
GetPropertyProvider failed for haTask--vim.AgentManager.prepareToUpgrade-158860713
GetPropertyProvider failed for haTask--vim.AuthorizationManager.setEntityPermissions-158860711
Event 51 : User vpxuser logged out
Throw vmodl.fault.RequestCanceled
(vmodl.fault.RequestCanceled) {
dynamicType = <unset>,
msg = ""
}
Failed to send response to the client: Broken pipe
GetPropertyProvider failed for haTask-ha-host-vim.HostSystem.updateManagementServerIp-158860827 GetPropertyProvider failed for haTask-ha-compute-res-vim.ComputeResource.reconfigureEx-158860828 GetPropertyProvider failed for haTask--vim.SessionManager.updateMessage-158860826 GetPropertyProvider failed for haTask--vim.AuthorizationManager.setEntityPermissions-158860830
Hw info file: /etc/vmware/hostd/hwInfo.xml
GetPropertyProvider failed for haTask-ha-host-vim.HostSystem.updateManagementServerIp-158860839
GetPropertyProvider failed for haTask--vim.SessionManager.updateMessage-158860838
GetPropertyProvider failed for haTask-ha-host-vim.HostSystem.acquireCimServicesTicket-158860841
Throw vmodl.fault.RequestCanceled
(vmodl.fault.RequestCanceled) {
dynamicType = <unset>,
msg = ""
}
Failed to send response to the client: Broken pipe
Hi PSL4401,
we have since a few days the same problem. Do you have a resolution for this problem?
Thomas
Make sure that UDP port 902 is opened from your ESX hosts to vCenter server
This can be caused if you are using server 2008 as your vCenter server and the server's firewall does not permit all incoming VMware traffic. In my case, this was caused by the firewall believing it was in a private/work network instead of the correct Domain network.
This was resolved by allowing VMware traffic inbound in ALL profiles in teh firewall configuration.
This is very often caused by a network or server firewall issue.
Make sure all required ports are available in both directions from vCenter to the ESX(i) host.
As a test you could disable the firewall on your vCenter server and create an ANY/ANY rule for your vCenter to ESX host connection.
i would also create a vmware sr and let them support get it fix asap .. most of the info can be found in the esx and vcenter log files.