Eric Schrock wrote:
> For x86 systems, you can use ipmitool to manipulate the led state
> (ipmitool sunoem led ...). On older galaxy systems, you can only set the
> fail LED ('io.hdd0.led'), as the ok2rm LED is not physically connected
> to anything. On newer systems, you can set both the 'fail' and 'okrm'
> LEDs. You cannot change the activity LED except by manually sending the
> 'set sensor reading' IPMI command (not available via impitool).
>
> For external enclosures, you'll need a SES control program.
>
> Both of these problems are being worked on under the FMA sensor
> framework to create a unified view through libtopo. Until that's
> complete, you'll be stuck using ad hoc methods.
>
Hi Eric,
I've looked at your blog and have tried your suggestions, but I need a
little more advice.
I am on an x86 system running SXCE svn_74 - the system has 6 SAS
backplanes but, according to the integrator, no "real" scsi enclosure
services. according to the man page, I found that I could use `sdr
elist generic` to list LEDs, but that command doesn't return any output:
# ipmitool sdr elist generic
# /* there was no output */
Is it not returning sensor ids because I don't have real scsi enclosure
services? Is there anything I can do or am I doomed to ad hoc methods
forever?
Thanks,
Kent
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
