VMware Cloud Community
RickPollock
Enthusiast
Enthusiast
Jump to solution

VC 2.5 and ESX 3.0.2

I know I saw a compatibility matrix somewhere, but heck if I can find it now. Can you use VC 2.5 to manage 3.0.2 hosts? If so, is anyone doing this successfully? I tried to connect to one of my hosts using the VC 2.5 client is it only prompted me to download the 2.0 version of the client.

Just trying to plan out my upgrade path and this compatibility issue is a key factor!

0 Kudos
1 Solution

Accepted Solutions
MR-T
Immortal
Immortal
Jump to solution

Allowing an ESX 3.5 host to access the VMFS volumes created with 3.0.2 shouldn't cause any problems as you're not re-formatting the disk.

As far as I'm aware, there's no significant difference between the 2 versions.

I've not read of any issues with older hosts seeing LUNS formated by 3.5 servers.

View solution in original post

0 Kudos
8 Replies
MR-T
Immortal
Immortal
Jump to solution

Yes you can manage ESX 2.x & 3.x servers with VC 2.5.

Yes I have tested this with 3.0.2 and it works.

0 Kudos
MR-T
Immortal
Immortal
Jump to solution

VI Client version 2.0.1 can only manage ESX 3.0.x

VI Client version 2.0.2 can only manage ESX 3.0.x

VI Client version 2.5 should be able to manage ESX 3.0.x, 3.5 & 3i

0 Kudos
RickPollock
Enthusiast
Enthusiast
Jump to solution

Did you just import your hosts into 2.5 or perform an upgrade on VC 2.0 with hosts already added?

Right now I have several hosts in VC 2.0. If I upgrade that to VC 2.5 would I need to perform any other tasks?

0 Kudos
RickPollock
Enthusiast
Enthusiast
Jump to solution

One more question. I'm running 3.0.2 and VMFS version is 3.2.1. ESX 3.5 is version 3.3.1.

All the hosts can "see" all the LUN's in the SAN. What will happen if I upgrade a host that has a running VM on the LUN?

0 Kudos
MR-T
Immortal
Immortal
Jump to solution

During the beta I upgraded my VC 2.0.2 to 2.5 and it contained a number of 3.0.2 hosts.

Yesterday I deployed a new VC 2.5 and just added my ESX 3.0.2 host to this.

I've not experienced a problem.

0 Kudos
MR-T
Immortal
Immortal
Jump to solution

Allowing an ESX 3.5 host to access the VMFS volumes created with 3.0.2 shouldn't cause any problems as you're not re-formatting the disk.

As far as I'm aware, there's no significant difference between the 2 versions.

I've not read of any issues with older hosts seeing LUNS formated by 3.5 servers.

0 Kudos
RickPollock
Enthusiast
Enthusiast
Jump to solution

Thanks for your help!

0 Kudos
esiebert7625
Immortal
Immortal
Jump to solution

http://vmware.com/pdf//vi3_35/esx_3/r35/vi3_35_25_compat_matrix.pdf

Eric Siebert

VMware Communities User Moderator

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

Visit my website:

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

0 Kudos