Sensors implemented on the am5010, 1 sensor, List – Kontron AM5010 IPMI User Manual
Page 22: Ipmi firmware user guide am5010

IPMI Firmware User Guide
AM5010
Page 22
© 2008 Kontron AG
ID 1022-2948, Rev. 1.0
Settings changed with this command are volatile (in particular quiesce timeout and OS
daemon present). Bits [6:5] are always settable, but once the quiesce request comes they
cannot be cleared until quiescence state is entered and exited.
6.3
Sensors Implemented on the AM5010
The MMC includes many sensors for voltage or temperature monitoring and various others
for pass/fail type signal monitoring.
Every sensor is associated with a Sensor Data Record (SDR). Sensor Data Records contain
information about the sensors identification such as sensor type, sensor name, sensor unit.
SDRs also contain the configuration of a specific sensor such as threshold/hystheresis, event
generation capabilities that specifies sensor behavior. Some fields of the sensor SDR are
configurable through IPMI v1.5 commands and are set to built-in initial value. Finally one
field which is the sensor owner must reflect the module addresses that allow the AMC Carrier
to identify the owner of the SDR when it is scanned from the module management controller
and merged within the AMC Carrier Device SDR repository.
From the IPMI perspective, the MMC is set up as a satellite management controller (SMC). It
does support sensor devices and uses the IPMI static sensor population feature of IPMI v1.5.
All SDRs can be queried using Device SDR commands to the MMC.
The sensor name in its SDR has a name prefix which after module insertion is automatically
adapted to the physical position of the module in a carrier or in a µTCA chassis.
The format of this prefix is:
• in AMC bay 1…8 or µTCA slot 1…8: ‘A1:’, ‘A2:’, ‘A3:’, ‘A4:’, ‘B1:’, ‘B2:’, ‘B3:’,
‘B4:’.
• in µTCA slot 9…12: ‘C1:’, ‘C2:’, ‘C3:’, ‘C4:’.
Please note that in the case that the module is installed elsewhere, then the IPMB-L address of
the module is unknown and the interface is off.
Module sensors that have been implemented are listed in the sensor list below.
6.3.1 Sensor List
For OEM (Kontron) specific sensor types and codes in the following table please refer to
chapter 6.3.2.
SENSOR
NUMBER
NAME
SENSOR TYPE
(CODE) /
EVENT/READING
TYPE (CODE)
Ass. Mask
/ Deass.
Mask /
Reading
Mask
DESCRIPTION
Causes red
Health LED
on error
0
IPMI Info-1
OEM Firmware Info 1
(C0h) / OEM (70h)
0003h /
0000h /
7FFFFh
For internal use only
N
1
OEM Firmware Info 2
0003h /
0000h /
For internal use only
N