I'm experiencing the same issue as the OP and lots of other people who are running ESXi 6.5U2/6.7 with LSI Raid Controllers in their environments.
I am unable to view the status of the raid controller and individual drives in the Web Client or through the vSphere API; instead I see lots of unrelated hardware with 'Unknown' status.
This is preventing us from upgrading our ESXi hosts as we rely on this status for our monitoring. We query the vSphere API for the hardware status information and an alarm is triggered if the drives have failed or the raid is degraded.
After creating a case with VMware support and reading some of the other community posts regarding the issue (e.g. LSI SMIS на ESXi 6.7 ), I was led to believe this issue was with the LSI SMI-S Provider not supporting the latest version of ESXi and that this would be resolved in the next release (MegaRaid 7.9).
However, even after installing the latest version released on 25/3/2019 (VMW-ESX-6.5.0-lsiprovider-500.04.V0.73), I was still unable to see the correct hardware status information in vSphere. Broadcom support confirmed that they do not support the vCenter Web Client (even though it has worked in the past) and that I should contact VMware Support.
@ipv6 you seem to be aware of this issue and claim that this will be resolved in the next release of vSphere. Can you confirm that this is a vSphere related issue and that it will also be resolved in the next release of vSphere 6.7? Can you elaborate on how this issue arose in the first place and why it has taken so long to fix?
This should have been tested and discovered imo by VMware prior to the release of 6.5U2. Something as crucial as displaying drive status in the hardware health should not break for devices which are supported according to the HCL.
Same issue with LSI 9260-8i RAID Controller.
Wish Broadcom and/or VMWare would just give a straight answer so we know to wait or move to new hardware.
I contacted Broadcom support and the reply I got back is posted below. I tried the SMIS they provided, but it didn't seem to work for me. Let me know if you have any luck because I may not know what I am doing.
Yes we will come out with an SMIs provider or find the root cause.
6.5 was working fine and theoretically, the 6.5 SMIs provider should have worked.
But it is broken and no one seems to have a reliable fix at tthe moment.
But we are working on it.
We have had some success with this version:
You are more than welcome to try it.
If it does not work, just uninstall it and I will keep your case open until the final release comes out.
If to no avail, use storcli
Latest storcli for all OS:
Thank you and let me know if you have any questions,
Storage Technical support
unfortunately the SMIS providers posted on the FTP address didn't worked for me
FYI I have LSI MegaRAID SAS 9341-8i card and I tried with ESXi 6.7 U2.
I just tried the SMIS providers posted on the FTP site as well, and they did not work for me either on 6.7 U2.
I have installed the LSI Provider from Lenovo on 6.7U1
with the LSI Storage Authority (replacement of Mega RAID Storage Manager) I can manage the LSI controller
Hardware is Supermicro Mainboard with LSI Controller
Tried with Lenovo SMIS providers (also drivers), but still not able to see drives/card status under Monitor -> Hardware -> Storage .
I'm also on Supermicro server HW (SYS-5028D-TN4T)
Thanks, best regards
Have someone try to connect via Megaraid Storage Manager on a 6.7?
Install the MSM on a Virtual Windows Machine and try to connect over IP?
I've tried to install the LSI Storage Authority (LSA) which, as I understand, is the replacement for Megaraid Storage Manager (MSM), and fully supported by LSI as the method for monitoring RAID controllers.
User Guide - LSI Storage Authority Software User Guide
My hope was that I would be able to monitor the raid status for my ESXi 6.5 and 6.7 hosts using this software.
However, I encountered problems when trying to add more than a single ESXi host to the LSI Storage Authority server. Apparently there is a bug which prevents you from being to monitor more than a single ESXi server per LSA instance:
The workaround is to install an LSA Server per ESXi host, which just doesn't scale if you have more than a handful of hosts. And to be honest, I'd rather SSH to each ESXi host and run storcli to monitor the raid status, that have to install a few hundred LSA servers...
At this point I'm starting to lose hope. It is so frustrating that neither VMware or LSI/Broadcom appear to be taking ownership of this issue. It's almost as though they don't understand the gravity of the problem.
https://www.vmware.com/resources/compatibility/pdf/vi_cim_guide.pdf here officially listed that 6.5u2 is the last version of LSI Provider support. Same boat here: controller is fully supported but vib not. So seems like moving back to 6.5
does someone has any update on this...?
i looking for days about solution for this issue
Since the release of 6.7u3, Broadcom apparently have flagged the existing provider for both 6.5 and 6.7 (I think it was only flagged for 6.5 before that).
I have installed the provider on a 6.7u3 (where it was previously failing with 6.7u2) and what I can say is:
- It doesn't seem to crash anymore (no core dumps)
- LSA can talk to it
However, as my server has no IPMI whatsoever, I still don't get any health information in the web UI but that might be normal.