Upgraded VC to 2.5 cannot connect to ESX host

[s189jds]

I am currently running a single ESX 3.0.0 Host and just upgraded VC from 2.0 to 2.5. During the upgrade it was decided to do a fresh DB rather than upgradng the MSDE we had. So when I added the ESX host to the datacenter is looked like it was ading it just fine. At the end there was a pop up that said the VCagent was not upgraded. Looking in VC the host is there but shows disconnected. When trying to connect it just times out. Anyone have this issue or a fix? We are planning to upgrade ESX to 3.5 this weekend but would like to get VC working first.

Thanks!

[Troy_Clavell · Accepted solution]

you probably just need to manually install the VC agent. Here is a link

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

[azn2kew]

User "vpxa -v" to find out the VC build number

rpm -qa | grep vpx* to find out VC package installed

rpm -e vpxpackagename to install the package

Refer to www.vmware-land.com for further documentations!

"Reading Is Fundamental" There is no limit to education

[csk026]

I also upgrade my virtualcenter 2.0 to 2.5 on a new database (does not used the old one).

My servers are still esx 3.02.

3 of my servers succeeed to communicate with the vertual servers.

2 of my servers can not connect to virtual center.

While i try to connect the servers, virtual center connect to the ESX and display all virtual machines.

in the end of the process i get the following error.

"unable to access the specified host......"

I did the following checks

1) vpxa -v and found my version and get:

VMware VirtualCenter Agent Agent Daemon 2.5.0 build-64192

2) /sbin/service mgmt-vmware status and get:

vmware-hostd (pid 14852) is running...

3) restart services.

4) ping to virtualcenter host

succeed.

5) check license log.

10:35:55 (VMWARELM) OUT: "ESX_FULL_BACKUP" root@zil06esx05.mcil.comm.mot.com (2 licenses)

10:40:17 (VMWARELM) OUT: "PROD_ESX_STARTER" root@zil06esx04.mcil.comm.mot.com (2 licenses)

Do you have any idea?

Regards

[vthyng]

I am in the same situation as the last response, agent level appears to be correct (2.5) after the upgrade. I don't get a disconnected message in Virtual Center, but I can not launch any remote console windows to the VMs with a "could not connect to host" message.

[azn2kew]

People have different problems and it varies so best way is to test one by one to validate and look at this thread solve other users too. Try to add static entries for /etc/hosts files for both ESX/VC servers.

http://communities.vmware.com/message/892221

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

Regards,

Stefan Nguyen

iGeek Systems LLC.

VMware, Citrix, Microsoft Consultant

[csk026]

Hi

I solved the problem.

I found some VM with validation problems .

• Illegal CDROM (does not exist ISO host file)

• VM VMDK does not exist.

I fixed it and now i can connect the host.

Regards

[ssarav]

Illegal CDROM (does not exist ISO host file)

VM VMDK does not exist.

How these VM issues prevent the Host connection?

In my case we had firewall port issue after VC 2.5 upgrade. running esxcfg-firewall --allowOutgoing solved the issue.