The upgrade has VIBs that are missing dependencies:
VMware_bootbank_net-qlge_3.0.0.57-1vmw.550.0.0.1198611
CSCO_bootbank_scsi-snic_0.0.1.26-1OEM.600.0.0.2494585
LSI_bootbank_scsi-mpt3sas_06.00.00.00.1vmw-1OEM.550.0.0.1331820
VMware_bootbank_net-qlge_3.0.0.57-1vmw.550.0.0.1198611
CSCO_bootbank_scsi-snic_0.0.1.26-1OEM.600.0.0.2494585
LSI_bootbank_scsi-mpt3sas_06.00.00.00.1vmw-1OEM.550.0.0.1331820
Remove the VIBs or use Image Builder to create a custom upgrade ISO image that contains the missing dependencies, and try to upgrade again.
But list command show not sure use or not?
[root@BPKESX02:~] esxcfg-scsidevs -a
vmhba0 vmw_ahci link-n/a sata.vmhba0 (000 0:00:11.4) Intel Corporation Wellsburg AHCI Controller
vmhba1 vmw_ahci link-n/a sata.vmhba1 (000 0:00:1f.2) Intel Corporation Wellsburg AHCI Controller
vmhba2 lsi_mr3 link-n/a sas.578da6e715daf7b0 (000 0:05:00.0) Avago (LSI / Symbios Logic) MegaRAID SAS Invader Controller
vmhba3 nfnic link-down fc.1000843dc6fb1f3c:2000843dc6fb1f3c (000 0:0d:00.0) Cisco Systems Inc Cisco VIC FCoE HBA Driver
vmhba4 nfnic link-down fc.1000843dc6fb1f3d:2000843dc6fb1f3d (000 0:0e:00.0) Cisco Systems Inc Cisco VIC FCoE HBA Driver
vmhba64 iscsi_vmk online iqn.1998-01.com.vmware:bpkpsesx02 iSCS I Software Adapter
[root@BPKESX02:~] esxcli software vib list | grep -i scsi_mpt3sas
[root@BPKESX02:~] esxcli software vib list | grep -i scsi-snic
scsi-snic 0.0.1.26-1OEM.600.0.0.2494585 CSCO VMwareCertified 2020-04-06
I prefer rebuilding the ESXi host with the new image ( with latest drivers ) than going with a version upgrade. That gives a clean system with configuration re-applied.
Here in the below case , you certainly need to create an image with latest drivers for the upgrade if choose to go with the upgrade.
Recently, I just upgraded firmware UCS to support ESXi 7.0u1. I want to know if I can remove which one.
That's a easy one. If you take a look to the version numbers like 550 and 600 it indicates that these drivers are from the ESXi 5.5/6.0 period and VMware have dropped the support for VMKlinux style drivers.
Your grep is not working because the driver have a slightly different name. Use just "mpt3sas" for example or try "550".
Regards,
Joerg