Hi, I need to upgrade the version of ESXi to v7 (from 6.7.0 U2) on our HP ProLiant DL380 Gen9 server.
I have patched the server's firmware so it can support v7, but on running the upgrade command I get the following errors :0
VIB QLogic_bootbank_scsi-bfa_3.2.5.0-1OEM.550.0.0.1331820 requires vmkapi_2_2_0_0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLogic_bootbank_scsi-bfa_3.2.5.0-1OEM.550.0.0.1331820 requires com.vmware.driverAPI-9.2.2.0, but the requirement cannot be satisfied within the ImageProfile.
I'm using a custom ESXI package as follows :-
VMware-ESXi-7.0.0-16324942-HPE-700.0.0.10.5.5.32-Jun2020-depot.zip
I'm a bit nervous about removing those VIBs without knowing what thet are for, can anyone advise if these are safe to remove ? Thanks.
@ ofnl
Thank you for posting on VMware Communities.
Please use the latest version of HPE Custom ESXi .zip file provided & recommended by the hardware vendor.
Migrate or power off the virtual machines running on the host and put the host into maintenance mode. The host can be put into maintenance mode by running this command:
#vim-cmd hostsvc/maintenance_mode_enter
Put the host in maintenance mode and take backup of the host configuration using:
#vim-cmd hostsvc/firmware/sync_config
#vim-cmd hostsvc/firmware/backup_config
hostname -i to get the IP address of the hostname
hostname -f to get the FQDN for the ESXi host
Note: The command should output a URL in which a web browser may be used to download the file.
For example : Bundle can be downloaded at : http://*/downloads/123456/configBundle-xx.xx.xx.xx.tgz where * denotes the host IP/FQDN.
The backup file is also located in the /scratch/downloads directory as configBundle-HostFQDN.tgz
Browse to that datastore location using the following command:
#cd /vmfs/volumes/datastore_name/folder_name/file.zip
Run this command to list the profiles:
#esxcli software sources profile list -d <absolute path of the .zip file>
Example: esxcli software sources profile list -d /vmfs/volumes/datastore_name/folder_name/file.zip
Output:
Name Vendor Acceptance Level
-------------------------------- ------------ ----------------
ESXi-6.0.0-20171101001s-standard VMware, Inc. PartnerSupported
ESXi-6.0.0-20171101001s-no-tools VMware, Inc. PartnerSupported
ESXi-6.0.0-20171104001-no-tools VMware, Inc. PartnerSupported
ESXi-6.0.0-20171104001-standard VMware, Inc. PartnerSupported
Choose one of the profile from point 5 that says -standard and run this command against it:
#esxcli software profile update -d <absolute path of the .zip file> -p <output from 5>
If it complains about the comflicting VIBs please perform the below:
-------------------------------------------------------------------
List the VIBs used for storage and network respectively through the following commands:
#esxcfg-scsidevs -a
#esxcfg-nics -l
If the above two commands do not show the conflicting VIB names then you can safely remove them
List the conflicting VIB name:
#esxcli software vib list | grep -i <Conflicting VIB NAME>
Remove the conflicting VIB one by one using the below command:
#esxcli software vib remove --vibname=Conflicting VIB Name
#reboot -f
Only after the reboot the conflicting VIBS will be removed
-------------------------------------------------------------------
SSH again to the same host after enabling SSH.
Browse to that datastore location using the following command:
#cd /vmfs/volumes/datastore_name/folder_name/file.zip
Run this command to list the profiles:
#esxcli software sources profile list -d <absolute path of the .zip file>
Example: esxcli software sources profile list -d /vmfs/volumes/datastore_name/folder_name/file.zip
Output:
Name Vendor Acceptance Level
-------------------------------- ------------ ----------------
ESXi-6.0.0-20171101001s-standard VMware, Inc. PartnerSupported
ESXi-6.0.0-20171101001s-no-tools VMware, Inc. PartnerSupported
ESXi-6.0.0-20171104001-no-tools VMware, Inc. PartnerSupported
ESXi-6.0.0-20171104001-standard VMware, Inc. PartnerSupported
Choose one of the profile from point 5 that says -standard and run this command against it:
#esxcli software profile update -d <absolute path of the .zip file> -p <output from 5>
For example:
#esxcli software profile update -d /vmfs/volumes/abcderskfjfggjgjgg5h33n444/ESXi600-201711001.zip -p ESXi-6.0.0-20171104001-standard
It will say that the upgrade completed successfully.
Run this command to reboot the host:
reboot -f
------------------------------------------------------------------------------------------------------------------
Arun Kumar
Install Upgrade Specialist
"Did you find this helpful? Let us know by completing this survey (takes 1 minute!)"
Hi,
try to download and install this ISO version "VMware_ESXi_7.0.0_16324942_HPE_700.0.0.10.5.5.46_Jun2020.iso":
https://my.vmware.com/web/vmware/downloads/details?downloadGroup=OEM-ESXI70-HPE&productId=974
ARomeo
Hi, that link takes me to the same download page that I got the zip file from. Not sure how to install from ISO.
Can you please provide the command line that you are using for the upgrade?
Do you have any additional drivers installed, which did not come with the HPE customized ESXi image?
André
Have you checked the (multiple) options provided in VMware Knowledge Base
Hi,
I had shown how to manually update via the .iSO file starting from USB.
I did the post in Italian, but you can follow the images:
Come fare l’upgrade da ESXi 6.7 a ESXi 7.0 – AleAdmin.it
ARomeo
Hi André, this is the command I am using.
esxcli software profile update --depot=file:///vmfs/volumes/57d13ac3-f23337b8-7e1f-288023b4f634/esxi/VMware-ESXi-7.0.0-16324942-HPE-700.0.0.10.5.5.32-Jun2020-depot.zip --profile=HPE-Custom-AddOn_700.0.0.10.5.5-46 --dry-run
Also, I don't believe we have any additional drivers installed.
Hi Techie01, I did see that page but the drivers listed don't match the errors I have.
What I use for major version upgrades is s.th. like:
esxcli software profile install --depot=/vmfs/volumes/57d13ac3-f23337b8-7e1f-288023b4f634/esxi/VMware-ESXi-7.0.0-16324942-HPE-700.0.0.10.5.5.32-Jun2020-depot.zip --profile=HPE-Custom-AddOn_700.0.0.10.5.5-46 --ok-to-remove --dry-run
Depending on the current version "--ok-to-remove" may not be required.
As a side note, did you see that VMware released ESXi 7.0 Update 1 a few days ago? A HPE customized image is also available.
André
As the error suggests, the problem is due to deprecated version of vmkapi in the machine. ESXi 7.0 do not support vmkapi_2_2_0_0 . That is mentioned in the KB listed above.
The KB also says that, "The above list may not be exhaustive." So, please do not ignore the KB steps. The fundamental problem lies with deprecated vmkapi verison and that KB provides complete details for this issue.
The options possible are, try out latest 7.0 custom ISO from HPE and check if the latest version of the iso has a VIB which replaces this VIB
Second option is to upgrade this VIB to the latest supported version of the vib in 6.7 and then try to upgrade
If these two do not work, i guess you will have to remove this VIB before upgrade ( but before that make sure these vibs are not used for any storage drives)
What HPE firmware version did you update to? Did you use the iLO firmware update utility?
removed
removed2
@ ofnl
Thank you for posting on VMware Communities.
Please use the latest version of HPE Custom ESXi .zip file provided & recommended by the hardware vendor.
Migrate or power off the virtual machines running on the host and put the host into maintenance mode. The host can be put into maintenance mode by running this command:
#vim-cmd hostsvc/maintenance_mode_enter
Put the host in maintenance mode and take backup of the host configuration using:
#vim-cmd hostsvc/firmware/sync_config
#vim-cmd hostsvc/firmware/backup_config
hostname -i to get the IP address of the hostname
hostname -f to get the FQDN for the ESXi host
Note: The command should output a URL in which a web browser may be used to download the file.
For example : Bundle can be downloaded at : http://*/downloads/123456/configBundle-xx.xx.xx.xx.tgz where * denotes the host IP/FQDN.
The backup file is also located in the /scratch/downloads directory as configBundle-HostFQDN.tgz
Browse to that datastore location using the following command:
#cd /vmfs/volumes/datastore_name/folder_name/file.zip
Run this command to list the profiles:
#esxcli software sources profile list -d <absolute path of the .zip file>
Example: esxcli software sources profile list -d /vmfs/volumes/datastore_name/folder_name/file.zip
Output:
Name Vendor Acceptance Level
-------------------------------- ------------ ----------------
ESXi-6.0.0-20171101001s-standard VMware, Inc. PartnerSupported
ESXi-6.0.0-20171101001s-no-tools VMware, Inc. PartnerSupported
ESXi-6.0.0-20171104001-no-tools VMware, Inc. PartnerSupported
ESXi-6.0.0-20171104001-standard VMware, Inc. PartnerSupported
Choose one of the profile from point 5 that says -standard and run this command against it:
#esxcli software profile update -d <absolute path of the .zip file> -p <output from 5>
If it complains about the comflicting VIBs please perform the below:
-------------------------------------------------------------------
List the VIBs used for storage and network respectively through the following commands:
#esxcfg-scsidevs -a
#esxcfg-nics -l
If the above two commands do not show the conflicting VIB names then you can safely remove them
List the conflicting VIB name:
#esxcli software vib list | grep -i <Conflicting VIB NAME>
Remove the conflicting VIB one by one using the below command:
#esxcli software vib remove --vibname=Conflicting VIB Name
#reboot -f
Only after the reboot the conflicting VIBS will be removed
-------------------------------------------------------------------
SSH again to the same host after enabling SSH.
Browse to that datastore location using the following command:
#cd /vmfs/volumes/datastore_name/folder_name/file.zip
Run this command to list the profiles:
#esxcli software sources profile list -d <absolute path of the .zip file>
Example: esxcli software sources profile list -d /vmfs/volumes/datastore_name/folder_name/file.zip
Output:
Name Vendor Acceptance Level
-------------------------------- ------------ ----------------
ESXi-6.0.0-20171101001s-standard VMware, Inc. PartnerSupported
ESXi-6.0.0-20171101001s-no-tools VMware, Inc. PartnerSupported
ESXi-6.0.0-20171104001-no-tools VMware, Inc. PartnerSupported
ESXi-6.0.0-20171104001-standard VMware, Inc. PartnerSupported
Choose one of the profile from point 5 that says -standard and run this command against it:
#esxcli software profile update -d <absolute path of the .zip file> -p <output from 5>
For example:
#esxcli software profile update -d /vmfs/volumes/abcderskfjfggjgjgg5h33n444/ESXi600-201711001.zip -p ESXi-6.0.0-20171104001-standard
It will say that the upgrade completed successfully.
Run this command to reboot the host:
reboot -f
------------------------------------------------------------------------------------------------------------------
Arun Kumar
Install Upgrade Specialist
"Did you find this helpful? Let us know by completing this survey (takes 1 minute!)"
Excellent you help me a lot!