Get Event Management
更新时间： 2026/08/06
在Gitcode上查看源码Get Event Management
Change History
| openUBMC Version | Revision Date | Description |
|---|---|---|
| 25.06 | 2025/06/26 | Initial draft: add command details |
Basic Information
Function Description
This API is used to query event control information.
Privilege
Command Information
Request Information
| Byte | Data Field |
|---|---|
| NetFn | 30h |
| CMD | 94h |
| 1:3 | Manufacturer 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. |
| 4 | Sub command, subcommand = 34h |
| 5:8 | Event ID, in the little endian format. The event ID is carried when the event is reported. It is a new event ID. |
| 9 | Segment, 1 based For high-performance servers such as 9032, each segment indicates a 4-socket system. Segment Id is used to identify a 4-socket system. The value 0 indicates that no segment is involved. The value 0xff indicates that all segments are involved. |
| 10 | Indicates the group ID. If the slot ID (silkscreen number) of a product is repeated, the group ID is used to identify the product. The group ID starts from 1. The value 0xff indicates all groups of the specified segment ID. For example, the DIMM numbers on different memory risers are the same. The group ID is used to identify the memory riser. If the value of GroupId is 0xff, the DIMM numbers on all memory risers are the same. In most cases, the component silkscreens are different, in this case, there is only one group. Therefore, GroupId is set to 1. |
| 11:12 | This 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. |
| 13 | Block Selector (00h if parameter does not require a block number) |
| 14 | For details about the event information parameters, see Table 1. |
| 15 | Indicates the read offset. The value starts from 0. |
| 16 | Length: read length. |
Response Information
| Byte | Data Field |
|---|---|
| 1 | Completion Code |
| 2:4 | Manufacturer 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. |
| 5 | End of List, indicating whether the current data is complete. Long data may need to be read multiple times. This field is used to check whether data is completely read. |
| 6:N | [7:1]: reserved [0]: End of list 0=last data 1=middle data Indicates the data. The returned data may be less than or equal to the read length. |
Command Example
Display event control information.
Request:
bash
ipmicmd -k "0f 00 MM NN" smi 0Response:
text
0f MM NN