(cross-post from fm-discuss) 

Hello.  I'm a core developer for the net-snmp project.  My particular
area of expertise is sensors and my specific interest is populating
HOST-RESOURCES-MIB and LM-SENSORS-MIB.  Up until now, on most platforms
I've been able to do it with kstat and/or picld library calls.

I'm currently working with T2000's and having little or no luck getting
at the sensors.  At best, I can program the ALOM to send me a trap, but
I need to monitor the temperator sensors live.  I've got a server room
with cooling issues and if the temperature gets too high, I need to get
the doors open and set up fans.  I've been monitoring ambient
temperature using SNMP graphing and monitoring tools.  

Hence, I'm interested in libtopo and whatever I can derive from it.
Hell, I'll even write the damn code if someone will tell me where to
pick up the information from the bus.

In order to simplify our API, we ended up coding a HAL (Hardware
Abstraction Layer) and moved the underlying nasty code underneath it.
Hence, I welcome your effort to do the same thing for a Sensor
Abstraction Layer and would like to get involved.

For all three projects (net-snmp, libtopo, SAL) I need to be able to see
the sensors on the bus and I'm coming up empty.  My last hope was
busstat and I'm seeing:

#busstat -l
Busstat Device(s):
dram0 dram1 dram2 dram3 jbus0 jbc0 pciex_imu0 pciex_imu1 pciex_mmu0
pciex_mmu1 pciex_tlu0 pciex_tlu1 pciex_lpu0 pciex_lpu1

busstat -e of the various devices isn't giving me anything I recognize
as being associated with sensors, and it doesn't appear to have any way
of drilling down to lower layers.

Am I missing something or can I simply assume that a T2000's sensors
simply don't show up on the bus at all.  

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify the system manager. This 
message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail.


Reply via email to