Get Device ID
更新时间： 2026/08/06
在Gitcode上查看源码Get Device ID
Change History
| openUBMC Version | Revision Date | Description |
|---|---|---|
| 25.06 | 2025/06/26 | Initial draft: add command details |
Basic Information
Function Description
Obtain the device ID.
Privilege
ReadOnly
Command Information
Request Information
| Byte | Data Field |
|---|---|
| NetFn | App 06h |
| CMD | 01h |
| - | N/A |
Response Information
| Byte | Data Field |
|---|---|
| 1 | Completion Code |
| 2 | Device ID, 00h=unspecified. |
| 3 | Device Revision [7] 1=device provides Device SDRs 0=device does not provide Device SDRs [6:4] reserved, Return as 0. [3:0] Device Revision, binary encoded. |
| 4 | Firmware Revision 1 [7] Device available: 0=normal operation, 1= device firmware, SDR Repository update or self -initialization in progress. [Firmware/SDR Repository updates can be differentiated by issuing a Get SDR command and checking the completion code.] [6:0] Major Firmware Revision, binary encoded. Note: Field 4 in Get Device ID cannot be used to distinguish iBMC V2 from iBMC V3 because in the two-segment version scenario, the latest field of the iBMC version is greater than 5. Run the ipmi command 30 90 08 00 01 00 ff to query the firmware version. If the version number is in four-segment format and the first segment is greater than or equal to 5, the firmware version is V3. Otherwise, the firmware version is V2. |
| 5 | Firmware Revision 2: Minor Firmware Revision. BCD encoded. |
| 6 | IPMI Version. Holds IPMI Command Specification Version. BCD encoded. 00h=reserved. Bits 7:4 hold the Least Significant digit of the revision, while bits 3:0 hold the Most Significant bits. 02h for implementations that provide IPMI v2.0 capabilities. |
| 7 | Additional Device Support (formerly called IPM Device Support). Lists the IPMI 'logical device' commands and functions that the controller supports that are in addition to the mandatory IPM and Application commands. [7] Chassis Device (device functions as chassis device per ICMB spec.) [6] Bridge (device responds to Bridge NetFn commands) [5] IPMB Event Generator (device generates event messages [platform event request messages] onto the IPMB.) [4] IPMB Event Receiver (device accepts event messages [platform event request messages] from the IPMB.) [3] FRU Inventory Device [2] SEL Device [1] SDR Repository Device [0] Sensor Device On the system interface, the BMC returns 2Fh. On other interfaces, the BMC returns 2Dh. On the system interface, the BMC returns 8Fh. On other interfaces, the BMC returns 8Dh. |
| 8:10 | Manufacturer ID, LS Byte first. The manufacturer ID is a 20-bit value that is derived from the IANA 'Private Enterprise' ID (see below). Most significant four bits=reserved (0000b). 000000h=unspecified. 0FFFFFh=reserved. This value is binary encoded. E.g. the ID for the IPMI forum is 7154 decimal, which is 1BF2h, which would be stored in this record as F2h, 1Bh, 00h for bytes 8 through 10, respectively. |
| 11:12 | Product ID, LS Byte first. This field can be used to provide a number that identifies a particular system, module, add-in card, or board set. The number is specified according to the manufacturer given by Manufacturer ID (see below). 0000h=unspecified. FFFFh=reserved. NOTE: When the BMC is used, the value of ProductID must be the same as that in the HPM upgrade package. |
| (13:16) | Auxiliary Firmware Revision Information. This field is optional. Byte13: 14-Board ID, LS Byte first. OEM by Huawei. Byte15-Version, BMC Platform Verify. OEM by Huawei. For iBMCBMC V2(Hi1710): [7:4]-Version.V 0-V100 1-V200 [3:0]-Version.R 0-R001 1-R002 For iBMCBMC V3(Hi1711): Release Major Firmware Revision. BCD encoded. Byte16-Reserved For iBMCBMC V2(Hi1710): ECO-FT support status. For iBMCBMC V3(Hi1711): Release Minor Firmware Revision. BCD encoded. |
Command Example
Obtain the device ID.
Request:
bash
ipmicmd -k "0f 00 06 01" smi 0Response:
text
0f 07 00 01 00 01 81 03 01 02 af db 07 00 0d 00 90 00 17 43