VMware Cloud Community
bluebull2rhyme
Enthusiast
Enthusiast
Jump to solution

ESX 3.03 to ESX3.5(U2) & ESX 3.01 to ESX 3.5(U2)

Guys,

We are planning to upgrade our ESX to the latest 3.5(U2)..have some questions..

We have 1 Cluster with 2 ESX 3.03 servers in it & an other cluster with 2 ESX 3.01 servers in it..However i'm upgrading the VC to 2.5 on both and proceeding with ESX upgrade.Assuming the VC upgrade went fine , Once i start the upgrade on the Clusters with ESX3.03 & ESX3.01..i will upgrade one servers on both clusters to ESX3.5 update2.

Once the upgrade is complete,the cluster will have (1 server with esx301 & 1 server with 3.5) & (1 server with 303 and 1 server with 3.5)..now when i click "enter maintainance mode" on the 2nd....will the VM's can VMOTION to the other without any problem?

Thx

Shiv

If you find this useful,award me Helpful or Correct answer
Reply
0 Kudos
1 Solution

Accepted Solutions
kjb007
Immortal
Immortal
Jump to solution

It should be fine, although you may have to answer a warning message, so you may have to run vmotion manually on your vm's. 3.5 adds some CPUID information to the vm's config file, and you get a warning about that when you move vm's to/from these hosts. Also, once you upgrade the vmware tools to the version on the 3.5 hosts, you'll have problems trying to vmotion to 3.0.x. Make sure the vmware tools upgrade is the last thing you do once all your servers have been updated.

ESX U3 is also available, and if you're upgrading, then I'd upgrade to that version.

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB

View solution in original post

Reply
0 Kudos
2 Replies
kjb007
Immortal
Immortal
Jump to solution

It should be fine, although you may have to answer a warning message, so you may have to run vmotion manually on your vm's. 3.5 adds some CPUID information to the vm's config file, and you get a warning about that when you move vm's to/from these hosts. Also, once you upgrade the vmware tools to the version on the 3.5 hosts, you'll have problems trying to vmotion to 3.0.x. Make sure the vmware tools upgrade is the last thing you do once all your servers have been updated.

ESX U3 is also available, and if you're upgrading, then I'd upgrade to that version.

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos
mikepodoherty
Expert
Expert
Jump to solution

We've one the 3.0.1 to 3.5 upgrade and have discovered that the patch level on the 3.0.1 servers makes a difference. If the servers are early versions of 3.0.1 and haven't been patched VMotion may not work between the 3.0.1 to 3.5 servers. You can shut down the guest and move them easily to the 3.5 servers - but live migration fails.