ANNOUNCE: saftemon - SCSI Enclosure monitor for linux

ANNOUNCE: saftemon - SCSI Enclosure monitor for linux

[Michael Clark]

saftemon - SCSI Enclosure monitor for SAFTE enclosures

   http://gort.metaparadigm.com/saftemon/

saftemon reads disk enclosure status information from SAF-TE
capable enclosures (SCSI Accessible Fault Tolerant Enclosures).
SAF-TE is a component of SES (SCSI Enclosure Services) which
is common on most SCSI disk enclosures these days. saftemon
can monitor multiple SAF-TE devices and will automatically probe
and detect them.

The information retreived includes power supply and fan status,
temperature, audible alarm, drive faults, array critical /
failed / rebuilding state and door lock status. saftemon logs
changes in the status of these enclosure elements to syslog and
can optionally execute an alert help program with details of the
component failure. This could send a pager message for example.
Temperate alert limits also be set.

saftemon is specifcally useful if you have equipment deployed in
remote locations or unattended over weekends when no-one may hear
an audible alarm.

It also includes an embedded web server for web status display
of enclosure information.

This is the initial public release so i'd be keen to receive any
feedback or compatibility testing. It has currently only been
tested on nStor external enclosures and Intel internal SAFTE
capable enclosures.

~mc

RE: ANNOUNCE: saftemon - SCSI Enclosure monitor for linux

[Matt_Domsch]

> saftemon - SCSI Enclosure monitor for SAFTE enclosures
> 
> This is the initial public release so i'd be keen to receive any
> feedback or compatibility testing. It has currently only been
> tested on nStor external enclosures and Intel internal SAFTE
> capable enclosures.

Works beautifully on my Dell PowerEdge 2400 internal SAFTE backplane.  We'll
give it a shot on our other SAFTE capable enclosures in the coming weeks.  

Thanks!
Matt

--
Matt Domsch
Sr. Software Engineer
Dell Linux Solutions www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
#1 US Linux Server provider for 2001!

Re: ANNOUNCE: saftemon - SCSI Enclosure monitor for linux

[Mathieu Chouquet-Stringer]

Matt_Domsch@Dell.com writes:
> > saftemon - SCSI Enclosure monitor for SAFTE enclosures
> > 
> > This is the initial public release so i'd be keen to receive any
> > feedback or compatibility testing. It has currently only been
> > tested on nStor external enclosures and Intel internal SAFTE
> > capable enclosures.
> 
> Works beautifully on my Dell PowerEdge 2400 internal SAFTE backplane.  We'll
> give it a shot on our other SAFTE capable enclosures in the coming weeks.  

Tested it too on my server and it works perfectly. Congratulations!

Cheers, Mathieu.
-- 
Mathieu Chouquet-Stringer              E-Mail : mathieu@newview.com
    It is exactly because a man cannot do a thing that he is a
                      proper judge of it.
                      -- Oscar Wilde

Re: ANNOUNCE: saftemon - SCSI Enclosure monitor for linux

[Michael Clark]

Matt_Domsch@Dell.com wrote:

>>saftemon - SCSI Enclosure monitor for SAFTE enclosures
>>
>>This is the initial public release so i'd be keen to receive any
>>feedback or compatibility testing. It has currently only been
>>tested on nStor external enclosures and Intel internal SAFTE
>>capable enclosures.
>>
>
>Works beautifully on my Dell PowerEdge 2400 internal SAFTE backplane.  We'll
>give it a shot on our other SAFTE capable enclosures in the coming weeks. 
>
You may have some trouble with some RAID HBAs that don't pass through
non disk devices (or maybe just processor devices). I have some Mylex HBAs
that I can't see the SAFTE processors through although my AMI Megaraids can.

~mc

Re: ANNOUNCE: saftemon - SCSI Enclosure monitor for linux

[Mathieu Chouquet-Stringer]

mathieu@newview.com (Mathieu Chouquet-Stringer) writes:
> Tested it too on my server and it works perfectly. Congratulations!
> 
> Cheers, Mathieu.

Well I spoke probably too fast. It work perfectly but only once...
Here's what I got (using saftemon -p):

Found 1 SAF-TE devices
SAF-TE Device DELL 1x8 U2W SCSI BP (2:0:6:0)
no. of fans           = 3
no. of power supplies = 0
no. of device slots   = 8
door lock installed   = 0
no. of temp sensors   = 2
audible alarm         = 0
no. of thermostats    = 0
fan 0 is operational
fan 1 is operational
fan 2 is operational
device slot 0 disk present,active,no error
device slot 1 disk present,active,no error
device slot 2 disk present,active,no error
device slot 3 disk present,active,no error
device slot 4 disk present,active,no error
device slot 5 disk present,active,no error
device slot 6 disk present,active,no error
device slot 7 disk present,active,no error
temp sensor 0 is 26.1 c and okay
temp sensor 1 is 26.7 c and okay
overall temperature is okay

Third tries, I got this:

Found 1 SAF-TE devices
SAF-TE Device DELL 1x8 U2W SCSI BP (2:0:6:0)
no. of fans           = 0
no. of power supplies = 0
no. of device slots   = 2
door lock installed   = 0
no. of temp sensors   = 32
audible alarm         = 0
no. of thermostats    = 0
device slot 0 disk not present
device slot 1 insert ready,parity check
temp sensor 0 is -5.6 c and okay
temp sensor 1 is -23.3 c and okay
temp sensor 2 is -23.3 c and okay
temp sensor 3 is 4.4 c and okay
temp sensor 4 is 19.4 c and okay
temp sensor 5 is 32.8 c and okay
temp sensor 6 is 33.9 c and okay
temp sensor 7 is 30.6 c and okay
temp sensor 8 is 22.2 c and okay
temp sensor 9 is 12.8 c and okay
temp sensor 10 is 17.2 c and okay
temp sensor 11 is 14.4 c and okay
temp sensor 12 is 18.9 c and okay
temp sensor 13 is 14.4 c and okay
temp sensor 14 is 3.3 c and okay
temp sensor 15 is -5.6 c and okay
temp sensor 16 is 0.0 c and okay
temp sensor 17 is 0.0 c and okay
temp sensor 18 is 0.0 c and okay
temp sensor 19 is 0.0 c and okay
temp sensor 20 is 0.0 c and okay
temp sensor 21 is 0.0 c and okay
temp sensor 22 is 0.0 c and okay
temp sensor 23 is 0.0 c and okay
temp sensor 24 is 0.0 c and okay
temp sensor 25 is 0.0 c and okay
temp sensor 26 is 0.0 c and okay
temp sensor 27 is 0.0 c and okay
temp sensor 28 is 0.0 c and okay
temp sensor 29 is 0.0 c and okay
temp sensor 30 is 0.0 c and okay
temp sensor 31 is 0.0 c and okay
overall temperature is okay

zsh: 24211 segmentation fault  saftemon -p

And now the daemon refuses to start and I have got this in the saftemon
logfile:
Wed Apr 17 11:18:06 2002 [25319] *** saftemon-0.0.4 starting
Wed Apr 17 11:18:06 2002 [25319] No SAF-TE devices present. exiting

Let me know if you want me to provide more data.

Regards, Mathieu.

-- 
Mathieu Chouquet-Stringer              E-Mail : mathieu@newview.com
    It is exactly because a man cannot do a thing that he is a
                      proper judge of it.
                      -- Oscar Wilde

RE: ANNOUNCE: saftemon - SCSI Enclosure monitor for linux

[Matthew Jacob]

will it also drive SES?


On Wed, 17 Apr 2002 Matt_Domsch@Dell.com wrote:

> > saftemon - SCSI Enclosure monitor for SAFTE enclosures
> > 
> > This is the initial public release so i'd be keen to receive any
> > feedback or compatibility testing. It has currently only been
> > tested on nStor external enclosures and Intel internal SAFTE
> > capable enclosures.
> 
> Works beautifully on my Dell PowerEdge 2400 internal SAFTE backplane.  We'll
> give it a shot on our other SAFTE capable enclosures in the coming weeks.  
> 
> Thanks!
> Matt
> 
> --
> Matt Domsch
> Sr. Software Engineer
> Dell Linux Solutions www.dell.com/linux
> Linux on Dell mailing lists @ http://lists.us.dell.com
> #1 US Linux Server provider for 2001!
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

RE: ANNOUNCE: saftemon - SCSI Enclosure monitor for linux

[Matt_Domsch]

> will it also drive SES?

Some Dell SCSI backplanes are SES capable, I believe that some aren't.  I'm
not sure off-hand of the matrix which is which.  Once we get some time to
investigate further I'll report back our findings.

Thanks,
Matt

--
Matt Domsch
Sr. Software Engineer
Dell Linux Solutions www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
#1 US Linux Server provider for 2001!

RE: ANNOUNCE: saftemon - SCSI Enclosure monitor for linux

[Les Niles]

A README.install would be useful:

On a stock RH7.2 system, after a ./configure, make all, and 
make install, the /var/run/saftemon and /var/log/saftemon 
directories ended up with permissions 0755, user root and group 
root.  This caused saftemon to die because it couldn't open the 
pid file in /var/run/saftemon after setuid(daemon).  I changed 
the ownership of those directories to daemon and now it seems 
to work.  (The saftemon startup script did not get installed in 
/etc/rc.d/init.d; I don't know if this is intentional.)  Nice!  
This is all on a PowerEdge 6450. 

It also does the right thing on a Tyan SCSI motherboard: "No 
SAF-TE devices present"

  -les

> -----Original Message-----
> From: Michael Clark [mailto:michael@metaparadigm.com]
> Sent: Wednesday, April 17, 2002 4:01 AM
> To: linux-scsi@vger.kernel.org
> Subject: ANNOUNCE: saftemon - SCSI Enclosure monitor for linux
> 
> 
> saftemon - SCSI Enclosure monitor for SAFTE enclosures
> 
>    http://gort.metaparadigm.com/saftemon/
> 
> saftemon reads disk enclosure status information from SAF-TE
> capable enclosures (SCSI Accessible Fault Tolerant Enclosures).
> SAF-TE is a component of SES (SCSI Enclosure Services) which
> is common on most SCSI disk enclosures these days. saftemon
> can monitor multiple SAF-TE devices and will automatically probe
> and detect them.

Re: ANNOUNCE: saftemon - SCSI Enclosure monitor for linux

[Michael Clark]

I seem to remember reading somewhere that SAF-TE is component of SES,
enough so for me to put it in the readme, but I can't back it up as I've 
never
had it run on a device that says it is SES capable.

I'd like to know too so I can correct the readme if need be.

cheers,
~mc

Matt_Domsch@Dell.com wrote:

>>will it also drive SES?
>>
>
>Some Dell SCSI backplanes are SES capable, I believe that some aren't.  I'm
>not sure off-hand of the matrix which is which.  Once we get some time to
>investigate further I'll report back our findings.
>
>Thanks,
>Matt
>
>--
>Matt Domsch
>Sr. Software Engineer
>Dell Linux Solutions www.dell.com/linux
>Linux on Dell mailing lists @ http://lists.us.dell.com
>#1 US Linux Server provider for 2001!
>

Re: ANNOUNCE: saftemon - SCSI Enclosure monitor for linux

[Michael Clark]

The SES command set is supposedly documented in the SFF-8067 specification
developed by an X3 committee. I assume is different to SAF-TE and have
removed the reference to it in the readme.

Michael Clark wrote:

> I seem to remember reading somewhere that SAF-TE is component of SES,
> enough so for me to put it in the readme, but I can't back it up as 
> I've never
> had it run on a device that says it is SES capable.
>
> I'd like to know too so I can correct the readme if need be.
>
> cheers,
> ~mc
>
> Matt_Domsch@Dell.com wrote:
>
>>> will it also drive SES?
>>>
>>
>> Some Dell SCSI backplanes are SES capable, I believe that some 
>> aren't.  I'm
>> not sure off-hand of the matrix which is which.  Once we get some 
>> time to
>> investigate further I'll report back our findings.
>>
>> Thanks,
>> Matt
>>
>> -- 
>> Matt Domsch
>> Sr. Software Engineer
>> Dell Linux Solutions www.dell.com/linux
>> Linux on Dell mailing lists @ http://lists.us.dell.com
>> #1 US Linux Server provider for 2001!
>>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: ANNOUNCE: saftemon - SCSI Enclosure monitor for linux

[Martin K. Petersen]

>>>>> "Michael" == Michael Clark <michael@metaparadigm.com> writes:

Michael> The SES command set is supposedly documented in the SFF-8067
Michael> specification developed by an X3 committee. I assume is
Michael> different to SAF-TE and have removed the reference to it in
Michael> the readme.

Yes.  SES is the successor to SAF-TE.

It's different in the sense that there's no SAF-TE processor device
visible on the bus.  Instead devices on an SES-capable bus will have
EnvServ set in the inquiry page.

I have some sample code kicking around, if you're interested.  Also,
the SES specs are official T10 ones (unlike SAF-TE).  You can download
them off t10.org.

-- 
Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc.
mkp@linuxcare.com, http://www.linuxcare.com/
SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/

Re: ANNOUNCE: saftemon - SCSI Enclosure monitor for linux

[Matthew Jacob]

No- SAF-TE was what an *early* version of SES looked like. Then it went it's
own way. Currently there is a bunch of SAF-TE chips out there (e.g. GEM-I and
GEM-II), but the spec is no longer owned by anyone and www.safte.org
disappeared over two years ago, so the ability to even find the spec is
limited to finding those who had downloaded both the .doc and the addendum.

Somebody out there correct me if I'm wrong.

At any rate, you *can* emulate SAF-TE within SES. In fact, it's better to
create an SES driver and then map SAF-TE into it (which is what I did for
Solaris && *BSD). There are a couple of global status items that don't map
easily- and the one wierd thing is to map the overtemp bits (all 17 of them)  
into SES temperature elements. Plus the conversion of SAF-TE temp ranges for
SAF-TE temp elements into SES temperature elements (different ranges). What a
PITA.

-matt


On Thu, 18 Apr 2002, Michael Clark wrote:

> I seem to remember reading somewhere that SAF-TE is component of SES,
> enough so for me to put it in the readme, but I can't back it up as I've 
> never
> had it run on a device that says it is SES capable.
> 
> I'd like to know too so I can correct the readme if need be.
> 
> cheers,
> ~mc
> 
> Matt_Domsch@Dell.com wrote:
> 
> >>will it also drive SES?
> >>
> >
> >Some Dell SCSI backplanes are SES capable, I believe that some aren't.  I'm
> >not sure off-hand of the matrix which is which.  Once we get some time to
> >investigate further I'll report back our findings.
> >
> >Thanks,
> >Matt
> >
> >--
> >Matt Domsch
> >Sr. Software Engineer
> >Dell Linux Solutions www.dell.com/linux
> >Linux on Dell mailing lists @ http://lists.us.dell.com
> >#1 US Linux Server provider for 2001!
> >
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: ANNOUNCE: saftemon - SCSI Enclosure monitor for linux

[Michael Clark]

Martin K. Petersen wrote:

>>>>>>"Michael" == Michael Clark <michael@metaparadigm.com> writes:
>>>>>>
>
>Michael> The SES command set is supposedly documented in the SFF-8067
>Michael> specification developed by an X3 committee. I assume is
>Michael> different to SAF-TE and have removed the reference to it in
>Michael> the readme.
>
>Yes.  SES is the successor to SAF-TE.
>
>It's different in the sense that there's no SAF-TE processor device
>visible on the bus.  Instead devices on an SES-capable bus will have
>EnvServ set in the inquiry page.
>
>I have some sample code kicking around, if you're interested.  Also,
>the SES specs are official T10 ones (unlike SAF-TE).  You can download
>them off t10.org.
>

Thanks. Okay, i just had a quick look at the spec and yes, it's quite 
different to SAF-TE.

I don't have any SES devices to test on but I may think about 
abstracting saftemon to handle
more than one protocol for inquiring enclosures. The SES attributes 
match pretty closely although
SES is s superset of SAF-TE.

It probably makes sense to include SMART, SAF-TE and SES monitoring into 
s single
consistent package. I'm not using SMART as with most RAID controllers, 
you only see logical
devices and have no contact directly with the drives (unless you use 
SCSI passthrough APIs
althoug these are different from one RAID controller driver to the next).

~mc

Re: ANNOUNCE: saftemon - SCSI Enclosure monitor for linux

[Michael Clark]

Matthew Jacob wrote:

>No- SAF-TE was what an *early* version of SES looked like. Then it went it's
>own way. Currently there is a bunch of SAF-TE chips out there (e.g. GEM-I and
>GEM-II), but the spec is no longer owned by anyone and www.safte.org
>disappeared over two years ago, so the ability to even find the spec is
>limited to finding those who had downloaded both the .doc and the addendum.
>

Okay. Yeah, for a while they weren't accessible and I initially worked off a
google cached copy. The SAF-TE spec and addendum can now be found here:

    http://www.nstor.com/white_papers.cfm

>
>Somebody out there correct me if I'm wrong.
>
>At any rate, you *can* emulate SAF-TE within SES. In fact, it's better to
>create an SES driver and then map SAF-TE into it (which is what I did for
>Solaris && *BSD). There are a couple of global status items that don't map
>easily- and the one wierd thing is to map the overtemp bits (all 17 of them)  
>into SES temperature elements. Plus the conversion of SAF-TE temp ranges for
>SAF-TE temp elements into SES temperature elements (different ranges). What a
>PITA.
>

Yes, would make sense to do it that way. The SAF-TE specific code in 
saftemon
is mostly limited to a handful of functions that probe the device and 
populate
the enclosure information structures. All the state information 
bitfields are
currently SAF-TE, although as you say, it could be changed to SES and 
make the
safte probing routines do the conversion.

Somebody with an SES enclosure may want to do this.
(unless someone wants to donate one to me - full of disks of course ;).

I can probably make some changes like changing safte_device_t to 
enclosure_t,
etc. to make the code a bit more generic. When I get time, i'll take a look
at that.

~mc

Re: ANNOUNCE: saftemon - SCSI Enclosure monitor for linux

[Thomas Tonino]

There is a SES monitor at http://www.feral.com/bk.html . I think it is 
only available in bitkeeper format.

I've tried it on a Eurologic/Dell fibre JBOD. It works there, but the 
status output is not parsed into human readable format. The config 
output is readable. It is a start however, and the 4 bit status output 
at least allows noticing critical faults.


Thomas