Re: [Ipmitool-devel] generic test for system component failure

2012-04-12 Thread Timothy Gelter
m Events. Thanks again to all, - Tim From: "Schafer, Randy A" Date: Thu, 12 Apr 2012 19:10:46 + To: Andy Cress , Ryan Cox , Timothy Gelter Cc: "ipmitool-devel@lists.sourceforge.net" Subject: RE: [Ipmitool-devel] generic test for system component failure I don’t know

Re: [Ipmitool-devel] generic test for system component failure

2012-04-12 Thread Andy Cress
ubject: Re: [Ipmitool-devel] generic test for system component failure In my opinion, locate LED serves for chassis(server) identification, not to determine whether server requires service. But I have to admit I wouldn't be surprised if some vendors would do such thing. Anyway, you want to

Re: [Ipmitool-devel] generic test for system component failure

2012-04-12 Thread Schafer, Randy A
Andy Cress [mailto:andy.cr...@us.kontron.com] Sent: Thursday, April 12, 2012 11:53 AM To: Ryan Cox; Timothy Gelter Cc: ipmitool-devel@lists.sourceforge.net Subject: Re: [Ipmitool-devel] generic test for system component failure Tim, The Chassis Identify LED has a standard IPMI command to set it, but O

Re: [Ipmitool-devel] generic test for system component failure

2012-04-12 Thread Andy Cress
Tim, The Chassis Identify LED has a standard IPMI command to set it, but OEM-specific commands to read it. The system health/fault LED (if present) is entirely custom and OEM-specific. Even if there were a common way to read that health LED, what would that really accomplish? You would stil

Re: [Ipmitool-devel] generic test for system component failure

2012-04-12 Thread Duncan Idaho
this same way. > I was hoping not to have to parse the SEL but that's what I'll do if > that's my only option. > Thanks, > - Tim > > From: Andy Cress > Date: Thu, 12 Apr 2012 07:34:48 -0700 > To: Timothy Gelter , < > ipmitool-deve

Re: [Ipmitool-devel] generic test for system component failure

2012-04-12 Thread Ryan Cox
>> Date: Thu, 12 Apr 2012 07:34:48 -0700 To: Timothy Gelter mailto:timo...@gelter.com>>, <mailto:ipmitool-devel@lists.sourceforge.net>> Subject: RE: [Ipmitool-devel] generic test for system component failure Tim, The 'system health light' will be different for eac

Re: [Ipmitool-devel] generic test for system component failure

2012-04-12 Thread Ryan Cox
anks, - Tim From: Andy Cress <mailto:andy.cr...@us.kontron.com>> Date: Thu, 12 Apr 2012 07:34:48 -0700 To: Timothy Gelter mailto:timo...@gelter.com>>, <mailto:ipmitool-devel@lists.sourceforge.net>> Subject: RE: [Ipmitool-devel] generic test for system component failure Tim,

Re: [Ipmitool-devel] generic test for system component failure

2012-04-12 Thread Timothy Gelter
#x27;s what I'll do if that's my only option. Thanks, - Tim From: Andy Cress Date: Thu, 12 Apr 2012 07:34:48 -0700 To: Timothy Gelter , Subject: RE: [Ipmitool-devel] generic test for system component failure Tim, The ‘system health light’ will be different for each chassis vendor.

Re: [Ipmitool-devel] generic test for system component failure

2012-04-12 Thread Andy Cress
Tim, The 'system health light' will be different for each chassis vendor. Which chassis vendor is this? In any case, parsing the IPMI SEL (waiting for IPMI events) is the surest way to detect faults on an IPMI-capable system. That's the trigger for the firmware to turn on the system health