Moving to 3.0.2 ... have some questions...

[Brahmzy]

All,

My 6 hosts (2 clusters) are currently on ESX 3.0.1 and my VC is 2.0.1.

I want to do fresh installs on all hosts (I'm also adding a new one) and I want to upgrade VC.

I'm wondering what order I have to do this in. Will VMotion break if I have a 3.0.2 host in the same cluster with 2 other 3.0.1 hosts? In other words, can I hot migrate VMs on a 3.0.1 host to a new 3.0.2?

Also, should I upgrade VC first before everything?

Thanks!

Message was edited by:

Brahmzy

[Texiwill]

Hello,

You can vMotion from 301 to 302... .It is what I did.

You do not need to reinstall unless you absolutely need to for other reasons. the upgrade option works just fine.

You do not need to upgrade to VC 201 first. I did mine in the middle and it did not hurt anything.

Best regards,

Edward

[esiebert7625]

According to the release notes ESX 3.0.2 is not compatible with VC 2.0.1. Not sure what they mean by that and it may work OK but you might want to upgrade VC to 2.0.2 first.

http://www.vmware.com/support/vi3/doc/releasenotes_esx302.html#whatsnew

[boydd]

Like above - I seem to remember that you must upgrade VC first to 2.0.2 and then you can upgrade the hosts to 3.0.2 (This has also been the case in the past). That's the way I have done it. It has worked out well so far (Knock on wood).

DB

[admin]

I also used the upgrade approach and have not had any issues