Upgrade vc from 4.0 to 4.01 issue #2
时间:2010-05-14 来源:hiyangyong
[What’s the issue?]
Issue1: Attach baseline in update manager for ESX4 Update 1 upgrade, after scan, it shows “incompatible” and cannot remediate
Issue2: After get CMD update solution, ESX servers vmse1esx167 and vmse1esx168 have been updated successfully, but vmse1esx166 cannot be updated due to a foreign package.
[What’s the root cause?]
Issue1: ESX4 -> ESX4 Update1 is not a upgrade, so we cannot use update manager or host upgrade utility to upgrade it. Actually we need to consider it as a patch update.
Issue2: ESX vmse1esx166 has installed a custom package “cross_cisco-vem-v110-esx_4.0.4.1.2.0.80-0.4.179” for Cisco Nexus 1000v, and this results update fail.
[What’s the solution?]
Issue1:
Download zip package for command line update
ESX4 Update1: https://hostupdate.vmware.com/software/VUM/OFFLINE/release-166-20091202-254879/ESX-4.0.0-update01a.zip
ESX4i Update1: https://hostupdate.vmware.com/software/VUM/OFFLINE/release-162-20091127-830520/ESXi-4.0.0-update01.zip
Upload the package to a web server and extract it in www directory
E.g. http://10.100.22.211/esx4/metadata.zip or http://10.100.22.211/esx4i/metadata.zip
Put target ESX server to “Maintenance mode”
Execute following command in target ESX4 server:
ESX4:
#esxupdate -m http://10.100.22.211/esx4/metadata.zip scan
#esxupdate -m http://10.100.22.211/esx4/metadata.zip update
ESX4i:
#esxupdate -m http://10.100.22.211/esx4i/metadata.zip scan
#esxupdate -m http://10.100.22.211/esx4i/metadata.zip update
After done, we need to reboot the ESX server to activate the new version.