Set Event Management
更新时间: 2026/08/06
在Gitcode上查看源码

Set Event Management

Change History

openUBMC VersionRevision DateDescription
25.062025/06/26Initial draft: add command details

Basic Information

Function Description

Configure event management and control.

Privilege

ReadOnly

Command Information

Request Information

ByteData Field
NetFn30h
CMD94h
1:3Manufacturer ID, LS Byte first. The length is fixed to three bytes. For example, if the vendor ID is 2011 and the corresponding hexadecimal value is 0x0007DB, the first byte is DBh, the second byte is 07h, and the third byte is 00h.
4Sub command, subcommand = 35h
5:08Indicates the event ID, which is in the little endian format. The event ID is carried when the event is reported.
9Segment ID, indicating the segment of the event. The value is 1 based on.
For high-performance servers such as 9032, each segment indicates a 4-socket system. The segment ID is used to identify a 4-socket system. The value 0 indicates that this parameter is not involved.
10Group ID, indicating the ID of the group to which an event belongs.
If there are duplicate slot IDs (silkscreen numbers), use group IDs to identify them. The group ID starts from 1. For example, if a DIMM is installed on a memory riser, the number of the DIMM is the same on different memory risers. Group IDs are used to identify memory risers. If the value of GroupId is 0xff, DIMMs on all memory risers are identified, in most cases, the component silkscreens are unique. In this case, there is only one group of silkscreens. Therefore, set GroupId to 1.
11:12This byte indicates the event body number, which starts from 1 and increases in the same sequence as the silk screen number.
The value 0xff indicates that all event bodies of a specified segment and group are involved. The value 0 indicates that no event body is involved.
13Parameter selector. For details, see Table 1.
14[7:1]: reserved
[0]: cascading flag
0: last data
1: middle data
15Offset, indicating the offset of the written data. The value starts from 0.
Write data in sequence when they are written as multiple frames.
16Length: length of the data to be written.
17:NData to write

Response Information

ByteData Field
1Completion Code
2:04Manufacturer ID, LS Byte first. The length is fixed to three bytes. For example, if the vendor ID is 2011 and the corresponding hexadecimal value is 0x0007DB, the first byte is DBh, the second byte is 07h, and the third byte is 00h.

Reference

Table 1 Event Info

Parameter#Data#(Decimal)
Event Moderead-writeData1: event monitoring mode
0h: no monitoring
1 hour - local automatic scanning
2h: manual simulation
3h – Reserved
4h: reserved
5h: controlled by a third party (The State attribute is directly updated by the local or BMC external module, and is not scanned by the monitoring task.)
data2: analog operation. This field is valid when data1 is 02h. Otherwise, this field is set to 0. This field is also set to 0 when data1 is read.
0h: disabled
1h – enabled
data3: event status. This field is valid when data2 is 01h. Otherwise, this field is set to 0. This field is also set to 0 for the read operation.
0h: recovery
1h: generated
data4:4 – Reserved. The value is 0 (reserved for threshold event simulation reading, which is not implemented currently).
1
Event Stateread-writedata1 – Event State: event status
0h: not generated
1h: generated
2
Description Dynamic DataWrite onlyBlock Selector=Number of dynamic data. The value ranges from 1 to 4.
Data1:N: dynamic data of event description
3
Suggestion Dynamic DataWrite onlyBlock Selector=Dynamic data number. The value ranges from 1 to 2.
Data1:N: dynamic data of event handling suggestions
4

Command Example

Configure event management and control.

Request:

bash
ipmicmd -k "0f 00 30 94 db 07 00 35 23 00 00 00 00 01 00 01 01 00 00 20 01" smi 0

Response:

text
0f db 07 00

Back to Index