
Publication No. 500-657806-000 Rev. G
IPMI Firmware and OEM Extensions 91
E.5 Platform Events
The Abaco IPMI subsystem contains several sensors for reading the voltages and
temperature of the system. Each sensor is configured with a threshold, hysteresis,
and nominal value. When the value of a sensor crosses a threshold, a platform
event is sent to the “Event Receiver”.
The following events are generated by the Abaco IPMI Subsystem:
• Threshold Events – Events of this type are generated if the sensors exceed
their threshold settings. Threshold events are either an Assertion Event or a
De-Assertion Event.
The Generator ID field is a required element of an Event Request Message. For
IPMB messages, this field is equated to the Requestor’s Slave Address and LUN
fields. Thus, the Generator ID information is not carried in the data field of an
IPMB request message.
Table E-18 NetFn 0x04, Cmd 0x02
Byte
Value
Data Field
Comments
Request-data
-
-
Generator ID (RqSA, RqLun)
1
03h
EvMRev
IPMB v 1.0 message
2
XXh
Sensor Type
02h = voltage sensors
01h = temperature sensors
3
XXh
Sensor #
Sensor numbers will be one of
41h, 42h, 43h, 44h, 60h or 61h
4
XXh
[7] - Event Dir
0b = Assertion Event
1b = De-assertion Event
[6:0] - Event Type
Event Type indicates the type
of threshold crossing that
produced the event.
5
XXh
Event Data 1
[7:6] - 01b = trigger reading in byte2
[5:4] - 01b = trigger threshold value in byte3
[3:0] - offset from Event/Reading
code for threshold event
6
XXh
Event Data 2
Sensor reading
7
XXh
Event Data 3
Threshold value that triggered
event.
Response-data 1
XXh
Completion Code