VIC 2.5 and ESX 3.0.1

[cgorsline]

I recently installed VIC 2.5, not an upgrade, and I'd like to use it to manage my ESX servers. I have the proper licenses. One of my server is running 3.0.2 and I have been able to successfully connect to that system. However, when I try to connect to my other ESX server which is running 3.0.1 it fails with the message "Failed to install the VirtualCenter Agent service." I have gathered that I need to manually install the agent. My issue is with which file do I use to upgrade the agent. From the upgrade folde on VIC 2.5 I have several to choose from. The files are named 'vpx-upgrade-esx-0-linux-64192' but there are several numbered from 0-7. Can anyone tell me which I should run?

[Named_Jason]

Hi - I was performing an upgrade today and ran into this same issue - 2 ESX hosts (both vanilla 3.0.1), upgrading VC from 2.0 to 2.5. One host configured just fine and the other could not install the VC Agent. I found that simply restarting the management service on the failing host resolved the issue.

From the command line:

service mgmt-vmware restart

[Named_Jason]

I realize that I should probably go into a little more detail and as I seem unable to edit my prior post, I'll do it here.

The process that I went through to resolve this was to

1) restart the management service

(at the command line) service mgmt-vmware restart

2) Reconnect to the host

(in the VIClient connected to VirtualCenter) Right click on the Host -> Connect -> Walk through the wizard entering all requested information. If you just select the "datacenter" object as the location for your VMs, it will apparently preserve their current folder placement.

After these two steps, it reconnected just fine. HA did not immediately come up, so I disabled it at the Cluster and then reenabled it and both hosts configured successfully (after verifying name resolution).

[asutosh]

Create vmware-root folder in /tmp:

mkdir -p /tmp/vmware-root

And try adding the ESX3.0.1 host to VC2.5 , it should work.

If still it fails, logs from /var/log/vmware/hostd.log would help in understanding whats the problem.

[avarcher]

This worked for me, thanks. Give it a couple of minutes after the restart to do the reconnect.