ESXi 5.1 host with LSI 92xx RAID adapter can run a VM with fully functional MegaRAID Storage Manager UI, here’s how

I’ve been wanting this capability since summer of 2011, when I got my LSI 9265-8i RAID controller for my vZilla build, back on ESXi 4.1. Thanks to a Tinkertry site visitor and a talented Russian, this problem now has a solution.*(see new addendum at the end of article for new, easier way to do this)

I’ve always been a bit jealous of the simplicity of Areca and other models, that simply use an RJ45 Ethernet port on the card itself, for all RAID management and alerting functions. But ESXi compatibility and speed were more important considerations, since I really wanted read and write caching of RAID 5 using SSDs.

Ideally, this would be with full health monitoring and alerting from within this vSphere lab in a box, since knowing when a drive fails is, of course, important.

Finally, the ability to run the far easier-to-use MegaRAID from a VM. No more dual booting. No more awkward to use WebBIOS, or MegaCLI to carefully type.

The first prerequisite is to have the driver loaded and the VMware SMIS Provider VIB loaded, as I explain in detail here:
How to make ESXi 5.1 see the health of an LSI 9265-8i RAID controller and array (probably works with all 92xx controllers)

Next, installing MegaRAID has gotten much easier too, with that installation-while-logged-in-as-Administrator nonsense no longer a requirement. Even works on Windows 8 64 bit. The UI is still a little finicky (under Windows 8 anyway), but at least it works well, once the ESXi 5.1 host is actually located.

So in the video below, you’ll see me succeed in using a nice little workaround, using this tip I received from Roman Shein, who points to Alex’s Blog in Russia. The specific post is titled:
How to make friends and LSI VMWare ESXi, the second part – the final decision
or at least that’s what Google Translate thinks it says. At least I was able to glean from the translation what’s needed to get this working, here’s an excerpt:

…small utility that would convert your multicast requests from MSM in unicast requests to ESXi-server, and pass back the answers. A kind of small Proxy, which allows the MSM to communicate with the server, bypassing the multicast…

Until LSI chooses to fix this, Alex gets us around an issue that many have noticed where MSM (MegaRAID Storage Manager) cannot locate the SMIS provider that is running on the ESXi host. I take his script, make the appropriate simple edit to it, and add it to my startup folder, running from a directory where Alex’s included php.exe lives. That’s pretty much the gist of it. With no install necessary, just a small set of files with a dash of Alex’s creativity, and you too may have a way to get MegaRAID working, in a lab environment at least.

Download “MegaRAID Storage Manager – Windows – 5.3 Version 12.05.03.00 June 18 2012″ for yourself from this direct download link, or browse your way to the most recent version by visiting lsi.com and clicking on the Support tab.

When I have a chance, I’ll get some step-by-step screenshots up here as well, making the walk-through of the technique easier to replicate. But the video will give you all you need to know to get this working right now, here you go!


*Oct 15, 2012 Update:
You no longer need the custom utility! LSI has fixed this discovery problem, with MSM 5.4, you can now get your VM’s MSM to “see” the CIMON running on your ESXi 5.1 host. It’s all explained and shown at:
LSI 9265-8i 5.1 October 8, 2012 Firmware 1881 for LSI CacheCade and non-CacheCade RAID controllers has arrived


May 04 2014 Update:
Even on ESXi 5.5, you can get MegaRAID running in a VM, but you still need to be very sure the one line of your ESXi’s hosts file perfectly matches your Windows system’s hosts file, described and pictured below, with a video walkthrough of the windows editing procedure at this spot in the related video. See also this particular discussion below:

It’s important that the one line of your ESXi hosts file exactly match whatever is in the Windows host file, seen pictured here below. It seems my DHCP router likes to feed a fully qualified domain name of .ri.cox.net (Cox Communications is my ISP). This has implications, strangely enough, on MSM, it’s VERY particular.

Using PuTTY or WinSCP to have a look at your ESXi host’s /etc/hosts file (see picture here). Put the entire line that’s in there for your ESXi host, and past that into your Windows c:\Windows\system32\drivers\etc\hosts file (you’ll need to be at CMD as Admin), and suddenly, you’ll find the “Configure Host…” dialogue in MegaRAID, followed by “Display all the ESXi-CIMOM servers in the network of local server.” works (also pictured here).

Let us know how it goes!

(I realize I really need to revisit this topic on ESXi 5.5, with a whole new article, meanwhile, this host file matching works there, assuming the right driver is used)

esxi host file entry

MegaRAID Storage Manager finds ESXi if hosts files on ESXi and Windows match perfectly

 


written by

The author didn‘t add any Information to his profile yet.

10 Pingbacks/Trackbacks

  • Pingback: How to make ESXi 5.1 see the health of an LSI 9265-8i RAID controller and array (probably works with all 92xx controllers) | Tinkertry()

  • frolic78

    Thank you and Alex, very much for this tip

  • http://www.facebook.com/mmittelman Michael Mittelman

    I can see the traffic in the console, but still not showing up in the MSM. Thoughts?

    • tinkererguy

      If you are still having an issue, can you explain exactly what the issue is? I’m afraid I don’t quite know what you mean by seeing traffic. Thanks!

  • Pingback: LSI 9265-8i 5.1 October 8 2012 Firmware 23.9.0-0015 for LSI CacheCade and non-CacheCade RAID controllers has arrived | Tinkertry()

  • Pingback: How to make ESXi 5.0 recognize an LSI 9265-8i RAID controller | Tinkertry()

  • James R.

    I want to thank you for all the blog posts you’ve made in regards to the 9265 and ESXI 5.1. I watched a few of your videos this weekend when setting up a whitebox at home with my Intel RS25DB080. I eventually got everything running and with the latest version of MSM, I can modify my Raid Array as I please. This was crucial for me as the web bios won’t load on my motherboard. No more megacli for me! ;)

    • tinkererguy

      Nice way to start my week. Thank you James!

    • http://TinkerTry.com/about Paul Braren

      Feels good, avoiding MegaCLI, don’t it?
      Thanks you for the thank you!

    • ChrisNZ

      Quick question, how did you get it to work? I can’t seem to get my RS25DB080 to work with ESXi 5.1

  • http://www.facebook.com/allen.st.clair Allen St.Clair

    Hello. Thanks for this post. But I cannot get it done.
    I’m using 9260-8i on ESXi 5.1. My MegaRaid Storage Manager (12.08.03.03) can find the ESXi host but cannot connect.
    Login failed: Unable to connect to CIMOM server!

    It’s sure that the IP, user name (root and another account I created for test) and password are correct.

    Any idea?
    Thanks

    • http://www.facebook.com/allen.st.clair Allen St.Clair

      Sorry. I know the reason. I have to start CIM Server from Security Profile of vSphere Client.
      Thanks for your post.

      • tinkererguy

        Please, no need to apologize! You took the time to tell us all about a potential gotcha. Thank you! Remember, less than 1 in a 1000 site visitors comment at all.
        Strange that I don’t recall having to do that (start CIM Server). Thought it was autostarting by default, but I’m not 100% certain. I’ll lookout for this during my next fresh install.

  • Snufflespa

    Thanks for your write-ups – I’m trying to get EXSi 5.1 to play nicely with my LSI 8888elp SAS card. The general good news is the card works “out of the box” with EXSi, its able to be recognized and able to see volumes hanging off the card. However out of the box there is of course no management ability (other than through WebBIOS).

    On the LSI website I was able to upgrade the 8888elp driver to v6.504.51.00 (updated Oct 8) and MegaCLI to version 8.05.06 on my EXSi box. However oddly on the LSI 8888elp page there is no SIMS provider. I used the link in your series of articles though to install the SIMS provider version 500.04.V0.32-0003 – even though in the readme.txt the 8888elp card isn’t listed.

    Within the vSphere client I am able to monitor and see the health of the card – but for the life of me I can not get MegaRaid Storage Manager to “see” the card. I’ve tried the latest version of MSM v12.08.03.03 that even has the dedicated “Display all the ESXi-CIMOM servers” discovery setting. As well as using Alex’s “unicast tool.”

    Has anyone been able to get a LSI 1078 based card (or better yet specifically the 8888elp) to be managed by MSM on EXSi?

  • Daniel Bomya

    Thank you for posting and writing efforts, I’m still struggling to work. Not able to find host after I have followed this video. Do I need to install “VMWare SMIS Provider VIB – 5.3″ ??

  • http://www.facebook.com/fabio.busa.3 Fabio Busa

    Paul,many thanks.
    Reading this post I fixed it.
    Just to note it works with ESX5i 5.0 as well.
    http://communities.vmware.com/thread/343867?tstart=0
    Fabio

  • Pingback: LSI 9265-8i CacheCade Pro 2.0 is working with my Samsung 830 256GB SSD at last, with RAID5 read and write caching, and great performance | Tinkertry()

  • Alan

    Great help and it got me up running… although took me a day of banging my head on the desk. Comment for those who may want to avoid some pain. I didn’t see anything here (or anywhere until I really started to dig) about SIMS… make sure this is installed on esxi so you can both see the health on sphere client and that is what solved my connection issue on the VM… before I setup and installed SIMS I was unable to connect even with the Alex fix. I used MSM 5.3 with the Alex genious stuff… THANK YOU!!!

  • Technobro

    Hi gentlemen, I got Esxi 5.0 recognized my lsi 9240-8i (ibm reflash)recognized and seeing Health

    But i cant get the MSM to work on (win7 vm) , it only seems the 127.0.0.1, CIMON is started, i can ping my esxi by his hostname.. Wats the password anyways , the esxi one of one that we set in the raid bios ?

    • http://tinkerty.com/ Paul Braren

      ESXi password. See also my video, as it takes 2 tries to get in. But something does sound off with your DNS or host files. Let us know. And what makes you so sure we’re all gentlemen? ;-)

      • Technobro

        HI, ladys and gents :), After looking closely i realize i have a 9211-8i, flash in IR. I cant get in the WEBbios , there no control -H , And as a little clarification when i am in my VM, the only two server i see are my ip and 127.0.0.1, as a esxi server , I wonder if its what you guys got whit the 0.0.0.0 or if its really local host

  • Pingback: LSI 9265-8i 5.5 has arrived, time to update to MegaRAID 12.10.03.01, firmware 3.230.05-2100, and SMIS 00.34.V0.01, right from your VM! | TinkerTry IT @ home()

  • Mark Heyworth

    Thanks very much for the article and Video, I have this working with a PERC 6i in a Whitebox server running ESXi 5.1.
    The only thing I cant seem to do is alter the config, the options to create virtual drives are not available, and everything on the ‘Go To’ menu is greyed out. Is this just a limitation I will have to live with, and is it likely to be a result of using MSM with a Dell card or using MSM in a VM?

    My problem is that I want to extend an array, which can only be done from MSM as far as I can tell.

    • http://tinkerty.com/ Paul Braren

      To me, seems more likely that MSM is not “liking” the Dell card is the reason, rather than MSM from a VM (can you see RAID health etc in side the VM?)

      But I just don’t know for sure, having not used the Dell version (just some older PERCs long ago). Hoping somebody else with the PERC 6i might chime in here to assist.

  • Gerald Hopf

    Does an IBM M5014/M5015 need to be crossflashed to the LSI Bios for this to work?
    Or can health be monitored even with the card in it’s original state?

    • http://www.tinkertry.com/about/ Paul Braren

      Does anybody have an IBM version with feedback to give Gerald?

      Gerald, I see a few results only when seeking M5015 hits across my entire site including comments, but it doesn’t see they’ll help you much as I was hoping:
      http://www.google.com/webhp?sourceid=chrome-instant&ion=1&ie=UTF-8#hl=en&sclient=psy-ab&q=ibm%20m1015%20site%3Atinkertry.com&oq=&gs_l=&pbx=1&fp=52cf9100d701ae34&ion=1&bav=on.2,or.r_cp.r_qf.&bvm=bv.45645796,d.dmQ&biw=2560&bih=1315

      but a good chunk of Google hits guide me to where I expected actually, which is ServeTheHome.com. It’s a well-respected site, where they have very active LSI discussions. Here’s a sampling:
      http://www.google.com/webhp?sourceid=chrome-instant&ion=1&ie=UTF-8#hl=en&biw=2560&bih=1315&sclient=psy-ab&q=m5015%20cross%20flash%20site%3Aservethehome.com&oq=&gs_l=&pbx=1&fp=52cf9100d701ae34&ion=1&bav=on.2,or.r_cp.r_qf.&bvm=bv.45645796,d.aWc

      I hope this helps!

      • Satty

        Hi Paul…I request you to use a better video recording software…the videos are lenghtly, but am not able to see what you are clicking as the fonts are very small…all I can see is you are using ESXi

        • http://TinkerTry.com/about Paul Braren

          Satty, I struggle with this, no doubt.

          But using Camtasia to produce videos at 1280×720 resolution just doesn’t cut it for most of the UIs these days, which tend to require a higher resolution to fit everthing without constantly resorting to scrollbars. The next logical, YouTube friendly format is full HD 1920×1080, which you’re right, only plays well (extremely well, crystal clear) on 1920×1080 or higher resolution. Honestly, a vast majority of my site visitors are not mobile, and are visiting with just such HD screens (when I look at my analytics). And 1920×1080 video allows me to screenshot right from that video, saving a lot of time for complex posts with a lot of screenshots.

          As far as producing videos that scan around and zoom in on the areas of focus (to help with font size), I find it way too burdensome to do that much post-production, given my extremely limited free time to work on such “free” donations of my weekend PC escapades to the YouTubes. But I will always continue to try to leverage software to do better, and see if there’s viable ways to make my fonts more legible for lower resolution vistors/tablets, since I admit I haven’t revisited my use/workflow of Camtasia in quite some time.

  • Pingback: TinkerTry IT @ home | Presented at Connecticut VMUG User Conference on May 14 2013, “Virtualization at home can be practical, affordable, and available, 24×7.”()

  • Pingback: TinkerTry IT @ home | Superguide: VMware vSphere()

  • Pingback: TinkerTry IT @ home | Presented at Security BSides Boston on May 18 2013, “Build Your Own VMWare ESXi and Microsoft Hyper-V lab at Home, Using Affordable and Efficient Hardware”()

  • Pingback: TinkerTry IT @ home | Featured on “The Home Tech Podcast” Episode #119 “The first one about Virtualization”()

  • Mike

    Hi Paul,
    Got this working thanks to your various guides…. do you find that after a few days, you cannot connect to the card? I have a whitebox with a PERC 6, and have been able to connect and manage successfully… Now, a few days of uptime later, I cannot access the card at all!
    Tried restarting the CIM services, no joy though… I know it is still running as I can see the health of the disks etc, and can access the datastore on the local disk..
    is this a common thing or any way round this?

    • http://TinkerTry.com/about Paul Braren

      I have not experienced that issue, but I’m not sure my experiences would have much in common with your rig. Seems you’ve unearthed a nasty side effect of your particular combo of PERC 6 raid firmware, and/or the VMware software stack supporting it (ESXi device driver, and the added SMIS-VIB).

  • Urs

    Tried it right now with a CentOS (6.4) on a local VM (Workstation , bridged) did not work, copied the CentOS to the ESXi, didn’t work also.

    So I tried it With a Windows 2003 R2 (32) bit. I could install MRSM 13.04 and after struggling a bit, I managed to get it running. I see my ESXi 5.1, but I couldn’t connect to it.

    Get a: “Login failed: Unable to connect to CIMOM server!”.

    I am sure to provide my ESXi password and user. I also checked for CIM-Server to be started. On the local shell, I installed storcli and it’s working.

    Kind of strange. I am using vSphere 5.1 in Trial Mode (60 Day period). I got a license number to, but only for “ESXi free”. So this could be a problem perhaps? ESXi free has some limatation for scripting too.

    Or any firewall / DNS problems?

    • http://TinkerTry.com/about Paul Braren

      Hmm, disappointing, but fairly confident we’ll be able to figure out what’s different between our configuration and yours.

      Before we go too deep into the other potential differences between our configurations, did you get a chance to read through this article as well? Can you see the health of the array?
      http://www.tinkertry.com/lsi92xx-health-under-esxi-51

      • Urs

        Indeed, I already installed the LSI VIB and I see the status of the RAID and all the disks through the VI-Client.
        In addition, I am able to manage the LSI through storcli for VMware ESXi. I am not afraid of cmdlines, but sometimes a GUI is also quiet handy ;-)

    • Chris

      Yes, DNS is necessary for this to work. Make sure a dns server has a host record for the vm servers address. The 0.0.0.0 will turn into the ip address of the server when you click discover on the MSM.

  • Sokolum

    I managed to to install the latest version of MSM 13_04_03_01 inlcuded with the IP helper tool on my ESXI 5.1.

    Does someone have a experience to upgrade a IBM M5015 to the latest firmware from IBM with the MegaRAID Storage Manager from LSI? Or used also the LSI firmware to upgrade the M5015 (if possible)?

  • Pingback: mooZilla build – a tour | Moo Trader()

  • Ben

    Thanks for the great posts, I was able to install the VIB and I can see the health of my M1015 but when I discover it shows the IP as 0.0.0.0 and fails to connect to the CIMOM server. I verified that the CIM server is running and I have my hosts file on the ESXi referencing my MSM machine, and my MSM machine references the ESXi host in it’s hosts file.

    Any thoughts?

    • http://TinkerTry.com/about Paul Braren

      I’m sorry Ben, I haven’t revisited RAID since this article, and I just don’t have an answer for you, and don’t have any M1015 cards. But I will be revisiting the 9265-8i on ESXi 5.5 pretty soon. Consider giving LSI Support a try:
      http://www.lsi.com/about/contact/Pages/support.aspx

      • Ben

        weirdest thing, I opened MSM this morning without doing anything more just to check it and it worked! Thanks again for the great articles.

      • chune

        Appears to be broken in esxi 5.5. Tried both versions of MSM [12.05.03.00(pre CIM fix) & 12.08.03.03(post CIM fix). Tried both versions with the russian ip helper as well but no joy. The vib installs successfully, i can see array health, i started the CIMs service manually and it started, then i tried restarting CIMs service and i got a timeout error from esxi. Only difference is i have a dell SAS6i/r controller (lsi sas1068e based) but even if the card is unsupported by MSM, i should still be able to connect to the CIMs provider right? Have you gotten a chance to play with this in esxi 5.5?

        • http://TinkerTry.com/about Paul Braren

          That is disappointing to hear (that MSM under ESXi 5.5 is flakey), but I cannot be surprised, as MSM under ESXi has always been a challenge (which is part of why this article is extremely popular/valuable). I do hope that LSI takes resolving this seriously, and I haven’t had a go at this in my own home lab quite yet, expecting to try again later this year…

  • maac68

    Hello to all
    I have tried this tutorial with ESXi 5.1U1 and LSI 9211-8, Now I can see the status of the card inside vsphere client and the status of my raid volume, and when scanning with MSM i get this weird IP address that i don’t know, is there anyway to fix this ? im running latest vib provider esxi and MSM on windows 7 Thank you :)

  • Andy

    Hello,

    I am trying to connect via MegaRaid Storage Manager (Version 13.08.04.01) to the Raid-Controller of an IBM ServeRaid M5015 Controller of my ESXi 5.1.0 (build 1117900). I am able to see the Controller within the Hardware Status of the ESX server, but the controller is not recognized by MSM.
    The MSM Client is installed on VM (WinXP), stored on the same ESXi.
    Of course I installed the necessary .vib to both ESX-Servers, also I run the slp_helper application.

    Additional I tried to add a ServeRaid M5110e of another ESXi Server to the MSM, but without any success.

    The virtual machine (MSM installed), is able to ping the servers (CIM service is running). But while discovering the hosts, it will be finished with “Server could not be found because server my be down or server not installed in the host system”.

    Does anybody have the same problem or maybe a solution?

    Any further checks, I can try?

    • http://TinkerTry.com/about Paul Braren

      Andy, I wish I had a M5015 laying around to test, but I do not. I do hope somebody is able to chime in and help here, especially since Google has now indexed your comments, for folks to easily find. Yeah, MSM is, in general, finicky, and trying alternative firmware flash images is what people seem to do when looking for things to try, when issues are identified. Sorry I wasn’t able to be more help on this one!

    • Red

      Hy andy have you resolved???
      I ve the same issue.

      TKS.

  • Patryk Wojtachnio

    Hello

    I have ESXi 5.5 (10.10.134.205) and i have some probilem. Im gettig tie out. What is going on, any ideas ?

    C:UsersAdministratorDesktopslp_helper>

    C:UsersAdministratorDesktopslp_helper>runme.cmd

    SLP Helper starting. No errors must follow this line.

    Using Unicast IPs:

    10.10.134.205

    Received request from 10.10.134.203:53685 of length 55.

    Assigning socket to 10.10.134.203:53685.

    Transmitting request from 10.10.134.203:53685 of length 55 to 10.10.134.205.

    Received response from 10.10.134.205:427 of length 56.

    Transmitting response from 10.10.134.205:427 of length 56 to 10.10.134.203:53685

    .

    Received request from 10.10.134.203:53687 of length 63.

    Assigning socket to 10.10.134.203:53687.

    Transmitting request from 10.10.134.203:53687 of length 63 to 10.10.134.205.

    Received response from 10.10.134.205:427 of length 492.

    Transmitting response from 10.10.134.205:427 of length 492 to 10.10.134.203:5368

    7.

    Received request from 10.10.134.203:53689 of length 91.

    Assigning socket to 10.10.134.203:53689.

    Transmitting request from 10.10.134.203:53689 of length 91 to 10.10.134.205.

    Received request from 10.10.134.203:53691 of length 91.

    Assigning socket to 10.10.134.203:53691.

    Transmitting request from 10.10.134.203:53691 of length 91 to 10.10.134.205.

    Received request from 10.10.134.203:53693 of length 91.

    Assigning socket to 10.10.134.203:53693.

    Transmitting request from 10.10.134.203:53693 of length 91 to 10.10.134.205.

    Received request from 10.10.134.203:53695 of length 91.

    Assigning socket to 10.10.134.203:53695.

    Transmitting request from 10.10.134.203:53695 of length 91 to 10.10.134.205.

    Received request from 127.0.0.1:53697 of length 63.

    Assigning socket to 127.0.0.1:53697.

    Transmitting request from 127.0.0.1:53697 of length 63 to 10.10.134.205.

    Received request from 10.10.134.203:53698 of length 63.

    Assigning socket to 10.10.134.203:53698.

    Transmitting request from 10.10.134.203:53698 of length 63 to 10.10.134.205.

    Received response from 10.10.134.205:427 of length 492.

    Transmitting response from 10.10.134.205:427 of length 492 to 127.0.0.1:53697.

    Received response from 10.10.134.205:427 of length 492.

    Transmitting response from 10.10.134.205:427 of length 492 to 10.10.134.203:5369

    8.

    Received request from 10.10.134.203:53701 of length 91.

    Assigning socket to 10.10.134.203:53701.

    Transmitting request from 10.10.134.203:53701 of length 91 to 10.10.134.205.

    Received request from 10.10.134.203:53703 of length 91.

    Assigning socket to 10.10.134.203:53703.

    Transmitting request from 10.10.134.203:53703 of length 91 to 10.10.134.205.

    Received request from 10.10.134.203:53705 of length 91.

    Assigning socket to 10.10.134.203:53705.

    Transmitting request from 10.10.134.203:53705 of length 91 to 10.10.134.205.

    Received request from 10.10.134.203:53707 of length 91.

    Assigning socket to 10.10.134.203:53707.

    Transmitting request from 10.10.134.203:53707 of length 91 to 10.10.134.205.

    Received request from 127.0.0.1:53709 of length 63.

    Assigning socket to 127.0.0.1:53709.

    Transmitting request from 127.0.0.1:53709 of length 63 to 10.10.134.205.

    Received response from 10.10.134.205:427 of length 492.

    Transmitting response from 10.10.134.205:427 of length 492 to 127.0.0.1:53709.

    Destroying socket for 10.10.134.203:53685 because of timeout.

    Destroying socket for 10.10.134.203:53687 because of timeout.

    Destroying socket for 10.10.134.203:53689 because of timeout.

    Destroying socket for 10.10.134.203:53691 because of timeout.

    Destroying socket for 10.10.134.203:53693 because of timeout.

    Destroying socket for 10.10.134.203:53695 because of timeout.

    Destroying socket for 127.0.0.1:53697 because of timeout.

    Destroying socket for 10.10.134.203:53698 because of timeout.

    Destroying socket for 10.10.134.203:53701 because of timeout.

    Destroying socket for 10.10.134.203:53703 because of timeout.

    Destroying socket for 10.10.134.203:53705 because of timeout.

    Destroying socket for 10.10.134.203:53707 because of timeout.

    Destroying socket for 127.0.0.1:53709 because of timeout.

    • http://TinkerTry.com/about Paul Braren

      I haven’t had a chance to upgrade my 9265-8i yet (firmware/vib, under ESXi 5.5), so I don’t yet know what to do about this issue. If anybody has contacted LSI support
      http://www.lsi.com/company/contact/pages/support.aspx
      about this already, please share resolution with us. Thanks!

      • Patryk Wojtachnio

        Hello

        I installed .vip into my ESXi 5.5
        Latest MegaRAID SMIS ProviderVMWare 5.xSep 23, 2013
        http://www.lsi.com/products/raid-controllers/pages/megaraid-sas-9271-8i.aspx#tab/tab3

        Also please visit my home lab project called Virtual Olivia :)

        http://www.fb.com/VirtualOlivia
        http://www.youtube.com/VirtualOlivia

        and soon web page

        http://www.VirtualOlivia.com :)

        • http://TinkerTry.com/about Paul Braren

          My Polish is rather weak, but I know some people…
          That video, now that I understand, looks familiar!
          Usually, I just rely on Google Translate, the lazy American way ;-)
          Good luck on your endeavors Patryk, stay in touch!

      • frolic78

        Hello

        since I upgraded from ESXi 5.1. to 5.5 the MSM does not show my ESX Server with the IBM ServeRAID M5014 controller.

        Not from Windows 8 with 13.08.04.01_Windows_MSM nor to old school way with slp_helper, very bad :-(
        So I learned again, don’t touch a running system :-)
        Hope someone has a solution

  • http://TinkerTry.com/about Paul Braren

    multiflex:
    You practically wrote my new article that I had worked on, THANK YOU!

    It’ll be entitled something like “How to make ESXi 5.5 see the health of an LSI 9265-8i RAID controller and array (seems to work with all 92xx controllers)”
    but the reason it was still a draft was this little problem: it didn’t work!

    Much like many others have noticed, I played around a couple of weeks ago for about 2 hours, with about 6 different Windows 8.1 VMs, and never got it to see my LSI 9265-8i again, even with firewall disabled, and with that IP helper re-added, nada, always 0.0.0.0 for the ESXi host.

    So, can you share with us, what operating system was your VM running? Any other pertinent details (host file tweaks, etc)?

    Thanks again!

    • multiflex

      I have edited the hosts file in the same way as your previous guides (otherwise I only get 0.0.0.0 as well).
      The host I’ve tested on is running Windows 2008 R2 SP1.

  • http://TinkerTry.com/about Paul Braren

    Interesting that the driver you’re using is Dec 2013, that must be the key here.

    Trying now:

    esxcli software vib install -v /tmp/scsi-megaraid-sas-6.602.54.00-1OEM.550.0.0.1198610.x86_64.vib

    • http://TinkerTry.com/about Paul Braren

      Driver installed, next up, try MSM in a VM again.
      By the way, does your BBU (RAID battery) status show up under health?
      Mine didn’t with the driver ESXi 5.5 came with, nor does it with the newer driver you pointed us to.

  • Sokolum

    Are you aware of installing the following VIB (or an earlier version), the ‘IP Helper’ tool is not needed?

    LSI_bootbank_lsiprovider_500.04.V0.39-0006.vib

    esxcli software vib install -v /tmp/LSI_bootbank_lsiprovider_500.04.V0.38-0006.vib –no-sig-check

    Ofcourse enable ‘CIM Server’ on your ESXI and you are able to run Megaraid Storage Manager from a VM and controll you M5015 or such.

    • http://TinkerTry.com/about Paul Braren

      Sokolum, thank you!
      I did make mention above, pasted below here as well. And yes, it’s cool that it works without it! Well, at least until 5.5, where MegaRAID no longer works. I’m also hearing from LSI that there is no official support for 9265-8i in ESXi 5.5, sigh…will try to write something up about that.

      *Oct. 15, 2012 Update:
      You no longer need the custom utility! LSI has fixed this discovery problem, with MSM 5.4, you can now get your VM’s MSM to “see” the CIMON running on your ESXi 5.1 host. It’s all explained and shown at:
      LSI 9265-8i 5.1 October 8, 2012 Firmware 1881 for LSI CacheCade and non-CacheCade RAID controllers has arrived

  • Claudio

    In my configuration MSM work ONLY with slp_helper and option “Display all the ESXi-CIMOM servers in the network of local server.”

    Config:

    Guest Machine: Windows 8
    Controller RAID: IBM M5014 (Crossflash lsi 9260-8i)
    ESXI: 5.5
    Driver: scsi-megaraid-sas-6.602.54.00-1OEM.550.0.0.1198610.x86_64.vib
    MegaRAID SMIS Providers: 00.50.V0.04
    MegaRAID Storage Manager (Windows): 13.11.01.00

    • http://TinkerTry.com/about Paul Braren

      Wow, excellent details, thank you Claudio!

      Still failing to get my working with ESXi 5.5, and the wave of LSI drivers and SMIS provider updates that came out last weekend, whether I’m on 8.1 or 2008R2, with our without slp_helper. This is a time consuming annoyance, no doubt!

  • Cyril

    It works well with IBM M1015 so I’m sure it’ll work with M5015/M5014 and LSI 9260-8i on VM Server 2012. The tricky thing for me was to edit the hosts file because the software was seeing 0.0.0.0 for the IP address. You really have to use the FQDN of the server to have it to work. Pretty nice trick, thanks again!

  • Pat

    By the way, Paul, after watching this video, I was able to get my 9266-8i to be recognized/viewed/programmed from my Win 8.1 Pro VM this evening.
    I have only had my new ESXI 5.5 machine running for about 1 day now.

    With all your training and videos it appears the sky is the limit~

    Thanks again…… Super explanations!

    • http://TinkerTry.com/about Paul Braren

      Cool, thank you Pat!

      Got my 9265-8i working under ESXi 5.5. Only if I use the fully qualified domain name in the MegaRAID system’s host file (taken from the esxi /etc/hosts file) does it all work.

  • Pat

    Well, I do not know what I did, but it does not work today. I have been trying for a while now.

    Where is the MegaRaids system hosts file? Is that the same as the esxi’s hosts file or does it reside in the card and I have to use the cli to access it. How do I do that? Maybe I should watch some more videos??

  • Pat

    While I was in the MegaRaid Ui in my Win 8.1 Pro, I was able to upgrade my firmware in the LSI card. It takes effect after boot, so do you think that might have broken something?

  • Pat

    When ping the host (esxi) the VM sees the host?

  • Pat

    Well, again, It would certainly be wonderful if I knew something about what I am doing. The MegaRaid UI is now working again through the VM again. I just rebooted again?

    Imagine that> ?

    Thanks again and again….

  • http://TinkerTry.com/about Paul Braren

    Got an answer for you here (sorry, it’s an old device):
    http://www.tinkertry.com/installvsphere55/#comment-1103237691
    http://www.tinkertry.com/installvsphere55/#comment-1246722652
    this newer device woudl likely be a whole lot more practical:
    http://amzn.to/1jGMD1G

    and is something whitebox builder Mark Gabryjelskiis is rather fond of:
    http://www.tinkertry.com/superguide-home-virtualization-server-enthusiasts-colorful-variety-of-esxi-whiteboxes
    featured also in his video:
    YouTube.com/channel/UCNwtoV_iLvZy1fTcVl5UnUg

  • http://www.nanok-consulting.dk Martin Kingo

    So… Thanks a lot for this GREAT article – as I see many people have had some problems with this… An so have I…

    Setup:
    VMware ESXi vers. 5.1
    VMware ESXi 5.5 Driver: scsi-megaraid-sas-6.602.54.00-1OEM.550.0.0.1198610.x86_64.vib
    LSI SMIS: MR6.2

    After following this article I easyly could se an connect via MSM, however when loggin in it just “hangging” (see pict)

    It looks like it gets some kind of timeout??

    Anyone have any Idea??

    * I have also tried with MSM vers. 13

    Martin

    • http://TinkerTry.com/about Paul Braren

      I have some confidence we can fix this, but it may take a bit of back and forth, given I’ve been on 5.5 for some time (so have no way to reproduce your circumstance in 5.1).

      It’s important that the Windows hosts file exactly matching whatever is in the ESXi host file, seen pictured here. It seems my DHCP router likes to feed a fully qualified domain name of .ri.cox.net (Cox Communications is my ISP). This has implications, strangely enough, on MSM, it’s VERY particular.

      Using PuTTY or WinSCP to have a look at your ESXi host’s /etc/hosts file (see picture here). Put the entire line that’s in there for your ESXi host, and past that into your Windows c:windowssystem32driversetchosts file (you’ll need to be at CMD as Admin), and suddenly, you’ll find the “Configure Host…” dialogue in MegaRAID, followed by “Display all the ESXi-CIMOM servers in the network of local server.” works (also pictured here).

      Let us know how it goes!

      (I realize I really need to revisit this topic on ESXi 5.5, with a whole new article, meanwhile, this host file matching works there, assuming the right driver is used)

    • Kenneth Wellin

      @Martin Kingo: Same problem here. ESXi 5.5 / IBM X3650 server with M5110e controller (LSI 9286CV-8e)
      Have you managed to get this working yet?
      Kenneth

  • deblex

    Thank you very much for all your work (again!)

    I’ve got monitoring working with MSM for an LSI 9260-8i inside an esxi 5.5 (homelab) within a Win 8.1 VM thanks to your article.

  • Krisztian Hegyvari

    I spent a hell of a time to make this work, because I got 127.0.0.1 instead of 0.0.0.0 as my discovered ip address. After a lot of thinking I realized that the only way a discovery would tell me 127.0.0.1 is because the esxi reported itself as localhost. I logged in with SSH, typed hostname in the console and the hostname was localhost. I changed the hostname, rebooted the host and the ip reported back was 0.0.0.0. After that I followed the instructions with the hostfile to have matching entries for both host and client and it worked. I guess there are other people like me who just does not care and enter/next their way through the setup.

    • http://TinkerTry.com/about Paul Braren

      :-)

  • Sebastien Couture

    Wow thanks!! That help a lot !! Did you figure out how to detect automaticly the server in MSM?

    • http://TinkerTry.com/about Paul Braren

      No, not an automatic way, I just click to discover each time I have to restart the MegaRAID UI.