I have 3 ESX servers in cluster and a Virtual Center server.
Upgraded the virtual center server to version 2.5. Then I planned to upgrade ESX servers. Migrated all virtual machines from one of the ESX. The upgrade failed (due to noe unplug fibre cables to SAN), and I had to do a totally new install of 3.5. The install went well, and looks good in vCenter.
Have manually setup switches and vnics. But when trying to migrate virtual machines from one of the esx with version 3.02 the migrate fails with error: Operation timed out
Validating is reporting OK. I had 2 virtual machines that was powered off when re-installing. Powering one of this on is working OK.
Have also applied all Critical and Non Critical updates from Update Manager to the new installed ESX server.
Update: When doing a cold migrate, the migrate works OK, but powering the machine o, reveale that the network cable is plugged out. So I guess my neworking config that I manually have entered is not correct. Is it an easy way to export/import all network settings to my new 3.5 ESX ...? Have tried ITQ Infrastructure Client version 1.0.0.22631 with no luck
Hope this helps
http://everythinglinux.org/rsync/
since you are not well versed with GNU/Linux, you can even try this if it works
On ESX server 1
cd /vmfs/volumes
then use scp -r DATASTORE/* root@ESX_SERVER_2:/vmfs/volumes/REQUIRED_DATASTORE
by this way you will be syncing the vmfs partitions or technically speaking copying the VM's from one server to another...
Regards
Anil
Save the planet, Go Green
if you found my answer to be useful, feel free to mark it as Helpful or Correct.
This document was generated from the following thread: ESX upgrade from 3.02 to 3.5 - Migrate fails, operation timed out
