Logo.jpg
Logo.jpg

Preparation:
Be­fore de­ploy­ing a host up­grade, en­sure that all vir­tual ma­chines in this host should be shut down and Back Up VMware ESXi Host Configuration.

There are two types of up­grade files

  • The .iso is bootable and follows instructions.
  • The .zip is upgraded via SSH using CLI commands.
In this sce­nario, I use Of­fline Bun­dle (.zip) to up­grade host.


Upgrade Path
Run­ning ESXi 6.7U(1-3) or ESXi 7.0U(1-3), you can up­grade di­rectly from these ver­sions to ESXi 8.0.
UpgradePath.png
UpgradePath.png

From: Product Interoperability Matrix (vmware.com)


Upgrade Procedure:
From ESXi 6.7 to ESXi 6.7U3
HypervisorBeforeAfter
ESXiVMware ESXi 6.7.06.7.0 Update 3

2022-12-28_150342.png
2022-12-28_150342.png

Up­load the up­grade file(ESXi670-201912001.zip) to a data­s­tore

The file lo­ca­tion: /vmfs/volumes/63abe767-b0668188-650d-005056b5b2ef/ESXi670-201912001.zip

2022-12-28_151805.png
2022-12-28_151805.png

En­able SSH Ser­vice

Put the node into main­te­nance mode

con­nect to the con­sole via SSH.
vim-cmd hostsvc/maintenance_mode_enter

2022-12-28_150716.png
2022-12-28_150716.png

View the im­age pro­files

Con­nect to the con­sole via SSH and run the fol­low­ing com­mand to check the im­age pro­file.
esxcli software sources profile list -d /vmfs/volumes/63abe767-b0668188-650d-005056b5b2ef/ESXi670-201912001.zip

2022-12-28_150608.png
2022-12-28_150608.png

2022-12-28_150100.png
2022-12-28_150100.png

Com­pared to the ex­ist­ing im­age pro­file ESXi-6.7.0-8169922-standard (VMware, Inc.), the up­grade pro­file name ESXi-6.7.0-20191204001-standard should be se­lected.

Run the up­grade and ap­pend the pro­file name (ESXi-6.7.0-20191204001-standard) at the end of the com­mand.

esxcli software profile update -d /vmfs/volumes/63abe767-b0668188-650d-005056b5b2ef/ESXi670-201912001.zip -p ESXi-6.7.0-20191204001-standard

2022-12-28_150910.png
2022-12-28_150910.png

When see­ing the mes­sage: The Update completed successfully

The up­grade is com­pleted and a reboot is re­quired for the changes to take ef­fect.

Fi­nally, exit main­te­nance mode in the node af­ter re­boot.

vim-cmd hostsvc/maintenance_mode_exit

2022-12-28_150748.png
2022-12-28_150748.png


From ESXi 6.7U3 to ESXi 7.0 U3
HypervisorBeforeAfter
ESXi6.7.0 Update 37.0 Update 3

2022-12-28_151817.png
2022-12-28_151817.png

Up­load the up­grade file(VMware-ESXi-7.0U3g-20328353-depot.zip) to a data­s­tore

The file lo­ca­tion: /vmfs/volumes/63abe767-b0668188-650d-005056b5b2ef/VMware-ESXi-7.0U3g-20328353-depot.zip

2022-12-28_151805.png
2022-12-28_151805.png

En­able SSH Ser­vice

Put the node into main­te­nance mode

con­nect to the con­sole via SSH.
vim-cmd hostsvc/maintenance_mode_enter

View the im­age pro­files

Con­nect to the con­sole via SSH and run the fol­low­ing com­mand to check the im­age pro­file.
esxcli software sources profile list -d /vmfs/volumes/63abe767-b0668188-650d-005056b5b2ef/VMware-ESXi-7.0U3g-20328353-depot.zip

2022-12-28_152115.png
2022-12-28_152115.png

2022-12-28_151948.png
2022-12-28_151948.png

Com­pared to the ex­ist­ing im­age pro­file (Updated) ESXi-6.7.0-20191204001-standard (VMware, Inc.), the up­grade pro­file name ESXi-7.0U3g-20328353-standard should be se­lected.

Run the up­grade and ap­pend the pro­file name (ESXi-7.0U3g-20328353-standard) at the end of the com­mand.

esxcli software profile update -d /vmfs/volumes/63abe767-b0668188-650d-005056b5b2ef/VMware-ESXi-7.0U3g-20328353-depot.zip -p ESXi-7.0U3g-20328353-standard

2022-12-28_152246.png
2022-12-28_152246.png

When see­ing the mes­sage: The Update completed successfully

The up­grade is com­pleted and a reboot is re­quired for the changes to take ef­fect.

Fi­nally, exit main­te­nance mode in the node af­ter re­boot.

vim-cmd hostsvc/maintenance_mode_exit

From ESXi 7.0 U3 to ESXi 8.0
HypervisorBeforeAfter
ESXi7.0 Update 38.0

2022-12-28_154037.png
2022-12-28_154037.png

Up­load the up­grade file(VMware-ESXi-8.0-20513097-depot.zip) to a data­s­tore

The file lo­ca­tion: /vmfs/volumes/63abe767-b0668188-650d-005056b5b2ef/VMware-ESXi-8.0-20513097-depot.zip

2022-12-28_151805.png
2022-12-28_151805.png

En­able SSH Ser­vice

Put the node into main­te­nance mode

con­nect to the con­sole via SSH.
vim-cmd hostsvc/maintenance_mode_enter

View the im­age pro­files

Con­nect to the con­sole via SSH and run the fol­low­ing com­mand to check the im­age pro­file.
esxcli software sources profile list -d /vmfs/volumes/63abe767-b0668188-650d-005056b5b2ef/VMware-ESXi-8.0-20513097-depot.zip

2022-12-28_155042.png
2022-12-28_155042.png

2022-12-28_154958.png
2022-12-28_154958.png

Com­pared to the ex­ist­ing im­age pro­file (Updated) ESXi-7.0U3g-20328353-standard (VMware, Inc.), the up­grade pro­file name ESXi-8.0.0-20513097-standard should be se­lected.


2022-12-30_152853.png
2022-12-30_152853.png

If the RAM ca­pac­ity not match the min­i­mum re­quires, the up­grade will be failed.

2022-12-28_155236.png
2022-12-28_155236.png

So, I Up­grade the RAM from 4 GB to 8 GB

2022-12-28_160738.png
2022-12-28_160738.png


Run the up­grade and ap­pend the pro­file name (ESXi-8.0.0-20513097-standard) at the end of the com­mand.

esxcli software profile update -d /vmfs/volumes/63abe767-b0668188-650d-005056b5b2ef/VMware-ESXi-8.0-20513097-depot.zip -p ESXi-8.0.0-20513097-standard

2022-12-28_161113.png
2022-12-28_161113.png

When see­ing the mes­sage: The Update completed successfully

The up­grade is com­pleted and a reboot is re­quired for the changes to take ef­fect.

Fi­nally, exit main­te­nance mode in the node af­ter re­boot.

vim-cmd hostsvc/maintenance_mode_exit

2022-12-28_161708.png
2022-12-28_161708.png


Conclusions:
Us­ing the com­mand line in­ter­face to Up­grade by ES­X­CLI. This method can be used for stand­alone ESXi hosts and ESXi hosts man­aged by vCen­ter.