{"id":2957,"date":"2015-10-29T10:10:00","date_gmt":"2015-10-29T10:10:00","guid":{"rendered":"https:\/\/wiki.melberi.com\/uncategorized\/upgrade-vsphere-4-to-4-1-using-vcenter-update-manager"},"modified":"2017-10-24T10:01:38","modified_gmt":"2017-10-24T10:01:38","slug":"upgrade-vsphere-4","status":"publish","type":"post","link":"https:\/\/www.melberi.com\/wiki\/vmware\/upgrade-vsphere-4","title":{"rendered":"Upgrade Vsphere 4 to 4.1 using vCenter Update Manager"},"content":{"rendered":"
\n

Step by step procedure to Upgrade Vsphere 4 to 4.1 using vCenter Update Manager<\/span><\/b><\/u><\/h2>\n

Prerequisites:<\/b><\/span><\/u><\/h3>\n

The following space requirements for partitions must be met.
\nThe \/root partition must have at least 1.8GB.
\nThe \/boot partition must have at least 24MB of free space.<\/span>
\nTo upgrade ESX 4.0 to 4.1<\/span>
\nDownload<\/b> – upgrade-from-ESX4.0-to-4.1.0-0.0.260247-release.zip\u00a0<\/span>
\n(note: Pre upgrade pack not required if you are using update manager)<\/span><\/b>
\nStep 1<\/b><\/span>
\n <\/b><\/p>\n

Import Upgrade Release:<\/u><\/h3>\n

Login to Vsphere Client -> go to Update Manager -> Host Upgrade Releases\u00a0<\/b><\/span> <\/b>
\nClick on <\/span>Import Upgrade Release<\/b> and follow the below steps<\/span><\/p>\n

<\/a><\/div>\n

Browse and Point the downloaded <\/span>upgrade-from-ESX4.0-to-4.1.0-0.0.260247-release.zip file<\/span><\/p>\n

<\/a><\/div>\n
<\/a><\/div>\n
<\/a><\/div>\n
<\/a><\/div>\n

Step 2 : <\/b>Create Baseline<\/b>:<\/u><\/h3>\n

In Update Manager -> Host Upgrade Releases <\/b><\/span>click on Create Baseline <\/b>and follow the below steps<\/span><\/p>\n

<\/a><\/div>\n
<\/a><\/div>\n
<\/a><\/div>\n
<\/a><\/div>\n
<\/a><\/div>\n

Baseline created Successfully<\/span><\/p>\n

Step 3<\/b><\/span>: <\/span>vSphere 4 up-gradation<\/span>:\u00a0<\/b><\/span><\/u><\/h3>\n

Attach the created baseline at Cluster level or Data center level and scan for updates<\/span><\/p>\n

<\/a><\/div>\n


\n<\/span>
\n
\n<\/b><\/span>
\n
\n<\/b><\/span>
\n
\n<\/b><\/span>
\n
\n<\/b><\/span>
\n
\n<\/b><\/span>
\n
\n<\/b><\/span><\/p>\n

Now right click the data center or individual hosts and click on remediate.\u00a0<\/span>
\nand follow the below steps.
\n<\/b><\/span><\/p>\n

<\/a><\/div>\n
<\/a><\/div>\n
<\/a><\/div>\n
<\/a><\/div>\n


\n<\/b><\/span>
\n
\n<\/b><\/span>
\n
\n<\/b><\/span>
\n
\n<\/b><\/span>
\n
\n<\/b><\/span><\/p>\n\n\n\n\n
<\/a><\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n


\n<\/b><\/span>
\n
\n<\/b><\/span>
\n
\n<\/b><\/span>
\n
\n<\/b><\/span>
\n
\n<\/b><\/span>
\n
\n<\/b><\/span><\/p>\n


\n<\/span>This will move all the vm to other host and goes to standby mode and apply the patches.<\/span><\/p>\n

Or you can put the Host in to stand-by mode and apply the upgrade<\/span><\/p>\n

Upgradation will take 15 to 30 min to complete. After the reboot, host will show the new version number 4.1.0, 260247\u00a0 <\/b><\/span><\/p>\n

<\/a><\/div>\n

Errors<\/b>:<\/span><\/u><\/h4>\n

Remediation did not succeed for SingleHostRemediate: esxupdate error, version: 1 .30, operation:\u00a0 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
\n<\/b><\/span>
\nSolution:<\/b><\/span>
\nRemove the conflicting package and retry <\/span>
\n#rpm -e sblim-sfcb-1.3.2Dell-9.1.el4<\/b><\/span><\/p>\n

If low space available on \/boot<\/b><\/span><\/h4>\n

df -h
\nuname -a<\/span><\/i>
\nEdit grub.conf and remove the old boot menu files
\n#vi \/boot\/grub\/grub.conf<\/span><\/i>
\nmove the old initrd-2.4.21-57 files<\/span><\/i>
\n#mv initrd-2.4.21-57* \/tmp<\/span><\/i>
\n#mv vmlinux-2.4.* \/tmp<\/span><\/i>
\n#mv vmlinuz-2.4* \/tmp<\/span><\/i><\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

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… Read more »<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1037],"tags":[1628],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.melberi.com\/wiki\/wp-json\/wp\/v2\/posts\/2957"}],"collection":[{"href":"https:\/\/www.melberi.com\/wiki\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.melberi.com\/wiki\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.melberi.com\/wiki\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.melberi.com\/wiki\/wp-json\/wp\/v2\/comments?post=2957"}],"version-history":[{"count":3,"href":"https:\/\/www.melberi.com\/wiki\/wp-json\/wp\/v2\/posts\/2957\/revisions"}],"predecessor-version":[{"id":4162,"href":"https:\/\/www.melberi.com\/wiki\/wp-json\/wp\/v2\/posts\/2957\/revisions\/4162"}],"wp:attachment":[{"href":"https:\/\/www.melberi.com\/wiki\/wp-json\/wp\/v2\/media?parent=2957"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.melberi.com\/wiki\/wp-json\/wp\/v2\/categories?post=2957"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.melberi.com\/wiki\/wp-json\/wp\/v2\/tags?post=2957"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}