VMware Cloud Community
Vaibhav_shah
Contributor
Contributor

Not able to add new host on virtual center server 2.5

Hi I have upgrade my virtual center server from 2.0 to 2.5. I want to add my existing ESX 3.0 server on that virtual center server. After giving Host IP and its credetials i am getting error "Request Time out". I am able to ping the host from virtual center server. The licence parts seem OK.

Can any one tell me the reason behind the error and solution for same.

Thanks.

vaibhav

Reply
0 Kudos
15 Replies
weinstein5
Immortal
Immortal

Try restarting the mgmt-vmware agent on your esx host - from the Command Line service mgmt-vmware restart

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
Reply
0 Kudos
Vaibhav_shah
Contributor
Contributor

i already tried the same.

I am successfully telent 443 and 902 ports from VC server.

Reply
0 Kudos
williamarrata
Expert
Expert

If that does not work, Disconnect your host adn reconnect your host to the VC. Also make sure you upgrade your host to 3.5. I did not see anywhere that you stated the host was upgraded. You want to do this so you can take advantage of the upgrades 3.5 gives you. Also, after you do the service mgmt-vmware restart you may wanna do this also. service vmware-vpxa restart. You should be good after that.

Hope that helped. Smiley Happy

Hope that helped. 🙂
Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

....also, try to manually install the VC agent on the host in question

http://vmware-land.com/Vmware_Tips.html#ESX6

Reply
0 Kudos
kjb007
Immortal
Immortal

Is the hostname in DNS or does the name resolve via hosts file? An IP by itself will cause problems if proper name resolution is not in place. Make your your vc and esx hosts all are able to resolve each other's names.

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos
williamarrata
Expert
Expert

Opps, forgot to say this too, make sure your DNS setting are set correctly by going into your VC, Congiguration tab, DNS and Routing. Make sure your good there. Also, just for kicks, click your licenced features and make sure your ALL good in that area.

Hope that helped. Smiley Happy

Hope that helped. 🙂
Reply
0 Kudos
Vaibhav_shah
Contributor
Contributor

sorry guys. none of the soulution help me out. host name ping is happening properly. restarting service also not help and stoping firewall also not help me get issue resolve.

Reply
0 Kudos
kjb007
Immortal
Immortal

On the esx host, run hostname command on the service console to make sure your name is set properly.

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos
Vaibhav_shah
Contributor
Contributor

I had already check in starting and its OK.

Reply
0 Kudos
kjb007
Immortal
Immortal

Run 'rpm -qa |grep -i vpx' and it will give you the version of the vc client that is installed.

Run rpm -e <file_name_of_rpm>

Run userdel vpxuser

Run service mgmt-vmware restart

Then try to add the host into vc again

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos
williamarrata
Expert
Expert

Vaibhav,

I'm not sure what your support level is with VMWare but I'de like to see you please make an SR and respond to this thread with what the fix is.

Hope that helped. Smiley Happy

Hope that helped. 🙂
Reply
0 Kudos
azn2kew
Champion
Champion

What is your ESX and VC version to be exact and have you done upgrades lately? Virtual Center 2.5 Update 1 should be able to run both ESX 3.0.x/3.5 hosts.

Generally speaking, this problems caused when you do an ESX ugprade because the VPX agent doesn't like to do so and each scenario are different and you have to at least test 5 different steps to resolve your problems and one of them should fix it. I've answered a lot of this questions on the forum you can search more details.

1. Make sure DNS is working correctly if not place /etc/hosts entries for ESX servers should help resolve problems.

2. Manually remove VPX agent with rpm -e vpxagentbuild

3. Restart hostd and vpxa services "service mgmt-vmware restart" & "service vmware-vpxa restart" commands.

4. Double check your / root partition not being filled up and full

5. Check to see if vmware-root folder has been created if not create them.

These should help with many problems with ESX hosts not connected.

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

Regards,

Stefan Nguyen

iGeek Systems Inc.

VMware, Citrix, Microsoft Consultant

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!! Regards, Stefan Nguyen VMware vExpert 2009 iGeek Systems Inc. VMware vExpert, VCP 3 & 4, VSP, VTSP, CCA, CCEA, CCNA, MCSA, EMCSE, EMCISA
Reply
0 Kudos
admin
Immortal
Immortal

Does the timeout happen after you enter the root user/pass details and press "Next" or at the end of the wizard?

If it times out after pressing "Next", the issue is being caused by communication with authd or hostd but not the vpxa agent.

Can you connect directly to the ESX server using the VI Client from the VC server?

Do you get any errors when you run the following command on the ESX server? vmware-cmd -l

Is the ESX server swapping heavily or low on disk space?

free -m

df -h

Reply
0 Kudos
Vaibhav_shah
Contributor
Contributor

Hi,

Find the result of the cmds.

1) vmware-cmd -l

/usr/bin/vmware-cmd: Could not connect to server

(VMControl error -14: Unexpected response from vmware-authd: 511-The process exited with an error:

Incorrectly built binary which accesses errno or h_errno directly. Needs to be fixed.

Can't open perl script "/usr/lib/vmware/serverd/init.pl": No such file or directory

VMServerd Panic: Could not initialize Perl script handler.

511 End of error message)

2) free -m

total used free shared buffers cached

Mem: 262 250 11 0 10 129

-/+ buffers/cache: 110 151

Swap: 541 3 537

3)df -h

Filesystem Size Used Avail Use% Mounted on

/dev/sda2 4.9G 4.7G 0 100% /

/dev/sda1 99M 29M 66M 31% /boot

none 132M 0 132M 0% /dev/shm

/dev/sda6 2.0G 52M 1.8G 3% /var/log

I am not able to connect to server from VI client from VC server. Its giving error for server response time out.

Thanks

Vaibhav

Reply
0 Kudos
kjb007
Immortal
Immortal

Looks like your / drive is basically full. You'll need to clean some of that space out to continue. Maybe check /tmp and clean out what you can.

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos