Upgrade Vsphere 4 to 4.1 using vCenter Update Manager




Step by step procedure to Upgrade Vsphere 4 to 4.1 using vCenter Update Manager

Prerequisites:

The following space requirements for partitions must be met.
The /root partition must have at least 1.8GB.
The /boot partition must have at least 24MB of free space.

To upgrade ESX 4.0 to 4.1
Download – upgrade-from-ESX4.0-to-4.1.0-0.0.260247-release.zip 
(note: Pre upgrade pack not required if you are using update manager)
Step 1

Import Upgrade Release:

Login to Vsphere Client -> go to Update Manager -> Host Upgrade Releases 
Click on Import Upgrade Release and follow the below steps

Browse and Point the downloaded upgrade-from-ESX4.0-to-4.1.0-0.0.260247-release.zip file

Step 2 : Create Baseline:

In Update Manager -> Host Upgrade Releases click on Create Baseline and follow the below steps

Baseline created Successfully

Step 3: vSphere 4 up-gradation

Attach the created baseline at Cluster level or Data center level and scan for updates














Now right click the data center or individual hosts and click on remediate. 
and follow the below steps.






















This will move all the vm to other host and goes to standby mode and apply the patches.

Or you can put the Host in to stand-by mode and apply the upgrade

Upgradation will take 15 to 30 min to complete. After the reboot, host will show the new version number 4.1.0, 260247 

Errors:

Remediation did not succeed for SingleHostRemediate: esxupdate error, version: 1 .30, operation:  15: Error running RPM transaction: file /etc/pam.d/sfcb from install of vmware-esx-im-4.1.0-0.0.260247.i386 conflicts with file from package sblim-sfcb-1.3.2Dell-9.1.el4.i386; file /etc/sfcb/sfcb.cfg from install of vmware-esx-cim-4.1.0-0.0.260247.i386 conflicts with file from package sblim-sfcb-1.3.2Dell-9.1.el4.i386; file var/lib/sfcb/stage/default.reg from install of vmware-esx-cim-4.1.0-0.0.260247.i386 conflicts with file from package sblim-sfcb-1.3.2Dell-9.1.el4.i386 .error8/7/2010 1:41:34 PM Remediate entity

Solution:
Remove the conflicting package and retry
#rpm -e sblim-sfcb-1.3.2Dell-9.1.el4

If low space available on /boot

df -h
uname -a

Edit grub.conf and remove the old boot menu files
#vi /boot/grub/grub.conf

move the old initrd-2.4.21-57 files
#mv initrd-2.4.21-57* /tmp
#mv vmlinux-2.4.* /tmp
#mv vmlinuz-2.4* /tmp