User Tools

Site Tools


os:esxi:update

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
os:esxi:update [2016-03-16 20:39] – HP update infos added rootos:esxi:update [2019-04-19 17:33] (current) root
Line 39: Line 39:
  
 <code> <code>
-~ # esxcli software sources profile list -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml | grep ESXi-6+~ # esxcli software sources profile list -d https://hostupdate.VMware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml | grep ESXi-6
 ESXi-6.0.0-20150404001-standard   VMware, Inc.  PartnerSupported ESXi-6.0.0-20150404001-standard   VMware, Inc.  PartnerSupported
 ESXi-6.0.0-20150704001-standard   VMware, Inc.  PartnerSupported ESXi-6.0.0-20150704001-standard   VMware, Inc.  PartnerSupported
Line 121: Line 121:
  
 <code> <code>
-~ # esxcli software profile update -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml -p ESXi-6.0.0-20150704001-standard+~ # esxcli software profile update -d https://hostupdate.VMware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml -p ESXi-6.0.0-20150704001-standard
  
 Update Result Update Result
Line 138: Line 138:
  
 <code> <code>
-~ # esxcli software vib update -d https://vibsdepot.hpe.com/hpe/index.xml+~ # esxcli software vib update -d https://vibsdepot.hpe.com/hpe/hpe-index.xml
  [MetadataDownloadError]  [MetadataDownloadError]
- Could not download from depot at https://vibsdepot.hpe.com/hpe/index.xml, skipping (('https://vibsdepot.hpe.com/hpe/index.xml', '', '[Errno 14] HTTP Error 404: Not Found')) + Could not download from depot at https://vibsdepot.hpe.com/hpe/hpe-index.xml, skipping (('https://vibsdepot.hpe.com/hpe/hpe-index.xml', '', '[Errno 14] HTTP Error 404: Not Found')) 
-        url = https://vibsdepot.hpe.com/hpe/index.xml+        url = https://vibsdepot.hpe.com/hpe/hpe-index.xml
  Please refer to the log file for more details.  Please refer to the log file for more details.
 </code> </code>
Line 149: Line 149:
 Another way to upgrade is to download the depot and do an offline installation. Another way to upgrade is to download the depot and do an offline installation.
  
-Download the depot ZIP file on [[https://my.vmware.com/]]. You will find it in the section "Custom ISOs". It's name will be similar to "VMware-ESXi-6.0.0-Update2-3620759-HPE-600.U2.9.4.7.13-Mar2016-depot.zip". Now you have to extract the ZIP file on a datastore which is accessible by your ESX (myDataStore).+Download the depot ZIP file on [[https://my.VMware.com/]]. You will find it in the section "Custom ISOs". It's name will be similar to "VMware-ESXi-6.0.0-Update2-3620759-HPE-600.U2.9.4.7.13-Mar2016-depot.zip". Now you have to extract the ZIP file on a datastore which is accessible by your ESX (myDataStore).
  
 Update the HP VIB's with the local depot. Update the HP VIB's with the local depot.
Line 198: Line 198:
  
 VMware offers supported, powerful system administration tools.  Please VMware offers supported, powerful system administration tools.  Please
-see www.vmware.com/go/sysadmintools for details.+see www.VMware.com/go/sysadmintools for details.
  
 The ESXi Shell can be disabled by an administrative user. See the The ESXi Shell can be disabled by an administrative user. See the
Line 220: Line 220:
 ===== Credits ===== ===== Credits =====
  
-  * Thanks to William Lam for his uncountable and wonderful blog post about VMware and ESXi including the one I got the upgrade information from [[http://www.virtuallyghetto.com/2012/09/a-pretty-cool-method-of-upgrading-to.html|A Pretty Cool Method of Upgrading to ESXi 5.1]]. +  * William Lam [[http://www.virtuallyghetto.com/2012/09/a-pretty-cool-method-of-upgrading-to.html|A Pretty Cool Method of Upgrading to ESXi 5.1]]. 
-  * Thanks to Andreas Peetz for maintaining the [[https://esxi-patches.v-front.de/|VMware ESXi Patch Tracker]].+  * Andreas Peetz [[https://esxi-patches.v-front.de/|VMware ESXi Patch Tracker]]. 
 + 
 + 
 +====== Update ESXi 6.0 HPE Custom Image to 6.5  ====== 
 + 
 +===== Prerequisites ===== 
 + 
 +  * ESXi 6.0 installed 
 +  * HPE Custom ESXi 6.5 Image downloaded and extracted to /vmfs/volumes/myDatastore/Sources/ 
 +  * Host is in Maintenance Mode 
 +  
 +===== Update Process ===== 
 + 
 +==== Get Image Profile ==== 
 + 
 +Get the name of the image profile in the downloaded depot (in this example: HPE-ESXi-6.5.0-OS-Release-650.9.6.0.28). 
 + 
 +<code> 
 +~ # esxcli software sources profile list --depot=file:///vmfs/volumes/myDatastore/Sources/VMware-ESXi-6.5.0-OS-Release-4564106-HPE-650.9.6.0.28-Nov2016-depot/index.xml 
 +Name                                    Vendor                      Acceptance Level 
 +--------------------------------------  --------------------------  ---------------- 
 +HPE-ESXi-6.5.0-OS-Release-650.9.6.0.28  Hewlett Packard Enterprise  PartnerSupported 
 +</code> 
 + 
 +==== Start Update ==== 
 + 
 +Execute the update command and replace the string after **-p** with the image profile name. 
 + 
 +<code> 
 +~ # esxcli software profile update --depot=file:///vmfs/volumes/myDatastore/Sources/VMware-ESXi-6.5.0-OS-Release-4564106-HPE-650.9.6.0.28-Nov2016-depot/index.xml -p HPE-ESXi-6.5.0-OS-Release-650.9.6.0.28 
 +Update Result 
 +   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective. 
 +   Reboot Required: true 
 +   VIBs Installed: ELX_bootbank_elx-esx-libelxima.so_11.1.216.0-03, EMU_bootbank_elxiscsi_11.1.216.0-1OEM.650.0.0.4240417, .... 
 +   VIBs Removed: EMU_bootbank_elxnet_11.1.145.0-1OEM.600.0.0.2768847, EMU_bootbank_lpfc_11.1.145.18-1OEM.600.0.0.2768847, EMU_bootbank_scsi-be2iscsi_11.1.145.8-1OEM.600.0.0.2494585, ... 
 +   VIBs Skipped: Avago_bootbank_scsi-mpt2sas_15.10.06.00-1OEM.550.0.0.1331820, HPE_bootbank_conrep_6.0.0.01-02.00.1.2494585, HPE_bootbank_hpbootcfg_6.0.0.02-02.00.6.2494585, ... 
 +</code> 
 + 
 +==== Reboot the Host ==== 
 + 
 +<code> 
 +~ # reboot 
 +</code> 
 + 
 +====== Update HPE Tools & Drivers - May 2017 ====== 
 + 
 +<code> 
 +~ # esxcli software vib update -d http://vibsdepot.hpe.com/hpe/may2017/index.xml 
 +Installation Result 
 +   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective. 
 +   Reboot Required: true 
 +   VIBs Installed: HPE_bootbank_hpe-ilo_650.10.0.2-2.4240417 
 +   VIBs Removed: HPE_bootbank_hpe-ilo_650.10.0.1-24.4240417 
 +   VIBs Skipped: HPE_bootbank_amshelper_650.10.6.0-24.4240417, HPE_bootbank_conrep_6.0.0.01-02.00.1.2494585, HPE_bootbank_hpbootcfg_6.0.0.02-02.00.6.2494585, HPE_bootbank_hpe-cru_650.6.5.8.24-1.4240417, HPE_bootbank_hpe-esxi-fc-enablement_650.2.6.10-4240417, HPE_bootbank_hpe-nmi_600.2.4.16-2494575, HPE_bootbank_hpe-smx-provider_650.03.11.00.17-4240417, HPE_bootbank_hponcfg_6.0.0.4.4-2.4.2494585, HPE_bootbank_hptestevent_6.0.0.01-01.00.5.2494585, HPE_bootbank_ssacli_2.60.18.0-6.0.0.2494585 
 +</code> 
 + 
 +====== Update to ESXi 6.5.0 U1 and HPE Drivers - InstallationError: No space left on device ====== 
 + 
 +The installation of version 6.5.0 update 1 stopped with the error "No space left on device". I found some information to resolve this problem. [[https://www.reddit.com/r/vmware/comments/6q4akd/error_trying_to_update_an_esxi_65_host_to_the/dkugskj/|reddit: Error trying to update an ESXi 6.5 Host to the brandnew release]] 
 + 
 +<code> 
 +[root@mfr-vx00:~] esxcli software profile update -d https://hostupdate.VMware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml -p ESXi-6.5.0-20170702001-standard 
 + [InstallationError] 
 + [Errno 28] No space left on device 
 +       vibs = VMware_locker_tools-light_6.5.0-0.23.5969300 
 + Please refer to the log file for more details. 
 +</code> 
 + 
 +Download the VMware-Tools VIB file and copy it to a datastore which can be accessed by the esx host. 
 +<code> 
 +[root@my-client:~] cd /mnt/NASDatastore 
 +[root@my-client:/mnt/NASDatastore] wget "https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vib20/tools-light/VMware_locker_tools-light_6.5.0-0.23.5969300.vib" 
 +</code> 
 + 
 +Install the downloaded VIB file. 
 +<code> 
 +[root@my-host:~] esxcli software vib install -v /vmfs/volumes/NASDatastore/VMware_locker_tools-light_6.5.0-0.23.5969300.vib 
 +Installation Result 
 +   Message: Operation finished successfully. 
 +   Reboot Required: false 
 +   VIBs Installed: VMware_locker_tools-light_6.5.0-0.23.5969300 
 +   VIBs Removed: 
 +   VIBs Skipped: 
 +</code> 
 + 
 +Retry the installation. It should work now. 
 +<code> 
 +[root@my-host:~] esxcli software profile update -d https://hostupdate.VMware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml -p ESXi-6.5.0-20170702001-standard 
 +Update Result 
 +   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective. 
 +   Reboot Required: true 
 +   VIBs Installed: VMW_bootbank_i40en_1.3.1-5vmw.650.1.26.5969303, VMW_bootbank_igbn_0.1.0.0-14vmw.650.1.26.5969303, VMW_bootbank_ixgben_1.4.1-2vmw.650.1.26.5969303, ... 
 +   VIBs Removed: QLogic_bootbank_qlnativefc_2.1.50.0-1OEM.600.0.0.2768847, VMW_bootbank_i40en_1.1.0-1vmw.650.0.0.4564106, VMW_bootbank_igbn_0.1.0.0-12vmw.650.0.0.4564106, ... 
 +   VIBs Skipped: VMW_bootbank_ata-libata-92_3.00.9.2-16vmw.650.0.0.4564106, VMW_bootbank_ata-pata-amd_0.3.10-3vmw.650.0.0.4564106, ... 
 +</code> 
 + 
 +Update the HPE tools and drivers. 
 +<code> 
 +[root@my-host:~] esxcli software vib update -d http://vibsdepot.hpe.com/hpe/jul2017/index.xml 
 +Installation Result 
 +   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective. 
 +   Reboot Required: true 
 +   VIBs Installed: HPE_bootbank_amsd_650.11.1.0-24.4240417, HPE_bootbank_bootcfg_6.0.0.02-03.00.5.2494585, HPE_bootbank_conrep_6.0.0.02-00.00.12.2494585, ... 
 +   VIBs Removed: HPE_bootbank_amshelper_650.10.6.0-24.4240417, HPE_bootbank_conrep_6.0.0.01-02.00.1.2494585, HPE_bootbank_hpbootcfg_6.0.0.02-02.00.6.2494585, ... 
 +   VIBs Skipped: 
 +</code> 
 + 
 +Reboot the host. 
 +<code> 
 +[root@my-host:~] reboot 
 +</code> 
 + 
 +====== Update form ESXi 6.7U1 to 6.7U2 with the offline bundle ====== 
 + 
 +The offline bundle was downloaded and extracted to myDatastore/Sources/update-from-esxi6.7-6.7_update02/ on a NAS which is attached to the ESXi host. 
 + 
 +<code> 
 +[root@my-host:~] esxcli software vib update -d /vmfs/volumes/myDatastore/Sources/update-from-esxi6.7-6.7_update02/ 
 +</code>
  
os/esxi/update.1458157176.txt.gz · Last modified: 2016-03-16 20:39 by root