I have just updated to 2.5.1 and can confirm that it now reports the device correctly - thank you
Thanks for reporting this. SHD collects the driver version from vib list output (commands/localcli_software-vib-get.json). Driver version appearing as '0' suggests the failure in either parsing the file or driver lookup. Are you able to see driver versions for other devices (say vminc)?. If no, then it is full failure in parsing the file. If versions for other devices are visible, then probably we have a lookup failure in picking up the driver version.
Let me check tis one and update. Will it be possible to provide the out puts of esxcli storage core adapter list and esxcli software vib list from the ESXi server?
Thanks
-Ram
Also what is the ESXi version you are running on these servers?
@raycward I think I know the cause here. It is a driver lookup failure. Since bfa driver is from pre 6.x era, it uses a different naming convention for driver module. Though the driver is named as bfa, it's provided driver name is scsi-bfa (VIB Name: scsi-bfa-.*.x86_64.vib). You can confirm this by looking into output of esxcli software vib list.
We have an internal mapping to handle this scenario. bfa is not on that mapping, hence we see a lookup failure. Let me make sure we update the mapping for this driver and have it in next release
Thanks
-Ram
All hosts are running ESXi 6.5 u3 (p06) - 17477841
The other devices are being correctly defined - so it is only related to the "bfa" driver for the QLogic HBA
I suspect you are correct here, the driver is 3.2.5.0
vmkload_mod -s bfa | grep Version
Version: Version 3.2.5.0, Build: 1331820, Interface: 9.2 Built on: Sep 29 2014
and running the vib list does indeed report the device driver as scsi-bfa
esxcli software vib list | grep bfa
scsi-bfa 3.2.5.0-1OEM.550.0.0.1331820 QLogic VMwareCertified 2020-11-12
Can you let me know when the new release is likely to be available please
Thanks for the prompt response
Ray
Thanks for the update. Most likely we will have a new release in a week or two.
-Thanks
Ram
I have just updated to 2.5.1 and can confirm that it now reports the device correctly - thank you