vCenter 5.1. Update 3 has no Upgrade path?

[stv7777777777]

The Solution Upgrade Path of the interoperability matrix is showing that there is no upgrade path available from either vCenter Server 5.1 Update 3 or from ESXi 5.1 Update 3.

I am having a hard time believing that the latest patch for the 5.1 versions cannot upgrade.  Normally a rebuild would do just fine, but there is replication and SRM integrated and I need to upgrade in place.   Has anyone upgraded from 5.1 Update 3 to 5.5 Update 2 or anything in between?  I am really hoping this is just a glitch in the interoperability matrix.

[a_p_ · Accepted solution]

This looks indeed strange. However, from the date when 5.1U3 was release (5.1U3 in 12/2014 - 5.5U2 09/2014) there's a good chance that 5.1U3 already contains code that's not integrated in 5.5U2 yet, but might come with 5.5U3.

André

[stv7777777777]

That is a valid argument and makes perfect sense.  I also have a query case open with support and will update this thread with what I hear back.

[a_p_]

Yes, please report back what you hear from support. That's certainly interesting for others too.

VMware released several patch packages since 5.5U2, so maybe it's supported to create an up-to-date installation image using Image Builder!?

André

[stv7777777777]

VMware Technical Support replied with the following message (typo and all).  I am not entirely convinced with this reply, so I will be holding out for version 6.  They did not address why the upgrade path was excluded from the matrix.  I half wonder if they even researched my query.

"The highest available 5.1 version is VCenter 5.1 Update 3. 

The highest available 5.1 version is VCenter 5.5 Update 2d

You can upgrade vCenter from 5.1 to 5.5, regardless of what patch/ update version (of 5.1) VCenter is running on"

[Lord_Klaud]

Here is why I believe the upgrade is not available :-

5.1 U3 release will include some newer bug fixes which were reported to VMware between 5.1 U2 release and U3 release date which is December 2014. Now If we allow customer to upgrade to  5.5 U2 which has a release date of Sep 2014, we are potentially exposing him to the possibility of running into issues (reported and fixed between Sep 2014 and Dec 2014) which he already had a fix for.

[BenLiebowitz]

This is why I prefer to build new...  I put a host into maintenance mode, remove it from the cluster, rebuild it, re-join it to vCenter and then re-add it back to the cluster. 

Then, rinse and repeat. 

[stv7777777777]

I agree that building new is the most recommended approach, but there is not a supported migration option for SRM which is why we have to upgrade the existing.