Computer Cheese: [IPMI] Event Commands

[IPMI] Event Commands Set Event Receiver- NetFn Sensor/Event (0x04h) CMD = 0x00h, Privilege Level = Admin, M/O = M [Event Generator], O [Event Receiver]
| Linux |
[IPMItool]

ipmitool raw 0x04 0x00 D[1] Byte 1
Event Receiver Slave Address
FFh disables Event Message Generation, Otherwise:
[7:1] - IPMB (I2C) Slave Address
[0] - always 0b when [7:1] hold I2C slave address
D[2] Byte 2
Request Data Byte 2
[7:2] - reserved
[1:0] - Event Receiver LUN

[ipmiutil]

ipmiutil cmd 00 20 10 00 D[1] Byte 1
Event Receiver Slave Address
FFh disables Event Message Generation, Otherwise:
[7:1] - IPMB (I2C) Slave Address
[0] - always 0b when [7:1] hold I2C slave address
D[2] Byte 2
Request Data Byte 2
[7:2] - reserved
[1:0] - Event Receiver LUN

icmd 00 20 10 00 D[1] Byte 1
Event Receiver Slave Address
FFh disables Event Message Generation, Otherwise:
[7:1] - IPMB (I2C) Slave Address
[0] - always 0b when [7:1] hold I2C slave address
D[2] Byte 2
Request Data Byte 2
[7:2] - reserved
[1:0] - Event Receiver LUN

[FreeIPMI]

ipmi-raw 0x00 0x04 0x00 D[1] Byte 1
Event Receiver Slave Address
FFh disables Event Message Generation, Otherwise:
[7:1] - IPMB (I2C) Slave Address
[0] - always 0b when [7:1] hold I2C slave address
D[2] Byte 2
Request Data Byte 2
[7:2] - reserved
[1:0] - Event Receiver LUN

| MS-DOS |
[ipmitool]

ipmitool 20 10 00 Data[1:2]

For example Hint: hover over Place your mouse over the highlighted area in below
for Response Data description
[IPMItool in Linux]

$ ipmitool raw 0x04 0x00 0x20 0x00

[ipmiutil in Linux]

$ icmd 00 20 10 00 20 00
ipmiutil ver 3.08
icmd ver 3.08
This is a test tool to compose IPMI commands.
Do not use without knowledge of the IPMI specification.
-- BMC version 1.7, IPMI version 2.0
send_icmd ret = 0
ipmiutil cmd, completed successfully

[FreeIPMI in Linux]

$ ipmi-raw 0x00 0x04 0x00 0x20 0x00
rcvd: 00 00 Byte 1
Completion Code
00h = Command Completed Normally

[ipmitool in DOS]

C:\> ipmitool 20 10 00 20 00
20 14 00 00

Get Event Receiver - NetFn = Sensor/Event (0x04h), CMD = 0x01h, Privilege Level = User, M/O = M [Event Generator], O [Event Receiver]
| Linux |
[IPMItool]

ipmitool raw 0x04 0x01

[ipmiutil]

ipmiutil cmd 00 20 10 01
icmd 00 20 10 01

[FreeIPMI]

ipmi-raw 0x00 0x04 0x01

| MS-DOS |
[ipmitool]

ipmitool 20 10 01

For example Hint: hover over Place your mouse over the highlighted area in below
for Response Data description
[IPMItool in Linux]

$ ipmitool raw 0x04 0x01
20 Byte 2
Event Receiver Slave Address
FFh indicates Event Message Generation has been disabled. Otherwise:
[7:1] - IPMB (I2C) Slave Address
[0] - always 0b when [7:1] hold I2C slave address
00 Byte 3
Response Data Byte 3
[7:2] - reserved
[1:0] - Event Receiver LUN

[ipmiutil in Linux]

$ icmd 00 20 10 01
ipmiutil ver 3.08
icmd ver 3.08
This is a test tool to compose IPMI commands.
Do not use without knowledge of the IPMI specification.
-- BMC version 1.7, IPMI version 2.0
respData[len=2]: 20 Byte 2
Event Receiver Slave Address
FFh indicates Event Message Generation has been disabled. Otherwise:
[7:1] - IPMB (I2C) Slave Address
[0] - always 0b when [7:1] hold I2C slave address
00 Byte 3
Response Data Byte 3
[7:2] - reserved
[1:0] - Event Receiver LUN

send_icmd ret = 0
ipmiutil cmd, completed successfully

[FreeIPMI in Linux]

$ ipmi-raw 0x00 0x04 0x01
rcvd: 01 00 Byte 1
Completion Code
00h = Command Completed Normally
20 Byte 2
Event Receiver Slave Address
FFh indicates Event Message Generation has been disabled. Otherwise:
[7:1] - IPMB (I2C) Slave Address
[0] - always 0b when [7:1] hold I2C slave address
00 Byte 3
Response Data Byte 3
[7:2] - reserved
[1:0] - Event Receiver LUN

[ipmitool in DOS]

C:\> ipmitool 20 10 01
20 14 01 00 20 00

Platform Event Message - NetFn = Sensor/Event (0x04h), CMD = 0x02h, Privilege Level = Operator, M/O = M
| Linux |
[IPMItool]
IPMB MESSAGING

ipmitool raw 0x04 0x02 D[1] Byte 1
EvMRev
One byte
Event Message Revision
This field is used to identify different revisions of the Event Message format
The revision number shall be 04h for Event Messages that comply with the format given in this specification
IPMI v1.0 messages use 03h
It is recommended that software be able to interpret both versions
D[2] Byte 2
Sensor Type
One byte
Indicates the event class or type of sensor that generated the Event Message
The Sensor Type Codes are specified in Table 42-3, Sensor Type Codes
D[3] Byte 3
Sensor #
One byte
A unique number (within a given sensor device) representing the 'sensor' within the management controller that generated the Event Message
Sensor numbers are used for both identification and access of sensor information, such as getting and setting sensor thresholds
D[4] Byte 4
Event Dir | Event Type
Event Dir
1-bit
Indicates the event transition direction
(0 = Assertion Event, 1 = Deassertion Event)
Event Type
7-bits
This field indicates the type of threshold crossing or state transition (trigger) that produced the event
This is encoded using the Event/Reading Type Code
See Section 42, Sensor and Event Code Tables
D[5] Byte 5
Event Data 1
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents
D[6] Byte 6
Event Data 2
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents
D[7] Byte 7
Event Data 3
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents

SYSTEM INTERFACE

ipmitool raw 0x04 0x02 D[1] Byte 1
Generator ID
This field identifies the device that has generated the Event Message
This is the 7-bit Requester’s Slave Address (RqSA) and 2-bit Requester’s LUN (RqLUN) if the message was received from the IPMB, or the 7-bit System Software ID if the message was received from system software
D[2] Byte 2
EvMRev
One byte
Event Message Revision
This field is used to identify different revisions of the Event Message format
The revision number shall be 04h for Event Messages that comply with the format given in this specification
IPMI v1.0 messages use 03h
It is recommended that software be able to interpret both versions
D[3] Byte 3
Sensor Type
One byte
Indicates the event class or type of sensor that generated the Event Message
The Sensor Type Codes are specified in Table 42-3, Sensor Type Codes
D[4] Byte 4
Sensor #
One byte
A unique number (within a given sensor device) representing the 'sensor' within the management controller that generated the Event Message
Sensor numbers are used for both identification and access of sensor information, such as getting and setting sensor thresholds
D[5] Byte 5
Event Dir | Event Type
Event Dir
1-bit
Indicates the event transition direction
(0 = Assertion Event, 1 = Deassertion Event)
Event Type
7-bits
This field indicates the type of threshold crossing or state transition (trigger) that produced the event
This is encoded using the Event/Reading Type Code
See Section 42, Sensor and Event Code Tables
D[6] Byte 6
Event Data 1
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents
D[7] Byte 7
Event Data 2
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents
D[8] Byte 8
Event Data 3
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents

ipmitool event <num> num
Number
Send generic test events
    1 : Temperature - Upper Critical - Going High
    2 : Voltage Threshold - Lower Critical - Going Low
    3 : Memory - Correctable ECC

ipmitool event <sensorid> sensorid
Sensor ID String
Sensor ID string to use for event data
<state> state
Sensor State
Sensor state, use 'list' to see possible states for sensor
[event_dir] event_dir
Event Direction
assert, deassert [default=assert]

[ipmiutil]
IPMB MESSAGING

ipmiutil cmd 00 20 10 02 D[1] Byte 1
EvMRev
One byte
Event Message Revision
This field is used to identify different revisions of the Event Message format
The revision number shall be 04h for Event Messages that comply with the format given in this specification
IPMI v1.0 messages use 03h
It is recommended that software be able to interpret both versions
D[2] Byte 2
Sensor Type
One byte
Indicates the event class or type of sensor that generated the Event Message
The Sensor Type Codes are specified in Table 42-3, Sensor Type Codes
D[3] Byte 3
Sensor #
One byte
A unique number (within a given sensor device) representing the 'sensor' within the management controller that generated the Event Message
Sensor numbers are used for both identification and access of sensor information, such as getting and setting sensor thresholds
D[4] Byte 4
Event Dir | Event Type
Event Dir
1-bit
Indicates the event transition direction
(0 = Assertion Event, 1 = Deassertion Event)
Event Type
7-bits
This field indicates the type of threshold crossing or state transition (trigger) that produced the event
This is encoded using the Event/Reading Type Code
See Section 42, Sensor and Event Code Tables
D[5] Byte 5
Event Data 1
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents
D[6] Byte 6
Event Data 2
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents
D[7] Byte 7
Event Data 3
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents

icmd 00 20 10 02 D[1] Byte 1
EvMRev
One byte
Event Message Revision
This field is used to identify different revisions of the Event Message format
The revision number shall be 04h for Event Messages that comply with the format given in this specification
IPMI v1.0 messages use 03h
It is recommended that software be able to interpret both versions
D[2] Byte 2
Sensor Type
One byte
Indicates the event class or type of sensor that generated the Event Message
The Sensor Type Codes are specified in Table 42-3, Sensor Type Codes
D[3] Byte 3
Sensor #
One byte
A unique number (within a given sensor device) representing the 'sensor' within the management controller that generated the Event Message
Sensor numbers are used for both identification and access of sensor information, such as getting and setting sensor thresholds
D[4] Byte 4
Event Dir | Event Type
Event Dir
1-bit
Indicates the event transition direction
(0 = Assertion Event, 1 = Deassertion Event)
Event Type
7-bits
This field indicates the type of threshold crossing or state transition (trigger) that produced the event
This is encoded using the Event/Reading Type Code
See Section 42, Sensor and Event Code Tables
D[5] Byte 5
Event Data 1
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents
D[6] Byte 6
Event Data 2
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents
D[7] Byte 7
Event Data 3
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents

SYSTEM INTERFACE

ipmiutil cmd 00 20 10 02 D[1] Byte 1
Generator ID
This field identifies the device that has generated the Event Message
This is the 7-bit Requester’s Slave Address (RqSA) and 2-bit Requester’s LUN (RqLUN) if the message was received from the IPMB, or the 7-bit System Software ID if the message was received from system software
D[2] Byte 2
EvMRev
One byte
Event Message Revision
This field is used to identify different revisions of the Event Message format
The revision number shall be 04h for Event Messages that comply with the format given in this specification
IPMI v1.0 messages use 03h
It is recommended that software be able to interpret both versions
D[3] Byte 3
Sensor Type
One byte
Indicates the event class or type of sensor that generated the Event Message
The Sensor Type Codes are specified in Table 42-3, Sensor Type Codes
D[4] Byte 4
Sensor #
One byte
A unique number (within a given sensor device) representing the 'sensor' within the management controller that generated the Event Message
Sensor numbers are used for both identification and access of sensor information, such as getting and setting sensor thresholds
D[5] Byte 5
Event Dir | Event Type
Event Dir
1-bit
Indicates the event transition direction
(0 = Assertion Event, 1 = Deassertion Event)
Event Type
7-bits
This field indicates the type of threshold crossing or state transition (trigger) that produced the event
This is encoded using the Event/Reading Type Code
See Section 42, Sensor and Event Code Tables
D[6] Byte 6
Event Data 1
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents
D[7] Byte 7
Event Data 2
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents
D[8] Byte 8
Event Data 3
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents

icmd 00 20 10 02 D[1] Byte 1
Generator ID
This field identifies the device that has generated the Event Message
This is the 7-bit Requester’s Slave Address (RqSA) and 2-bit Requester’s LUN (RqLUN) if the message was received from the IPMB, or the 7-bit System Software ID if the message was received from system software
D[2] Byte 2
EvMRev
One byte
Event Message Revision
This field is used to identify different revisions of the Event Message format
The revision number shall be 04h for Event Messages that comply with the format given in this specification
IPMI v1.0 messages use 03h
It is recommended that software be able to interpret both versions
D[3] Byte 3
Sensor Type
One byte
Indicates the event class or type of sensor that generated the Event Message
The Sensor Type Codes are specified in Table 42-3, Sensor Type Codes
D[4] Byte 4
Sensor #
One byte
A unique number (within a given sensor device) representing the 'sensor' within the management controller that generated the Event Message
Sensor numbers are used for both identification and access of sensor information, such as getting and setting sensor thresholds
D[5] Byte 5
Event Dir | Event Type
Event Dir
1-bit
Indicates the event transition direction
(0 = Assertion Event, 1 = Deassertion Event)
Event Type
7-bits
This field indicates the type of threshold crossing or state transition (trigger) that produced the event
This is encoded using the Event/Reading Type Code
See Section 42, Sensor and Event Code Tables
D[6] Byte 6
Event Data 1
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents
D[7] Byte 7
Event Data 2
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents
D[8] Byte 8
Event Data 3
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents

[FreeIPMI]
IPMB MESSAGING

ipmi-raw 0x00 0x04 0x02 D[1] Byte 1
EvMRev
One byte
Event Message Revision
This field is used to identify different revisions of the Event Message format
The revision number shall be 04h for Event Messages that comply with the format given in this specification
IPMI v1.0 messages use 03h
It is recommended that software be able to interpret both versions
D[2] Byte 2
Sensor Type
One byte
Indicates the event class or type of sensor that generated the Event Message
The Sensor Type Codes are specified in Table 42-3, Sensor Type Codes
D[3] Byte 3
Sensor #
One byte
A unique number (within a given sensor device) representing the 'sensor' within the management controller that generated the Event Message
Sensor numbers are used for both identification and access of sensor information, such as getting and setting sensor thresholds
D[4] Byte 4
Event Dir | Event Type
Event Dir
1-bit
Indicates the event transition direction
(0 = Assertion Event, 1 = Deassertion Event)
Event Type
7-bits
This field indicates the type of threshold crossing or state transition (trigger) that produced the event
This is encoded using the Event/Reading Type Code
See Section 42, Sensor and Event Code Tables
D[5] Byte 5
Event Data 1
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents
D[6] Byte 6
Event Data 2
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents
D[7] Byte 7
Event Data 3
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents

SYSTEM INTERFACE

ipmi-raw 0x00 0x04 0x02 D[1] Byte 1
Generator ID
This field identifies the device that has generated the Event Message
This is the 7-bit Requester’s Slave Address (RqSA) and 2-bit Requester’s LUN (RqLUN) if the message was received from the IPMB, or the 7-bit System Software ID if the message was received from system software
D[2] Byte 2
EvMRev
One byte
Event Message Revision
This field is used to identify different revisions of the Event Message format
The revision number shall be 04h for Event Messages that comply with the format given in this specification
IPMI v1.0 messages use 03h
It is recommended that software be able to interpret both versions
D[3] Byte 3
Sensor Type
One byte
Indicates the event class or type of sensor that generated the Event Message
The Sensor Type Codes are specified in Table 42-3, Sensor Type Codes
D[4] Byte 4
Sensor #
One byte
A unique number (within a given sensor device) representing the 'sensor' within the management controller that generated the Event Message
Sensor numbers are used for both identification and access of sensor information, such as getting and setting sensor thresholds
D[5] Byte 5
Event Dir | Event Type
Event Dir
1-bit
Indicates the event transition direction
(0 = Assertion Event, 1 = Deassertion Event)
Event Type
7-bits
This field indicates the type of threshold crossing or state transition (trigger) that produced the event
This is encoded using the Event/Reading Type Code
See Section 42, Sensor and Event Code Tables
D[6] Byte 6
Event Data 1
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents
D[7] Byte 7
Event Data 2
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents
D[8] Byte 8
Event Data 3
One to three Bytes
The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM)
The contents and format of this field is specified in Table 29-6, Event Request Message Event Data Field Contents

| MS-DOS |
[ipmitool]
IPMB MESSAGING

ipmitool 20 10 02 Data[1:7]

SYSTEM INTERFACE

ipmitool 20 10 02 Data[1:8]

For example Hint: hover over Place your mouse over the highlighted area in below
for Response Data description
[IPMItool in Linux]

[ipmiutil in Linux]

$ icmd 00 20 10 02 01 04 0c 00 00 01 00 00
ipmiutil ver 3.08
icmd ver 3.08
This is a test tool to compose IPMI commands.
Do not use without knowledge of the IPMI specification.
-- BMC version 1.7, IPMI version 2.0
send_icmd ret = 0
ipmiutil cmd, completed successfully
$ isel
ipmiutil ver 3.08
isel: version 3.08
-- BMC version 1.07, IPMI version 2.0
SEL Ver fe Support 0f, Size = 3582 records (Used=1, Free=3581)
RecId Date/Time_______ SEV Src_ Evt_Type___ Sens# Evt_detail - Trig [Evt_data]
0001 01/01/12 11:23:14 MAJ EFI Memory #00 Uncorrectable ECC, DIMM[0] 00 [01 00 00]
ipmiutil sel, completed successfully

[FreeIPMI in Linux]

[ipmitool in DOS]
Unknown #0x17 Event

C:\> ipmitool 20 10 02 00 04 30 17 75 a0 04 07
20 14 02 00

BIOS Event

C:\> ipmitool 20 10 02 01 04 0c 00 00 01 00 00
20 14 02 00

SMI Handler Event

C:\> ipmitool 20 10 02 21 04 0c 00 00 01 00 00
20 14 02 00

System Management Software Event

C:\> ipmitool 20 10 02 41 04 0c 00 00 01 00 00
20 14 02 00

Remote Console Software Event

C:\> ipmitool 20 10 02 81 04 0c 00 00 01 00 00
20 14 02 00

Terminal Mode Remote Console Software Event

C:\> ipmitool 20 10 02 8F 04 0c 00 00 01 00 00
20 14 02 00

Reference
[1] "Intelligent Platform Management Interface Specification Second Generation v2.0 Document Revision 1.1"
https://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/ipmi-second-gen-interface-spec-v2-rev1-1.pdf
[2] "IPMItool" http://sourceforge.net/projects/ipmitool/
[3] "IPMI Command Test Tool" http://www.intel.com/design/servers/ipmi/ipmi_tool.htm
[4] "IPMIUTIL USER GUIDE" http://ipmiutil.sourceforge.net/
[5] "FreeIPMI Documentation" http://www.gnu.org/software/freeipmi/index.html

Last Updated: May 24, 2018

Computer Cheese

Pages

Friday, May 10, 2013

[IPMI] Event Commands

No comments:

Post a Comment