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 still have to also read the corresponding
SEL event to know what happened.
Andy
---
On 04/12/2012 10:47 AM, Timothy Gelter wrote:
Hello Andy,
I appreciate your quick response!
The systems I'm currently targeting are all Dell (C1100, C6220, and
R620) but I'd also want to be able to monitor a variety of HP servers
(DL360, DL185, BL460, & more) in 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
-----
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 light.
Andy
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Ipmitool-devel mailing list
Ipmitool-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
