VMware Cloud Community
aecro
Contributor
Contributor
Jump to solution

LSI provider not working under ESXi 6

Hey,

has anyone got the LSI SMIS provider working with ESXi 6? The LSI support site only lists downloads for 5.0 and 5.x. I tried both, but when I try to discover the host with MegaRAID Storage Manager, I'm unable to find it.

Maybe I'm missing something?

Thanks,

aecro

39 Replies
r2504
Contributor
Contributor
Jump to solution

I'm currently working on a PowerCLI script that I will schedule to run nightly on a Windows machine and will warn me via e-mail whenever an item in the storage hardware health section will turn from green to yellow or red.

Maybe you can have a look at http://poshcode.org/3355 ... it already provides querying the CIMON interface.

Reply
0 Kudos
peetz
Leadership
Leadership
Jump to solution

LSI has now published an update of the SMIS provider for ESXi 5.5 and 6.0:

http://www.lsi.com/support/pages/download-results.aspx?component=Storage+Component&productfamily=RAI...

I will try that today.

The issue with the disk hardware status disappearing from the vSphere Client seems to be solved with ESXi 6.0.0b. At least it did not reappear here for several days.

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de
Reply
0 Kudos
r2504
Contributor
Contributor
Jump to solution

There's also a new MSM version (15.05.01.00).

I'll try both this evening as well... just wonder if the alarms in MSM will work as this is my main concern now.

Reply
0 Kudos
r2504
Contributor
Contributor
Jump to solution

The update of the SMIS provider only lists two fixes...

CGCQ00832757 (CSET) - Memory leak while CC start/stop is executed continuously

SCGCQ00832799 (CSET) - SNMP TRAPS are not recieved on importing foreign configuration

... and is actually the 5.5 version which now got labeled "5.5 and 6.0", so I don't think there's any difference with the prior version.

LSI refreshed almost everything, apart from a new MSM they also have a new STORcli version (both with tons of changes).

Reply
0 Kudos
r2504
Contributor
Contributor
Jump to solution

Running both the new SMIS and MSM... but no apparent changes.

I can still manage it from within a VM, but I also still lack monitoring :smileyangry:

I wonder how MSM should know which hosts to monitor (and their credentials).

Reply
0 Kudos
r2504
Contributor
Contributor
Jump to solution

Bad news... I see the CIMON server is stopped after a while again :disappointed_face:

Reply
0 Kudos
r2504
Contributor
Contributor
Jump to solution

peetz

Any news on this ?  I tried contacting LSI but no answer at all :disappointed_face:

Yesterday I got an alarm on my server... without a having a single clue... not an ideal situation.

Reply
0 Kudos
aecro
Contributor
Contributor
Jump to solution

The new CIM provider is available since end of July, it's working for me.

Reply
0 Kudos
r2504
Contributor
Contributor
Jump to solution

What do mean by "working" ?  What can you do, what do you see ?

MegaRaid is already working quite some time for me (even with the previous version) but I don't see any messages in MegaRaid apart from the initial "Successful log on".

Reply
0 Kudos
aecro
Contributor
Contributor
Jump to solution

Mmh, you're right. Didn't notice that before. Well my issue was with the older version, that I couldn't detect my ESX server with MegaRAID before, which is now fixed.

Reply
0 Kudos
r2504
Contributor
Contributor
Jump to solution

The result is running "blind" at the moment... as mentioned I don't even know what the alarm was about yesterday :disappointed_face:

Peetz was working on a script to read the status... but I don't understand that LSI is delivering a half solution like this.

Reply
0 Kudos
redowk
Contributor
Contributor
Jump to solution

no updates on this yet.

looks like lsi is just not interested!

Reply
0 Kudos
JarryG
Expert
Expert
Jump to solution

LSI/Avago already released SMIS-provider for ESXi6 and it works well for me (ESXi 6.0 with OEM LSI9271 controller). Just do not forget to update drivers too (I'm using native one), because the one included in ESXi is quite old...

_____________________________________________ If you found my answer useful please do *not* mark it as "correct" or "helpful". It is hard to pretend being noob with all those points! :winking_face:
Reply
0 Kudos
r2504
Contributor
Contributor
Jump to solution

What do you mean by "it works well for me"... do you get alarms or are you just able to configure it ?

Reply
0 Kudos
JarryG
Expert
Expert
Jump to solution

If you want to get alarms, you have to configure them. That's different story. But smis-provider definitely works. I can see controller-status (incl. all raid-arrays, disks, battery, etc) in hardware health tab of vSphere-client. Without smis-provider working (or installed) I could not see anything concerning LSI-controller...

_____________________________________________ If you found my answer useful please do *not* mark it as "correct" or "helpful". It is hard to pretend being noob with all those points! :winking_face:
Reply
0 Kudos
peetz
Leadership
Leadership
Jump to solution

Same for me ...

JarryG‌: Are you also using vCenter? If yes: is the hardware status properly displayed in the Web Client?

Thanks

Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de
Reply
0 Kudos
r2504
Contributor
Contributor
Jump to solution

Since this is a home lab I can't afford myself vCenter... so I neither have VMWare solutions to define the alarms.

MSM running standalone does however have this feature, so I was wondering why it doesn't work in a VM (since the drivers allow all required access to the hardware).

Can it work, should it work, does it work... for someone is the question.

Reply
0 Kudos
peetz
Leadership
Leadership
Jump to solution

The issue of Hardware health not being displayed in the vCenter Web Client is solved after applying Update 1 to my VCSA 6.0 !

Great, now I can monitor the health of the LSI controller and attached disks using vCenter alarms.

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de
Reply
0 Kudos
bbkdigicon
Contributor
Contributor
Jump to solution

I get the MSM not working.

My Enviroment:

MegaRAID SAS9361-8i

[root@esx:/opt/lsi/storcli] vmware -vl

VMware ESXi 6.0.0 build-3380124

VMware ESXi 6.0.0 Update 1

[root@esx:/opt/lsi/storcli] esxcli software vib list

Name                           Version                               Vendor  Acceptance Level  Install Date

-----------------------------  ------------------------------------  ------  ----------------  ------------

scsi-megaraid-sas              6.610.15.00-1OEM.600.0.0.2494585      Avago   VMwareCertified   2016-02-17

lsiprovider                    500.04.V0.58-0006                     LSI     VMwareAccepted    2016-02-17

vmware-esx-storcli-1.18.05     1.18.05-01                            LSI     PartnerSupported  2016-02-17

MegaRAID Storage Manager 15.11.00.13

In the Hardwarestatus Tab I can see the full Details od the RAID-Controller. Storcli is working fine.

But Megaraid Storage Manager can't find the Esxi. Some Idea?

Greetings from Germany

PS: In the Vsphere Console CIM Service  (Sfcbd-watchdog) shows "Stopped".

But both are running.

[root@esx:/opt/lsi/storcli] /etc/init.d/sfcbd-watchdog status

sfcbd is running.

[root@esx:/opt/lsi/storcli] /etc/init.d/sfcbd status

sfcbd is running

Reply
0 Kudos
pierrepardon201
Contributor
Contributor
Jump to solution

Hello,

I have the same behavior: LSI MegaRAID Storage Manager is unable to discover my host.

I have follow this documentation:51530-00_RevP_MegaRAID_SAS_SW_UserGd.pdf. Quote:

"Network communication is a key element for a proper communication between the ESXi CIM provider and the LSI

management software. Make sure that the network settings are correct by making the following changes:

 Provide a proper host name and an IP address while doing the initial configurations for the ESXi host.

 For networks that do not have DNS configured, the “hosts” file in the machine on which the MegaRAID Storage

Manager software is installed must be edited as follows:

a. Add an entry to map the VMware host’s IP address with the host name. This is for the discovery process to

happen correctly. In the absence of this entry, the VMware host would be discovered as 0.0.0.0.

b. Add an entry to map the actual IP address of the localhost with its hostname (an entry for the loopback

address would be present by default in the hosts file and it should not be removed). This is to ensure that the

Asynchronous Event Notifications (AENs) are delivered correctly."

Thus, I've add these records to my host file (C:\Windows\System32\drivers\etc\host):

192.168.1.10    esxi.domain.local.

192.168.2.40    mycomputer.otherdomain.local.

Ping OK from mycomputer to esxi.

Hardware:

Controller = 0

Model = LSI MegaRAID SAS 9271-4i

Serial Number = XXXXXXXXXXXXXXXXXXXXX

Current Controller Date/Time = 03/15/2016, 15:00:33

Current System Date/time = 03/15/2016, 15:00:34

SAS Address = XXXXXXXXXXXXXXXXXXX

PCI Address = 00:04:00:00

Mfg Date = 12/29/15

Rework Date = 00/00/00

Revision No = 07C

Version :

=======

Firmware Package Build = 23.34.0-0005

Firmware Version = 3.460.05-4565

Bios Version = 5.50.03.0_4.17.08.00_0x06110200

WebBIOS Version = 6.1-76-e_76-Rel

Preboot CLI Version = 05.07-00:#%00011

NVDATA Version = 2.1507.03-0155

Boot Block Version = 2.05.00.00-0010

Bootloader Version = 07.26.26.219

Driver Name = megaraid_sas

Driver Version = 6.603.55.00.1vmw

My build:

vmware -vl

VMware ESXi 6.0.0 build-3568940

VMware ESXi 6.0.0 Update 1

esxcli software vib list

Name                          Version                              Vendor  Acceptance Level  Install Date

-----------------------------  -----------------------------------  ------  ----------------  ------------

lsi-mr3                        6.610.17.00-1OEM.600.0.0.2768847    Avago  VMwareCertified  2016-03-14

lsiprovider                    500.04.V0.58-0006                    LSI    VMwareAccepted    2016-03-14

vmware-esx-storcli-1.18.05    1.18.05-01                          LSI    PartnerSupported  2016-03-14

Here I can see that the driver listed with storcli is not the driver I've installed:

ESXi 6.0 Native driver Invader only

https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESXI60-LSI-LSI-MR3-66101700-1OEM&productId...

Does anyone known is this driver is compatible with SMI-S provider (and LSI MSM of course)?

I will try to install the last  megaraid_sas legacy driver and post my progress:

ESXi 6.0 Legacy driver

https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESXI60-LSI-SCSI-MEGARAID-SAS-66101500-1OEM...

I don't know if it's possible to switch for a driver to an other.

After, CIM server (sfcbd-watchdog) is opened and listening on 5989.

Does Anyone known how to check is SMI-S provider is working as expected?

For information, telnet is OK

Thank you in advance for your help guys.

Regards !

Reply
0 Kudos