I successfully updated another HPE host yesterday using the same method. Today, I'm trying another host. I tried the standard update command and the command using the profile and neither work. I'm already running vCenter 7 on the host as an appliance. I prefer to update via cli if possible. The host is running HPE Customized Image ESXi 6.7.0 Update 3 version 670.U3.10.5.0 released on December 2019 and based on VMware ESXi 6.7.0 Update 3.
:~] esxcli software vib update -d /vmfs/volumes/datastore1/patc
h/VMware_ESXi_7.0.0_15843807_HPE_700.0.0.10.5.0.108_April2020_depot.zip
[DependencyError]
VIB QLC_bootbank_qedi_2.10.19.0-1OEM.670.0.0.8169922 requires vmkapi_2_2_0_0, b ut the requirement cannot be satisfied within the ImageProfile.
VIB QLC_bootbank_qedi_2.10.19.0-1OEM.670.0.0.8169922 requires qedentv_ver = X.1 1.15.0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLC_bootbank_qedf_1.3.41.0-1OEM.600.0.0.2768847 requires qedentv_ver = X.11 .15.0, but the requirement cannot be satisfied within the ImageProfile.
VIB HPE_bootbank_scsi-hpdsa_5.5.0.68-1OEM.550.0.0.1331820 requires com.vmware.d riverAPI-9.2.2.0, but the requirement cannot be satisfied within the ImageProfil e.
VIB HPE_bootbank_scsi-hpdsa_5.5.0.68-1OEM.550.0.0.1331820 requires vmkapi_2_2_0 _0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLC_bootbank_qfle3f_1.0.75.0-1OEM.670.0.0.8169922 requires vmkapi_2_2_0_0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLC_bootbank_qedf_1.3.41.0-1OEM.600.0.0.2768847 requires vmkapi_2_3_0_0, bu t the requirement cannot be satisfied within the ImageProfile.
VIB QLC_bootbank_qedf_1.3.41.0-1OEM.600.0.0.2768847 requires vmkapi_2_2_0_0, bu t the requirement cannot be satisfied within the ImageProfile.
Please refer to the log file for more details.
[root@wellsesxi02:~] esxcli software sources profile list -d /vmfs/volumes/datastore1/patch/VMware_ESXi_7.
0.0_15843807_HPE_700.0.0.10.5.0.108_April2020_depot.zip
Name Vendor Acceptance Level Creation Time Mo dification Time
----------------------------------- -------------------------- ---------------- ------------------- -- -----------------
HPE-Custom-AddOn_700.0.0.10.5.0-108 Hewlett Packard Enterprise PartnerSupported 2020-03-26T19:47:53 20 20-03-26T19:47:53
[root@wellsesxi02:~] esxcli software profile update -d /vmfs/volumes/datastore1/patch/VMware_ESXi_7.0.0_15
843807_HPE_700.0.0.10.5.0.108_April2020_depot.zip -p HPE-Custom-Addon_700.0.0.10.5.0-108
[NoMatchError]
No image profile found with name 'HPE-Custom-Addon_700.0.0.10.5.0-108'
id = HPE-Custom-Addon_700.0.0.10.5.0-108
Please refer to the log file for more details.
[root@wellsesxi02:~] esxcli software profile update -d /vmfs/volumes/datastore1/patch/VMware_ESXi_7.0.0_15
843807_HPE_700.0.0.10.5.0.108_April2020_depot.zip -p HPE-Custom-AddOn_700.0.0.10.5.0-108
[DependencyError]
VIB QLC_bootbank_qedf_1.3.41.0-1OEM.600.0.0.2768847 requires vmkapi_2_2_0_0, but the requirement cannot b e satisfied within the ImageProfile.
VIB QLC_bootbank_qedf_1.3.41.0-1OEM.600.0.0.2768847 requires qedentv_ver = X.11.15.0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLC_bootbank_qedf_1.3.41.0-1OEM.600.0.0.2768847 requires vmkapi_2_3_0_0, but the requirement cannot b e satisfied within the ImageProfile.
VIB HPE_bootbank_scsi-hpdsa_5.5.0.68-1OEM.550.0.0.1331820 requires com.vmware.driverAPI-9.2.2.0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLC_bootbank_qedi_2.10.19.0-1OEM.670.0.0.8169922 requires qedentv_ver = X.11.15.0, but the requiremen t cannot be satisfied within the ImageProfile.
VIB QLC_bootbank_qfle3f_1.0.75.0-1OEM.670.0.0.8169922 requires vmkapi_2_2_0_0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLC_bootbank_qedi_2.10.19.0-1OEM.670.0.0.8169922 requires vmkapi_2_2_0_0, but the requirement cannot be satisfied within the ImageProfile.
VIB HPE_bootbank_scsi-hpdsa_5.5.0.68-1OEM.550.0.0.1331820 requires vmkapi_2_2_0_0, but the requirement ca nnot be satisfied within the ImageProfile.
Please refer to the log file for more details.
[root@wellsesxi02:~] esxcli software profile update -p HPE-Custom-AddOn_700.0.0.10.5.0-108 -d /vmfs/volume
s/datastore1/patch/VMware_ESXi_7.0.0_15843807_HPE_700.0.0.10.5.0.108_April2020_depot.zip
[DependencyError]
VIB QLC_bootbank_qedf_1.3.41.0-1OEM.600.0.0.2768847 requires qedentv_ver = X.11.15.0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLC_bootbank_qedi_2.10.19.0-1OEM.670.0.0.8169922 requires qedentv_ver = X.11.15.0, but the requiremen t cannot be satisfied within the ImageProfile.
VIB HPE_bootbank_scsi-hpdsa_5.5.0.68-1OEM.550.0.0.1331820 requires com.vmware.driverAPI-9.2.2.0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLC_bootbank_qedf_1.3.41.0-1OEM.600.0.0.2768847 requires vmkapi_2_2_0_0, but the requirement cannot b e satisfied within the ImageProfile.
VIB QLC_bootbank_qedf_1.3.41.0-1OEM.600.0.0.2768847 requires vmkapi_2_3_0_0, but the requirement cannot b e satisfied within the ImageProfile.
VIB HPE_bootbank_scsi-hpdsa_5.5.0.68-1OEM.550.0.0.1331820 requires vmkapi_2_2_0_0, but the requirement ca nnot be satisfied within the ImageProfile.
VIB QLC_bootbank_qfle3f_1.0.75.0-1OEM.670.0.0.8169922 requires vmkapi_2_2_0_0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLC_bootbank_qedi_2.10.19.0-1OEM.670.0.0.8169922 requires vmkapi_2_2_0_0, but the requirement cannot be satisfied within the ImageProfile.
Please refer to the log file for more details.
[root@wellsesxi02:~] [root@wellsesxi02:~] esxcli software profile update -p HPE-Custom-AddOn_700.0.0.10.5.
0-108 -d /vmfs/volume
-sh: [root@wellsesxi02:~]: not found
[root@wellsesxi02:~] s/datastore1/patch/VMware_ESXi_7.0.0_15843807_HPE_700.0.0.10.5.0.108_April2020_depot.
zip
-sh: s/datastore1/patch/VMware_ESXi_7.0.0_15843807_HPE_700.0.0.10.5.0.108_April2020_depot.zip: not found
[root@wellsesxi02:~] [DependencyError]
-sh: [DependencyError]: not found
[root@wellsesxi02:~] VIB QLC_bootbank_qedf_1.3.41.0-1OEM.600.0.0.2768847 requires qedentv_ver = X.11.15.0
, but the requirement cannot be satisfied within the ImageProfile.
-sh: VIB: not found
[root@wellsesxi02:~] VIB QLC_bootbank_qedi_2.10.19.0-1OEM.670.0.0.8169922 requires qedentv_ver = X.11.15.
0, but the requirement cannot be satisfied within the ImageProfile.
-sh: VIB: not found
[root@wellsesxi02:~] VIB HPE_bootbank_scsi-hpdsa_5.5.0.68-1OEM.550.0.0.1331820 requires com.vmware.driver
API-9.2.2.0, but the requirement cannot be satisfied within the ImageProfile.
-sh: VIB: not found
[root@wellsesxi02:~] VIB QLC_bootbank_qedf_1.3.41.0-1OEM.600.0.0.2768847 requires vmkapi_2_2_0_0, but the
requirement cannot be satisfied within the ImageProfile.
-sh: VIB: not found
[root@wellsesxi02:~] VIB QLC_bootbank_qedf_1.3.41.0-1OEM.600.0.0.2768847 requires vmkapi_2_3_0_0, but the
requirement cannot be satisfied within the ImageProfile.
-sh: VIB: not found
[root@wellsesxi02:~] VIB HPE_bootbank_scsi-hpdsa_5.5.0.68-1OEM.550.0.0.1331820 requires vmkapi_2_2_0_0, b
ut the requirement cannot be satisfied within the ImageProfile.
-sh: VIB: not found
[root@wellsesxi02:~] VIB QLC_bootbank_qfle3f_1.0.75.0-1OEM.670.0.0.8169922 requires vmkapi_2_2_0_0, but t
he requirement cannot be satisfied within the ImageProfile.
-sh: VIB: not found
[root@wellsesxi02:~] VIB QLC_bootbank_qedi_2.10.19.0-1OEM.670.0.0.8169922 requires vmkapi_2_2_0_0, but th
e requirement cannot be satisfied within the ImageProfile.^C
[root@wellsesxi02:~]
There are more drivers listet. Most likely also all 5.0.0 drivers needs to be removed
esxcli software vib list | grep 500
Tip you can use multiple -n Drivername like
esxcli software vib remove -n Drivername -n Drivername -n Drivername
Regards,
Joerg
you need to remove following drivers
esxcli software vib remove -n qfle3f
esxcli software vib remove -n scsi-qedil
esxcli software vib remove -n qedf
It may need to remove more drive
There are more drivers listet. Most likely also all 5.0.0 drivers needs to be removed
esxcli software vib list | grep 500
Tip you can use multiple -n Drivername like
esxcli software vib remove -n Drivername -n Drivername -n Drivername
Regards,
Joerg
A command that "usually" works if no additional components are installed is:
esxcli software profile install -d /vmfs/volumes/vcsa/ISO/VMware_ESXi_7.0.0_15843807_HPE_700.0.0.10.5.0.108_April2020_depot.zip -p HPE-Custom-AddOn_700.0.0.10.5.0-108 --ok-to-remove --dry-run
Note: "--dry-run" is used to test the command without changing anything
However, I remember that I read somewhere that HPE's Offline Bundle is not supported for an upgrade from the command line! Unfortunately, I can't find this right now because HPE's documentation site seem to be unavailable at the moment (Server error 500).
As a side note: For upgrades (rather than patches) it's always the "esxcli software profile ..." command has to be used.
André
Question about upgrades. Is a upgrade a major release change like 6.x -> 7.x or also 6.7u1 -> 6.7u3?
Regards,
Joerg
This is where things may become complicated 😉
VMware's official wording is from e.g. Differences Between vSphere Upgrades, Patches, Updates, and Migrations is:
VMware product versions are numbered with two digits, for example, vSphere 7.0. A release that changes either digit, for example, from 6.5 to 6.7, or from 6.7 to 7.0, involves major changes in the software, and requires an upgrade from the previous version. A release that makes a smaller change, requiring only a patch or update, is indicated by an update number, for example, vSphere 6.7 Update 1
Even with that in mind, I usually use the "esxcli software profile [update|install] ... " command, independent of whether it's considered an update or upgrade, because this will make sure that the host is in a defined state after applying the new bits. The "esxcli software vib ..." command is something that I only use to install individual drivers, or tools.
In some situations - especially when using the offline bundle - the different commands may produce the same result, so that it's up to the user's preference what to use. However, from my past experience, I recommend the "profile" option.
André
Thx for the explanation.
Regards,
Joerg
A quick follow up.
Please read the following KB and the information in the provided links carefully, before you decide to upgrade to the HPE customized ESXi 7.0 image: https://kb.vmware.com/s/article/78487
André
I removed the dependencies and then used the vib update command. Everything worked just fine. The packages that caused issues were from the original 6.7 install. Thank you all for your help.