VMware Cloud Community
VistaTec
Contributor
Contributor

How to check automatically LSI RAID 9240 controller health status

Hi,

how can I check status of my controller ? ESXi5

I can see it but how can I receive a mail or something other in case of drive failure ? (maybe from virtual machine running in the host

Is there a step by step guide ?

Thanks in advance

bsa

status.jpg

0 Kudos
24 Replies
Dave_Mishchenko
Immortal
Immortal

It seems that you just have a stand alone host.  Is that correct?   If you have vCenter it can be configured to send alerts by email.

For a standalone host there are scripts that can be run to check the heath status or you could use a tool like Veeam Monitor (free edition) - http://www.veeam.com/esxi-monitoring-free.html?ad=menu

0 Kudos
VistaTec
Contributor
Contributor

Dave,

you are correct, I have a standalone ESXi5 free host and I'm a newbie.

Can you point me to the exact vCenter link you are talking about ?

As I have installed the smis LSI provider following thi post (http://tinkertry.com/lsi92658iesxi5/)  looking for this paragraph (Click this button to view my ill-fated attempt to run MegaRAID from within a VM), I supposed to be ok with the stuff:

  1. check for a remote host using LSI MegaRaidStorageManager or
  2. within a VM (ubuntu) inside the host with the megacli tools.

But I was not be able to get the goal.

Many thx

Bsa

0 Kudos
VistaTec
Contributor
Contributor

ahi !

maybe I have made a mixup but I'm not able to find the right way

Below the LSI provider

Thanks in advance

lsi.jpg

0 Kudos
DCValentine
Contributor
Contributor

I have been able to use the LSI MegaRaid Storage Manager (ver: LSI MegaRaid Storage Manager 6.50-11) for Windows to send SMTP mail (when RAID failure event occurs) on a VM hosted by ESXi 5.0.  Althought this was with DELL PERC 5/e and 6/e Raid controllers, both mfg by LSI.

I had to reference several source to accomplish this task.  Below are the references I used.

Have you looked at this video:  Video for current LSI MSM walk thru although for more current LSI cards.

http://www.youtube.com/watch?v=wJVwiSuyFNc

My notes on the implementation of PERC 6/E on ESXi 5.0

http://www.vm-help.com/forum/viewtopic.php?f=31&t=3360

LSI write up on this subject.

http://kb.lsi.com/KnowledgebaseArticle16430.aspx?Keywords=esxi

I have read that you may be require to open the firewall on the ESXi host for the ports used by the more current version of LSI MSM, but can't confirm.

0 Kudos
VistaTec
Contributor
Contributor

Poor man.

No steps forward 😞

Tried your way but, maybe, made some mistakes.

Anyway the strange is that I have found in LSI doc this paragraph:

The MegaRAID Storage Manager software requires ports 3071 and 5571 to be open to
function. Follow these steps to prepare to run the MegaRAID Storage Manager Remote
Administration.

while my ESXi5 firewall is configured with CIM 5988/5989:

cim_1.jpg

So I tried with MSM installed on my remote PC and looked at used ports:

cim_2.jpg

192.168.0.8 is my PC

192.168.0.155 is a ws2003 hosted on esxi5 with MSM installed and not working as you suggested

192.168.0.140 is ESXi5 server that in this list was not discovered.

then tried to stop esxi5 firewall with this link

http://www.maartendamen.com/2011/10/disable-firewall-on-esxi/

but without any result.

Any advice ?

Thanks

bsa

0 Kudos
DCValentine
Contributor
Contributor

Question:

  • Which version of LSI MSM have you installed?  assuming you installed 9.00-01_Windows_MSM.zip?
  • DId you add entries in your HOSTS files for both your ESXi 5.0 and your VM with LSI MSM installed?

Create exceptions for LSI_MSM on the ESXi firewall.

1) SSH Console (via PUTTY or similar). Created a File named: LSI_MSM.xml, on your ESXi 5.0 Host.... in the location: /etc/vmware/firewall/

cd /etc/vmware/firewall/

vi LSI_MSM.xml

2) add the below CODE to the file... this will create the exceptions to the ESXi 5.0 Firewall.

<!-- Firewall configuration information for LSI MSM -->
<ConfigRoot>
<service>
  <id>LSI_MSM</id>
  <rule id='0000'>
   <direction>inbound</direction>
   <protocol>tcp</protocol>
   <porttype>dst</porttype>
   <port>5571</port>
  </rule>
  <rule id='0001'>
   <direction>outbound</direction>
   <protocol>tcp</protocol>
   <porttype>dst</porttype>
   <port>5571</port>
  </rule>
  <rule id='0002'>
   <direction>inbound</direction>
   <protocol>udp</protocol>
   <porttype>dst</porttype>
   <port>5571</port>
  </rule>
  <rule id='0003'>
   <direction>outbound</direction>
   <protocol>udp</protocol>
   <porttype>dst</porttype>
   <port>5571</port>
  </rule>
  <rule id='0004'>
   <direction>inbound</direction>
   <protocol>tcp</protocol>
   <porttype>dst</porttype>
   <port>3071</port>
  </rule>
  <rule id='0005'>
   <direction>outbound</direction>
   <protocol>tcp</protocol>
   <porttype>dst</porttype>
   <port>3071</port>
  </rule>
  <rule id='0006'>
   <direction>inbound</direction>
   <protocol>udp</protocol>
   <porttype>dst</porttype>
   <port>3071</port>
  </rule>
  <rule id='0007'>
   <direction>outbound</direction>
   <protocol>udp</protocol>
   <porttype>dst</porttype>
   <port>3071</port>
  </rule>
  <enabled>true</enabled>
  <required>true</required>
</service>
</ConfigRoot>

3) Refresh firewall to include above settings, Comfirm LSI_MSM exception is running, Confrim LSI_MSM ports configure correctly.

esxcli network firewall refresh

esxcli network firewall ruleset list

esxcli network firewall ruleset rule list | grep LSI_MSM

4) if all is correct SAVE the changes

/sbin/auto-backup.sh

0 Kudos
VistaTec
Contributor
Contributor

Valentine,

Which version of LSI MSM have you installed?  assuming you installed 9.00-01_Windows_MSM.zip?

yes, unistalled 11 and installed 9

DId you add entries in your HOSTS files for both your ESXi 5.0 and your VM with LSI MSM installed?

ESXi5

127.0.0.1        localhost.localdomain localhost
::1                localhost.localdomain localhost
192.168.0.155        ws2003.DOMAIN.LOCAL ws2003
192.168.0.140        vmware1

ws2003

127.0.0.1       localhost
192.168.0.140    vmware1.DOMAIN.LOCAL vmware1

Followed your way and Installed correctly FW exception: I was able to see open port,  but,

tryed agin with no host found.

Rebooted ESXi5 and ... no FW rules visible.

Maybe ESXi5 Free cannot do this steps ?

many thanks for you support

Bsa

0 Kudos
VistaTec
Contributor
Contributor

Hi guys,

does anybody have a clue ?

My mistake ?

My wrong question  or, better, a config mistake so, as a result, a stupid moveon ?

Thanks in advance.

bsa

0 Kudos
markm9999
Contributor
Contributor

where you ever able to get this to work?  If so, can you please post your solution.  i'm having similar problems.  Thanks!

0 Kudos
VistaTec
Contributor
Contributor

Hi mark, I would have written it. Smiley Sad

But, unfortunatley, I did not resolve anything, so I set the issue in standby waiting for someone to reply here.

Anyway, I found someone (you)  with the same issue and this peace a little be my anger as I'm not alone.

It seems all clear, though quite complicated, but it doesnt work.

Perhaps should we post this on LSI forum ?

regards

bsa

0 Kudos
markm9999
Contributor
Contributor

Vistatec,

I can confirm I got it working.  Exact steps a little foggy since I tried a bunch of things.

One thing for sure is I installed the ESXi 5 Update Rollup 2, found here http://downloads.vmware.com/d/details/rollupiso_50_2/dHRAYndlZEBiZHAlJQ==

The posts above helped me work through the issue of 0.0.0.0 address. Weird that when it discovers it, it shows an IP address but apparently this IP is actually the result of a DNS lookup of the name of the server (ESXi or otherwise) the LSI controller is in. In my case, I setup a static DNS value in our DNS server. Once I did that, 0.0.0.0 is now reported as the correct IP, and I'm able to connect.

Also, I did successfully connect with MSM v8.x, v9.x, and while I did seemingly have trouble with MSM v11.x to start, I'm now able to use it also.

I do have to investigate why I'm not seeing all the log entries though.  Not sure if this is a firmware issue or not.  This is also using v11.x.  I will also try another version shortly.

I'm planning on installing ESXi 5 on another box in the next week or so, so if the above doesn't work for you, post again and I'll be sure to report back any other steps I rediscover during that install. :smileygrin:

Mark

0 Kudos
Tomek24VMWARE
Contributor
Contributor

You can use OpenManage for manage RAID

0 Kudos
VistaTec
Contributor
Contributor

Hi Mark,

this sounds good.

So rollup2 works.

Unfortunately, as far as I know, it can be used only for fresh installation.

Maybe some guys skilled on VMware way know the roadmap for this kind of things.

Do you ?

Thanks

bsa

0 Kudos
VistaTec
Contributor
Contributor

Tomek,

can you point me to the exact link of this stuff ?

Do it work with Esx5 free ?

thanks

bsa

0 Kudos
Tomek24VMWARE
Contributor
Contributor

Yes is work on esxi free

try this http://vmblog.pl/link/223

0 Kudos
markm9999
Contributor
Contributor

Vistatec,

I successfully performed an 'upgrade' of the current install, despite what the release notes state.  You do need to boot off of the Rollup 2 CD.

Here is the 'Release Notes':

http://www.vmware.com/support/vsphere5/doc/vsphere-esxi-50-driver-rollup2-release-notes.html

Here is more on potential issues:

http://v-front.blogspot.com/2012/02/vsphere-hypervisor-esxi-50-driver.html

Most of issues I've read about are driver related per the above site link.  That is probably why the release notes state:

"If the installer in the ESXi 5.0 Driver Rollup 2 finds an existing ESXi installation, the installer displays an option to upgrade the existing installation
Do not select the option to upgrade an existing installation. The ESXi 5.0 Driver Rollup 2 is designed for fresh installations of ESXi hosts. VMware does not support using the ESXi 5.0 Driver Rollup 2 to upgrade an existing ESXi installation. If you use the ESXi 5.0 Driver Rollup 2 to perform a fresh installation on a system with an existing installation, the ESXi 5.0 Driver Rollup 2 installation will overwrite the existing installation. To preserve your existing installation, consider an alternate method to install the drivers."


However, in my case it updated the LSI driver just fine. YMMV.

I haven't yet done a fresh install on another box, though I'm still planning on doing this week or next.

VMWARE: Why do you release something called a 'ROLLUP' when it can supposedly only be installed as a 'fresh' install?

Mark

0 Kudos
markm9999
Contributor
Contributor

UPDATE:

While searching for more info for the post above, I found this:

Here is a link to the Release Notes:

http://downloads.vmware.com/d/details/esxi50u1/dHRAYndkZSpidHclZQ==#version_history

Download
VMware ESXi 5.0 Installable Update 1Download
Version5.0.0 U1
Build Number623860
Release Date2012/03/15
TypeProduct Binaries
ComponentsThis download contains the following components. Hide Details
ESXi 5.0 ISO image (Includes VMware Tools)
File size: 293M
File type: iso
Version: 5.0.0U1
MD5SUM: 38b9847bfd1737dc6bf82e2f7ec87d3c
SHA1SUM: 5de04f5c8951d82830ca3650183d3986c5cb2148
ESXi5.0 Offline Bundle
File size: 564M
File type: zip
Version: 5.0.0U1
MD5SUM: 55c25bd990e2881462bc5b66fb5f6c39
SHA1SUM: ecd871bb09b649c6c8c13de82d579d4b7dcadc88
VMware Tools 5.0 - CD image for Linux Guest OSes
File size: 107M
File type: iso
Version: 5.0.0U1
MD5SUM: 6f8fc854aec09b6a9284c63368258214
SHA1SUM: 3e0e29b28e04d22adfe2196f7a1a686ec53b3bdd
VMware vSphere Client 5.0
File size: 351M
File type: exe
Version: 5.0.0U1
MD5SUM: 0028875dc732477edc14d9fe48c6b773
SHA1SUM: 057b7b49942d4d35d6cb41f69e110c577329240a

Mark

VistaTec
Contributor
Contributor

Hi Mark,

many thanks for yours notes !!

And, I suppose, thanks to VMW to be able to answer so quickly to your prev message. :smileylaugh:

We will try it asap.

bsa

0 Kudos
markm9999
Contributor
Contributor

Ok,

As I'm new to VMware and have yet to RTFM, I did some test installs and here is what I found:

ESXi 5.0 VM Kernel Build (469512) [free download iso]

ESXi 5.0 VM Kernel Build (474610) [free download iso, updated using Rollup 1]

ESXi 5.0 VM Kernel Build (623860) [clean install using licensed iso of Update 1]

Only Rollup 1 worked for me regarding MegaRAID monitoring. Unfortunately, time constraints stopped me from being able to see what the cause is (driver or otherwise).

A fresh Google today though turned up something else of interest:

http://www.chriscolotti.us/vmware/vsphere/how-to-patch-vsphere-5-esxi-without-update-manager/

Which lead to this

http://www.vmware.com/patchmgr/findPatch.portal

Guess I need to study up on the 'proper' methodology and locations of downloads for updating ESXi 5, both free and licensed versions.

If anybody with advanced knowledge could post a 'quick' guide or links to same it would be much appreciated!

Mark

0 Kudos