Tuesday, March 13, 2012

Upgrade from vSphere 4.x to vSphere 5

Have visited several customers and everyone is on different version of vSphere 4.x update and some on vSphere 5 (that is good) and some are still in VI3.5.

Many are not considering to do further upgrade but intend to migrated directly to vSphere 5.  The good news is the upgrade can be in place upgrade by using the CD or simply use the vCenter Update Manager.

However there are some issues arised for specific versions of vSphere 4.x which need to be take care of  before doing the upgrade/migration to vSphere 5 else you might just lose the environment.

Users who are on

vSphere 4.0 Update 2:
 vSphere 4.1:

Take care if you environment contains any of the two mentioned build of vSphere 4.x, do upgrade to the next build before upgrading/migrating to vSphere 5.

Update 23 Mar 2012
For vSphere 4.0 Update 2 issues with vCenter 5.0 is been resolved in vSphere 5.0. Update 1.  This can be found in the release note on 15 Mar 2012 (3 days after my post above).

ESX 4.0 hosts with certain build numbers cannot be managed by vCenter 5.0
A purple screen of death (PSOD) may occur on hosts running ESXi 4.0 releases between Patch03 (build 219382) and Patch09 (build 360236).This occurs when the host is being managed by vCenter 5.0 in a cluster with HA enabled and VPXA agent gets reinstalled on the host e.g. if the host was removed and re-added into the vCenter inventory. With this fix, hosts are allowed to be managed by vCenter and the ESX 4.0 hosts does not PSOD.
This issue is resolved in this release.
Post a Comment

Windows 2016 Core Licensing FAQ

A very busy month for me and also traveling to take a break from work. Finally to sit down and compose which got confused by many of my co-w...