update vsphere 6.0 (custom hp image) to 6.0u3

[clamaz]

Hi users,

I should update a vsphere HP proliant 460 blade host, 6.0 installed with hp custom image: Build 6765062.

The latest hp custom image I found on vmware website is ESXi 6.0 Update 3, HPE Custom Image for VMware ESXi 6.0 U3 Install CD.

VMware-ESXi-6.0.0-Update3-13635687-HPE-Gen9plus-600.10.4.5.15-Sep2019.iso    Release Date: 2019-09-09

on the same page I found also offline bundle

VMware-ESXi-6.0.0-Update3-13635687-HPE-Gen9plus-600.10.4.5.15-Sep2019-depot.zip  Release Date: 2019-09-09

Question before update:

Is it correct that I can proceed in two ways?:

1) shut down all VMs, Enter in mantenace mode, restart host with boot 6.0U3 boot CD and follow istruction.

or

2) shut down all VMs, Enter in mantenace mode, copy VMware-ESXi-6.0.0-Update3-13635687-HPE-Gen9plus-600.10.4.5.15-Sep2019-depot.zip on a folder in datastore, and then launch command:  esxcli software vib install -d /vmfs/volumes/MyDatastoreID/patchrepository/VMware-ESXi-6.0.0-Update3-13635687-HPE-Gen9plus-600.10.4.5.15-Sep2019-depot.zip

I would point to second way because on proliant blade I should attach a virtual image or burn a CD.

Is it correct?

ps: Then, could I apply the latest VMware patch ESXi600-202002001 build  15517548  released on february 2020, even if hypervisor is HP customized?

Or do I have to waith an hp patch?

Thank you

[berndweyand · Accepted solution]

first of all: do not use "esxcli software vib install -d" because then it can happen to overwrite custom drivers.

use "esxcli software vib update -d"

and yes - you can update via esxcli or booting the customized iso and choose upgrade.

and yes - you can install the latest patches from vmware afterwards

[clamaz]

thank you Bewe,

so the right command is:

esxcli software vib update -d /vmfs/volumes/MyDatastoreID/patchrepository/VMware-ESXi-6.0.0-Update3-13635687-HPE-Gen9plus-600.10.4.5.15-Sep2019-depot.zip

instead, If I want to reset or reinstall all original hp drivers, I use:

esxcli software vib install -d /vmfs/volumes/MyDatastoreID/patchrepository/VMware-ESXi-6.0.0-Update3-13635687-HPE-Gen9plus-600.10.4.5.15-Sep2019-depot.zip

ps: note that file  VMware-ESXi-6.0.0-Update3-13635687-HPE-Gen9plus-600.10.4.5.15-Sep2019-depot.zip   is hp branded too.

It shoud contain official update hp drivers

thank you

[clamaz]

...just one other thing Bewe

for patching, is command  the same (update)?

esxcli software vib update -d /vmfs/volumes/MyDatastoreID/patchrepository/ESXi600-202002001.zip

thank you

[berndweyand]

yes here is "update" important

because esxi is installed you can always use update and forget install.

except for third party vibs which are not installed yet

[clamaz]

before to update in production, I try on a whitebox (6.0 with injected realtek nic driver, because it is a home pc).

if i use Update I obtain:

[root@localhost:~] esxcli software vib update -d /vmfs/volumes/5e85fa48-4fbba9ab-146c-ac9e178194ab/patch/ESXi600-201706001.zip

[DependencyError]

VIB VMware_bootbank_esx-base_6.0.0-3.69.5572656 requires vsan << 6.0.0-3.70, but the requirement cannot be satisfied within the ImageProfile.

VIB VMware_bootbank_esx-base_6.0.0-3.69.5572656 requires vsan >= 6.0.0-3.69, but the requirement cannot be satisfied within the ImageProfile.

Please refer to the log file for more details.

if I use install it finish update correctly and ask me to reboot:

[root@localhost:~] esxcli software vib install -d /vmfs/volumes/5e85fa48-4fbba9ab-146c-ac9e178194ab/patch/ESXi600-201706001.zip

Installation Result

   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.

   Reboot Required: true

Could it be because the first base vsphere 6 installaion is customized with injected realtek nic driver?

Shoud it happens also with producrion hp server (6.0 hp customized image)?

[clamaz]

then I tried UPDATE option, with a recent patch  ESXi600-202002001.zip

[root@localhost:~] esxcli software vib update -d /vmfs/volumes/5e85fa48-4fbba9ab-146c-ac9e178194ab/patch/ESXi600-202002001.zip

Installation Result

   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.

   Reboot Required: true

In this case, UPDATE switch, instead of INSTALL, worked fine….

[berndweyand]

sometimes this is happening when the time span between base install and patch ist very long. but update is the recommended procedure: VMware Knowledge Base

but why are you installing a 3 years old patch ? is your hardware not compatible with newer builds ? and check if your hardware supports 6.5/6.7

btw: do you have no vcenter with update manager ?

[clamaz]

Hi Bewe,

VMware-ESXi-6.0.0-Update3-13635687-HPE-Gen9plus-600.10.4.5.15-Sep2019-depot.zip   Release Date: 2019-09-09 is the latest available hp branded, no more recent. (6 months old)

Then as you suggested, I could apply latest VMware original (no hp branded) patch ESXi600-202002001.zip.

No 6.5 or 6.7 so far, because I shoud upgrade Vcenter first.

[berndweyand]

ok - but if you have vcenter why do you not use updatemanager ? include the depot from hpe and patch through vum

[clamaz]

Ok Bewe, thank you for suggestion, I will think about..

And more, thank you very much for your precise answers

Take care and StayHome! (as we use to do and to say here in Italy now)