Get Device Status
更新时间： 2026/08/06
在Gitcode上查看源码Get Device Status
Change History
| openUBMC Version | Revision Date | Description |
|---|---|---|
| 25.06 | 2025/06/26 | Initial draft: add command details |
Basic Information
Function Description
The device status is queried.
Privilege
Command Information
Request Information
| Byte | Data Field |
|---|---|
| NetFn | 30h |
| CMD | 92h |
| 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, sub command=06h |
| 5 | Device IDTable 1 |
| 6 | reserved. |
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 | device status1 |
| 6 | device status2 |
| 7 | device status3 |
| 8 | device status4 |
| 9 | device status5 |
| 10 | device status6 |
Reference Information
Table 1 Definition of the Device Status Code Reported by the BIOS
| Part | BIOS -> BMC event format | BIOS | ||
|---|---|---|---|---|
| Device ID | Device Status1 | Event | Alarm Description | |
| CPU | 01h | 00h | Firmware Mismatch | When the system is started, it checks whether the CPU microcode is loaded. If an exception occurs, the system reports the exception information to the BMC through a BT message. |
| 01h | CPU Mismatch Device Status2: CPU ID | Check whether the CPU is supported. If the BMC is not supported, a BT message is sent to report the BMC exception. | ||
| 02h | CPU BIST Failure Device Status2: CPU ID Device Status3: least significant eight bits of Cache Way Number Device Status4: most significant eight bits of Cache Way Number Device Status3: Isolation core number Lower eight bits of the number of isolated cores Device Status3: Isolation core number High-order eight bits of the number of isolated cores | When the system is powered on, the CPU performs BIST detection. If an exception occurs, the CPU reports the exception information to the BMC through a BT message if the system can be powered on. Device Status3 to Device Status6 are parsed only by the BMC of storage products. The BMC of computing and TCE products does not parse Device Status3 to Device Status6. The interfaces are compatible. | ||
| 04h | Cpu Offline Succeed Device Status2: CPU ID | The CPU is successfully offline, that is, a CPU is successfully isolated. This is a message level and can be used by the BMC to monitor whether the current CPU is online in real time. [EX] | ||
| 05h | Unsupported opcode Device Status2: CPU ID | An error occurs when the CPU executes an unsupported machine code at run time. This error is a fatal error. [EX] | ||
| 07h | VMSE Link Failure In Mirror Mode Device Status2: CPU ID Device Status3: VMSE Channel Device Status4: Node ID | In memory mirroring mode, the SMI2 link fails, which is an uncorrectable but recoverable error. [EX] | ||
| 08h | VMSE Link Failure Device Status2: CPU ID Device Status3: VMSE Channel Device Status4: Node ID | In non-memory mirroring mode, the SMI2 link fails. This is a fatal error. [EX] | ||
| 09h | VMSE Err Observed Device Status2: CPU ID Device Status3: VMSE Channel Device Status4: Node ID | Jordan Creek internal error, which is an uncorrectable non-fatal error. [EX] | ||
| 0ah | VMSE DIMM Register Parity Error Device Status2: CPU ID Device Status3: VMSE Channel Device Status4: Node ID | A parity error occurs on the VMSE link. This is a fatal error. [EX] | ||
| 0bh | VMSE Nb Persistent Counter Reached Device Status2: CPU ID Device Status3: VMSE Channel Device Status4: Node ID | The number of errors that occur when data is sent from Jordan Creek to the memory controller reaches the threshold. This is a non-fatal error. [EX] | ||
| 0ch | VMSE Sb Persistent Counter Reached Device Status2: CPU ID Device Status3: VMSE Channel Device Status4: Node ID | The number of errors generated during the process of sending data from the memory controller to Jordan Creek reaches the threshold. This is a non-fatal error. [EX] | ||
| 0dh | Qpi Error Detected Device Status2: CPU ID Device Status3: QPI ID Device Status4: MSCOD Device Status5: Current Tx Lane(start with 1) Device Status6: Current Rx Lane(start with 1) | The QPI link is faulty. MSCOD: helps locate the cause of a fault. Event code: 0x00: A QPI fault (Config error) is detected during power-on. 0x01: QPI link failure is detected during the power-on self-test. 0x02: QPI degrade failure is detected during the power-on self-test. Current Tx Lane: The default value is 0x14. If the value is not equal to this value, the TX link is faulty. Current Rx Lane: The default value is 0x14. If the value is not equal to this value, the RX link is faulty. [EX] | ||
| 0eh | Socket Boot Isolation Device Status2: CPU ID | In the startup phase, if the CPU self-check fails, the CPU is isolated and the isolated socket information is sent to the BMC. [EX] | ||
| 0fh | Core Boot Isolation Device Status2: CPU ID Device Status3: Core ID Bitmap Bit0 to bit7 correspond to core0 to core7 respectively. Device Status4: Core ID Bitmap Bit0 to bit7 correspond to Core8 to Core15 respectively. Device Status5: Core ID Bitmap Bit0 to bit7 correspond to core16 to core23 respectively. ...... Considering future scalability, the number of device statuses is not limited. | In the startup phase, if the core self-check fails, the core is isolated and the isolated core information is sent to the BMC. [EX] | ||
| 10h | PCI resource configuration Device Status2: CPU ID | During the startup, if a card that requires I/O resources is inserted into a restricted slot, the BIOS stops. [EX] | ||
| 11h | Vmse Config Error Device Status2: CPU ID Device Status3: Vmse channel id Device Status4: Node ID | JC errors sent during startup or SMI2 channel errors between the CPU and JC [EX] | ||
| Pcie | 02h | 00h | Pcie error: Device Status 2: Bus Device Status 3: Device Device Status 4: Function | pcie device fatal error |
| F7h | MMIO resource not enough | |||
| F8h | legacy IO resource not enough | |||
| F9h | legacy oprom resource not enough | |||
| FAh | PCIe Bandwitdh Error | |||
| F5h | Pcie error: Device Status 2: Bus Device Status 3: Device Device Status 4: Function Device Status 5: MaxSpeed Device Status 6: NegoSpeed | PCie Link Speed Error | ||
| Video | 03h | 00h | Video device error | When the graphics card chip is abnormal, a BT message is sent to report the exception to the BMC. |
| Memory | 04h | 00h | Memory config error: Device Status 2: NODE ID Device Status 3: channel id Device Status 4: dimm id Device Status 5:serverity (0:invalid,1:ok,2:minor,3:major,4:critical) | 1. Check whether the DIMM installation method is correct. If the DIMM installation method is abnormal, report the exception information to the BMC through BT messages when the server can be powered on. 2. When no DIMM is detected, a BT message is sent to report an alarm indicating that no DIMM is detected on the BMC. 3. Detects DIMM exceptions. If the memory is detected during the startup, the memory is masked after the training is complete. The BMC exception is reported through BT messages, and a message indicating that the memory cannot be used is displayed on the screen. 4. During the startup, the BIOS reports all MRC faults through this event. The MRC faults are detected and generated by the code provided by Intel. Currently, Intel provides only the code but does not provide any document. Therefore, the BIOS cannot know which MRC faults are reported in which scenarios, the severity of each MRC fault cannot be determined. 5. The severity of MRC errors is reported by the BIOS as a reference for the BMC to generate alarms. Currently, all MRC faults are reported as critical, which is the same as the current configuration error severity. If other severities are reported, the BIOS needs to adjust them. |
| 01h | DDDC Sparing Device Status 2: NODE ID Device Status 3: channel id Device Status 4: dimm id Device Status 5: rank id | For a rank (x4 chips with lock-step enabled) that meets the DDDC feature, when the number of correctable errors on the rank exceeds the threshold, the BIOS replaces the faulty chip with a redundant chip in the rank. This error is a correctable error. | ||
| 02h | RANK Sparing Device Status 2: NODE ID Device Status 3: channel id Device Status 4: dimm id Device Status 5: error rank id | When the memory rank sparing feature is enabled and the number of correctable errors on a rank exceeds the threshold, the BIOS replaces the faulty rank with a backup rank. | ||
| 03h | Devicce Tagging Device Status 2: NODE ID Device Status 3: channel id Device Status 4: dimm id Device Status 5: rank id | For a rank (x4 or x8 chips with lock-step enabled) that meets the DeviceTagging feature, when the number of correctable errors on the rank exceeds the threshold, the BIOS replaces the faulty chip with an odd or even chip. This error is a correctable error. | ||
| 04h | Memory migration Device Status 2: ErrorNode Device Status 3: SpareNode Device Status 4: EventID | Memory migration: ErrorNode: faulty MBM SpareNode: backup board EventID: migration event code EventID: 0x0: MIGRATION_SUCCESS 0x1: MIGRATION_CFG_ERR 0x2: MIGRATION_NON_NUMA 0x3: MIGRATION_SMALL_MEMSIZE 0x4: MIGRATION_ONLINE_FAIL 0x5: MIGRATION_COPY_FAIL 0x6: MIGRATION_ONLINE_INPROGRESS 0x7: MIGRATION_ONLINE_SUCCESS 0x8: MIGRATION_INPROGRESS 0x9: MIGRATION_BEGIN 0xa: MIGRATION_CANCEL 0xb: MIGRATION_PATROLSCRUB_START 0xc: MIGRATION_PATROLSCRUB_END | ||
| 05h | Mirror FailOver Device Status 2: NODE ID Device Status 3: channel id | When the memory mirroring feature is enabled, if an uncorrectable error occurs in the memory of a channel, the mirroring fails. This is a correctable error. [EX] | ||
| 07h | Memory Board Add Fail Device Status 2: NODE ID | An error occurred during memory riser hot swap. [EX] | ||
| 08h | CE overflow (correctable errors exceeding the threshold) Device Status 2: NODE ID Device Status 3: channel id Device Status 4: dimm id Device Status 5: rank id | Correctable errors after the RAS feature takes effect | ||
| 0ah | Spare Rank Info Device Status 2: NODE ID Device Status 3: channel id Device Status 4: dimm id Device Status 5: rank id | If rank sparing is enabled, the backup rank information is reported. | ||
| 0bh | Spare Memory Board Info Device Status 2: NODE ID | If memory migration is enabled, the backup memory riser information is reported. [EX] | ||
| 0ch | Memory Board Online Succeed Device Status 2: NODE ID | The memory riser is online successfully. [EX] | ||
| 0eh | Memory Board Offline Succeed Device Status 2: NODE ID | The memory riser is offline. [EX] | ||
| 11h | Mirror Node Device Status2: LowBitmapOfMirrorNode (node0-7) Device Status3: HighBitmapOfMirrorNode (node8-15) Device Status4: LowBitmapOfMirrorNode (node16-23) Device Status5: HighBitmapOfMirrorNode (node24-31) Device Status6: LowBitmapOfMirrorNode (node32-39) Device Status7: HighBitmapOfMirrorNode (node40-47) Device Status8: LowBitmapOfMirrorNode (node48-55) Device Status9: HighBitmapOfMirrorNode (node56-64) (reserved) | The memory riser enters the mirroring mode. [EX] | ||
| 12h | PFAE Device Status 2: NODE ID Device Status 3: channel id Device Status 4: dimm id | Memory pre-fault event | ||
| 20h | FailDimmInfo Device Status 2: NODE ID Device Status 3: channel id Device Status 4 :dimm id Device Status 5: rank id Device Status 6: bank group id Device Status 7: bank id | Memory failure event | ||
| KBC | 05h | 00h | Unrecoverable PS/2 or USB keyboard failure | The KBC controller performs self-check during startup. If any problem occurs, the KBC controller reports the problem to the BMC through a BT message. |
| Memory Board | 06h | 00h | Memory Board Memory Controler Fault Device Status 2: NODE ID Device Status 3: channel id Device Status 4: dimm id Device Status 5: memory control id | [EX] |
| 01h | Memory Board Power Chip Fault Device Status 2: NODE ID Device Status 3: channel id Device Status 4: dimm id Device Status 5: power chip id | [EX] | ||
| 02h | Memory Board Hot Remove Device Status 2: Operate Code Device Status 3: NODE ID 1 Device Status 4: NODE ID 2 | Operate Code: 00h, which is used to deliver the heat removal start command. [EX] | ||
| 02h | Memory Board Hot Remove Device Status 2: Operate Code Device Status 3: NODE ID 1 Device Status 4: NODE ID 2 | Operate Code: The value is 01h, which is used by the BIOS to report the hot removal start flag. [EX] | ||
| 02h | Memory Board Hot Remove Device Status 2: Operate Code Device Status 3: NODE ID 1 Device Status 4: NODE ID 2 Device Status 5: Progress Code | Operate Code: The value is 02h, which is used by the BIOS to report the hot removal progress. Progress Code: 0x00: memory board offline 0x01: The OS migration is complete. 0x02: write NC 0x03: BE directory clearance 0x04: The memory board is powered off. [EX] | ||
| 02h | Memory Board Hot Remove Device Status 2: Operate Code Device Status 3: NODE ID 1 Device Status 4: NODE ID 2 Device Status 5: Event Code | Operate Code: 03h, which is used by the BIOS to report hot removal failure information. Event Code: 0x00: unknown error 0x01: The remaining memory is insufficient. [EX] | ||
| 02h | Memory Board Hot Remove Device Status 2: Operate Code Device Status 3: NODE ID 1 Device Status 4: NODE ID 2 Device Status 5: Result Code | Operate Code: 03h, which is used by the BIOS to report hot removal failure information. Event Code: 0x00: unknown error 0x01: The remaining memory is insufficient. [EX] | ||
| 02h | Memory Board Hot Remove Device Status 2: Operate Code Device Status 3: NODE ID 1 Device Status 4: NODE ID 2 Device Status 5: Result Code | Operate Code: The value is 04h, which is used by the BIOS to report the hot removal end flag. Result Code: 0x00: success 0x01: failure [EX] | ||
| 03h | Memory Board Hot Plug Device Status 2: Operate Code Device Status 3: NODE ID 1 Device Status 4: NODE ID 2 | Operate Code: 00h, which is used to deliver the heating start command. [EX] | ||
| 03h | Memory Board Hot Plug Device Status 2: Operate Code Device Status 3: NODE ID 1 Device Status 4: NODE ID 2 | Operate Code: The value is 01h, which is used by the BIOS to report the hot-add start flag. [EX] | ||
| 03h | Memory Board Hot Plug Device Status 2: Operate Code Device Status 3: NODE ID 1 Device Status 4: NODE ID 2 Device Status 5: Progress Code | Operate Code: The value is 02h, which is used by the BIOS to report the hot-add progress. Progress Code: 0x00: The memory board is powered off. 0x01: memory board power-on initialization 0x02: Modify SAD/TAD information. 0x03: The memory is added to the OS. [EX] | ||
| 03h | Memory Board Hot Plug Device Status 2: Operate Code Device Status 3: NODE ID 1 Device Status 4: NODE ID 2 Device Status 5: Event Code | Operate Code: The value is 03h, which is used by the BIOS to report hot-add failure information. Event Code: 0x00: unknown error 0x01: The capacities of two memory boards are different. 0x02: Two memory risers are not installed at the same time. (The node IDs of the memory risers that are not installed in ds3 and ds4 are 0xff.) [EX] | ||
| 03h | Memory Board Hot Plug Device Status 2: Operate Code Device Status 3: NODE ID 1 Device Status 4: NODE ID 2 Device Status 5: Result Code | Operate Code: The value is 04h, which is used by the BIOS to report the hot-add end flag. Result Code: 0x00: success 0x01: failure [EX] | ||
| IOH | 07h | 00h | IOH Fault Device Status 2: IOH ID | - |
| IOH | 07h | 00h | IOH Fault Device Status 2: IOH ID | - |
| Chassis | 09h | 00h | General Chassis Intrusion | Chassis unpacking indication |
| Cpu Board | 0ah | 00h | Cpu Board Hot Remove Device Status 2: Operate Code Device Status 3: CPU ID 1 Device Status 4: CPU ID 2 | Operate Code: 00h, which is used to deliver the heat removal start command. [EX] |
| 00h | Cpu Board Hot Remove Device Status 2: Operate Code Device Status 3: CPU ID 1 Device Status 4: CPU ID 2 | Operate Code: The value is 01h, which is used by the BIOS to report the hot removal start flag. [EX] | ||
| - | Cpu Board Hot Remove Device Status 2: Operate Code Device Status 3: CPU ID 1 Device Status 4: CPU ID 2 Device Status 5: Progress Code | Operate Code: The value is 02h, which is used by the BIOS to report the hot removal progress. Progress Code: 0x00: The IIO goes offline. 0x01: The memory starts to go offline. 0x02: The CPU starts to go offline. 0x03: The CPU goes offline. 0x04: The processor board starts to be powered off. [EX] | ||
| 00h | Cpu Board Hot Remove Device Status 2: Operate Code Device Status 3: CPU ID 1 Device Status 4: CPU ID 2 Device Status 5: Event Code | Operate Code: 03h, which is used by the BIOS to report hot removal failure information. Error Code: 0x00: unknown error [EX] | ||
| 00h | Cpu Board Hot Remove Device Status 2: Operate Code Device Status 3: CPU ID 1 Device Status 4: CPU ID 2 Device Status 5: Result Code | Operate Code: The value is 04h, which is used by the BIOS to report the hot removal end flag. Result Code: 0x00: success 0x01: failure [EX] | ||
| 01h | Cpu Board Hot Plug Device Status 2: Operate Code Device Status 3: CPU ID 1 Device Status 4: CPU ID 2 | Operate Code: 00h, which is used to deliver the heating start command. | ||
| 01h | Cpu Board Hot Plug Device Status 2: Operate Code Device Status 3: CPU ID 1 Device Status 4: CPU ID 2 | Operate Code: The value is 01h, which is used by the BIOS to report the hot-add start flag. [EX] | ||
| 01h | Cpu Board Hot Plug Device Status 2: Operate Code Device Status 3: CPU ID 1 Device Status 4: CPU ID 2 Device Status 5: Progress Code | Operate Code: The value is 02h, which is used by the BIOS to report the hot-add progress. Progress Code: 0x00: power-on OK message sent from the BMC 0x01: CPU online completed [EX] | ||
| 01h | Cpu Board Hot Plug Device Status 2: Operate Code Device Status 3: CPU ID 1 Device Status 4: CPU ID 2 Device Status 5: Event Code | Operate Code: The value is 03h, which is used by the BIOS to report hot-add failure information. Error Code: 0x00: unknown error [EX] | ||
| 01h | Cpu Board Hot Plug Device Status 2: Operate Code Device Status 3: CPU ID 1 Device Status 4: CPU ID 2 Device Status 5: Result Code | Operate Code: The value is 04h, which is used by the BIOS to report the hot-add end flag. Result Code: 0x00: success 0x01: failure [EX] | ||
| Computing Unit | 0Bh | 00h | Computing Unit Hot Plug Device Status 2: Operate Code Device Status 3: Cluster ID 1 Device Status 4: Cluster ID 2 | Operate Code: 00h, which is used to deliver the heating start command. [EX] |
| 00h | Computing Unit Hot Plug Device Status 2: Operate Code Device Status 3: Cluster ID 1 Device Status 4: Cluster ID 2 | Operate Code: The value is 01h, which is used by the BIOS to report the hot-add start flag. [EX] | ||
| 00h | Computing Unit Hot Plug Device Status 2: Operate Code Device Status 3: Cluster ID 1 Device Status 4: Cluster ID 2 Device Status 5: Progress Code | Operate Code: The value is 02h, which is used by the BIOS to report the hot-add progress. Progress Code: 0x00: power-on OK information 0x01: CPU online progress [EX] | ||
| 00h | Computing Unit Hot Plug Device Status 2: Operate Code Device Status 3: Cluster ID 1 Device Status 4: Cluster ID 2 Device Status 5: Event Code | Operate Code: The value is 03h, which is used by the BIOS to report hot-add failure information. Error Code: 0x00: unknown error [EX] | ||
| 00h | Computing Unit Hot Plug Device Status 2: Operate Code Device Status 3: Cluster ID 1 Device Status 4: Cluster ID 2 Device Status 5: Result Code | Operate Code: The value is 04h, which is used by the BIOS to report the hot-add end flag. Result Code: 0x00: success 0x01: failure [EX] | ||
| 01h | System Merging error detected: Device Status 2: Error Code Device Status 3: Cluster ID | Error Code: 0x01: firmware post error (reported by the active BIOS) 0x02: No physical partition is configured (reported by each BIOS). 0x03: The setup configuration information fails to be synchronized (reported by each BIOS). 0x04: The memory frequencies of the clusters are inconsistent. (This alarm is reported by the active BIOS.) [EX] | ||
| 02h | Configuration Error: (configuration error) Device Status 2: Error Code Device Status 3: Cluster ID Device Status 4: CPU ID | Error Code: 0x1--Memory module and DIMMs must be configured in pairs for each (Memory boards on the same node must be configured in pairs.) [EX] | ||
| RAID | 0Eh | 00h | RAID hardware fault. Device Status2: pcie bus number(root port) Device Status3: pcie device number(root port) Device Status4: pcie function number(root port) Device Status5: error code | The RAID controller card hardware is faulty. The peripheral components (such as the memory) of the RAID controller card chip are faulty. The BMC cannot detect the fault through the error pin of the RAID controller card or there is no error pin (PCIe RAID controller card). Therefore, the BIOS detects and reports the fault. However, running detection is not supported. Error code: 00h: normal Other values: faulty |
| Boot Error | 0Fh | 00h | No Boot Device Error | No boot device. |
| 01h | Non-bootable diskette left in drive | No bootable hard disk. | ||
| 02h | PXE Server not found | The PXE server cannot be found. | ||
| 03h | Invalid boot sector | Invalid startup item. | ||
| 04h | Timeout waiting for selection | Boot option selection timed out. | ||
| Boot End Flag | 10h | 01h | Post end flag | BIOS startup completed (new in V100R006C20) |
| Certificate | 11h | 00h | NA | The BIOS certificate is normal. |
| 01h | BIOS certificate is about to expire or has expired. | The BIOS certificate has expired or is about to expire. | ||
| Memory | 12h | 00h-20h | NA | The capability of this interface is the same as that of Memory 04h. The only difference lies in the channel ID, which is specified as the logical channel ID. |
| 24h | PPR Device Status 2: system id(global system id) Device Status 3: local system id Device Status 4: socket id (compatible with CPUs and NPUs) Device Status 5: channel id(logical channel) Device Status 6: dimm id (same as Rank Group ID) Device Status 7: subchannel id Device Status 8: device Device Status 9: rank id Device Status 10: bank group id Device Status 11: bank id Device Status 12: row addr high Device Status 13: row addr mid Device Status 14: row addr low Device Status 15: repair type(0-hPPR;1-sPPR;2-mPPR) | Memory PPR Event | ||
| 25h | ACLS Device Status 2: system id(global system id) Device Status 3: local system id Device Status 4: socket id (compatible with CPUs and NPUs) Device Status 5: channel id(logical channel) Device Status 6: dimm id (same as Rank Group ID) Device Status 7: subchannel id Device Status 8: device Device Status 9: rank id Device Status 10: bank group id Device Status 11: bank id Device Status 12: row addr high Device Status 13: row addr mid Device Status 14: row addr low Device Status 15: col addr high Device Status 16: col addr low Device Status 17: transfer num(burst id) Device Status 18: spare index | Memory ACLS Events | ||
| Link Error | 13h | 00h | PSULinkAbnormal Device Status 2: CPU ID Device Status 3: PSU Type Device Status 4 :Die Device Status 5 :Channel | Power Module PMBUS/AVSBUS Access Exception PSU Type: indicates the power supply type. 0x00--CORE 0x01--UNCODE 0x02--DDR VDD 0x03--Nimbus 0x04--DDR VDDQ Die: Survey the power supply die area. 0x00--NA 0x01--TA 0x02--NB 0x03--TB Channel: power channel 0x00–PMBUS 0x01--AVSBUS NOTE: The parameters vary depending on the CPU. For details about the parameter mapping, contact O&M personnel. |
| 01h | Memory I2CI3Clink Abnormal Device Status 2: CPU ID Device Status 3: Channel Index Device Status 4 :DIMM Index | |||
| VR | 14h | 00h | VR Power Phase Redundancy Device Status 2: CPU ID Device Status 3: PSU Type Device Status 4 :Die | VR power phase redundancy PSU Type: indicates the power supply type. 0x00--CORE 0x01--UNCORE 0x02--DDR VDD 0x03--Nimbus 0x04--DDR VDDQ 0x05--CORE_MEM 0x06--UNCORE_MEM 0x07--SIOE Die: power supply die area 0x00--NA 0x01--TA 0x02--NB 0x03--TB NOTE: The parameters vary depending on the CPU. For details about the parameter mapping, contact O&M personnel. |
| Base OS Boot | 15h | 06h | boot completed - boot device not specified |
Command Example
Query the device status.
Request:
bash
ipmicmd -k "0f 00 MM NN" smi 0Response:
text
0f MM NN