Got a warning raised this morning about this alert on the vcenter skyline health check (KB 77304)
All my ESXi are yellow on this warning page. I am trying to find which dev raises this alert ... Servers are not that old (r740xd bought in 2018 for the oldest)
I downloaded the 3 excel files but couldn't find any devices are that are present in my servers.
I did read https://blogs.vmware.com/vsphere/2019/04/what-is-the-impact-of-the-vmklinux-driver-stack-deprecation... but vmklinux module is not loaded on my ESXi
The closest match I could find using VID DID SVID and SSID is this one :
|Marvell||88SE9230 PCIe SATA 6Gb/s Controller||ahci||1b4b||9230||0000|
I am using "dell boss s1 adapter" for local esxi system storage, and the device code is 1b4b:9230 1028:1fe2
Not the same code, but couldn't find anything closer.
Also, when looking on HCL, my device (ending with 1028:1fe2) is supported for vsphere 7, but I also noticed that the one listed on the excel file is displayed to be still supported by vsphere 7 :
Anyone has a clever way to know which device is raising this alarm ?
Just for some added notes... I'm having the same issue but only with two of our 740xd hosts. These two are newer hosts that were purchased with in the last year. Our older hosts are also 740xd's but do not show this warning.
We are not running any vmklinux drivers which is the primary cause of this alert.
The main thing that I see different between the two is that the older hosts use Intel X710 NICs while the newer hosts use Broadcom BCM75412 NICs. I cannot find any indication of the Broadcom NICs being the issue.
The newer hosts also have Dell BOSS-S1 Adapters, but I also can't find any indication that those would be an issue.
If you can find any correlation, please let me know. I will also be following up with VMware soon.
As was already noted, this definitely appears to be related to the BOSS-S1 card. I have another client with three 740xd hosts, with only the newest one having a BOSS-S1 card and it is the only one showing the device deprecation warning.
this is a known issue, as I reported here: https://communities.vmware.com/t5/VMware-vSphere-Discussions/DEVICES-deprecated-and-unsuppoted-in-ES...
it is being investigated as we speak by engineering.
I just got the confirmation on the bug that the problem was resolved, verified it in my own lab as well. The device ID was incorrectly added to the list unfortunately. Thanks folks for reporting!