Hi Ingard, I realized another possibility. The sensor could be "shared". So you could try the --shared-sensors option.
Al On Fri, 2014-02-14 at 10:26 -0800, Albert Chu wrote: > Hi Ingard, > > Searching through the NEWS file it was released in FreeIPMI 1.0.2. > > Is it possible you're looking at FRU info? (b/c the option is called > -psfruinfo). You can try ipmi-fru with the --bridge-fru option and see > if that works. > > Also try running ipmi-sensors with --bridge-sensors. If that doesn't > work, then this might be an OEM extension from Supermicro. The Slave > Addresses they list (0x70 and 0x72) are not the defaults. If > ipmi-sensors cannot find this sensor in the SDR (sensor data > repository), then Supermicro is getting this through some other means > that isn't standard. > > If you ask Supermicro for the OEM extension information, then it's > possible it could be added into FreeIPMI. > > Al > > It appears in the ipmicfg example below that they are going through the FRU > to get information. > > On Fri, 2014-02-14 at 08:14 +0100, ingard Mevåg wrote: > > Hi Al > > > > Thanks for the information. I had already tried to reset the device, but > > running with —ignore-unrecognized-events did the trick :) > > At least my monitoring is happy now for this one node running latest beta. > > I was wondering if you knew when this feature got introduced and/or if > > there are deb packages for the ubuntu LTS releases somewhere? I’ve got > > quite a few Lucid and Precise servers running version 0.7.15 and 0.8.12. > > > > Also, is it possible to get information per PSU somehow? Supermicro’s > > ipmicfg gives the following for instance: > > > > root@dn-080:~/ipmicfg_1.14.3_20130725/linux/64bit# ./ipmicfg-linux.x86_64 > > -psfruinfo > > [SlaveAddress = 70h] [Module 1] > > Item | Value > > ---- | ----- > > Status | On > > Temperature | 29C/84F > > Fan 1 | 7213 RPM > > Fan 2 | 10076 RPM > > > > [SlaveAddress = 72h] [Module 2] > > Item | Value > > ---- | ----- > > Status | On > > Temperature | 28C/82F > > Fan 1 | 7213 RPM > > Fan 2 | 9732 RPM > > > > Regards > > Ingard > > > > On 13 Feb 2014, at 17:12, Al Chu <[email protected]> wrote: > > > > > Hi Ingard, > > > > > > This sounds familiar, although I cannot recall how to fix it through the > > > firmware. It's possible a cold reset of the BMC could to it. You can > > > do a cold reset via > > > > > >> bmc-device --cold-reset > > > > > > If that doesn't work, you can tell ipmimonitoring to ignore unrecognized > > > events via the --ignore-unrecognized-events option. After that > > > everything should work. > > > > > > Al > > > > > > On Thu, 2014-02-13 at 16:17 +0100, Ingard Mevåg wrote: > > >> Hi guys > > >> > > >> I've been upgrading the firmware on the ipmi module on some > > >> supermicro X8SIU recently and I'm now experiencing problems with the PS > > >> Status sensor. Is there anything I can do to make the sensor detect the > > >> PSUs properly? > > >> > > >> Link to board: > > >> http://www.supermicro.com/products/motherboard/Xeon3000/3400/X8SIU.cfm?IPMI=Y > > >> The latest firmware as of now is version 3.12. > > >> Output from ipmimonitoring: > > >> root@dn-080:/usr/local# ./sbin/ipmimonitoring -V > > >> ipmi-sensors - 1.4.0.beta0 > > >> > > >> root@dn-080:/usr/local# ./sbin/ipmimonitoring > > >> ID | Name | Type | State | Reading | Units > > >> | > > >> Event > > >> 4 | System Temp | Temperature | Nominal | 32.00 | C > > >> | > > >> 'OK' > > >> 71 | CPU Temp | OEM Reserved | N/A | N/A | N/A > > >> | > > >> 'OEM Event = 0000h' > > >> 205 | FAN 2 | Fan | Nominal | 1695.00 | RPM > > >> | > > >> 'OK' > > >> 272 | FAN 3 | Fan | Nominal | 4655.00 | RPM > > >> | > > >> 'OK' > > >> 473 | CPU Vcore | Voltage | Nominal | 0.85 | V > > >> | > > >> 'OK' > > >> 540 | +3.3VCC | Voltage | Nominal | 3.31 | V > > >> | > > >> 'OK' > > >> 607 | +12 V | Voltage | Nominal | 12.19 | V > > >> | > > >> 'OK' > > >> 674 | CPU DIMM | Voltage | Nominal | 1.54 | V > > >> | > > >> 'OK' > > >> 741 | +5 V | Voltage | Nominal | 5.15 | V > > >> | > > >> 'OK' > > >> 808 | -12 V | Voltage | Nominal | -12.48 | V > > >> | > > >> 'OK' > > >> 875 | VBAT | Voltage | Nominal | 3.25 | V > > >> | > > >> 'OK' > > >> 942 | +3.3VSB | Voltage | Nominal | 3.30 | V > > >> | > > >> 'OK' > > >> 1009 | AVCC | Voltage | Nominal | 3.31 | V > > >> | > > >> 'OK' > > >> 1076 | Chassis Intru | Physical Security | Nominal | N/A | N/A > > >> | > > >> 'OK' > > >> 1143 | PS Status | Power Supply | N/A | N/A | N/A > > >> | > > >> 'Unrecognized Event = 0100h' 'Unrecognized Event = 0200h' 'Unrecognized > > >> Event = 0400h' 'Unrecognized Event = 0800h' 'Unrecognized Event = 1000h' > > >> 'Unrecognized Event = 2000h' 'Unrecognized Event = 4000h' > > >> > > >> Kind Regards > > >> Ingard > > >> _______________________________________________ > > >> Freeipmi-users mailing list > > >> [email protected] > > >> https://lists.gnu.org/mailman/listinfo/freeipmi-users > > > -- > > > Albert Chu > > > [email protected] > > > Computer Scientist > > > High Performance Systems Division > > > Lawrence Livermore National Laboratory > > > > > -- Albert Chu [email protected] Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-users mailing list [email protected] https://lists.gnu.org/mailman/listinfo/freeipmi-users
