When I was installing vSphere 4.1 ESXi I ran into a problem. I received the following error when I added the ESXi host to my cluster:
Call “Datacenter.QueryConnectionInfo” for object “yellow bricks” on vCenter Server “W2K8-001” failed.
Although the error didn’t make much sense I had the feeling it had something to do with name resolution(This KB article gave a hint I guess). After I added my dns suffix on my NIC it worked. Problem solved.
Hello Duncan,
Can you expand on how you added the domain to your nic? I’m getting this error in my home lab and I’ not sure how to implement your fix. 🙂
Thanks.
– right click your network adaptor
– properties on your IP4 stack
– click advanced
– got to your DNS TAB
– add your dns suffix to “dns suffix for this connection”
Hi Duncan,
I found the same error poping up when adding an ESXi 4.1 host via IP to VC using the WRONG password for the root account.
D
One more problem solution involving networking…
I received this error and found that I could ping the management address from one machine but not another. We are connected to Cisco switches using port channels and I had not connected both nics to the management console. Even when I did connect both nics there was a mismatch in the settings. The VM default for the switch is to load balance on port ID but we needed IP hash to match the Cisco setup.
update to above…
You can configure the loadbalance (iphash) from the command line on the console if you are having trouble with communication. I leave it as separate research if you do not know how to get to the local tech support mode command line. Once you get there:
vim-cmd hostsvc/net/portgroup_set –nicteaming-policy-loadbalance_ip vSwitch0 “Management Network”
Same issue here. Everything was fine and then vCenter server crashed for an unknown reason, afterwhich it couldn’t connect to the host. I removed the host and tried readding each time getting this error either with IP or DNS name. All DNS was working correctly and suffixes setup as mentioned but still no joy. I rebuilt the host with the same details but still could not add it back to vCenter. In the end I added it using another management port (different IP) and it’s all fine. I haven’t had chance to look into it further or try the original IP again but perhaps there is some corrupt entry in the database?
Hi
I had the same issue identical setup on two hosts but one kept dropping out after updating to ESX4.1.
Even though DNS was working I still could not connect host using DNS name.
To solve the issue I added a host entry on the VirtualCenter server with the ESX hosts details and then it connected fine.
Richard
Does anyone has the solution? Please be more details on the issue discussed, which I try everywhere but still could solve the problem. thanks!
hello gentlemen the following fix worked for me , just as ” duncan epping”
stated it
– right click your network adaptor
– properties on your IP4 stack
– click advanced
– got to your DNS TAB
– add your dns suffix to “dns suffix for this connection
Had the same message as above, turned out if I used an AD account, the operation completed successfully. The Sr. Vmware Admin had configured AD so ESX Admins accounts worked to perform the “Add Hosts”.
After a brief power outage i couldnt connect my vc to esx. Using vc 4 and esx 4.1 and this all happened after a brief power outage. I tired all of the responses above but still no joy, please help!!!! my boss will kill me otherwise!
Hello Guys,
When I had similar problem I did something like this:
1. Log on to ESX console as root of course,
2. Write simple command as /etc/init.d/network restart
3. After shutting down and bringing up the vmnics for management problem has gone.
I hope its helpful.
Regards,
cre.sa
I suffered with this issue and was banging my head against the wall. Ping worked, dns was configured correctly, but no luck. I connected directly to the host through the vShere client, and changed the ip address for the management network… tada all is well. Very bizarre problem that I spent hours on and changing the ip fixed it in about 30 seconds.
Guys
I had similar problem today.
There was be ip address confict. When I resolved that the problem still continued.
I had to do ipconfig /flushdns to flush the earlier mapping of hostname to ip to get the renewed ip.
As soon as that was done, I was good.
I had the exact same issue and tried all the above. However, I determined that the my problem was having an IP address conflict. I have a cisco server and I had the CIMC utility using the same IP address as the server. I changed that and was able to add the server.
hope this helps
I have tried the above and nothing works, there is not an IP address conflict. DNS is configured the same on both hosts. I have tried adding that connection info to the vCenter server NIC and nada.
I did try the ipconfig /flushdns as well on the vCenter server.
Does anyone have any other suggestions?
Thanks!
Tracy V
Duncan,
I know this is an old post, but quick question. which Nic are you refering too? the NIC of the client or the NIC of the vCenter.
vCenter in my case.
how can I stop the vlan service?cause I meet the same problem after I distribute a vlan port for every network.
I get the same error when I set up my VMotion network AFTER I have add the ESXi to VC.
The problem was that I had changed the VMkernel Default Gateway when I set up the VMotion network :-(. When I changed back to the right IP on the VMkernel Network everything was OK and I can add the ESXi to VC again!
thanks cre.sa , your steps worked for my lab environment had same issue.
once again thanks
Executing “Restore Network Settings” in the ESXi Console and then re-IP’ing the Management Interface worked for me.
Jaime Porras
logon on the console,
restart the management Agents
connect the server (vsphere client)
and it’s work for us
This just worked for me. I was confused at first after checking the suffix on the machine I was running vSphere Client from and found it to be set correctly.
The machine running vCenter, however, did not have a suffix configured. After doing so, adding the host went without issue. I didn’t have to restart anything.
Thanks Duncan! Love your blog and books.
I had this issue when attempting to add new hosts to vCenter. Using the ip address worked, but not the host name. I tried it with the FQDN and it worked properly.