Error while communicating with remote host when creating new virtual machine

[usmansiddiqui83]

I am running 7 ESX servers on IBM blade H22 There is an error prompts while i create a new virtual machine

on vcenter server

After 30 to 35 minutes, it gives an error

"Error while communicating with remote host"

Existing machines are running fine...I have tried to create Vms on other ESX servers as well

but same issue. I have also tried to make clone of an existing machines but no success

Can anyone help?

[AndreTheGiant]

ESX and vCenter are on the same network?

vCenter Server meets the right requirements of CPU and RAM?

DNS resolution is fine?

Andre

[joshp]

Do you have a firewall between your ESX hosts and vCenter (or software firewall application on vCenter enabled)?

VCP 3, 4

www.vstable.com

[jadelzein]

has this always been an issue, or something that recently popped up? is the vCenter on the same physical network as the hosts? looks to me like a basic communications issue, but need more details to determine.

please share the steps you are taking when provisioning a new VM -- a summary of your setup would help as well.

JE

[usmansiddiqui83]

This started happening just recently.....vcenter and esx servers are on same network i can ping esx servers from vcenter server by their names.......

I select Create new vitual machine from the cluster and then do things normally which i do while creating virtual machines.... i also tried to create virtual

machine while choosing esx servers myself still no result.....vcenter server has sufficient CPU and RAM resources..

[usmansiddiqui83]

I have successfully created a new vm on esx's local storage but when i try to create vm on SAN LUN it gives me same error..... i tried to upload a 186 KB file on one of the SAN LUN ..... and after 3 to 4 minutes it eventually uploaded successfully.

[mail2ibrahim21 · Accepted solution]

Have you rescan the LUNs once?

Have you restarted the management agent?

Have you restarted the vpxa?

If not please perform the above step and verfiy.

[Rohail2004]

did you restart the vmware mgmt services on the host?

[usmansiddiqui83]

Thanks a lot . Problem has been resolved by restarting vpxa