I found I have a HP DL380 Gen 8 server still on ESXi 5.0
This command worked perfectly to upgrade a 6.0 to 6.5 but can I go straight to 6.5 from as early as 5.0? Obviously I added the --dry-run to see the output before running it.
esxcli software profile update -d /vmfs/volumes/1fe43b18-44f1ee63/iso/VMware-ESXi-6.5.0-Update3-14990892
-HPE-preGen9-650.U3.9.6.10.1-Dec2019-depot.zip -p HPE-ESXi-6.5.0-Update3-preGen9-650.U3.9.6.10.1 --dry-run
You need an interim update to 6.0.0 U1 first.
Please check VMware Product Interoperability Matrices
Regards,
Joerg
_______________________________________________________________________________________________________
"Did you find this helpful? Let us know by completing this survey (takes 1 minute!)"
You need an interim update to 6.0.0 U1 first.
Please check VMware Product Interoperability Matrices
Regards,
Joerg
_______________________________________________________________________________________________________
"Did you find this helpful? Let us know by completing this survey (takes 1 minute!)"
Ok thanks,
Looks like I have to install VMware-ESXi-6.0.0-Update1-3380124-HPE-600.9.4.5.11-Jan2016-depot.zip first, reboot, then do the HP 6.5.
Glad I checked!
Ok I just tried with --dry-run to see what vibs would be changed and here is the output...
esxcli software profile update -d /vmfs/volumes/52fba882-5fd89a67-cf2c-2c44fd88b865/VMware-ESXi-6.0.0-Update1-3380124-HPE-600.9.4.5.11-Jan2016-depot.zip -p HPE-ESXi-6.0.0-Update1-600.9.4.5.11 --dry-run
[DependencyError]
VIB MEL_bootbank_nmst_4.0.0.20-1OEM.600.0.0.2295424 violates extensibility rule checks: [u'(line 39: col 0) Error validating value boolean', u'(line 39: col 0) Element vib failed to validate content']
Please refer to the log file for more details.
What the heck do I do there?
I was able to use the --force switch and get it upgraded from 5.0 to 6.0u3.
Howver when I do a dry run to go from 6.0u3 to 6.5 I get this
esxcli software profile update -d /vmfs/volumes/52841982-d39cbd38-721d-2c44fd9657f5/VMware-ESXi-6.5.0-Update3-14990892-HPE-preGen9-650.U3.9.6.10.1-Dec2019-depot.zip -p HPE-ESXi-6.5.0-Update3-preGen9-650.U3.9.6.10.1 --dry-run
[DependencyError]
VIB VMware_bootbank_scsi-qla2xxx_901.k1.1-14vmw.500.0.0.469512 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.
VIB VMware_bootbank_scsi-qla2xxx_901.k1.1-14vmw.500.0.0.469512 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.
VIB VMware_bootbank_scsi-lpfc820_8.2.2.1-18vmw.500.2.26.914586 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.
VIB VMware_bootbank_scsi-lpfc820_8.2.2.1-18vmw.500.2.26.914586 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.
Please refer to the log file for more details.
Ok I could vib remove them or force it again... but thats 4 drivers.
Nevermind this fixed it.
esxcli software vib list | grep 500
scsi-lpfc820 8.2.2.1-18vmw.500.2.26.914586 VMware VMwareCertified 2014-03-19
scsi-qla2xxx 901.k1.1-14vmw.500.0.0.469512 VMware VMwareCertified 2014-03-19
[root] esxcli software vib remove -n scsi-lpfc820 -n scsi-qla2xx
x
Removal Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed:
VIBs Removed: VMware_bootbank_scsi-lpfc820_8.2.2.1-18vmw.500.2.26.914586, VMware_bootbank_scsi-qla2xxx_901.k1.1-14vmw.500.0.0.469512
VIBs Skipped:
[root] esxcli software profile update -d /vmfs/volumes/52841982-d39cbd38-721d-2c44fd9657f5/VMware-ESXi-6.5.0-Update3-14990892-HPE-preGen9-650.U3.9.6.10.1-Dec2019-depot.zip -p HPE-ESXi-6.5.0-Update3-preGen9-650.U3.9.6.10.1
You did it right.
As you can see on the version nummer these old drivers comes from the ESXi 5.0.0 period of time and fallen behind. Devices like an old QLogic 2200 FC HBA are not supportet any more. If you donte use that kind of a device its save to remote the driver and if will fix the dependency problem.
Regards,
Joerg
Great to know, everything is running smoothly. I did two of these last night.