Does anyone have the slightest clue on how to monitor a LSI MegaRAID SCSI 320-1 adapter in a Linux environent? I've stared myself blind on LSI's website trying to find a way. Preferably a monitoring system that can send alerts via e-mail or to a monitoring client on a WinXP system. -- Anders Norrbring Norrbring Consulting
On Tue, 2005-08-02 at 19:43 +0200, Anders Norrbring wrote:
Does anyone have the slightest clue on how to monitor a LSI MegaRAID SCSI 320-1 adapter in a Linux environent? I've stared myself blind on LSI's website trying to find a way. Preferably a monitoring system that can send alerts via e-mail or to a monitoring client on a WinXP system.
--
Anders Norrbring Norrbring Consulting
First off get this package from LSI. http://www.lsilogic.com/downloads/license.do?id=2000&did=7776&pid=2411 It is the driver package for SuSe 9.1. In that drive packagte is a directory called Utilities then MegaMON. In MegaMON is a file named lsi_v35.tgz. do a tar -xzvf lsi_v35.tgz. This is the monitor app you will need. Then do a ./install -Suse. This will install the binaries and install the startup script of raidmon in /etc/init.d and set itself to start on the runlevels. I have modified my raidmon file to include some other items. Below is mine: ------------------------------------------------------------ #!/bin/sh # # chkconfig: 2345 20 80 # description: RAIDMon is a daemon that monitors the RAID subsystem # And generates e-mail to root # processname: MegaServ. # source function library . /lib/lsb/init-functions case "$1" in start) megadevice="megadev0" rm -f /dev/$megadevice 2>/dev/null megamajor=`cat /proc/devices|gawk '/megadev/{print$1}' ` mknod /dev/$megadevice c $megamajor 0 2>/dev/null # New check: 10-31-01: Does node exist if [ ! -c /dev/$megadevice ] then echo " Character Device Node /dev/$megadevice does not exist. Raid Monitor could not be started " exit 1 fi echo -n 'Starting RAID Monitor:' startproc /usr/sbin/MegaCtrl -start > /dev/null sleep 1 ; MegaCtrl -disMail touch /var/lock/subsys/raidmon MegaCtrl -enChkCon # check consistency on a Saturday at 01:00 very 4 weeks MegaCtrl -cons -h01 -w4 -d6 echo ;; stop) echo -n 'Stopping RAID Monitor:' startproc /usr/sbin/MegaCtrl -stop megadevice="megadev0" rm -f /dev/$megadevice 2>/dev/null rm -f /var/lock/subsys/raidmon 2>/dev/null echo ;; restart|reload) $0 stop $0 start ;; *) echo "RAID Monitor is not Started/Stopped" echo "Usage: raidmon {start|stop|restart}" exit 1 esac exit 0 ----------------------------------------------------------------------- Then just start the raidmon. The above changes tell my system to to a consistency check once a month at 1:00am. This make sure my RAID5 is working like it should. Also note there will be a log file of /var/log/megaserv.log. I use this setup on about a dozen production machines. It works perfectly. This will work on 32bit and 64bit machines. Brad Dameron SeaTab Software www.seatab.com
On 2005-08-02 20:05 Brad Dameron wrote:
On Tue, 2005-08-02 at 19:43 +0200, Anders Norrbring wrote:
Does anyone have the slightest clue on how to monitor a LSI MegaRAID SCSI 320-1 adapter in a Linux environent? I've stared myself blind on LSI's website trying to find a way. Preferably a monitoring system that can send alerts via e-mail or to a monitoring client on a WinXP system.
--
Anders Norrbring Norrbring Consulting
First off get this package from LSI. http://www.lsilogic.com/downloads/license.do?id=2000&did=7776&pid=2411
It is the driver package for SuSe 9.1. In that drive packagte is a directory called Utilities then MegaMON. In MegaMON is a file named lsi_v35.tgz. do a tar -xzvf lsi_v35.tgz. This is the monitor app you will need.
Then do a ./install -Suse. This will install the binaries and install the startup script of raidmon in /etc/init.d and set itself to start on the runlevels.
I have modified my raidmon file to include some other items. Below is mine:
------------------------------------------------------------
#!/bin/sh # # chkconfig: 2345 20 80 # description: RAIDMon is a daemon that monitors the RAID subsystem # And generates e-mail to root # processname: MegaServ.
# source function library . /lib/lsb/init-functions
case "$1" in start) megadevice="megadev0" rm -f /dev/$megadevice 2>/dev/null megamajor=`cat /proc/devices|gawk '/megadev/{print$1}' ` mknod /dev/$megadevice c $megamajor 0 2>/dev/null # New check: 10-31-01: Does node exist if [ ! -c /dev/$megadevice ] then echo " Character Device Node /dev/$megadevice does not exist. Raid Monitor could not be started " exit 1 fi
echo -n 'Starting RAID Monitor:' startproc /usr/sbin/MegaCtrl -start > /dev/null sleep 1 ; MegaCtrl -disMail touch /var/lock/subsys/raidmon MegaCtrl -enChkCon # check consistency on a Saturday at 01:00 very 4 weeks MegaCtrl -cons -h01 -w4 -d6 echo ;; stop) echo -n 'Stopping RAID Monitor:' startproc /usr/sbin/MegaCtrl -stop megadevice="megadev0" rm -f /dev/$megadevice 2>/dev/null rm -f /var/lock/subsys/raidmon 2>/dev/null echo ;; restart|reload) $0 stop $0 start ;; *) echo "RAID Monitor is not Started/Stopped" echo "Usage: raidmon {start|stop|restart}" exit 1 esac
exit 0
-----------------------------------------------------------------------
Then just start the raidmon. The above changes tell my system to to a consistency check once a month at 1:00am. This make sure my RAID5 is working like it should.
Also note there will be a log file of /var/log/megaserv.log.
I use this setup on about a dozen production machines. It works perfectly. This will work on 32bit and 64bit machines.
Brad Dameron SeaTab Software www.seatab.com
Thanks Brad! I'll give it a try... I can't find any documentation on the MegaServ application though, any tips on where I can find it? -- Anders Norrbring Norrbring Consulting
On Tue, 2005-08-02 at 21:38 +0200, Anders Norrbring wrote:
Thanks Brad! I'll give it a try... I can't find any documentation on the MegaServ application though, any tips on where I can find it?
None that I know of. The MegaCtrl program is what set's the MegaServ options. Just run MegaCtrl -help to see a lot of the config. Most of it is self explanatory. Brad Dameron SeaTab Software www.seatab.com
On 2005-08-02 22:11 Brad Dameron wrote:
On Tue, 2005-08-02 at 21:38 +0200, Anders Norrbring wrote:
Thanks Brad! I'll give it a try... I can't find any documentation on the MegaServ application though, any tips on where I can find it?
None that I know of. The MegaCtrl program is what set's the MegaServ options. Just run MegaCtrl -help to see a lot of the config. Most of it is self explanatory.
Yep, I noticed after installing. Now on to the trickier part.. Can I use the Power Console Plus application to connect to the Linux system? After just glancing at the docs, it can only support Windows systems. Or does that just apply to the client and registration server functions? I guess I can do it by trial and error, but it's always nice to know in beforehand.. :) -- Anders Norrbring Norrbring Consulting
On Tue, 2005-08-02 at 22:21 +0200, Anders Norrbring wrote:
On 2005-08-02 22:11 Brad Dameron wrote:
On Tue, 2005-08-02 at 21:38 +0200, Anders Norrbring wrote:
Thanks Brad! I'll give it a try... I can't find any documentation on the MegaServ application though, any tips on where I can find it?
None that I know of. The MegaCtrl program is what set's the MegaServ options. Just run MegaCtrl -help to see a lot of the config. Most of it is self explanatory.
Yep, I noticed after installing. Now on to the trickier part.. Can I use the Power Console Plus application to connect to the Linux system? After just glancing at the docs, it can only support Windows systems. Or does that just apply to the client and registration server functions? I guess I can do it by trial and error, but it's always nice to know in beforehand.. :) --
Anders Norrbring Norrbring Consulting
Sorry, never used the application. Didn't have any need for it. You can view/edit your drive configurations using the MegaMGR application located in the utilities directory. I would be careful on what you change in there tho. However I think it limits what you can do for those reason's. Brad Dameron SeaTab Software www.seatab.com
On 2005-08-02 22:48 Brad Dameron wrote:
On Tue, 2005-08-02 at 22:21 +0200, Anders Norrbring wrote:
On 2005-08-02 22:11 Brad Dameron wrote:
On Tue, 2005-08-02 at 21:38 +0200, Anders Norrbring wrote:
Thanks Brad! I'll give it a try... I can't find any documentation on the MegaServ application though, any tips on where I can find it?
None that I know of. The MegaCtrl program is what set's the MegaServ options. Just run MegaCtrl -help to see a lot of the config. Most of it is self explanatory.
Yep, I noticed after installing. Now on to the trickier part.. Can I use the Power Console Plus application to connect to the Linux system? After just glancing at the docs, it can only support Windows systems. Or does that just apply to the client and registration server functions? I guess I can do it by trial and error, but it's always nice to know in beforehand.. :) --
Anders Norrbring Norrbring Consulting
Sorry, never used the application. Didn't have any need for it. You can view/edit your drive configurations using the MegaMGR application located in the utilities directory. I would be careful on what you change in there tho. However I think it limits what you can do for those reason's.
I'm more looking at getting reports from the monitor, the config part is pretty static in the system, so I don't really care about other config tools than the one in BIOS on the adapter. I tried to enable mailing in the MegaCtrl app, it really spams e-mails at start-up.. Oh well, I'll look into it, I'll post my findings. ;) -- Anders Norrbring Norrbring Consulting
On Tue, 2005-08-02 at 22:54 +0200, Anders Norrbring wrote:
I'm more looking at getting reports from the monitor, the config part is pretty static in the system, so I don't really care about other config tools than the one in BIOS on the adapter. I tried to enable mailing in the MegaCtrl app, it really spams e-mails at start-up.. Oh well, I'll look into it, I'll post my findings. ;) --
Anders Norrbring Norrbring Consulting
Are you using my raidmon script? It has the reporting in it. I have had drives fail, battery fail and it reports it to me in a single email. Brad Dameron SeaTab Software www.seatab.com
On 2005-08-03 01:55 Brad Dameron wrote:
On Tue, 2005-08-02 at 22:54 +0200, Anders Norrbring wrote:
I'm more looking at getting reports from the monitor, the config part is pretty static in the system, so I don't really care about other config tools than the one in BIOS on the adapter. I tried to enable mailing in the MegaCtrl app, it really spams e-mails at start-up.. Oh well, I'll look into it, I'll post my findings. ;) --
Anders Norrbring Norrbring Consulting
Are you using my raidmon script? It has the reporting in it. I have had drives fail, battery fail and it reports it to me in a single email.
Maybe I was stupid, I enabled mail in the start script you provided, so it sent me a bunch of mails for every finding at startup. I guess I should let it settle first and not enable mail until its done its initial checks. I'll do some testing with it. Oh, it doesn't seem like the Power Console Plus works for servers on Linux. :( -- Anders Norrbring Norrbring Consulting
At 04:05 AM 3/08/2005, Brad Dameron wrote:
On Tue, 2005-08-02 at 19:43 +0200, Anders Norrbring wrote:
Does anyone have the slightest clue on how to monitor a LSI MegaRAID SCSI 320-1 adapter in a Linux environent? I've stared myself blind on LSI's website trying to find a way. Preferably a monitoring system that can send alerts via e-mail or to a monitoring client on a WinXP system.
--
Anders Norrbring Norrbring Consulting
First off get this package from LSI. http://www.lsilogic.com/downloads/license.do?id=2000&did=7776&pid=2411
It is the driver package for SuSe 9.1. In that drive packagte is a directory called Utilities then MegaMON. In MegaMON is a file named lsi_v35.tgz. do a tar -xzvf lsi_v35.tgz. This is the monitor app you will need.
Then do a ./install -Suse. This will install the binaries and install the startup script of raidmon in /etc/init.d and set itself to start on the runlevels.
I have modified my raidmon file to include some other items. Below is mine:
--
/cut WOW Thanks brad, as one who has to set up a new Server Farm in October, youvé saved me some work. Note to the unofficial FAQ Co-ordinator, can we have brad's origoinal (uncut Mail) added please somewhere. thanks to you both scsijon
* Brad Dameron (brad@seatab.com) [20050802 20:05]:
Then do a ./install -Suse. This will install the binaries and install the startup script of raidmon in /etc/init.d and set itself to start on the runlevels.
I've just had a look and this init script is bogus! The next time you run insserv (i.e. installing/updating/removing a package with init script) the runlevel links will be reset. Since 9.1 you should use LSB conforming init scripts if you want things to work correctly. At the end of the mail (because attachments aren't allowed) are apatch for the RAIDMon install script plus an init script that should work correctly on SUSE Linux. Just change to the raidmon directory, apply the patch with 'patch -p0 -i install.patch' and then call './install -suse'. Note that I haven't tested it! Philipp --------------------------->8 cut install.patch 8<------------------------------ --- install 2005/08/16 10:47:10 1.1 +++ install 2005/08/16 10:48:27 @@ -59,20 +59,14 @@ -suse|-Suse) rm -f /etc/init.d/raidmon 2>/dev/null - cp ./sus_rmon /etc/init.d/raidmon 2>/dev/null + cp ./suse-raidmon /etc/init.d/raidmon 2>/dev/null - ln -sf ../../init.d/raidmon /etc/rc.d/rc0.d/K80raidmon 2>/dev/null - ln -sf ../../init.d/raidmon /etc/rc.d/rc1.d/K80raidmon 2>/dev/null - ln -sf ../../init.d/raidmon /etc/rc.d/rc6.d/K80raidmon 2>/dev/null - ln -sf ../../init.d/raidmon /etc/rc.d/rc2.d/S20raidmon 2>/dev/null - ln -sf ../../init.d/raidmon /etc/rc.d/rc3.d/S20raidmon 2>/dev/null - ln -sf ../../init.d/raidmon /etc/rc.d/rc4.d/S20raidmon 2>/dev/null - ln -sf ../../init.d/raidmon /etc/rc.d/rc5.d/S20raidmon 2>/dev/null + insserv raidmon #cp ./MegaCt64 /usr/sbin/MegaCtrl 2>/dev/null cp ./MegaCt32 /usr/sbin/MegaCtrl 2>/dev/null cp ./MegaServ /usr/sbin 2>/dev/null - echo "Raidmon Installation on Suse Linux Completed" + echo "Raidmon Installation on SUSE Linux Completed" ;; *) ----------------------------------->8 cut 8<--------------------------- ------------------------>8 cut suse-raidmon 8<------------------- #! /bin/sh # Copyright (c) 1995-2005 SUSE Linux AG, Nuernberg, Germany. # All rights reserved. # # Author: Kurt Garloff # Please send feedback to http://www.suse.de/feedback/ # # /etc/init.d/raidmon # and its symbolic link # /(usr/)sbin/rcraidmon # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. # # LSB compatible service control script; see http://www.linuxbase.org/spec/ # ### BEGIN INIT INFO # Provides: raidmon # Required-Start: $ALL # Should-Start: $time sendmail # Required-Stop: $ALL # Should-Stop: $time sendmail # Default-Start: 2 3 5 # Default-Stop: 0 1 6 # Short-Description: Starts RAIDMon daemon to monitor RAID subsystems. # Description: Starts RIADMon to monitor RAID subsystems ### END INIT INFO # # Note on runlevels: # 0 - halt/poweroff 6 - reboot # 1 - single user 2 - multiuser without network exported # 3 - multiuser w/ network (text mode) 5 - multiuser w/ network and X11 (xdm) # # Note on script names: # http://www.linuxbase.org/spec/refspecs/LSB_1.3.0/gLSB/gLSB/scrptnames.html # A registry has been set up to manage the init script namespace. # http://www.lanana.org/ # Please use the names already registered or register one or use a # vendor prefix. # Check for missing binaries (stale symlinks should not happen) # Note: Special treatment of stop for LSB conformance RAIDMON_BIN=/usr/sbin/MegaCtrl test -x $FOO_BIN || { echo "$FOO_BIN not installed"; if [ "$1" = "stop" ]; then exit 0; else exit 5; fi; } # Check for existence of needed config file and read it FOO_CONFIG=/etc/sysconfig/FOO test -r $FOO_CONFIG || { echo "$FOO_CONFIG not existing"; if [ "$1" = "stop" ]; then exit 0; else exit 6; fi; } # Read config #. $FOO_CONFIG # Source LSB init functions # providing start_daemon, killproc, pidofproc, # log_success_msg, log_failure_msg and log_warning_msg. # This is currently not used by UnitedLinux based distributions and # not needed for init scripts for UnitedLinux only. If it is used, # the functions from rc.status should not be sourced or used. #. /lib/lsb/init-functions # Shell functions sourced from /etc/rc.status: # rc_check check and set local and overall rc status # rc_status check and set local and overall rc status # rc_status -v be verbose in local rc status and clear it afterwards # rc_status -v -r ditto and clear both the local and overall rc status # rc_status -s display "skipped" and exit with status 3 # rc_status -u display "unused" and exit with status 3 # rc_failed set local and overall rc status to failed # rc_failed <num> set local and overall rc status to <num> # rc_reset clear both the local and overall rc status # rc_exit exit appropriate to overall rc status # rc_active checks whether a service is activated by symlinks . /etc/rc.status # Reset status of this service rc_reset # Return values acc. to LSB for all commands but status: # 0 - success # 1 - generic or unspecified error # 2 - invalid or excess argument(s) # 3 - unimplemented feature (e.g. "reload") # 4 - user had insufficient privileges # 5 - program is not installed # 6 - program is not configured # 7 - program is not running # 8--199 - reserved (8--99 LSB, 100--149 distrib, 150--199 appl) # # Note that starting an already running service, stopping # or restarting a not-running service as well as the restart # with force-reload (in case signaling is not supported) are # considered a success. megadevice="megadev0" case "$1" in start) rm -f /dev/$megadevice 2>/dev/null megamajor=`cat /proc/devices|gawk '/megadev/{print$1}' ` mknod /dev/$megadevice c $megamajor 0 2>/dev/null # New check: 10-31-01: Does node exist if [ ! -c /dev/$megadevice ] then echo " Character Device Node /dev/$megadevice does not exist. Raid Monitor could not be started " exit 1 fi echo -n "Starting RAID Monitor: " ## Start daemon with startproc(8). If this fails ## the return value is set appropriately by startproc. startproc $FOO_BIN -start # Remember status and be verbose rc_status -v ;; stop) echo -n "Shutting down RAID Monitor: " ## Stop daemon with killproc(8) and if this fails ## killproc sets the return value according to LSB. killproc -TERM $FOO_BIN rm -f /dev/$megadevice 2>/dev/null # Remember status and be verbose rc_status -v ;; try-restart|condrestart) ## Do a restart only if the service was active before. ## Note: try-restart is now part of LSB (as of 1.9). ## RH has a similar command named condrestart. if test "$1" = "condrestart"; then echo "${attn} Use try-restart ${done}(LSB)${attn} rather than condrestart ${warn}(RH)${norm}" fi $0 status if test $? = 0; then $0 restart else rc_reset # Not running is not a failure. fi # Remember status and be quiet rc_status ;; restart) ## Stop the service and regardless of whether it was ## running or not, start it again. $0 stop $0 start # Remember status and be quiet rc_status ;; force-reload) ## Signal the daemon to reload its config. Most daemons ## do this on signal 1 (SIGHUP). ## If it does not support it, restart. echo -n "Reload service RAID Monitor " ## if it supports it: killproc -HUP $FOO_BIN #touch /var/run/FOO.pid rc_status -v ## Otherwise: #$0 try-restart #rc_status ;; reload) ## Like force-reload, but if daemon does not support ## signaling, do nothing (!) # If it supports signaling: echo -n "Reload service RAID Monitor " killproc -HUP $FOO_BIN #touch /var/run/FOO.pid rc_status -v ## Otherwise if it does not support reload: #rc_failed 3 #rc_status -v ;; status) echo -n "Checking for RAID Monitor " ## Check status with checkproc(8), if process is running ## checkproc will return with exit status 0. # Return value is slightly different for the status command: # 0 - service up and running # 1 - service dead, but /var/run/ pid file exists # 2 - service dead, but /var/lock/ lock file exists # 3 - service not running (unused) # 4 - service status unknown :-( # 5--199 reserved (5--99 LSB, 100--149 distro, 150--199 appl.) # NOTE: checkproc returns LSB compliant status values. checkproc $FOO_BIN # NOTE: rc_status knows that we called this init script with # "status" option and adapts its messages accordingly. rc_status -v ;; probe) ## Optional: Probe for the necessity of a reload, print out the ## argument to this init script which is required for a reload. ## Note: probe is not (yet) part of LSB (as of 1.9) test /etc/FOO/FOO.conf -nt /var/run/FOO.pid && echo reload ;; *) echo "Usage: $0 {start|stop|status|try-restart|restart|force-reload|reload|probe}" exit 1 ;; esac rc_exit --------------------------------->8 cut 8<-------------------------------- -- Philipp Thomas <pth AT suse.de> Research & Development SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuremberg, Germany
participants (4)
-
Anders Norrbring
-
Brad Dameron
-
Philipp Thomas
-
scsijon