Home

AT8070: IPMI Sensor User Guide

1. 14 S ensordata OM eG NETT TE T oo TETTE 14 Se COmimiallt access ses adsense RS AE E XM diu EER AE EE EEE ER M Rag A 14 LEN cue EEUU STU are autre tire een re err rr ere errr enn 15 Analy ng Adel OO TOUT 15 Read a discrete Sens DE uersa RE RV a lieve E oe bRH dee brenda cR slaw REF nu e SP ARM Nd ti eMe pRMR M RE 16 Annex A List of AT8070 RTM8070 Sensors ascia Re aa ao UE NUBE MEE QUAS SURRH PRENNE A RENI MONR NNMRN RI UA 17 Annex B Sensor SO SCI EVBRE aa casui iex uepus ar EP Ex OUI MERE EF deb a aa a a E 27 Annex C Cause of State Change Values sicasccccsacastauscadsuacaccssanenaaacenstndadaineaanesdnciauesensbaneduacsedaauacnns 30 3 AT8070 Sensor User Guide v1 0 AN09003 www kontron com Scope This document s main purpose is to show how to analyze and understand events generated by sensors of the AT8070 and RTM8063 which are stored in the System Event Log SEL Typical situations in which the SEL needs to be consulted are as followed e Unexpected shutdown or reboot e Front plate LEDs showing abnormality e Any unusual behavior In many cases analyzing the SEL will allow to determine the root cause of the events and provide essential guidance in determining either preventive or corrective action This document also contains information needed to understand sensor readings Readings provide useful information on the board s status e g which jumpers are present current POST code etc
2. ID Event Reading Type e Hex Name Class and Code Description Offset Data Byte 1 Data Byte 2 Data Byte 3 Entity ID Sensor Type Code Board FRU 0 Screen Sensor specific Hot Swap 00 Board Discrete Ox6F Sensor for 160 96 Hot Swap OxFO FRU 0 Front i Board Board FRU FRU1 Hot Sensor specific aeons Sensor for 7 4 Cause of state change See jen Swap RTM Discrete Ox6F FRU 1 RTM 7 4 Ah OEM code in Event Data 2 iyi 3 23 Cause of state change 192 96 Hot Swap 0xF0 Available only amp 3 values for values i 0 MO FRU Not Installed 3 0 Current State y when RTMIig QUInSta e id iba 3 0 Previous State inserted 1 M1 FRU Inactive 0 MO FRU Not Installed 0 MO FRU Not Installed Board FRU 22 M2 FRU Activation Request 1 M1 FRU Inactive 1 M1 FRU Inactive Hot Swap 3 M3 FRU Activation In Progress 2 M2 FRU Activation Request 2 M2 FRU Activation Request Sensor for 4 M4 FRU Active 3 M3 FRU Activation In Progress 3 M3 FRU Activation In Progress 7 0 FRU Device ID 2 FRU2Hot Sensor specific FRU2 RTM 5 M5 FRU Deactivation Request 4 M4 FRU Active 4 M4 FRU Active g o2 Swap RTM Discrete Ox6F Disk1 6 M6 FRU Deactivation In Progress 5 M5 FRU Deactivation Request E Ms _ FRU Deactivation Request Disk 4 96 Hot Swap OxFO available only 7 M7 FRU Communication Lost 6 M6 FRU Deactiv
3. 01h Non bootable diskette left in drive 01b previous state and or severity in Event Reading Code OFh if 02h PXE Server not found byte 2 unspecified 03h Invalid boot sector 10b OEM code in byte 2 3 0 Optional offset from 04h Timeout waiting for user selection of 11b sensor specific event extension Event Reading Type Code for 65 Boot Error Sensor Specific boot source code in byte 2 previous discrete event state OFh if 41 Front Board Discrete Ox6F Boot Error 5 4 00b unspecified byte 3 unspecified 160 96 Boot Error Ox1E 01b reserved 10b OEM code in byte 3 11b sensor specific event extension code in byte 3 3 0 Offset from Event Reading Code for discrete event state 00h Secure Mode Front Panel Lockout 7 6 00b unspecified byte 2 7 4 Optional offset from Severity Violation attempt 01b previous state and or severity in Event Reading Code OFh if 01h Pre boot Password Violation user byte 2 unspecified password 10b OEM code in byte 2 3 0 Optional offset from CMOS Sensor Specific 02h Pre boot Password Violation attempt 11b sensor specific event extension Event Reading Type Code for 66 Passwd Discrete Ox6F CMOS setup password code in byte 2 previous discrete event state OFh if 42 Front Board Platform Security Password 03h Pre boot Password Violation 5 4 00b unspecified byte 3 unspecified 160 96 Violation Attempt Failure network boot password 01b
4. 7 6 00b unspecified byte 2 For offset 14h For offset 14h value 01b previous state and or severity in POST Low Nibble POST High Nibble see AT8070 Manual section C byte 2 see AT8070 Manual section C see AT8070 Manual section 14h bit 14 Post code Error 10b OEM code in byte 2 C Sensor specific Show current All other offset are unused 11b sensor specific event extension POST Value Discrete Ox6F postcode Only offset 14h triggers an event code in byte 2 ib Pi OEM Kontron value Ai 5 4 00b unspecified byte 3 oar even 01b reserved 160 96 Rice pe generated by 10b OEM code in byte 3 this sensor 11b sensor specific event extension code in byte 3 3 0 Offset from Event Reading Code for discrete event state 00h Correctable ECC other correctable 7 6 00b unspecified byte 2 7 4 Optional offset from Severity The Event Data 3 field can memory error 01b previous state and or severity in Event Reading Code be used to provide an event 01h Uncorrectable ECC other byte 2 OFh if unspecified extension code for the 8h uncorrectable memory error 10b OEM code in byte 2 3 0 Optional offset from offset 02h Parity 11b sensor specific event extension Event Reading Type Code for 7 0 Memory 03h Memory Scrub Failed stuck bit code in byte 2 previous discrete event state OFh if module device e g 04h Memory Device Disabled 5 4 00b unspecified byte 3 unspecified DIMM SIMM RIMM 05h
5. 0x01 Temp Vcore Threshold based 8 O Front Threshold 0x01 CRYO Vcore 08 Board CPU Temperature Temp C 65 61 0x01 P Temp Vcore Threshold based 9 i Front Threshold 0x01 geile elis 09 Board CPU Temperature Threshold Values 7 6 00b unspecified byte 2 65 62 0x01 Temp C 00h Lower Non critical going low 01b trigger reading in byte 2 Temp DIMM Threshold based oon TE CR aol ia high 10b OEM code in byte 2 l 10 A Fron Threshold 0x01 DIMM k 03h Lower Critical going high 11b sensor specific event extension i Threshold value that 0A Board Mem Temperature Temp C dem code in byte 2 Reading that triggered the event 32 96 0x01 Oan Lower Non recoverable going iow 5 4 00b unspecified byte 3 FFh or not present if unspecified peret Md not Temp DIMM Threshold based 06h Upper Non critical Joina low g ted on te Mod in byte 3 mum eO with t present Event Data 2 must 08 Board Mem Temperature l Temp C E UN end ie high 11b z esos SPARE extension i bepresent 32 97 0x01 ore dh code in byte 3 Temp DIMM Threshold based OA Upper Non recoverable going low 20 Offset from Event Reading 12 C Fron Threshold 0x01 DIMM C OBh Upper Non recoverable going high Code for threshold event 0C Board Mem Temperature Temp C EPP Song Tg 32 98 0x01 Temp DIMM Threshold based 18 D Fron Threshold 0x01 DIMM D 0D Board Mem Temperature Temp
6. C 32 99 0x01 Temp DIMM Threshold based 14 E Fron Threshold 0x01 DIMM E OE Board Mem Temperature Temp C 82 100 0x01 Temp DIMM Threshold based 15 F Fron Threshold 0x01 DIMM F OF Board Mem Temperature Temp C 82 101 0x01 Temp DIMM Threshold based 16 G Fron Threshold 0x01 DIMM G 10 Board Mem Temperature Temp C 32 102 0x01 AN09003 17 AT8070 Sensor User Guide v1 0 www kontron com ID Sensor Event Reading Type Name Class and Code Description Offset Data Byte 1 Data Byte 2 Data Byte 3 Hex Entity ID Sensor Type Code Temp DIMM Threshold based 17 H Front Threshold 0x01 DIMM H 11 Board Mem Temperature Temp C 32 103 0x01 Threshold based i Ta Bel Threshold 0x01 fne 12 Temperature Threshold Values A f 4 96 C E POEM 7 6 00b unspecified byte 2 0x01 00h Lower Non critical going low 01b trigger reading in byte 2 Disk 1 01h Lower Non critical going high 10b S DEM codo in byte Temperature 02h Lower Critical going low 11b sensor specific event extension Tem Threshold based C 03h Lower Critical going high code in byte 2 Reading that triggered the event Threshold value that 19 p Threshold 0x01 Available only 04h Lower Non recoverable going low y B m iind triggered event FFh or not 13 Disk1
7. reserved Sensor Specific Advance 05h S5 G2 soft off 10b OEM code in byte 3 75 ACPI State Discrete OxGF Configuration 06h S4 S5 soft off particular S4 S5 11b sensor specific event extension 4B Front Board System ACPI and Power state cannot be determined code in byte 3 160 96 Power State 0x22 Interface 07h G3 Mechanical Off 3 0 Offset from Event Reading State 08h Sleeping in an S1 S2 or S3 states Code for discrete event state used when particular S1 S2 S3 state cannot be determined 09h G1 sleeping S1 S4 state cannot be determined OAh S5 entered by override OBh Legacy ON state OCh Legacy OFF state OEh Unknown This sensor is recommended for new 7 6 00b unspecified byte 2 7 4 interrupt type IPMI v1 0 and later implementations 01b previous state and or severity in Oh none 00h Timer expired status only no byte 2 1h SMI action no interrupt 10b OEM code in byte 2 2h NMI 01h Hard Reset 11b sensor specific event extension 3h Messaging Interrupt 02h Power Down code in byte 2 Fh unspecified IPMI Sensor Specific IPMI 03h Power Cycle 5 4 00b unspecified byte 3 all others reserved 76 Watchdog Discrete Ox6F Watchdog 04h 07h reserved 01b reserved 3 0 timer use at expiration 4C Front Board Watchdog 2 payload 08h Timer interrupt 10b OEM code in byte 3 Oh reserved 160 96 0x23 watchdog Event Data 2 can be used to provide an 11b sensor specific event extensio
8. 4 3 LUN for Master Write Read command or FRU Command 00b if device is non intelligent device directly on IPMB 2 0 Private bus ID if bus Private 000b if device directly on PMB or device is a logical FRU Device 27 AN09003 www kontron com For Logical FRU device accessed via FRU commands to mgmt controller 7 0 FRU Device ID within controller that generated the event FFh reserved For non intelligent FRU device 7 1 7 bit I2C Slave Address of FRU device This is relative to the bus the device is on For devices on the IPMB this is the slave address of the device on the IPMB For devices on a private bus this is the slave address of the device on the private bus 0 reserved AT8070 Sensor User Guide v1 0 Sensor Sensor Type Type Code Sensor Offset Event Data 2 Event Data 3 00h Unspecified 01h No system memory is physically installed in the system 02h No usable system memory all installed memory has experienced an unrecoverable failure 03h Unrecoverable hard disk ATAPI IDE device failure 04h Unrecoverable system board failure 05h Unrecoverable diskette subsystem failure 06h Unrecoverable hard disk controller failure 07h Unrecoverable PS 2 or USB keyboard failure 08h Removable boot media not found 09h Unrecoverable video controller failure OAh No video device detected OBh Firmware BIOS ROM corruption detected OCh CPU voltage mismatch processors that s
9. Data Byte 2 Data Byte 3 or ID I Entity ID 1 Sensor Type Code 00h bit 0 Hardware change detected with 7 6 00b unspecified byte 2 bit 7 O Version change type FFh associated Entity Informatonal This offset does O1b previous state and or severity in byte 2 O0h unspecified not imply whether the hardware change was 10b OEM code in byte 2 Oth management controller device ID change in one successful or not Only that a change occurred 11b sensor specific event extension code in byte 2 lor more fields from Get Device ID Oth bit 1 Firmware or software change detected 5 4 00b unspecified byte 3 02h management controller firmware revision with associated Entity informational Success or 01b reserved 03h management controller device revision failure not implied 10b OEM code in byte 3 04h management controller manufacturer ID 02h bit 2 Hardware incompatibility detected with 11b sensor specific event extension code in byte 3 05h management controller IPM version associated Entity 3 0 Offset from Event Reading Code for discrete event state 6h management controller auxiliary firmware ID O3h bit 3 Firmware or software incompatibility O7h management controller frmware boot block detected with associated Entity O8h other management controller firmware FW Ver Change Sensor specific 4h bit 4 Entity is of an invalid or unsupported OGh system firmware EFI BIOS change 81 PICMG Front Board Discre
10. In order to be able to accomplish these tasks the user will first be introduced to Sensors as defined in the IPMI specification v2 0 Once the first level knowledge has been acquired detailed information will be provided on how to analyze and interpret the data collected from these sensors with tools such as ipmitool and Pigeon Point s clia Annex A includes a detailed list of all the sensors implemented on the AT8070 and RTM8063 4 AT8070 Sensor User Guide v1 0 AN09003 www kontron com 1 Sensor Introduction Sensor Model Access to monitored information such as temperatures and voltages fan status etc is provided via the IPMI Sensor Model Instead of providing direct access to the monitoring hardware IPMI provides access by abstracted sensor commands such as the Get Sensor Reading command implemented via a management controller This approach isolates software from changes in the platform management hardware implementation Sensors are classified according to the type of readings they provide and or the type of events they generate A sensor can return either an analog or discrete reading Sensor events can be discrete or threshold based The different event types sensor types and monitored entities are represented using numeric codes defined in the IPMI specification IPMI avoids reliance on strings for management information Using numeric codes facilitates internationalization automated handling by higher level
11. No Event for this Sensor 60 Status Discrete Ox6F DIMM E Entity identified by the Entity ID for the 3C Front Board Entity Presence Status amp sensor is absent If the entity is absent Mem 0x25 Presence system management software should 32 100 consider all sensors associated with that DIMM F m Entity to be absent as well and ignore or Sms aeaea Dmme tose sensors 3D Front Board Entity Presence Status amp 02h Entity Disabled The Entity is Mem 0x25 Presence present but has been disabled A 32 101 deassertion of this event indicates that DIMM G Sensor specific ane the Entity has been enabled EA Front Board E Ee Status amp Mem Presence 32 102 0x25 pn Sensor specific DIMM H GP Front Board ped ieee Status amp Mem Presence 32 103 0x25 00h bit 0 State Deasserted 7 6 00b unspecified byte 2 Oth bit 1 State Asserted 01b previous state and or severity in byte 2 POST 10b OEM code in byte 2 Memory Digital Discrete Memory 11b sensor specific event extension 64 Resize Discrete 0x03 Resize code in byte 2 40 Front Board POST Memory Indicates if 5 4 00b unspecified byte 3 160 96 Resize 0x0E CMOS DID reserved i memory size 10b OEM code in byte 3 has changed 11b sensor specific event extension code in byte 3 3 0 Offset from Event Reading Code for discrete event state 00h No bootable media 7 6 00b unspecified byte 2 7 4 Optional offset from Severity
12. Specific Fabric code in byte 3 P 67 Board porre In ae 1 3 0 Offset from Event Reading 192 96 0x27 Ink status Code for threshold event 104 bu ar Sensor Specific Fabric 68 Board Discrete Ox6F Interface 2 192 96 LAN 0x27 ink status Kontron OEM Sensor giving info about firmware state Should not generate Event IPMI Info 1 Internal Diagnostic Internal Mgmt according to the Event Reading Type Please contact Kontron Canada Inc 107 Front Board Discrete 0x70 Controller The 2 first bits will have assertion mask Technical Support if an Event is 6B 192 96 Kontron OEM firmware set Used with event reading type code triggered T Firmware Info diagnostic 0xCO 0x70 OEM Firmware Info 1 Kontron OEM 0x71 OEM Firmware Info 2 j 7 IPMI Info 2 Internal Diagnostic Internal Mgmt 0x75 OEM Firmware Info 2 108 Front Board Discrete 0x75 Controller 6C 192 96 Kontron OEM firmware Firmware Info diagnostic 0xCO AN09003 26 AT8070 Sensor User Guide v1 0 www kontron com Sensor Type System Event Sensor Type Code Annex B Sensor Specific Event Sensor Offset Event Data 2 No Event Generated Event Data 3 No Event Generated No Event Generated this event would typically require system specific diagnostics to determine FRU failure type see PICMG 2 0 31 12 Get Auxiliary Log Status Command and 31 13 Set Auxiliary Log Status Comma
13. reserved d 0x06 04h Other pre boot Password Violation 10b OEM code in byte 3 05h Out of band Access Password 11b sensor specific event extension Violation code in byte 3 3 0 Offset from Event Reading Code for discrete event state PCle Error Sensor Specific 00h Front Panel NMI Diagnostic 7 6 00b unspecified byte 2 7 4 Optional offset from Severity 67 Front Board Discrete Ox6F General PCle Interrupt 01b previous state and or severity in Event Reading Code OFh if 43 160 96 Critical Interrup Error 01h Bus Timeout byte 2 unspecified 0x13 02h I O channel check NMI 10b OEM code in byte 2 3 0 Optional offset from PCle RTM Sensor Specific 03h Software NMI 11b sensor specific event extension Event Reading Type Code for 68 Error Front Discrete Ox6F RTM PCIe 04h PCI PERR code in byte 2 previous discrete event state OFh if 44 Board Critical Interrup Error 05h PCI SERR 5 4 00b unspecified byte 3 unspecified 160 96 0x13 06h EISA Fail Safe Timeout 01b reserved PCle BI Sensor Specific Base 07h Bus Correctable Error 10b OEM code in byte 3 69 Error Front Discrete Ox6F Interface 08h Bus Uncorrectable Error 11b sensor specific event extension 45 Board Critical Interrup PCle Error BAL ee port 61h bit 7 ol p vides eee 160 96 0x13 us Fatal Error 0 Offset from Event Reading ite FI ss Specific Fabri OBh Bus Degraded bus operating in a Code for discrete event state 71 Error F
14. software change code in byte 2 02h mgmt controller firmware 91 IPMC Front Discrete Ox6F Firmware detected with associated Entity 5 4 00b unspecified byte 3 revision 5B Board Version Change Change Informational Success or failure not 01b reserved 03h mgmt controller device revision 160 96 0x2B Detection implied 10b OEM code in byte 3 04h mgmt controller manufacturer ID 02h Hardware incompatibility detected 11b sensor specific event extension 05h mgmt controller IPMI version with associated Entity code in byte 3 06h mgmt controller auxiliary 03h Firmware or software incompatibility 3 0 Offset from Event Reading firmware ID detected with associated Entity Code for discrete event state 07h mgmt controller firmware boot 04h Entity is of an invalid or unsupported block hardware version 08h other mgmt controller firmware 05h Entity contains an invalid or 09h system firmware EFI BIOS unsupported firmware or software 0Ah SMBIOS change version OBh operating system change 06h Hardware Change detected with OCh operating system loader change Ver Change Sensor specific FPGA associated Entity was successful ODh service or diagnostic partition 92 FPGA Discrete Ox6F Firmware deassertion event means OEh mgmt software agent BC Front Board Version Change Change unsuccessful OFh mgmt software application 34 97 0x2B Detection 07h Software or F W Change detected change with associated Entity was successful 10h mgmt s
15. to M5 and M7 to M6 transitions Surprise State Change due to extraction The FRU has changed state abruptly to MO due to a non compliant removal from the system This is only valid for FRUs represented by a physically separate IPM Controller e g mezzanine cards Valid for the M2 to MO M3 to MO M4 to MO M5 to MO M6 to MO and M7 to MO transitions State Change due to provided information A new state is known for the FRU that could not be deduced previously This is used when a user verifies that a FRU has been extracted from the Shelf and is no longer available Valid for the M7 to MO state transition Invalid Hardware Address Detected This is an error condition where the Hardware Address did not pass the parity check Valid for the MO to MO transition Unexpected Deactivation The FRU has transitioned to deactivating without requesting permission from the Shelf Manager first Valid for M4 to M6 transition Surprise State Change due to power failure Case 1 The FRU has abruptly changed state to MO due to a serious power failure that precludes further use of the FRU until it is extracted and reinserted or replaced for example due to overcurrent in the Management Power domain This is valid for MO M1 M2 M3 M4 M5 M6 and M7 to MO transitions Case 2 The FRU has cut off the power to its Payload or a managing FRU has cut off the Payload Power to its Managed FRU due to an unexpected power failure that
16. 1 25V 3 0 Offset from Event Reading Code for discrete event state AN09003 19 AT8070 Sensor User Guide v1 0 www kontron com ID Sensor Event Reading Type Name Class and Code Description Offset Data Byte 1 Data Byte 2 Data Byte 3 Hex Entity ID Sensor Type Code 00h State asserted 7 6 OEM Data in Byte 2 Event Data 2 Reset Type Event Data 3 Reset Source 01h State Deasserted 5 4 OEM Data in Byte 3 00h Warm reset 00h IPM Watchdog cold 3 0 Reserved Oth Cold reset warm forced cold IPM 02h Forced Cold Warm reset Watchdog sensor gives reverted to cold additional details 03h Soft reset Software jump 01h IPM commands cold 04h Hard Reset warm or forced cold chassis 05h Forced Hard Warm reset control fru control reverted to Hard 02h Processor internal check stop 03h Processor internal reset request Board Digital Discrete 04h Reset button warm or 53 Reset Front Discrete 0x03 Board reset forced cold 85 Board OEM Kontron type and 05h Power up cold 160 96 Reset Sensor sources 06h Legacy Initial Watchdog li OxCF Warm Reset Loop Detection cold reset 07h Legacy Programmable Watchdog cold Warm or forced cold 08h Software initiated soft cold warm or forced cold 09h Setup Reset Software initiated Cold OAh Power Cycle Full Reset Global Platform Reset FFh Unknown 00h to 07h bit 0 7 Post Code low byte
17. 11b sensor specific event extension 98 Set Front Discret S SF Specify when 04h bit 4 PEF Action code in byte 2 62 Board System Event SEL time 05h bit 5 Timestamp Clock Synch 5 4 00b unspecified byte 3 IPMC 7 96 0x12 change 01b reserved 10b OEM code in byte 3 11b sensor specific event extension code in byte 3 3 0 Offset from Event Reading Code for discrete event state 25 AT8070 Sensor User Guide v1 0 www kontron com AN09003 ID Sensor Event Reading Type m Hex Name Class and Code Description Offset Data Byte 1 Data Byte 2 Data Byte 3 Entity ID Sensor Type Code 00h bit 0 Jumper 00 Present JP1 1 2 No Event for this Sensor No Event for this Sensor No Event for this Sensor Oth bit 1 Jumper 01 Present JP1 3 4 02h bit 2 Jumper 02 Present JP1 5 6 O3h bit 3 Jumper 03 Present JP1 7 8 04h bit 4 Jumper 04 Present JP1 9 0 i 05h bit 5 Jumper 05 Present JP1 11 12 Jumper OE DEM Reflects on 06h bit 6 Jumper 06 Present JP1 13 14 99 Status Kontron OEM Retirees 07h bit 7 Jumper 07 Present JP2 1 2 63 Front Board Jumper Status presence 08h bit 8 Jumper 08 Present JP2 3 4 160 96 0xD3 09h bit 9 Jumper 09 Present JP2 5 6 OAh bit 10 Jumper 10 Present JP2 7 8 OBh bit 11 Jumper 11 Present JP2 9 10 OCh bit 12 Jumper 12 Present JP2 1 12 ODh bit 13 Jumper13
18. 11b sensor specific event extension 2h Unable to drive data HI 160 96 state 0xC3 sensor code in byte 2 3h Unable to drive clock 5 4 00b unspecified byte 3 LO 01b reserved 4h Unable to drive data LO FRU1 Sensor specific IPMB L 10b OEM code in byte 3 5h clock low timeout IPMBL Discrete Ox6F branch from 11b sensor specific event extension 6h Under test the IPM 80 State OEM Kontron FRUM fault code in byte 3 Controller is attempting to 50 Front OEM IPMB L link detection 3 0 Offset from Event Reading determine who is causing a Board tate 0xC3 neor Code for discrete event state bus hang 160 96 state 0xC3 Senso 7h Undiagnosed Communication Failure 00h IERR 7 6 00b unspecified byte 2 7 4 Optional offset from Severity 01h Thermal Trip 01b previous state and or severity in Event Reading Code OFh if 02h FRB1 BIST failure byte 2 unspecified 03h FRB2 Hang in POST failure used 10b OEM code in byte 2 3 0 Optional offset from CPUO Sensor specific hang is believed to be due or related toa 11b sensor specific event extension Event Reading Type Code for 81 Status Di Poele OG Processor 0 processor failure Use System Firmware code in byte 2 previous discrete event state OFh if 51 Front Board Processor 0x07 Status Progress sensor for other BIOS hangs 5 4 00b unspecified byte 3 unspecified CPU 3 96 04h FRB3 Processor Startup 01b reserved Initialization failu
19. 3 0 Offset from Event Reading Code for discrete event state 00h bit 0 State Deasserted 7 6 00b unspecified byte 2 Oth bit 1 State Asserted 01b previous state and or severity in byte 2 10b OEM code in byte 2 IPMC Digital Discrete Mos sta M event extension 95 Reboot Discrete 0x03 IPMC reboot come nye BF Front Board Platform Alert detection Dd one byte 3 7 li 160 96 0x24 B 10b OEM code in byte 3 11b sensor specific event extension code in byte 3 3 0 Offset from Event Reading Code for discrete event state 00h sensor access degraded or 7 6 00b unspecified byte 2 For Offset 04h For Offset 05h Logical unavailable A sensor that is degraded 01b previous state and or severity in 7 0 Sensor Number Number of FRU device accessed via will still return valid results but may be byte 2 the failed sensor corresponding to FRU commands to mgmt operating with a slower response time or 10b OEM code in byte 2 event offset 04h or 00h controller may not detect certain possible states A 11b sensor specific event extension For Offset 05h 7 0 FRU Device ID within sensor that is unavailable is not able to code in byte 2 7 logical physical FRU device controller that generated the return any results scanning is disabled 5 4 00b unspecified byte 3 Ob device is not a logical FRU event FFh reserved 01h controller access degraded or 01b reserved Device For Offset 05h non unavaila
20. 42 2 Generic Event Reading Type Codes below Sensor specific Discrete Indicates that the discrete state information is specific to the sensor type State bit positions event offsets for a particular sensor type are specified in the sensor specific offset column in Table 42 3 Sensor Type Codes below OEM Discrete Indicates that the discrete state information is specific to the OEM identified by the Manufacturer ID for the IPM device that gt IPMI v2 0 Table 42 1 Event Reading Type Code Ranges p 499 AN09003 www kontron com 7 AT8070 Sensor User Guide v1 0 Sensor Reading Reading from a sensor is available through the Get Sensor Reading command All other more complex commands which provide sensor readings use this raw command Therefore it is important to understand the format in which data is returned Table 2 Get Sensor Reading Command Request Data a a N eaqui Ignore on read if sensor does not return an numeric analog reading Ob Event Messages disabled from this sensor B Ob sensor scanning disabled 5 b reading state unavailable formerly initial update in progress This bit is set to indicate that a re arm or Set Event Receiver command has been used to request an update of the sensor status and that update has not occurred yet Software should use this bit to avoid getting an incorrect status while the first sensor update is in progress This bit is only require
21. Correctable ECC other correctable 01b reserved identification relative to the memory error logging limit reached 10b OEM code in byte 3 entity that the sensor is 06h Presence detected Indicates 11b sensor specific event extension associated with if SDR presence of entity associated with the code in byte 3 provided for this sensor sensor Typically the entity will be a 3 0 Offset from Event Reading memory module or other entity Code for discrete event state representing a physically replaceable unit of memory 07h Configuration error Indicates a memory configuration error for the entity associated with the sensor i e a given implementation of the entity is not supported by the system e g particular Size of the memory module is unsupported or that the entity is part of an unsupported memory configuration Memory Eft Sensor specific e g configuration is not supported since 55 Front Discrete Ox6F Memory Error the memory module doesn t match other 37 Board Memory 0x0C memory modules 160 96 08h Spare Indicates entity associated with the sensor represents a spare unit of memory Event Data 3 field may contain an event extension code 09h Memory Automatically Throttled memory throttling triggered by a hardware based mechanism operating independent from system software such as automatic thermal throttling or throttling to limit power consumption OAh Critical over temperature Memory d
22. G kontron Kontron Application Note AT8070 IPMI Sensor User Guide Document Revision 1 0 December 2013 AN09003 If it s embedded it s Kontron Customer Service Contact Information Kontron Canada Inc Kontron Modular Computer GMBH 4555 Rue Ambroise Lafortune Sudetenstrasse 7 Boisbriand Qu bec Canada 87600 Kaufbeuren J7H 0A4 Germany Tel 450 979 5320 449 0 8341 803 333 800 354 4223 Fax 450 437 8053 49 0 8341 803 339 E mail support ca kontron com support kom kontron com Visit our web site at www kontron com 2013 Kontron an International Corporation All rights reserved The information in this user s guide is provided for reference only Kontron does not assume any liability arising out of the application or use of the information or products described herein This user s guide may contain or reference information and products protected by copyrights or patents and do not convey any license under the patent rights of Kontron nor the rights of others Kontron is a registered trademark of Kontron All trademarks registered trademarks and trade names used in this user s guide are the property of their respective owners All rights reserved This user s guide contains information proprietary to Kontron Customers may reprint and use this user s guide in other publications Customers may alter this user s guide and publish it only after they remove the Kontron name cover and logo Kontron rese
23. Present JP2 13 14 OEh bit 14 Jumper 14Present JP4 TEST 00h bit 0 transition to Running 7 6 00b unspecified byte 2 Oth bit 1 transition to In Test 01b previous state and or severity in 02h bit 2 transition to Power Off byte 2 03h bit 3 transition to On Line 10b OEM code in byte 2 ME Generic Discrete Provides 04h bit 4 transition to Off Line 11b sensor specific event extension 100 Availability Discrete 0x0A status on the 05h bit 5 transition to Off Duty code in byte 2 64 Front Management chipset Mamt 06h bit 6 transition to Degraded 5 4 00b unspecified byte 3 Board Subsystem Health t Ig 07h bit 7 transition to Power Save 01b reserved 192 96 0x28 ngng 08h bit 8 Install Error 10b OEM code in byte 3 11b sensor specific event extension code in byte 3 3 0 Offset from Event Reading Code for discrete event state LAN BI 0 iH 00h LAN Heartbeat Lost 7 6 00b unspecified byte 2 101 Link Front Sensor eerie Non 01h LAN Heartbeat 01b trigger reading in byte 2 65 Board Discrete OxGF iert ce 0 10b OEM code in byte 2 LAN 0x27 ink status Em i 192 96 11b sensor specific event extension LAN BI 1 m code in byte 2 102 Link Front e he i 5 4 00b unspecified byte 3 66 Board 7 LAN 0x27 ink status 01b trigger threshold value in byte 3 192 96 10b OEM code in byte 3 LAN FI 1 ie 11b sensor specific event extension 103 Link Front Sensor
24. RTM IT t hen 05h Lower Non recoverable going high 5 4 00b unspecified byte 3 FFh or not present if unspecified present if unspecified 13 Disk 4 96 emperaure wie f coverabe going NIJA o15 trigger threshold value in byte 3 Do not confuse reading with 0x01 RTM8063 06h Upper Non critical going low 10b OEM code in byte 3 Threshold Value If present Event Data 2 must and 1 disk s 07h Upper Non critical going high 11b ifi t extension be present is present 08h Upper Critical going low d Ei ues IG Event extensio Disk 2 09h Upper Critical going high 13 0 Offset tr m EvenReading Temperature 0Ah Upper Non recoverable going low Code for threshold event C OBh Upper Non recoverable going high Temp Threshold based Available only 20 i Threshold 0x01 1a Disk2 RTM Temperature when Disk 4 97 0x01 RTM8063 and both disks are present Threshold based l 21 cud Threshold 0x01 arose Other Unit Based consumption Threshold Values e E 05 iiec Sensor Watt W including 00h Lower Non critical going low ra 22D Berta n s 160 96 0x0B managed FRU Oth Lower Non critical going high 10b OEM code in byte 2 FRUO Brd Threshold based FRUS 02h Lower Critical going low 11b sensor specific event extension 22 P i Threshold 0x01 Board 03h Lower Critical going high code in byte 2 Reading that triggered the event Threshold value that ibd Other Unit Based Power 04h Lower Non
25. S Fron chon 1 0V suspend 20 Board Voltage 0x02 mgmt power 160 96 supply V On board as SUS ron Threshold based 0 75V 21 Board Threshold 0x01 suspend 160 96 Voltage 0x02 mgmt power supply V g4 Vcc 1 5V Threshold based onboard d 22 Front Board Threshold 0x01 aa l 160 96 Voltage 0x02 P V Pply 35 Vcc 1 2V Threshold based m d 23 Front Board Threshold 0x01 m 2 of l 160 96 Voltage 0x02 P v Pply AN09003 18 AT8070 Sensor User Guide v1 0 www kontron com Sensor ID Event Reading Type H Name Class and Code Description Offset Data Byte 1 Data Byte 2 Data Byte 3 Hex Entity ID Sensor Type Code Vcc 1 1V On board 36 ME Front Threshold based 4 ty payload 24 Board Threshold 0x01 power supply 160 96 Voltage 0x02 V On board 38 Mes iade Threshold based CPUO Vcore 26 Board Pwr Threshold 0x01 payload 20 96 Voltage 0x02 power supply V On board so euo Threshold based CPUOVIT 27 Front Board Threshold 0x01 payload Pwr 20 96 Voltage 0x02 power supply j V On board i aa Threshold based CPUO VDDQ 28 Front Board Threshold 0x01 payload Pwr 20 96 Voltage 0x02 power supply V On board 41 EUR Threshold based GPUO VSA Threshold Values 29 Fron
26. Sensor User Guide v1 0 This section will cover the sensordata and sel commands from the Shelf Manager s Command Line Interpreter For more info consult Pigeon Point s web site http www pigeonpoint com This command can be used to get more details on the sensors current readings It also indicates whether Event Messages are enabled or not for each sensor it clia sensor board 5 in this example the board is located in slot 5 Figure 4 clia sensor board 5 Command The clia sel command shows all the information you will need to find a definition for the event Data Bytes in Annex A s list Some Events are directly analyzed clia sel board 5 in this example the board is located in slot 5 Figure 5 clia sel Command Board s address J Channel Number Sensor Type Code Event Data 3 LUN Sensor ID Event Data 2 Event Reading Type Code Event Data 1 14 AT8070 Sensor User Guide v1 0 4 Example Analyzing the SEL Whenever an unusual situation is reported the SEL should be consulted Figure 6 SEL Event Example JOx0136 Event at Nov 3 14 55 29 2009 from 0xGa 0 0 sensor Ox2b 81 event 0x6 asserted OxCl 0x09 OxFF Since the sensor s ID 81 is between 0 and 103 as explained section 1 Sensor Introduction its ID can be used to locate the sensor in the Annex A list Sens SensorName EventReadng Type Class and Code Offset Data Byte 1
27. ation In z varon neg when RTM and 6 M6 FRU Deactivation In 14 disk is 8 Fh Reserved Progress e Progress inserted Pra KRY Communication Lost 7 M7 FRU Communication Lost poor FRU 2 8 Fh Reserved Hot Swap 3 FRUS Hot Sensor specific ERU 03 Swap RTM Discrete Ox6F Disk2 Disk 4 96 Hot Swap OXFO Available only when RTM and 1 disk is inserted 00h bit 0 System Reconfigured 7 6 00b unspecified byte 2 See Sensor Specific Event Oth bit 1 OEM System Boot Event 01b trigger reading in byte 2 Annex B 02h bit 2 Undetermined system 10b OEM code in byte 2 hardware failure 11b sensor specific event extension FRUO Sensor specific Sensor 03h bit 3 Entry added to Auxiliary Log code in byte 2 4 Reconfig Discrete Ox6F Population 04h bit 4 PEF Action 5 4 00b unspecified byte 3 04 Front Board System Event Changeon 05h bit 5 Timestamp Clock Synch 01b trigger threshold value in byte 3 160 96 0x12 Carrier 10b OEM code in byte 3 11b sensor specific event extension code in byte 3 3 0 Offset from Event Reading Code for threshold event Temp Board Threshold based 5 Inlet Front Threshold 0x01 Board Inlet 05 Board Temperature Temp C 66 97 0x01 Temp CPU Threshold based 6 0 Front Threshold 0x01 CPUO Temp 06 Board CPU Temperature C 65 97 0x01 Temp CPU Threshold based T 1 Front Threshold 0x01 CPU1 Temp 07 Board CPU Temperature C 65 98
28. ble Access to the controller has 10b OEM code in byte 3 1b device is logical FRU Device intelligent FRU device been degraded or is unavailable but the 11b sensor specific event extension accessed via FRU commands to 7 1 7 bit 12C Slave party that is doing the monitoring cannot code in byte 3 mgmt controller Address of FRU device This determine which 3 0 Offset from Event Reading 6 5 reserved is relative to the bus the 02h management controller off line Code for discrete event state 4 3 LUN for Master Write Read device is on For devices on 5 controller cannot be accessed for command or FRU Command the IPMB this is the slave IPMC Edi n normal operation because it has been 00b if device is non intelligent address of the device on the 96 Storage Err Management Kod HORE intentionally taken off line for a non error device directly on IPMB IPMB For devices on a 60 Front Board Subsystem Health volatile condition Note that any commands that 2 0 Private bus ID if bus private bus this is the slave 160 96 0x28 memory error 3 available must function according to Private address of the device on the y specification 00b if device directly on IPMB or private bus 03h management controller unavailable device is a logical FRU Device 0 reserved controller cannot be accessed because of an error condition See Sensor Specific Event See Sensor Specific Event 04h Sensor failure the sensor is known Anne
29. d if it is possible for the controller to receive and process a Get Sensor Reading or Get Sensor Event Status command for the sensor before the update has completed This is most likely to be the case for sensors such as fan RPM sensors that may require seconds to accumulate the first reading after a re arm The bit is also used to indicate when a reading state is unavailable because the management controller cannot obtain a valid reading or state for the monitored entity typically because the entity is not present See Section 16 4 Event Status Event Conditions and Present State and Section 16 6 Re arming for Present threshold comparison status 7 6 reserved Returned as 1b Ignore on read 5 1b at or above 2 upper non recoverable threshold 4 1b at or above upper critical threshold 3 1b at or above 2 upper non critical threshold 2 1b at or below lower non recoverable threshold 1 1b at or below lower critical threshold 0 1b at or below X lower non critical threshold For discrete reading sensors U 1b state 7 asserted 6 1b state 6 asserted 5 1b state 5 asserted 4 1b state 4 asserted For discrete reading sensors only jonal 00h Otherwise reserved Returned as 1b Ignore on read 1b state 14 asserted 1b state 13 asserted 1b state 12 asserted 1b state 11 asserted 1b state 10 asserted 1b state 9 asserted 1b state 8 asserted Comp
30. does not preclude further use of the FRU for example due to overcurrent in the Payload Power domain This is valid for M3 M4 M5 M7 to M6 and M6 M7 to M1 transitions Fh State Change Cause Unknown No cause could be determined All other values Reserved 30 AT8070 Sensor User Guide v1 0 AN09003 www kontron com
31. ent On board 44 ae Threshold based CPU1 VTT 2C Front Board Threshold 0x01 payload Pwr 20 97 Voltage 0x02 power supply j V On board as CALDO Threshold based CPU VDDQ 2D Front Board Threshold 0x01 payload Pwr 20 97 Voltage 0x02 power supply i V On board ae BUSA Threshold based CPU VSA 2E Front Board Threshold 0x01 payload Pwr 20 97 Voltage 0x02 power supply V On board az GU Thresholdbased CPU vsa 2F Front Board Discrete 0x01 payload Pwr 20 97 Voltage 0x02 power supply i V m Fuse Redundancy States Used 7 6 00b unspecified byte 2 48 pde E Deus DP presence 00h bit 0 Fully Redundant formerly 01b trigger reading in byte 2 30 Board Power Suppl fault Redundancy Regained Indicates that 10b OEM code in byte 2 160 96 0x08 ppy detection full redundancy has been regained 11b sensor specific event extension i 48V supply A 01h bit 1 Redundancy Lost Entered code in byte 2 any non redundant state including Non 5 4 00b unspecified byte 3 3 Fuse Pres B Sensor specific Fuse redundant Insufficient Resources 01b trigger threshold value in byte 3 49 Feed Front Discrete Ox6F presence 10b OEM code in byte 3 isi Discrete OxGF fault 11b sensor specific event extension 31 Board Power Supply P 160 96 0x08 detection code in byte 3 48V supply B 8 0 Offset from Event Reading Code for threshold event 00h Powe
32. evice has entered a critical over temperature state exceeding specified operating conditions Memory devices in this state may produce errors or become inaccessible AN09003 20 AT8070 Sensor User Guide v1 0 www kontron com ID Sensor Event Reading Type Hex Name Class and Code Description Offset Data Byte 1 Data Byte 2 Data Byte 3 Entity ID Sensor Type Code prem Sensor specific DIMM A 56 Discrete Ox6F 38 Front Board Entity Presence Status amp Mem 32 96 0x25 Presence Satusi Sensor specific DIMM B i Front Board JEN Pio Status amp Mem 0x25 Presence e This sensor type provides a mechanism in that allows a management controller to 58 Status Disce Dd DIMM C direct system management software to 8A Front Board Entity Presence Status amp ignore a set of sensors based on Mem 0x25 Presence detecting that presence of an entity This 32 98 sensor type is not typically used for event DIMM D Sensor specific generation but to just provide a present 59 p Status Discrete Ox6F DIMM D reading E 3B ront Board Entity Presence Status amp 00h Entity Present This indicates that peg l 0x25 Presence me Entity identified d the Entity ID for e sensor is present DIMM E eae Oth Entity Absent This indicates that the No Event for this Sensor No Event for this Sensor
33. from sensors However these commands provide most of the relevant information can be obtained from http ipmitool sourceforge net This PICMG command introduced in previous section can be used by raw command raw 0x04 Ox2d lt id gt 0x04 Network function Code for Sensor Event Ox2d Get Sensor Reading command id SensorID This command provides information on the board s sensors It is also the only sensor command excluding raw commands that lists the reading Data Byte 3 and 4 see Sensor Reading from section 1 Sensor Introduction Other command provides sensor reading Data Byte 3 sensor Figure 1 ipmitool sensor command Sensor Analog Type Reading Threshold Values Reading Byte 3 amp 4 11 AT8070 Sensor User Guide v1 0 The following command will provide additional information on sensors sdr list v Figure 2 ipmitool sdr list v Command 12 AT8070 Sensor User Guide v1 0 The command ipmitool sel shows the sensor s NAME ID and Event Data in human readable format for each event logged In some cases is not able to analyze the Event Data and will print Event Data 1 2 and 3 When this occurs the list in Annex A should be used to decode these bytes sel list Figure 3 ipmitool sel list Command It is recommended to use Pigeon Point s clia sel command to analyze SEL data since it provides more details on sensors 13 AT8070
34. g is disabled for following event reading type and offset has been disabled Event Data 2 Event Reading Type Code 7 6 reserved Write as 00b 5 1b logging has been disabled for all events of given type 4 1b assertion event Ob deassertion event 3 0 Event Offset 02h 03h 04h 05h If Event Data 3 is not provided then by default this event represents the SEL has reached a point of being 75 or more full For example if the SEL supports 215 entries the 75 value would be 161 25 entries Therefore the event would be generated on the 162nd entry Note that if this event itself is logged it would be logged as the 163rd entry Event Data 3 Contains hex value from 0 to 100 decimal 00h to 64h representing the 96 of which the SEL is filled at the time the event was generated 00h is 0 full SEL is empty 64h is 100 full etc 06h If the following field is not provided then this event indicates that Correctable Machine Check error logging has been disabled for all Processor sensors Event Data 2 may be optionally used to return an Entity Instance or a vendor selected processor number that identifies the processor associated with this event 7 0 Instance ID number of the processor Entity that the sensor is associated with if SDR provided for this sensor or a vendor selected logical processor number if no SDR If Event Data 2 is provided then Event Data 3 may be
35. hare same supply have mismatched voltage requirements ODh CPU speed matching failure OEh to FFh reserved uses same Event Data 2 definition as following System Firmware Progress offset 00h Unspecified System 01h Memory initialization Firmware 02h Hard disk initialization Progress OFh 03h Secondary processor s initialization formerly 04h User authentication POST Error 05h User initiated system setup 06h USB resource configuration 07h PCI resource configuration 08h Option ROM initialization 09h Video initialization OAh Cache initialization OBh SM Bus initialization OCh Keyboard controller initialization ODh Embedded controller management controller initialization OEh Docking station attachment OFh Enabling docking station 10h Docking station ejection 11h Disabling docking station 12h Calling operating system wake up vector 13h Starting operating system boot process e g calling Int 14h Baseboard or motherboard initialization 15h reserved 16h Floppy initialization 17h Keyboard test 18h Pointing device test 19h Primary processor initialization 1Ah to FFh reserved 00h 01h 02h 28 AT8070 Sensor User Guide v1 0 AN09003 www kontron com Sensor Type Event Logging Disabled Sensor Type Code 10h Sensor Offset 00h Event Data 2 7 0 Memory module device e g DIMM SIMM RIMM identification relative to the entity that the sensor Event Data 3 01h Event Loggin
36. ide greater levels of detail about what initiated a transition Valid for the MO to M1 M1 to M2 M2 to M3 M3 to M4 M4 to M5 M5 to M6 and M6 to M1 transitions Change Commanded by Shelf Manager with Set FRU Activation The Shelf Manager has issued a command to change states typically during an insertion or extraction Valid for the M2 to M1 M2 to M3 M4 to M6 M5 to M4 and M5 to M6 transitions State Change due to operator changing a Handle Switch The FRU has changed states as a result of an operator changing the state of a Handle Switch Valid for the M1 to M2 M3 to M6 M4 to M5 and M5 to M4 transitions State Change due to FRU programmatic action The FRU has changed states due to some non operator related internal requirement Such as Locked bit being cleared Valid for the M1 to M2 M3 to M6 M4 to M5 and M5 to M4 transitions Communication Lost or Regained The Shelf Manager has lost or regained contact with the FRU and generated an event on its behalf Valid for the M2 to M7 M3 to M7 M4 to M7 M5 to M7 and M6 to M7 M7 to M1 M7 to M2 M7 to M3 M7 to M4 M7 to M5 and M7 to M6 transitions Communication Lost or Regained locally detected The FRU has changed state as a result of an internal detection by the IPM Controller This is only valid for FRUs represented by a physically separate IPM Controller e g mezzanine cards Valid for the M2 to M7 M3 to M7 M4 to M7 M5 to M7 M6 to M7 M7 to M1 M7 to M2 M7 to M3 M7 to M4 M7
37. ios Flash 01h Non bootable diskette left in drive 01b previous state and or severity in Event Reading Code 0Fh if 78 0 Front Sensor Specific 02h PXE Server not found byte 2 unspecified 49 Board Discrete Ox6F Bios Flash 0 93h Invalid boot sector 10b OEM code in byte 2 3 0 Optional offset from 160 96 Boot Error Ox1E 04h Timeout waiting for user selection of 11b sensor specific event extension Event Reading Type Code for boot source code in byte 2 previous discrete event state OFh if 5 4 00b unspecified byte 3 unspecified 01b reserved Bios Fl sh Sensor Specific 100 OEM code in byte 3 l Discrete 0x6F Bios Flash 1 b sensor specific event extension 4A Board Boot Error 0x1E code in byte 3 160 96 3 0 Offset from Event Reading Code for discrete event state 00h S0 GO working 7 6 00b unspecified byte 2 7 4 Optional offset from Severity 01h S1 sleeping with system h w amp 01b previous state and or severity in Event Reading Code processor context maintained byte 2 OFh if unspecified 02h S2 sleeping processor context lost 10b OEM code in byte 2 3 0 Optional offset from 03h S3 sleeping processor amp h w 11b sensor specific event extension Event Reading Type Code for context lost memory retained code in byte 2 previous discrete event state OFh if 04h S4 non volatile sleep suspend to 5 4 00b unspecified byte 3 unspecified disk 01b
38. ious state and or severity in byte 2 10b OEM code in byte 2 Digital Discrete FRU Error 11b sensor specific event extension 84 im ensar Discrete 0x03 during code in byte 2 54 Board OEM Kontron external FRU 5 4 00b unspecified byte 3 160 96 OEM FRU sensor Sensor 01b reserved error 0xCC discovery 10b OEM code in byte 3 11b sensor specific event extension code in byte 3 8 0 Offset from Event Reading Code for discrete event state 23 AT8070 Sensor User Guide v1 0 www kontron com AN09003 ID Sensor Event Reading Type EP H Name Class and Code Description Offset Data Byte 1 Data Byte 2 Data Byte 3 Hex Entity ID Sensor Type Code 00h bit 0 State Deasserted 7 6 00b unspecified byte 2 Power denial cause FRU ID Oth bit 1 State Asserted 01b previous state and or severity in 00h Explicit by shelf manager or byte 2 application 10b OEM code in byte 2 Oth Decided by carrier based on FRU Pwr Digital Discrete 11b sensor specific event extension fru information 85 Denied Discrete 0x03 FRU Power code in byte 2 03h Timeout shelf manager didn t 55 Front OEM Kontron Denial 5 4 00b unspecified byte 3 grant power in time Board FRU Power Detection 01b reserved FFh Undefined 160 96 denied OxCD 10b OEM code in byte 3 11b sensor specific event extension code in byte 3 3 0 Off
39. l sensor command to determine the sensor s name With this name run a search in the Annex A list and verify that the other information match since it may occur that two sensors have the same name while they can belong to different Entity 15 AT8070 Sensor User Guide v1 0 AN09003 www kontron com Read a discrete sensor In some cases it can be useful to consult a discrete sensor s current state For example to know which jumpers are installed on a board without pulling it out of the chassis the Jumper Status sensors should be consulted To do so use the ipmitool sensor command or the raw Get Sensor Reading command These commands will provide Reading Byte 3 amp 4 which correspond to Response Data Byte 4 amp 5 as shown section 1 Sensor Introduction To analyze the reading table 2 and the offset column on Annex A should be consulted Example Reading Bytes 3 amp 4 0xA193 for the Jumper Status sensor Meaning 0xA193 1010 0001 1001 0011 00h bit 0 Jumper 00 Present JP1 1 2 05h bit 5 Jumper 05 Present JP1 11 12 07h bit 7 Jumper 07 Present JP2 1 2 O8h bit 8 Jumper 08 Present JP2 3 4 09h bit 9 Jumper 09 Present JP2 5 6 OCh bit 12 Jumper 12 Present JP2 11 12 16 AT8070 Sensor User Guide v1 0 AN09003 www kontron com Annex A List of AT8070 RTM8063 sensors Sensor
40. letion Code This will not be displayed if the Request Message completes successfully and normally Byte 1 Sensor Reading IPMI v2 0 Table 35 15 Get Sensor Reading Command p 464 8 AT8070 Sensor User Guide v1 0 AN09003 www k e For Discrete Sensors will return OOh e For Threshold based sensors will return the analog reading This value is coded according to the Event Reading Type and or Sensor type Tools such as ipmitool provide commands which will decode this information in a human readable format Byte 2 e Provides information on the sensor Byte 3 e For Threshold based sensor Indicates were the reading stands against the threshold values e For Discrete sensors Indicates which sensor offsets states are asserted for offset OO0h to 07h Byte 4 e For Threshold based sensor 80h since bit 7 is always 1b e For Discrete sensors Indicates which sensor offsets states are asserted for offset O8h to 14h NOTE Sensors have a reading mask which is OEM defined This is used to ignore unused states during reading Therefore if a state that should be asserted is not read the Reading Mask should be verified Event Data When a sensor changes state an Event Message is sent to the SEL only if the Event Mask indicates that the new state must generate an event The Event Data contains 3 bytes where only the first byte is used The signification of these bytes is listed in Annex A for e
41. n 1h BIOS FRB2 event extension code code in byte 3 2h BIOS POST 3 0 Offset from Event Reading 3h OS Load Code for discrete event state 4h SMS OS 5h OEM Fh unspecified all others reserved This sensor can be used for returning the 7 6 00b unspecified byte 2 General state and generating events associated 01b previous state and or severity in health status with alerts that have been generated by byte 2 Aggregation the platform mgmt subsystem 10b OEM code in byte 2 an r of critical 00h platform generated page 11b sensor specific event extension 77 E erat nt eo sensors 01h platform generated LAN alert code in byte 2 4D Board Platform Alert This list is 02h Platform Event Trap generated 5 4 00b unspecified byte 3 160 96 0x24 flexible and formatted per IPMI PET specification 01b reserved could be O3h platform generated SNMP trap 10b OEM code in byte 3 adjust based OEM format 11b sensor specific event extension on customer code in byte 3 requirements 3 0 Offset from Event Reading Code for discrete event state 22 AT8070 Sensor User Guide v1 0 www kontron com AN09003 ID Sensor Event Reading Type mu Hex Name Class and Code Description Offset Data Byte 1 Data Byte 2 Data Byte 3 Entity ID Sensor Type Code 00h IPMB A disabled IPMB B disabled 7 4 Ah OEM code in Event Data 7 4 Channel Number F
42. nd for more information 7 4 Log Entry Action Oh entry added 1h entry added because event did not be map to standard IPMI event 2h entry added along with one or more corresponding SEL entries 3h log cleared 4h log disabled 5h log enabled all other reserved 3 0 Log Type Oh MCA Log 1h 2 OEM 1 2h OEM 2 all other reserved The following bits reflect the PEF Actions that are about to be taken after the event filters have been matched The event is captured before the actions are taken 7 6 reserved 5 1b Diagnostic Interrupt NMI 4 1b OEM action 3 1b power cycle 2 1b reset 1 1b power off This event can be used to record when changes are made to the timestamp clock s so that relative time differences between SEL entries can be determined See Note 1 7 first second Ob event is first of pair 1b event is second of pair 6 4 reserved 3 0 Timestamp Clock Type Oh SEL Timestamp Clock updated Also used when both SEL and SDR Timestamp clocks are linked together 1h SDR Timestamp Clock updated Management Subsystem Health 7 0 Sensor Number Number of the failed sensor corresponding to event offset 04h or OOh 7 logical physical FRU device Ob device is not a logical FRU Device 1b device is logical FRU Device accessed via FRU commands to mgmt controller 6 5 reserved
43. oftware middleware deassertion event means change unsuccessful 11h programmable hardware e g Event data 2 can may contain additional FPGA event information on the type of version 12h board FRU module change change change of a module plugged into associated entity 13h board FRU component addition removal of a replaceable component on the board FRU not tracked as a FRU Ver Change Sensor specific BIOS x 93 BIOS Front Discrete 0x6F Firmware a co Paced witi 60 Board Verson Change Chang v ecc ME 34 98 0x2B Detection ia P 16h board FRU replaced with older version 17h board FRU hardware configuration change e g strap jumper cable change etc 24 AT8070 Sensor User Guide v1 0 www kontron com AN09003 ID Sensor Event Reading Type mu Hex Name Class and Code Description Offset Data Byte 1 Data Byte 2 Data Byte 3 Entity ID Sensor Type Code 00h Cable Interconnect is connected 7 6 00b unspecified byte 2 01h Configuration Error Incorrect cable 01b previous state and or severity in connected Incorrect interconnection byte 2 10b OEM code in byte 2 EventRcv Digital Discrete Detects 11b sensor specific event extension 94 ComLost Discrete 0x03 ak ME enis MT byte 3 5E E PE nnect event receiver 01b reserved ShMc 10b OEM code in byte 3 11b sensor specific event extension code in byte 3
44. optionally used to indicate whether Event Data 2 is being used to hold an Entity Instance number or a vendor specific processor number If Event Data 2 is provided by Event Data 3 is not then Event Data 2 is assumed to hold an Entity Instance number 7 Ob Entity Instance number 1b Vendor specific processor number 6 0 reserved 1 To track the relationship between timestamps the timestamp change events should be logged in pairs the first event being logged just before the timestamp clock update followed by a second event that is logged after the timestamp clock has been updated This enables software that reads the SEL to be able to determine time relationship between events that were logged before the update and those logged afterward The generation of these events is normally the responsibility of the software that changes the timestamp clock Note that some implementations may queue events prior to their being logged It is recommended that generic software read the SEL to verify that the first event has been recorded with the relative timestamp before setting the new timestamp value and generating the second event 29 AN09003 www kontron com AT8070 Sensor User Guide v1 0 Annex C Cause of State Change Values Normal State Change This is used when the FRU is proceeding normally through the state chart For instance an M3 to M4 transition is a normal state change Other values in this table can be used to prov
45. or 7 IPMB B Override State 01h IPMB A enabled IPMB B disabled 2 amp 3 AdvancedTCA this will typically be Ob Override state bus 02h IPMB A disabled IPMB B enabled 3 0 Offset Oh to indicate IPMB 0 isolated 03h IPMB A enabled IPMP B enabled 00h IPMB A disabled IPMB B 3 0 Reserved 1b Local Control state disabled IPM Controller determines 01h IPMB A enabled IPMB B state of bus disabled 6 4 IPMB B Local Status 02h IPMB A disabled IPMB B Oh No Failure Bus enabled enabled if no override in effect 03h IPMB A enabled IPMP B 1h Unable to drive clock HI ig enabled 2h Unable to drive data HI IPMBO Link Sensor specific ipe opu 3h Unable to drive clock 78 State Front Discrete Ox6F detection LO 4E 60 90 rcc ae sensor 4h Unable to drive data LO 5h Clock low timeout 6h Under test the IPM Controller is attempting to determine if it is causing a bus hang 7h Undiagnosed Communications Failure 3 IPMB A Override Status Same interpretation as 7 2 0 IPMB A Local Status Same interpretation as 6 4 02h bit 2 IPMB L Disable 7 6 00b unspecified byte 2 Always 0 Bit 7 3 Always 0 FRUO Sensor specific IPMB L 03h bit 3 IPMB L Enable 01b previous state and or severity in Bit 2 0 79 IPMBL Discrete Ox6F branch from byte 2 Oh No failure 4F State Front OEM Kontron FRUO fault 10b OEM code in byte 2 1h Unable to drive clock HI Board OEM IPMB L link detection
46. r ON 7 6 00b unspecified byte 2 01h Power OFF 01b previous state and or severity in 02h Power ON Request byte 2 03h Power ON in progress 10b OEM code in byte 2 Power Sensor specific 04h Power OFF Request 11b sensor specific event extension Discrete Ox6F 05h Graceful Power OFF Request code in byte 2 i2 i oa Kontron OEM Bad Fower 6h Power OFF in progress 5 4 00b unspecified byte 3 A 160 96 Power State 07h Synchronise Graceful Power OFF 01b reserved Sensor 0xD0 08h Power OFF Now Request 10b OEM code in byte 3 11b sensor specific event extension code in byte 3 8 0 Offset from Event Reading Code for discrete event state 7 Bit 0 VccGood 12V 7 6 00b unspecified byte 2 Power OEM Discrete Current Bit 1 VccGood 5V 01b previous state and or severity in 51 Good Front 0x77 power good Bit 2 VccGood 3 3V byte 2 33 Board Power Supply status Bit 3 VccGood 2 5V 10b OEM code in byte 2 160 96 0x08 Bit 4 VccGood 1 8V 11b sensor specific event extension Bit 5 VccGood 1 5V code in byte 2 Power good Bit 6 VccGood 1 2V 5 4 00b unspecified byte 3 Power Good OEM Discrete status event Bit 7 VecGood Core 01b reserved 52 Event Front 0x77 that occur Bit 8 VccGood 5V 10b OEM code in byte 3 34 Board Power Supply since the last Bit 9 VccGood 1 1V 11b sensor specific event extension 160 96 0x08 power on or Bit 10 VccGood 1 05V code in byte 3 reset Bit 11 VccGood
47. re CPU didn t start 10b OEM code in byte 3 05h Configuration Error 11b sensor specific event extension 06h SM BIOS Uncorrectable CPU code in byte 3 complex Error 3 0 Offset from Event Reading 07h Processor Presence detected Code for discrete event state 08h Processor disabled 09h Terminator Presence Detected OAh Processor Automatically Throttled CPU1 processor throttling triggered by a 82 Status oed Processor 1 hardware based mechanism operating 52 Front Board Processor 0x07 Status independent from system software such CPU 3 97 as automatic thermal throttling or throttling to limit power consumption OBh Machine Check Exception Uncorrectable OCh Correctable Machine Check Error 00h bit 0 State Deasserted 7 6 00b unspecified byte 2 00h Over Current on Management FRU ID Oth bit 1 State Asserted 01b previous state and or severity in power byte 2 01h Over Current on Payload 10b OEM code in byte 2 power FRU Over Digital Discrete 11b sensor specific event extension 83 lec Front Discrete 0x03 FRU Over code in byte 2 7 53 Board OEM Kontron Current 5 4 00b unspecified byte 3 160 96 OEM FRU Over Sensor 01b reserved i Current 0xCB 10b OEM code in byte 3 11b sensor specific event extension code in byte 3 8 0 Offset from Event Reading Code for discrete event state 00h bit 0 State Deasserted 7 6 00b unspecified byte 2 FRU ID Oth bit 1 State Asserted 01b prev
48. recoverable going low m i un triggered event FFh or not 16 Front Board R i ih 5 4 00b unspecified byte 3 FFh or not present if unspecified p n Sensor Watt consumption 05h Lower Non recoverable going high i h present if unspecified 160 96 other tenet 01b trigger threshold value in byte 3 Do not confuse reading with 0x0B W 06h Upper Non critical going low 10b OEM code in byte 3 Threshold Value If present Event Data 2 must FRU RTM 07h Upper Non critical going high 11b sensor specific event extension be present FRUI RTM Threshold based FRU2 RTM 08h Upper Critical going low code in byte 3 23 Power Threshold 0x01 Diskt FRUS 09h Upper Critical going high 3 0 Offset from Event Reading 17 Front Board Other Unit Based RTM Disk2 OAh Upper Non recoverable going low Code for threshold event 17 bs oan Sensor Watt Power OBh Upper Non recoverable going high d 160 96 0x0B consumption W Voc 48V 48v feed 24 Feed Fron Threshold ai Voltage 18 Board Voltage 0x02 board input 160 96 9 power V Vcc 12V On Board 25 SUS Fron que neo 12V suspend 19 Board mgmt power 160 96 Voltage 0x02 V Vcc 5V On board 26 SUS Fron ane enon 5 0V suspend 1A Board Voltage 0x02 mgmt power 160 96 V Vcc 3 3V On board 27 SUS Fron Hae eon 3 3V suspend 1B Board Voltage 0x02 mgmt power 160 96 V Vcc 1 8V On board 28 SUS Fron aaa 1 8V
49. ront Discrete 0x6F ilsi x a degraded performance state 47 Board Critical Interrup PCle Error 160 96 0x13 AN09003 21 AT8070 Sensor User Guide v1 0 www kontron com ID Sensor Event Reading Type mu Hex Name Class and Code Description Offset Data Byte 1 Data Byte 2 Data Byte 3 Entity ID Sensor Type Code 00h Front Panel NMI Diagnostic 7 6 00b unspecified byte 2 7 4 Optional offset from Severity Interrupt 01b previous state and or severity in Event Reading Code OFh if 01h Bus Timeout byte 2 unspecified 02h I O channel check NMI 10b OEM code in byte 2 3 0 Optional offset from 03h Software NMI 11b sensor specific event extension Event Reading Type Code for PCle MI Sensor Specific Mgmt 04h PCI PERR code in byte 2 previous discrete event state OFh if 72 Error Front Discrete Ox6F intetace 05h PCI SERR 5 4 00b unspecified byte 3 unspecified 7 48 Board Critical Interrupt PCle Error 06h EISA Fail Safe Timeout 01b reserved 160 96 0x13 07h Bus Correctable Error 10b OEM code in byte 3 08h Bus Uncorrectable Error 11b sensor specific event extension 09h Fatal NMI port 61h bit 7 code in byte 3 OAh Bus Fatal Error 3 0 Offset from Event Reading OBh Bus Degraded bus operating in a Code for discrete event state degraded performance state 00h No bootable media 7 6 00b unspecified byte 2 7 4 Optional offset from Severity B
50. rves the right to make changes without notice in product or component design as warranted by evolution in user needs or progress in engineering or manufacturing technology Changes that affect the operation of the unit will be documented in the next revision of this user s guide 2 AT8070 Sensor User Guide v1 0 AN09003 www kontron com Table of Contents SCOPE T 4 Pees rise lal gic Od DE esscr Dacis onde E Lii OL HALO Nap ap AREE EEE i 5 Sensor MOOG lh NR DU TM 5 Sens r Classes T 5 Event Reading UB diea sepu eod E EE equ REO fa aaO UE Da bx DIN ME 7 TOMUS c 5 Sensor ReadWiquis iaces ess esua s eva saa vean suau Ko dax Roa pet A ia bR Ga de ovbP Ye FR XM E Ea RE MEC NREE CN raw o MEE EN Gd RM AREE 8 Event Data sco teu ean pc ca EORUM np pO NR SUR HUNE CORPO agent dese C iub ee ameueng tous np RM Ss 9 EHUDU AA heater EE EUR box gee ves nae el Pa nu EDU E R DE AR RCM NE E EUM Da a ET MEE E INE UT 9 Sensor ID m P 10 MEE rop MNT 11 Get SENSOMREOGING COMMEANG ca csapSankd vex deua app RR mEM E RM danti rao pO a EPI MES QUIA S IMEU SEP FAC RPM c NUR 11 Sens r Fori ET ET 11 RERUM UT UT TT 12 Sel Comman direnian EE MEME aelnue sa misa Ta URDU E EEE ERE MUNI IC M N CONUM ERR rM E 13 3 Pigeon Point S CHG EE
51. set from Event Reading Code for discrete event state 00h bit 0 State Deasserted 7 6 00b unspecified byte 2 FRU ID Oth bit 1 State Asserted 01b previous state and or severity in byte 2 FRU 10b OEM code in byte 2 MngtPwr Digital Discrete 11b sensor specific event extension 86 Fail Discrete 0x03 FRU Mgmt code in byte 2 56 Front OEM Kontron Power Fail 5 4 00b unspecified byte 3 Board FRU Management 01b reserved 160 96 Power Fail 0xD2 10b OEM code in byte 3 11b sensor specific event extension code in byte 3 3 0 Offset from Event Reading Code for discrete event state FRUO Generic Discrete Tiii e E ic Fron o d sd DU j ent nuo l 7 Event Data 3 is used a bit 160 96 Info Agent OxC5 re a Error 7 6 00b unspecified byte 2 nm flag error etection Only offset 00h 01h 02h 06h and 08h 01b previous state and or severity in Bit 7 SetClockState Not FRU1 Generic Discrete FRU will trigger an event byte 2 Event Data 2 is used as bit flag error Supported 88 Agent Fron Discrete 0x0A xd 00h bit 0 transition to Running 10b OEM code in byte 2 Bit 7 unspecifiedError Bit 6 SetClockState Error 58 Board OEM Kontron FRU Nils Oth bit 1 transition to In Test 11b sensor specific event extension Bit 6 notPresentError Bit 5 SetPortState Not 160 96 Info Agent 0xC5 Detection 02h bit 2 transition to Power Off code in byte 2 Bit 5 multirecHeaderError Supported FRU 03h bit 3 transi
52. software and reduces management controller code and data space requirements For the purpose of this document the two most important characteristics of a sensor are e Event Reading Type e Sensor Type Sensor Type Discrete sensors defined with an Event Reading Type 6Fh Sensor specific will use Sensor Specific definition for their offset and Event Data Sensor specific definition is available for many Sensor Types and may be OEM defined for OEM class sensors IPMI v2 0 Section 1 7 5 p 13 5 AT8070 Sensor User Guide v1 0 AN09003 www kontron com Sensor Classes Sensors fall into the following classes Discrete e These are State Sensors The reading they return contains two bytes where each bit can represent a unique state Up to 15 possible states not 16 since bit15 from the returned reading is reserved e More than one state may be active simultaneously Events are generated by a unique state Thus Event Messages do not return a bit field just a single offset value corresponding to a single event Digital Discrete e A digital sensor is not really a unique class but a term commonly used to refer to special case of a discrete sensor that only has two possible states Threshold Threshold based e Changes event status on reading comparison to threshold values Threshold enumerations may be considered a special case of the discrete sensor type OEM e Special case of discrete
53. suspend 1C Board mgmt power 160 96 Voltage 0x02 V Threshold Values 7 6 00b unspecified byte 2 Veo 1 5V On board 00h Lower Non critical going low 01b trigger reading in byte 2 29 SUS Fron Threshold based 1 5V suspend Oth Lower Non critical going high 10b OEM code in byte 2 Threshold 0x01 p 02h Lower Critical going low B E n 1D Board Voltage 0x02 MIM Power pp ower Critical going high 1b sensor speeilic event extension Threshold value that 160 96 supply V 04h Lower Non recoverable going low code in byte 2 Reading that triggered the event triggered event FFh or not Vee 1 25V On board 05h Lower Non recoverable oina high 5 4 00b unspecified byte 3 FFh or not present if unspecified present if unspecified ceti Threshold based 1 25V te caren eas going hig 01b trigger threshold value in byte 3 Do not confuse reading with 30 SUS Fron 06h Upper Non critical going low If present Event Data 2 must 1E Board Threshold 0x01 suspend 07h Upper Non critical going high 10b OEM code in byte 3 Threshold Value be present 160 96 Voltage 0x02 gor TW 08h Upper Critical going low h Vice eodd event extension 09h Upper Critical going high A j re S n Threshold based E board q Oh Upper Non recoverable going low P mo eu UM F oa Threshold 0x01 RGB OBh Upper Non recoverable going high Voltage 0x02 160 96 supply V Vcc 1 0V On board 32 SU
54. t Board Threshold 0x01 payload 00h Lower Non critical going low 7 6 oop z unspecified byte 2 Pwr 20 96 Voltage 0x02 POMA Oth Lower Non critical going high vids EM reading in byte 2 oH 10b OEM code in byte 2 5 02h Lower Critical going low Wa Vcc PLL T On board 03h Lower Critical going high dit sensor specific event extensi n n Threshold value that hreshold based CPUO PLL a eer code in byte 2 Reading that triggered the event 42 CPU 0 04h Lower Non recoverable going low im 4 Me triggered event FFh or not Threshold 0x01 payload E i 5 4 00b unspecified byte 3 FFh or not present if unspecified p 2A Front Board 05h Lower Non recoverable going high A present if unspecified Pwr 20 96 Voltage 0x02 power supply pen Upper Non critical going low 01b trigger threshold value in byte 3 Do not confuse reading with If present Event Data 2 must V 07h Upper Non critical going high 10b ui OEM code m byte 3 Threshold Value be present On board insala 11b sensor specific event extension Vcc VCORE 08h Upper Critical going low i Threshold based CPU1 Vcore eal noiha hi code in byte 3 43 1 Front 09h Upper Critical going high Threshold 0x01 payload I pes 3 0 Offset from Event Reading 2B Board Pwr OAh Upper Non recoverable going low C forthrashol 20 97 Voltage 0x02 uh ad OBh Upper Non recoverable going high 09e for threshold ev
55. te Ox6f hardware version OAh SMBIOS change 160 96 Version Change 05h bit 5 Entity contains an invalid or OBh operating system change 0x2b unsupported firmware or software version OCh operating system loader change 06h bit 6 Hardware Change detected with ODh service or diagnostic partition change associated Entity was successful deassertion OEh management software agent change event means unsuccessful OFh management software applicaton change O7h bit 7 Software or F W Change detected with 10h management sofware middleware change associated Entity was successful deassertion 11h programmable hardware change e g FPGA event means unsuccessful 12h board FRU module change change of a module plugged into associated entity 13h board FRU component change addition or removal of a replaceable component on the board FRU that is not tracked as a FRU Let s analyze the Event Data Event Data 1 OxC1 OxC1 1100 0001 Bit 7 6 11b sensor specific event extension code in byte 2 Bit 5 4 00b unspecified byte 3 Bit 3 0 00001b offset from Event Reading code offset which triggered the event gt 01h bit 1 Firmware or software change detected with associated Entity Informational Success or failure not implied Event Data 2 0x09 bit 7 0 Version change type gt system firmware EFI BIOS change If the sensor s ID is out of the 0 103 range use the clia sensor or pmitoo
56. tion to On Line 5 4 00b unspecified byte 3 Bit 4 multirecDataError Bit 4 SetPortState Error FRU2 Generic Discrete information 04h bit 4 transition to Off Line 01b reserved Bit 3 timeout error Bit 3 Clock Internal 89 Agent Fron Discrete Ox0A Agent FRU2 O5h bit 5 transition to Off Duty 10b OEM code in byte 3 Bit 2 ipmcError Mismatch 59 Board OEM Kontron FRU Data Error 06h bit 6 transition to Degraded 11b sensor specific event extension Bit 1 fruDataError Bit 2 Clock Match Error Not 160 96 Info Agent 0xC5 Detection 07h bit 7 transition to Power Save code in byte 3 Bit 0 commonHeaderError a single clock matches FRUS Generic Discrete FRU 08h bit 8 Install Error 3 0 Offset from Event Reading Bit 1 Internal mismatch 90 Agent Fron Discrete 0x0A Information Code for discrete event state Bit 0 Match Error Not in 5A Board OEM Kontron FRU Agent FRU3 single link matches 160 96 Info Agent 0xC5 e 00h Hardware change detected with 7 6 00b unspecified byte 2 bit 7 0 Version change type associated Entity Informational This 01b previous state and or severity in 00h unspecified offset does not imply whether the byte 2 01h mgmt controller device ID hardware change was successful or not 10b OEM code in byte 2 change in one or more fields from Only that a change occurred 11b sensor specific event extension Get Device ID Ver Change Sensor specific IPMC 01h Firmware or
57. very sensors implemented on the AT8070 and RTM8063 Entity An Entity ID is a standardized numeric code that is used in SDRs to identify the types of physical entities or FRUs in the system In the case of the AT8070 up to 4 entities can be present FRUO Front Board the board itself FRU1 PICMG Rear Transition Module RTM8070 FRU2 Disk1 or Disk Bay1 RTM s Disk1 FRU3 Disk2 or Disk Bay2 RTM s Disk2 IPMI v2 0 Section 39 p 488 9 AT8070 Sensor User Guide v1 0 AN09003 www kontron com Sensor ID Sensors have a numerical ID used to identify them The sensor ID as seen in the list from Annex A might not be the same in particular cases The reason is that the sensor ID s are determined during the board s activation according to the order in which the entities are activated First sensors to be designated an ID are the ones populated on FRUO Entity Front Board Afterwards it depends on which entity is the first to ask for activation Therefore the RTM s sensors might have an offset compared to the IDs from the Annex A list The consequence is that only sensor 0 to 103 will be fixed Therefore all other Entities FRU1 and up sensors from the list should not be referred by a specific numerical ID but rather by their sensor name IE FRU1 AMC power denied 10 AT8070 Sensor User Guide v1 0 AN09003 www kontron com This section does not list all commands that can be used to get information
58. where the meanings of the state s offsets are OEM defined 6 AT8070 Sensor User Guide v1 0 AN09003 www kontron com Event Reading Type Event Reading Type codes are used in SDRs sensor data records and Event Messages to indicate the trigger type for an event These codes are also used in SDRs to indicate what types of present reading a sensor provides Event Reading Type Codes are used to specify a particular enumeration offset that identifies a set of possible events that can be generated by a sensor For Discrete sensors the specification of an Event Reading Type code enumeration also indicates the type of reading the sensor provides we Event Reading Type are listed in the following Table Table L Seri mening MH I ve Code Ranges Event Reading EventReading Type Code Code Description LL EE m nai EE 7 Event Reading Type unspecified iili iin nel u IPMI v2 0 Section 42 1 p 498 Threshold based Indicates a sensor that utilizes values that represent discrete threshold states in sensor access and or events The Event Reading event offsets for the different threshold states are given in Table 42 2 Generic Event Reading Type Codes below Generic Discrete Indicates a sensor that utilizes an Event Reading Type code amp State bit positions event offsets from one of the sets specified for Discrete or digital Discrete Event Reading class in Table
59. x B Annex B to be in error It may still be accessible by software Event Data 2 can be used to provide additional information on the type of failure for this offset 05h FRU failure Event Data 2 and 3 can be used to provide additional information on the type of failure for this offset 00h bit 0 Correctable Memory Error 7 6 00b unspecified byte 2 See Sensor Specific Event See Sensor Specific Event Logging Disabled 01b previous state and or severity in Annex B Annex B Oth bit 1 Event Type Logging byte 2 Disabled 10b OEM code in byte 2 m Specify if the 02h bit 2 Log Area Reset Cleared 11b sensor specific event extension o oe Es DERE status of the 03h bit 3 All Event Logging Disabled code in byte 2 61 Board Event Logging SEL 04h bi 4 SEL Full 5 4 00b unspecified byte 3 160 96 Disable 0x10 Cleared Alm 05h bit 5 SEL Almost Full 01b reserved 3 ost Full Full 06h bit 6 Correctable Machine Check 10b OEM code in byte 3 Error Logging Disabled 11b sensor specific event extension code in byte 3 3 0 Offset from Event Reading Code for discrete event state 00h bit 0 System Reconfigured 7 6 00b unspecified byte 2 See Sensor Specific Event Oth bit 1 OEM System Boot Event 01b previous state and or severity in Annex B 02h bit 2 Undetermined system byte 2 hardware failure 10b OEM code in byte 2 SEL Time Sensor specific 03h bit 3 Entry added to Auxiliary Log

AT8070: IPMI Sensor User Guide

Contents

Download Pdf Manuals

Related Search

Related Contents