freeipmi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Freeipmi-devel] Supermicro X7DBR-3 CPU Temperatur Sensors


From: Albert Chu
Subject: Re: [Freeipmi-devel] Supermicro X7DBR-3 CPU Temperatur Sensors
Date: Mon, 14 Feb 2011 16:03:39 -0800

Hey Werner,

Could you send me some ipmi-sensors output for this motherboard?  This
motherboard is old enough, I'm wondering if the OEM extensions were
different back then.  I have a motherboard with the identical
manufacturer/product ID, and it had normal CPU temperature sensors.

Al

On Mon, 2011-02-14 at 10:56 -0800, Albert Chu wrote:
> Hey Werner,
> 
> On Mon, 2011-02-14 at 02:33 -0800, Werner Fischer wrote:
> > Hi Al,
> > 
> >       * one of our customers discovered another Supermicro system where
> >         FreeIPMI has currently no product ID information to display the
> >         OEM CPU temp sensors (he tried up to
> >         freeipmi-1.0.2.beta2.tar.gz)
> >       * It is a 6015B-3R
> >         http://www.supermicro.com/products/system/1U/6015/SYS-6015B-3R.cfm 
> > with a X7DBR-3 mainboard 
> > http://www.supermicro.com/products/motherboard/Xeon1333/5000P/X7DBR-3.cfm 
> > Below I have attached his output of bmc-info.
> > 
> > My questions
> >      1. Can you add the Manufacturer-ID/Product-ID for the OEM CPU temp
> >         sensors for this board? (As it is a X7-board it has IPMI not
> >         onboard (like the X8-boards do), but it uses the AOC-SIMSO(+)
> >         add on card for IPMI. Therefore the Manufacturer ID is Peppercon
> >         (not Supermicro).)
> 
> Hmm.  I'll think about how to do this.  Since Peppercon can sell to
> other customers, I'm not sure how to tell it's definitely a Supermicro
> motherboard.
> 
> >      2. If it is not too difficult for me and if it could lower your
> >         necessary work: Maybe you can tell me where the
> >         Manufacturer-ID/Product-ID are matched in the FreeIPMI code for
> >         the OEM sensors (so I could try add them myself in the source
> >         and I could send you directly patches)
> 
> It can be difficult since there are many permutations and ways OEM
> extensions can be handled.  The Supermicro ones are particularly unique
> and have a special case.  (And the fact the above motherboard doesn't
> even list Supermicro as the vendor makes it more difficult.)
> 
> If you're interested in learning, the beginning steps are the files in
> libfreeipmi/include/freeipmi/spec/, libfreeipmi/src/spec, and
> libfreeipmi/src/util (this is just for sensors, not for SEL
> extensions :-).
> 
> Al
> 
> > Thanks for your help and best regards,
> > Werner
> > 
> > PS: Here is the output of bmc-info:
> > 
> > Device ID             : 34
> > Device Revision       : 1
> > Device SDRs           : unsupported
> > Firmware Revision     : 1.59
> > Device Available      : yes (normal operation)
> > IPMI Version          : 2.0
> > Sensor Device         : supported
> > SDR Repository Device : supported
> > SEL Device            : supported
> > FRU Inventory Device  : supported
> > IPMB Event Receiver   : unsupported
> > IPMB Event Generator  : unsupported
> > Bridge                : unsupported
> > Chassis Device        : supported
> > Manufacturer ID       : Peppercon AG (10437)
> > Product ID            : 4
> > Auxiliary Firmware Revision Information : 20540000h
> > 
> > GUID : 0F0E0D0C-0B0A-0908-BD20-9BFEFF483002
> > 
> > Channel Information
> > 
> > Channel Number       : 1
> > Medium Type          : 802.3 LAN
> > Protocol Type        : IPMB-1.0
> > Active Session Count : 1
> > Session Support      : multi-session
> > Vendor ID            : Intelligent Platform Management Interface forum
> > (7154)
> > 
> > Channel Number       : 5
> > Medium Type          : Asynch. Serial/Modem (RS-232)
> > Protocol Type        : IPMB-1.0
> > Active Session Count : 0
> > Session Support      : single-session
> > Vendor ID            : Intelligent Platform Management Interface forum
> > (7154)
> > 
> > 
-- 
Albert Chu
address@hidden
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory




reply via email to

[Prev in Thread] Current Thread [Next in Thread]