From owner-freebsd-proliant@FreeBSD.ORG Sun Oct 29 04:39:28 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC86B16A407 for ; Sun, 29 Oct 2006 04:39:28 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: from mail4out.barnet.com.au (mail4.barnet.com.au [202.83.178.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C4A843D53 for ; Sun, 29 Oct 2006 04:39:28 +0000 (GMT) (envelope-from edwin@mavetju.org) Received: by mail4out.barnet.com.au (Postfix, from userid 1001) id 948DC37BAB0; Sun, 29 Oct 2006 15:39:27 +1100 (EST) X-Viruscan-Id: <4544307F00015DEC37035E@BarNet> Received: from mail4auth.barnet.com.au (mail4.barnet.com.au [202.83.178.125]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail4.barnet.com.au (Postfix) with ESMTP id 62B734360BE for ; Sun, 29 Oct 2006 15:39:27 +1100 (EST) Received: from k7.mavetju (k7.mavetju.org [10.251.1.18]) by mail4auth.barnet.com.au (Postfix) with ESMTP id 26EF737B5FC for ; Sun, 29 Oct 2006 15:39:27 +1100 (EST) Received: by k7.mavetju (Postfix, from userid 1001) id E1A90307; Sun, 29 Oct 2006 15:39:26 +1100 (EST) Date: Sun, 29 Oct 2006 15:39:26 +1100 From: Edwin Groothuis To: freebsd-proliant@freebsd.org Message-ID: <20061029043926.GI90772@k7.mavetju> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: RAID monitoring tools X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Oct 2006 04:39:28 -0000 Greetings, Last week we had two failing disks, and if it wasn't for a walk through the datacenter (which is off-site, and ten dollars away) we wouldn't have noticed it. I've read the thread about hpacucli, and have had my failed attempts to get it up and running under the linuxolator. So the question is: how do *you* monitor the status of your disks and RAID arrays? Any suggestions will be appriciated. Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://weblog.barnet.com.au/edwin/ From owner-freebsd-proliant@FreeBSD.ORG Sun Oct 29 12:16:02 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7475F16A403 for ; Sun, 29 Oct 2006 12:16:02 +0000 (UTC) (envelope-from Philippe.Pegon@crc.u-strasbg.fr) Received: from mailhost.u-strasbg.fr (mailhost.u-strasbg.fr [130.79.200.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id C38F443D72 for ; Sun, 29 Oct 2006 12:16:01 +0000 (GMT) (envelope-from Philippe.Pegon@crc.u-strasbg.fr) Received: from baal.u-strasbg.fr (baal.u-strasbg.fr [IPv6:2001:660:2402::41]) by mailhost.u-strasbg.fr (8.13.8/jtpda-5.5pre1) with ESMTP id k9TCFxgL006552 ; Sun, 29 Oct 2006 13:15:59 +0100 (CET) Received: from [IPv6:::1] (crc.u-strasbg.fr [IPv6:2001:660:2402:1001::1]) by baal.u-strasbg.fr (8.13.7/jtpda-5.5pre1) with ESMTP id k9TCFvXn096072 ; Sun, 29 Oct 2006 13:15:59 +0100 (CET) Message-ID: <45449B30.3000306@crc.u-strasbg.fr> Date: Sun, 29 Oct 2006 13:14:40 +0100 From: Philippe Pegon User-Agent: Thunderbird 1.5.0.7 (X11/20060917) MIME-Version: 1.0 To: Edwin Groothuis References: <20061029043926.GI90772@k7.mavetju> In-Reply-To: <20061029043926.GI90772@k7.mavetju> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.5/2129/Sun Oct 29 08:02:26 2006 on mr5.u-strasbg.fr X-Virus-Status: Clean X-Spam-Status: No, score=0.0 required=5.0 tests=AWL,NO_RELAYS autolearn=disabled version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mr5.u-strasbg.fr Cc: freebsd-proliant@freebsd.org Subject: Re: RAID monitoring tools X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Oct 2006 12:16:02 -0000 Edwin Groothuis wrote: > Greetings, > > Last week we had two failing disks, and if it wasn't for a walk > through the datacenter (which is off-site, and ten dollars away) > we wouldn't have noticed it. I've read the thread about hpacucli, > and have had my failed attempts to get it up and running under the > linuxolator. > > So the question is: how do *you* monitor the status of your disks > and RAID arrays? Any suggestions will be appriciated. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=86004+0+archive/2006/freebsd-questions/20060625.freebsd-questions > > Edwin > -- Philippe Pegon From owner-freebsd-proliant@FreeBSD.ORG Sun Oct 29 13:17:46 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE8E416A407 for ; Sun, 29 Oct 2006 13:17:46 +0000 (UTC) (envelope-from greg@wholemeal.net) Received: from mail9.messagelabs.com (mail9.messagelabs.com [194.205.110.133]) by mx1.FreeBSD.org (Postfix) with SMTP id F1B2C43D45 for ; Sun, 29 Oct 2006 13:17:45 +0000 (GMT) (envelope-from greg@wholemeal.net) X-VirusChecked: Checked X-Env-Sender: greg@wholemeal.net X-Msg-Ref: server-7.tower-9.messagelabs.com!1162127864!2399560!1 X-StarScan-Version: 5.5.10.7; banners=-,-,- X-Originating-IP: [212.135.210.82] Received: (qmail 8042 invoked from network); 29 Oct 2006 13:17:44 -0000 Received: from dsl-212-135-210-82.dsl.easynet.co.uk (HELO warprecords.com) (212.135.210.82) by server-7.tower-9.messagelabs.com with SMTP; 29 Oct 2006 13:17:44 -0000 Received: from [194.106.52.52] (HELO [192.168.0.2]) by warprecords.com (CommuniGate Pro SMTP 5.0.10) with ESMTPS id 6933440 for freebsd-proliant@freebsd.org; Sun, 29 Oct 2006 13:17:44 +0000 Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <20061029120043.A82EF16A5C3@hub.freebsd.org> References: <20061029120043.A82EF16A5C3@hub.freebsd.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Greg Eden Date: Sun, 29 Oct 2006 13:17:42 +0000 To: freebsd-proliant@freebsd.org X-Mailer: Apple Mail (2.752.2) Subject: Re: freebsd-proliant Digest, Vol 39, Issue 4 X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Oct 2006 13:17:46 -0000 On 29 Oct 2006, at 12:00, freebsd-proliant-request@freebsd.org wrote: > So the question is: how do *you* monitor the status of your disks > and RAID arrays? Any suggestions will be appriciated. I stumbled across this thread (http://atm.tut.fi/list-archive/freebsd- stable-2005/msg09274.html) recently which details one method, assuming you are using the ciss driver. Essentially you monitor syslog output for status changes from the driver. best. greg. From owner-freebsd-proliant@FreeBSD.ORG Mon Oct 30 02:08:25 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C89B16A407 for ; Mon, 30 Oct 2006 02:08:25 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF05B43D66 for ; Mon, 30 Oct 2006 02:08:20 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.128]) by hub.org (Postfix) with ESMTP id 82C8E3A1DE8 for ; Sun, 29 Oct 2006 22:08:12 -0400 (AST) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 50587-03-2 for ; Mon, 30 Oct 2006 02:07:05 +0000 (UTC) Received: from ganymede.hub.org (blk-137-86-60.eastlink.ca [24.137.86.60]) by hub.org (Postfix) with ESMTP id 89F453A1E11 for ; Sun, 29 Oct 2006 22:05:17 -0400 (AST) Received: by ganymede.hub.org (Postfix, from userid 1001) id 0420235441; Sun, 29 Oct 2006 22:10:21 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id F1F00346CA; Sun, 29 Oct 2006 01:51:09 -0300 (ADT) Date: Sun, 29 Oct 2006 01:51:09 -0400 From: "Marc G. Fournier" To: Edwin Groothuis , freebsd-proliant@freebsd.org Message-ID: In-Reply-To: <20061029043926.GI90772@k7.mavetju> References: <20061029043926.GI90772@k7.mavetju> X-Mailer: Mulberry/4.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Re: RAID monitoring tools X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Oct 2006 02:08:25 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 camcontrol devlist: at scbus0 target 0 lun 0 (pass0,da0) I don't have *regular* monitoring on it, mind you, just do it periodically, by hand ... - --On Sunday, October 29, 2006 15:39:26 +1100 Edwin Groothuis wrote: > Greetings, > > Last week we had two failing disks, and if it wasn't for a walk > through the datacenter (which is off-site, and ten dollars away) > we wouldn't have noticed it. I've read the thread about hpacucli, > and have had my failed attempts to get it up and running under the > linuxolator. > > So the question is: how do *you* monitor the status of your disks > and RAID arrays? Any suggestions will be appriciated. > > Edwin > > -- > Edwin Groothuis | Personal website: http://www.mavetju.org > edwin@mavetju.org | Weblog: http://weblog.barnet.com.au/edwin/ > _______________________________________________ > freebsd-proliant@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-proliant > To unsubscribe, send any mail to "freebsd-proliant-unsubscribe@freebsd.org" - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFRDM94QvfyHIvDvMRAtNdAKC+AYhavYxQ4qZzP4/zqsBfLirE6gCbBebW Oxd406ykkw1tElrfzn1Y/zM= =fgIA -----END PGP SIGNATURE----- From owner-freebsd-proliant@FreeBSD.ORG Mon Oct 30 12:30:24 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B18DC16A492 for ; Mon, 30 Oct 2006 12:30:24 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from talk.nabble.com (www.nabble.com [72.21.53.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA4E243DAB for ; Mon, 30 Oct 2006 12:29:59 +0000 (GMT) (envelope-from bounces@nabble.com) Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1GeWH9-0000KP-Fe for freebsd-proliant@freebsd.org; Mon, 30 Oct 2006 04:29:59 -0800 Message-ID: <7073519.post@talk.nabble.com> Date: Mon, 30 Oct 2006 04:29:59 -0800 (PST) From: Darren1010 To: freebsd-proliant@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: dniblett@hotmail.co.uk Subject: Windows 2003 R2 Server -SCSI Raid Array Issues X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Oct 2006 12:30:24 -0000 Hi, I have configured a Compaq DL380G2 server with 6x Ultra 160 Ultra 3 18.2GB SCSI drives. The raid array has been configured in ACU to use RAID 0+1 Mirroring for the first 2 drives. All other drives have not been added to the array. When booting to Windows 2003 and running Disk Management it shows jsut one basic Disk as being installed (18.2Gb). Is this correct for a RAID 0+1 or show I be seeing the 2nd mirrored drive? Does 2003 show the additional disks in the array or do I need to configure them in a RAID 5 array config. before it shows this configuration in disk management. Thanks -- View this message in context: http://www.nabble.com/Windows-2003-R2-Server--SCSI-Raid-Array-Issues-tf2539023.html#a7073519 Sent from the freebsd-proliant mailing list archive at Nabble.com. From owner-freebsd-proliant@FreeBSD.ORG Mon Oct 30 20:05:17 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8911516A415 for ; Mon, 30 Oct 2006 20:05:17 +0000 (UTC) (envelope-from mikhollo@cisco.com) Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AAB843D4C for ; Mon, 30 Oct 2006 20:05:15 +0000 (GMT) (envelope-from mikhollo@cisco.com) Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 30 Oct 2006 12:05:15 -0800 Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9UK5EfT015318 for ; Mon, 30 Oct 2006 12:05:14 -0800 Received: from [64.101.130.181] ([64.101.130.181]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k9UK5EW4010953 for ; Mon, 30 Oct 2006 12:05:14 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: References: <20061029043926.GI90772@k7.mavetju> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Mike Holloway Date: Mon, 30 Oct 2006 14:03:19 -0600 To: freebsd-proliant@freebsd.org X-Mailer: Apple Mail (2.752.2) DKIM-Signature: a=rsa-sha1; q=dns; l=4086; t=1162238714; x=1163102714; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mikhollo@cisco.com; z=From:Mike=20Holloway=20 |Subject:Re=3A=20RAID=20monitoring=20tools; X=v=3Dcisco.com=3B=20h=3D+pgVBaOaSKnCytkW0o7PqW/IAx0=3D; b=M/u55AQKPctW+lnxkFqyrPdTe2xsTzHLOXPNh1GxZxlYleOix9t8A6AypiYDYXEyfKv2ITZ7 UXsZEcDYxmEayc9yAIdCIiqZGn2UtsE79nhXrxyXEomCW5rRDUEhyu3C; Authentication-Results: sj-dkim-3.cisco.com; header.From=mikhollo@cisco.com; dkim=pass ( sig from cisco.com verified; ); Subject: Re: RAID monitoring tools X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Oct 2006 20:05:17 -0000 Whoops, meant to copy the list... Appreciate the pointer to camcontrol, I previously had just been using swatch to watch syslog and send messages to nagios via nsca. My problem was that I never knew the initial state of the disks until an event happened in syslog. For reference, here's what I saw from camcontrol during my tests (FreeBSD 6.0 rel): During normal operation of the raid: # camcontrol inquiry da0 -D pass0: Fixed Direct Access SCSI-0 device After removing one of the raid member disks: # camcontrol inquiry da0 -D pass0: Fixed Direct Access SCSI-0 device After re-inserting the raid member disk: # camcontrol inquiry da0 -D pass0: Fixed Direct Access SCSI-0 device And about 45 minutes later: # camcontrol inquiry da0 -D pass0: Fixed Direct Access SCSI-0 device And here's the configuration I use for swatch to feed nsca in realtime: watchfor /ciss0.*removed/ exec "/usr/local/bin/nsca_report 2 \"Disk Array\" Hot-plug drive removed" watchfor /ciss0.*failure/ exec "/usr/local/bin/nsca_report 2 \"Disk Array\" Physical drive failure" watchfor /ciss0.*inserted/ exec "/usr/local/bin/nsca_report 1 \"Disk Array\" Hot-plug drive inserted" watchfor /ciss0.*recovery->recovering/ exec "/usr/local/bin/nsca_report 1 \"Disk Array\" Drive is rebuilding..." watchfor /ciss0.*recovering->OK/ exec "/usr/local/bin/nsca_report 0 \"Disk Array\" Drive has successfully rebuilt." For completeness, here's the nsca_report script that I use to send the alarms to nagios, substitute your own thishost and -H: #!/bin/bash outcode=$1 thisservice=$2 thishost=`echo $HOSTNAME | sed -e "s/\./ /g" | cut -f 1 -d ' '` shift shift echo -e "${thishost}\t${thisservice}\t${outcode}\t$*\n" | /usr/local/ bin/send_nsca -H www -c /usr/local/etc/send_nsca.cfg 2>&1 >> /dev/null -mike On Oct 29, 2006, at 12:51 AM, Marc G. Fournier wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > camcontrol devlist: > > at scbus0 target 0 lun 0 > (pass0,da0) > > I don't have *regular* monitoring on it, mind you, just do it > periodically, by > hand ... > > > > - --On Sunday, October 29, 2006 15:39:26 +1100 Edwin Groothuis > wrote: > >> Greetings, >> >> Last week we had two failing disks, and if it wasn't for a walk >> through the datacenter (which is off-site, and ten dollars away) >> we wouldn't have noticed it. I've read the thread about hpacucli, >> and have had my failed attempts to get it up and running under the >> linuxolator. >> >> So the question is: how do *you* monitor the status of your disks >> and RAID arrays? Any suggestions will be appriciated. >> >> Edwin >> >> -- >> Edwin Groothuis | Personal website: http:// >> www.mavetju.org >> edwin@mavetju.org | Weblog: http:// >> weblog.barnet.com.au/edwin/ >> _______________________________________________ >> freebsd-proliant@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-proliant >> To unsubscribe, send any mail to "freebsd-proliant- >> unsubscribe@freebsd.org" > > > > - ---- > Marc G. Fournier Hub.Org Networking Services (http:// > www.hub.org) > Email . scrappy@hub.org MSN . > scrappy@hub.org > Yahoo . yscrappy Skype: hub.org ICQ . 7615664 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (FreeBSD) > > iD8DBQFFRDM94QvfyHIvDvMRAtNdAKC+AYhavYxQ4qZzP4/zqsBfLirE6gCbBebW > Oxd406ykkw1tElrfzn1Y/zM= > =fgIA > -----END PGP SIGNATURE----- > > _______________________________________________ > freebsd-proliant@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-proliant > To unsubscribe, send any mail to "freebsd-proliant- > unsubscribe@freebsd.org" From owner-freebsd-proliant@FreeBSD.ORG Tue Oct 31 16:55:26 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A0DF16A4FB for ; Tue, 31 Oct 2006 16:55:26 +0000 (UTC) (envelope-from mikhollo@cisco.com) Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C39343D8B for ; Tue, 31 Oct 2006 16:55:11 +0000 (GMT) (envelope-from mikhollo@cisco.com) Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 31 Oct 2006 08:55:11 -0800 Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-2.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9VGtBr7007606; Tue, 31 Oct 2006 08:55:11 -0800 Received: from [64.101.130.181] ([64.101.130.181]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k9VGtBin004364; Tue, 31 Oct 2006 08:55:11 -0800 (PST) In-Reply-To: <8D7B26B6-A16E-4ECD-812A-27E4E9DBF70B@warprecords.com> References: <8D7B26B6-A16E-4ECD-812A-27E4E9DBF70B@warprecords.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <675649FB-EDF5-43AD-9BE5-333BC33D0361@cisco.com> Content-Transfer-Encoding: 7bit From: Mike Holloway Date: Tue, 31 Oct 2006 10:53:12 -0600 To: freebsd-proliant@freebsd.org X-Mailer: Apple Mail (2.752.2) DKIM-Signature: a=rsa-sha1; q=dns; l=3338; t=1162313711; x=1163177711; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mikhollo@cisco.com; z=From:Mike=20Holloway=20 |Subject:Re=3A=20RAID=20monitoring=20tools; X=v=3Dcisco.com=3B=20h=3D+pgVBaOaSKnCytkW0o7PqW/IAx0=3D; b=PF4dxWGYkhvDoGldSFRGIb5ZrEGbrNFhsC3ZJlsd/D9Bk3C4XosRMYMiuEalVF8E5xIfR2ER zsHLLV1iEWU1/A72/V9pF9RKNAoY7ww6CW6MhWlbnFkGgpO5uhMTDrhw; Authentication-Results: sj-dkim-2.cisco.com; header.From=mikhollo@cisco.com; dkim=pass ( sig from cisco.com verified; ); Cc: Greg Eden Subject: Re: RAID monitoring tools X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Oct 2006 16:55:26 -0000 Greg, you might find this thread useful: http://lists.freebsd.org/pipermail/freebsd-proliant/2006-February/ 000058.html It contains a perl script to run hpasmcli and exit if it doesn't return in a reasonable amount of time. John also mentioned disabling ASR on the server in the post below, which seemed to fix my reboot problem. Unfortunately, even still, the hpasmcli utility on FreeBSD is unstable for me in it's current form. You may have different results. http://lists.freebsd.org/pipermail/freebsd-proliant/2006-February/ 000059.html -mike On Oct 31, 2006, at 8:17 AM, Greg Eden wrote: > > Hi there > > Thanks for this very useful post to the proliant list. i'm just in > the process of getting to grips with SNMP and nagios with my > proliant hardware running freebsd - this will help no end. > > another task i'm just starting on is using output from SHOW TEMP, > SHOW FANS from the hpasmd/hpasmcli tools to graph hardware info > with nrg. if i get anywhere with it i'll post it to the list. > > cheers > > greg. > > > >> Whoops, meant to copy the list... >> >> >> Appreciate the pointer to camcontrol, I previously had just been >> using swatch to watch syslog and send messages to nagios via nsca. >> My problem was that I never knew the initial state of the disks until >> an event happened in syslog. >> >> >> For reference, here's what I saw from camcontrol during my tests >> (FreeBSD 6.0 rel): >> >> During normal operation of the raid: >> # camcontrol inquiry da0 -D >> pass0: Fixed Direct Access SCSI-0 device >> >> After removing one of the raid member disks: >> # camcontrol inquiry da0 -D >> pass0: Fixed Direct Access SCSI-0 device >> >> After re-inserting the raid member disk: >> # camcontrol inquiry da0 -D >> pass0: Fixed Direct Access SCSI-0 device >> >> And about 45 minutes later: >> # camcontrol inquiry da0 -D >> pass0: Fixed Direct Access SCSI-0 device >> >> >> >> And here's the configuration I use for swatch to feed nsca in >> realtime: >> >> watchfor /ciss0.*removed/ >> exec "/usr/local/bin/nsca_report 2 \"Disk Array\" Hot-plug >> drive removed" >> >> watchfor /ciss0.*failure/ >> exec "/usr/local/bin/nsca_report 2 \"Disk Array\" Physical >> drive failure" >> >> watchfor /ciss0.*inserted/ >> exec "/usr/local/bin/nsca_report 1 \"Disk Array\" Hot-plug >> drive inserted" >> >> watchfor /ciss0.*recovery->recovering/ >> exec "/usr/local/bin/nsca_report 1 \"Disk Array\" Drive is >> rebuilding..." >> >> watchfor /ciss0.*recovering->OK/ >> exec "/usr/local/bin/nsca_report 0 \"Disk Array\" Drive has >> successfully rebuilt." >> >> >> >> For completeness, here's the nsca_report script that I use to send >> the alarms to nagios, substitute your own thishost and -H: >> >> #!/bin/bash >> >> outcode=$1 >> thisservice=$2 >> >> thishost=`echo $HOSTNAME | sed -e "s/\./ /g" | cut -f 1 -d ' '` >> >> shift >> shift >> >> echo -e "${thishost}\t${thisservice}\t${outcode}\t$*\n" | /usr/local/ >> bin/send_nsca -H www -c /usr/local/etc/send_nsca.cfg 2>&1 >> /dev/ >> null >> >> >> >> -mike