Device Type (Component Type)
Change History
| iBMC 4-segment version | Revision Date | Description | Revised By |
|---|---|---|---|
| 3.10.02.33 | 2024-06-01 | The component type 95 is added, which points to the optical module and is used to display the Redfish interface for data collection. | Shi Junguo |
| 3.15.06.03 | 2024-06-05 | The component type 96 is added to specify the main type of the event reported by the HDU(High-voltage Distribute Unit) alarm. | Guan Mao Le |
| 3.15.06.03 | 2024-06-05 | The component type 94 is added as the event body type reported by the module (HiAM) object alarm. | Xu Junlin |
| 3.17.01.07 | 2024-11-07 | The component type 97 is added, which is used as the event body type for NP board alarm reporting. | Sun Yuanxing |
| 5.06.00.01 | 2024-12-26 | The 0x19 power transfer board is reused. The naming differences are as follows: A power transfer board is a device used to transfer electric energy from one power supply to another. It is usually used in wireless charging or power transmission systems. It can transfer electric energy from one source to another without using traditional wires or plugs. A power adapter board is a device used to adapt the output voltage and current of a power adapter (such as a power plug) to the requirements of a specific device. It is usually used to convert an alternating current into a direct current, and provide the direct current for an electronic device to use. | Yuan Jia |
| 5.08.00.01 | 2024-02-17 | The component type 98 is added, which is used as the event type reported by the LCN board. | He Shijie 00873585 |
| Not involved | 2025-05-19 | The component type 252=0xFC and Ascend software alarms (such as MindIE and MindCluster) are added. | Cao Chengjian c00616303 Cai Zhifang c00560437 Liu Xingsen l00583113 An Song a00582928 Yan Qingshui y00495752 |
| N/A | 2025-11-03 | The component type 253=0xFD is added, which is used for alarms of the PoDManager system software. | Liu Xingsen l00583113 Cao Yang/00642547 Zhou Kaiqi/00514808 |
iBMC V3: Fru Type and Component Type are defined in the same way. The exception part of Fru Type is separated.
Class and attribute: Fru.Type, Component.Type
Scenario
When information about a specified FRU is obtained through precise locating, the recommended obtaining mechanism is as follows: Run the Get Fruid Info command to obtain the FRU ID through the device_type=xx;group_id=xx;device_number=xx; parameter (xx is a hexadecimal value and is configured by the invoker. For example, the equipment personnel configure the FRU ID based on the BOM 0302 code). Then, query or set the electronic label and query the version information based on the FRU ID.
Related TU links are as follows:
https://anytestlab.huawei.com/business/tuManage/detail?tuSolutionId=1000013400
https://anytestlab.huawei.com/business/tuManage/detail?tuSolutionId=1000011600
Scenario 2:
1) Query the FRU types corresponding to all FRU IDs. 2) Find the FruId corresponding to the BCU/NPU and query information such as the UID based on the FruId.
Table 1
| Item | Bit | Function | Description |
|---|---|---|---|
| Highest | bit24-bit31 | Event subject type | See Table 1. |
| - | bit16-bit23 | Specifies the product ID. | See Product ID allocation table. |
| - | bit8-bit15 | Event offset, high byte | - |
| Lowest | bit0-bit7 | Event offset, low byte | Event offset. The events of each event type are numbered in a unified manner, starting from 1. |
Table 2 FRU type (Fru Type and Component Type are not normalized.)
| Component Type (Including Card Type) | Displayed Component Type | Type number (decimal) | Type number (hexadecimal) |
|---|---|---|---|
| PCBA | MotherBoard | 0 | 0x00 |
| Mezzanine card | - | 1 | 0x01 |
| AMC | - | 2 | 0x02 |
| MMC | - | 3 | 0x03 |
| Power module | - | 4 | 0x04 |
Table 3 Device type.
| Component Type (Including Card Type) | Displayed Component Type | Component Name Note: Items in [] are optional. | Type ID (decimal) | Type ID (hexadecimal) | Subsystem |
|---|---|---|---|---|---|
| CPU | CPU | CPU[1~N] | 0 | 0x00 | Heterogeneous computing power management |
| Memory | Memory | DIMM### and ### indicate the CPU ID, channel ID, and DIMM ID respectively. | 1 | 0x01 | Heterogeneous computing power management |
| Hard disk | Disk | Disk[0-N] or Disk[A-Z] | 2 | 0x02 | Universal Hardware Management |
| Power supply unit (PSU) | PSU | PSU[1~N] | 3 | 0x03 | Energy Efficiency Management |
| Fan | Fan | Fan[1~N] | 4 | 0x04 | Energy Efficiency Management |
| Hard Drive Backplane | Disk Backplane | Disk BP[1~N], first used by the RH8100 V5. | 5 | 0x05 | Universal Hardware Management |
| Screw-in RAID controller card | RAID Card | RAID Card[1~N] | 6 | 0x06 | Universal Hardware Management |
| Undefined (undefined or unknown) | UNKNOWN | UNKNOWN | 7 | 0x07 | NA |
| PCIe cards | PCIe Card | PCIe Card[1~N] NOTE: FunctionClass (PCIe Card Function Classification) 0: unknown 1: RAID 2: NIC (Ethernet, FC card, and FCoE card) 3: GPU card 4: storage card (SSD card/M.2 card) 5: SDI card 6: acceleration card 7: expansion card (PCIe riser card) 8: FPGA card 9: NPU card 10: storage DPU card 11: DPU card FunctionType description corresponding to FunctionClass: 0: Unknown 1: RAID Card 2: Net Card 3: GPU Card 4: Storage Card 5: SDI Card 6: Accelerate Card 7: PCIe Riser Card 8: FPGA Card 9: NPU Card 10: Storage DPU Card 11: DPU Card | 8 | 0x08 | Universal Hardware Management |
| AMC board | AMC | AMC[1~N] | 9 | 0x09 | Universal Hardware Management |
| HBA Controller Card | HBA | HBA[1~N] | 10 | 0x0A | Universal Hardware Management |
| mezzanine card | Mezz Card | Mezz Card[1~N] | 11 | 0x0B | Universal Hardware Management |
| Undefined (undefined or unknown) | UNKNOWN | UNKNOWN | 12 | 0x0C | NA |
| NIC | NIC | NIC[1~N] | 13 | 0x0D | Universal Hardware Management |
| Memory board | Memory Board | Memory Board[1~N] | 14 | 0x0E | Heterogeneous computing power management |
| PCIe riser card | PCIe Riser Riser Card | PCIe Riser[1~N] | 15 | 0x0F | Universal Hardware Management |
| PCBA | Mainboard | Mainboard[1~N] Application scenario: (Query the component or FRU whose FruId is 0. The FRU whose FruName is BMC is preferred.) For the Tianchi model, set FruId to 0 for the component whose FruName is BMC (FRU type is 26). The event body is chassisBMC/MotherBoard.For non-Tianchi models, set FruId to 0 for the component whose FruName is Mainboard (component type is 16). The corresponding event body is chassisMainboard.Tianchi and non-Tianchi models: The device type of the Redfish interface is MainBoard, corresponding to the https://device_ip/redfish/v1/Chassis/chassis_id/Boards/board_id interface."DeviceType": "MainBoard" | 16 | 0x10 | Universal Hardware Management |
| LCD | LCD | LCD[1~N] | 17 | 0x11 | Universal Hardware Management |
| Chassis | Chassis | Chassis[1~N] | 18 | 0x12 | Universal Hardware Management |
| Node controller module (NCM) | NCM | NCM[1~N] | 19 | 0x13 | Universal Hardware Management |
| Switch module | Switch Module | Switch Module[1~N] | 20 | 0x14 | Universal Hardware Management |
| Storage board | Storage Board | Storage Board[1~N] | 21 | 0x15 | Universal Hardware Management |
| Chassis backplane | Chassis Backplane | Chassis BP[1–N]. The RH8100 V5 is used first, and other models will be used later. | 22 | 0x16 | Universal Hardware Management |
| SMM/CMC | HMM/CMC | HMM/CMC[1~N]: centralized management module. | 23 | 0x17 | TCE |
| Fan backplane | Fan Backplane | Fan BP[1~N], first used in the RH8100 V5. | 24 | 0x18 | Energy Efficiency Management |
| PSU backplane | Power Backplane | PSU BP[1~N], first used in the RH8100 V5. Used for iBMC V2. | 25 | 0x19 | Energy Efficiency Management |
| Power Adapter Board | Power Transfer Board | Power Transfer Board[1~N]. Used in iBMC V3 and later versions | 25 | 0x19 | Energy Efficiency Management |
| BMC board | BMC BMCCard | BMC[1~N] | 26 | 0x1A | Universal Hardware Management |
| MMC/MM board | MM/MMC | MMC/MM[1–N]: peripheral component management board, which manages power supply and fan modules. | 27 | 0x1B | TCE |
| Twin node backplane | Twin Node Backplane | Twin Node Backplane[1~N] | 28 | 0x1C | NA |
| Base (switching plane) | Base Plane | Base Plane[1~N] | 29 | 0x1D | Cluster |
| Fabric (switching plane) | Fabric Plane | Fabric Plane[1~N] | 30 | 0x1E | Cluster |
| Switch mezzanine card (such as FC GW, FCoE, or M8PA) | Switch Mezz | Switch Mezz[1~N]: mezz modules on OSCA switch boards. | 31 | 0x1F | Universal Hardware Management |
| LED | LED | LED[1~N] | 32 | 0x20 | Universal Hardware Management |
| SD card | SD Card | SD Card[1~N] | 33 | 0x21 | Universal Hardware Management |
| TPM/TCM card | Security Module | Security Module[1~N] | 34 | 0x22 | Security management |
| I/O board | I/O Board | I/O Board[1~N] FIO Board[1~N] BIO Board[1~N] | 35 | 0x23 | Universal Hardware Management |
| Processor board/CPU board | CPU Board | CPU Board[1~N] | 36 | 0x24 | Heterogeneous computing power management |
| RMC board | RMC | RMC[1–N]: X8000 rack management module. | 37 | 0x25 | Universal Hardware Management |
| PCIe SSD adapter | PCIe Adapter | PCIe adapters 1 to N are inserted into standard PCIe slots for connecting PCIe buses to hard disks, for example, x16 to four x4 hard disks. | 38 | 0x26 | Universal Hardware Management |
| PCH | PCH | PCH[1~N] | 39 | 0x27 | Heterogeneous computing power management |
| Cable/Internal connection | Cable | Cable[1~N] | 40 | 0x28 | Universal Hardware Management |
| Port | Port | Port[1~N] | 41 | 0x29 | Universal Hardware Management |
| LSW | LSW | LSW[1~N] | 42 | 0x2A | Universal Hardware Management |
| PHY | PHY | PHY[1~N] | 43 | 0x2B | Universal Hardware Management |
| Service system/product | System | System | 44 | 0x2C | Universal Hardware Management |
| M.2 adapter | M.2 Transfer Card | M.2 Transfer Card[1~N] M.2 adapter | 45 | 0x2D | Universal Hardware Management |
| Expander | Expander | Expander[1~N] Note: This type is dedicated for the x86 V3 model. This type is discarded for the V6/ Kunpeng model and is switched to 0x5D/0xC1. | 45 | 0x2D | Universal Hardware Management |
| LED board | LED Board | LED Board[1~N] | 46 | 0x2E | Universal Hardware Management |
| LPM (or PBI board, that is, the PCH, BMC, and I/O combination board) | LPM | LPM[1–N]: used by the RH8100 V3. | 47 | 0x2F | Universal Hardware Management |
| PIC (flexible) | PIC Card | PIC Card[1~N]: used on the XCUK switch board. | 48 | 0x30 | Universal Hardware Management |
| Button | Button | ### Buttons, such as power button and UID button | 49 | 0x31 | Universal Hardware Management |
| Universal expansion board | Expander | Expander[1–N]: universal expansion board, for example, the expander of the expansion hard disk. Generally, the expander is located on the hard disk backplane. | 50 | 0x32 | Universal Hardware Management |
| CPI (Centralized Control Partition Unit, Central Partition Interconnect Module) | CPI | CPI[1–N]: applies to the 9032 and is managed by the CMC. | 51 | 0x33 | Cluster |
| Advanced clock module (ACM) | ACM | ACM[1–N]: applies to the 9032 and is managed by the CMC. | 52 | 0x34 | Cluster |
| Central interface module (CIM) | CIM | CIMs 1 to N are used in the 9032 and are managed by the CMC. | 53 | 0x35 | Cluster |
| Power and fan integrity module (PFM) | PFM | PFM[1~N]: a component of the KunLun 9032, managed by the CMC. | 54 | 0x36 | Cluster |
| KPAR (multi-partition system) | KPAR | KPAR (multi-partition system) | 55 | 0x37 | Cluster |
| JC | JC | JC[1–N]: For example, the JC chip is on the mainboard or memory riser. | 56 | 0x38 | Heterogeneous computing power management |
| System compute module (SCM), which is the computing unit of the CPU and memory | SCM | SCM[1~N] | 57 | 0x39 | Heterogeneous computing power management |
| MINISAS HD channel | Minisas HD channel | ARM product, used for fault diagnosis. | 58 | 0x3A | RAS Fault Management |
| SATADOM channel | SATA DOM channel | ARM product, used for fault diagnosis. | 59 | 0x3B | RAS Fault Management |
| GE channel | GE channel | ARM product, used for fault diagnosis. | 60 | 0x3C | RAS Fault Management |
| XGE channel | XGE channel | ARM product, used for fault diagnosis. | 61 | 0x3D | RAS Fault Management |
| PCIe Switch | PCIe Switch | PCIe Switch[1~N] | 62 | 0x3E | Universal Hardware Management |
| Interface component/interface board | Interface Device | Interface Device[1-N]: for example, the optical module on the E9000 rear board, DAC cable, or UB interface board | 63 | 0x3F | Cluster |
| xPU carrier board/xPU | xPU Carrier Board/xPU Board | xPU Board[1~N], such as GPU and VPU | 64 | 0x40 | Heterogeneous computing power management |
| Disk baseboard (CH222V3 SESA) | Disk BaseBoard | Disk BaseBoard | 65 | 0x41 | Universal Hardware Management |
| VGA adapter | VGA Interface Card | VGA Intf Card | 66 | 0x42 | Universal Hardware Management |
| Pass-through card (for example, SAS pass-through card) | Pass-Through Card | Pass-Through Card | 67 | 0x43 | Universal Hardware Management |
| Logical Disk | Logical Driver | Logical Driver[1~N] | 68 | 0x44 | Universal Hardware Management |
| PCIe Retimer | PCIe Retimer | PCIe Retimer[1~N] | 69 | 0x45 | Universal Hardware Management |
| PCIe Reperter | PCIe Repeater | PCIe Repeater1~N] | 70 | 0x46 | Universal Hardware Management |
| SAS | SAS | SAS[1~N] | 71 | 0x47 | Universal Hardware Management |
| Memory channel | Memory Channel | Memory Channel[1~N] | 72 | 0x48 | Heterogeneous computing power management |
| BMA | BMA | BMA | 73 | 0x49 | Universal Hardware Management |
| LOMs | LOM | LOM[1~N] Note: This type is not used currently. The value 0x0D is used to query LOM information. | 74 | 0x4A | Universal Hardware Management |
| Signal transfer board | Signal Adapter Board | Signal Adapter Board | 75 | 0x4B | Universal Hardware Management |
| Horizontal adapter | Horizontal Connection Board | Horizontal Connection Board | 76 | 0x4C | Universal Hardware Management |
| Node | Node | Nodes 1 to N, for example, front boards and switch boards on the E9000. | 77 | 0x4D | Cluster |
| Asset management and control board | Asset Locate Board | Asset Locate Board[1~N] | 78 | 0x4E | Cluster |
| Installation Position | Unit | Unit[1~N] | 79 | 0x4F | Cluster |
| Cabinet management module | RMM | RMM stands for rack management module. | 80 | 0x50 | Cluster |
| Cabinet | Rack | Rack | 81 | 0x51 | Cluster |
| Backup power supply module | BBU | BBU[1-N], Taishan: backup power module of the 2280 V2. | 82 | 0x52 | Cluster |
| OCP card | OCP Card | OCP Card[1~N] | 83 | 0x53 | Universal Hardware Management |
| Leakage detection card | Leakage Detection Card | Leakage Detection Card[1~N] | 84 | 0x54 | Cluster |
| Mesh card | MESH Card | MESH Card[1~N] | 85 | 0x55 | TCE |
| Neural network computing chip | NPU | NPU[1-N], AtlasA 800 neural network computing chip. | 86 | 0x56 | Heterogeneous computing power management |
| Converged interface card, Converged Interface Card | CIC Card | Converged Interface Card[1~N] | 87 | 0x57 | Storage |
| Expansion Module | Expansion Module | Expansion Module[1~N] | 88 | 0x58 | Universal Hardware Management |
| Fan module | Fan Module | Fan Module[0-N] | 89 | 0x59 | Energy Efficiency Management |
| AR card | AR Card | AR Card[1~N] | 90 | 0x5A | Storage |
| Convergence board | Converge Board | Converge Board[1~N] | 91 | 0x5B | Storage |
| SoC PCBA | SoC Board | SoC Board[1~N], Small SoC inference mainboard , for example, Atlas 200I SoC A1 | 92 | 0x5C | Universal Hardware Management |
| Extension board | Expand Board | ExpBoard[1-N] | 93 | 0x5D | Universal Hardware Management |
| HiAM | HiAM | HiAM [1~N] | 94 | 0x5E | RAS Fault Management |
| Optical Module | OpticalModule | OpticalModule[1-N] | 95 | 0x5F | RAS Fault Management |
| HDU | HDU | HDU[1~N] | 96 | 0x60 | Cluster |
| Network accelerator card | NP | Network Process Board | 97 | 0x61 | TCE |
| Regional computer network | LCN | Local Computer Network | 98 | 0x62 | Ascend, LingQu network |
| Basic Computing Unit | BCU | BCU[1~N] | 192 | 0xC0 | Heterogeneous computing power management |
| System Extension Unit | EXU | EXU[1~N] | 193 | 0xC1 | Universal Hardware Management |
| Storage Expansion Components | SEU | SEU[1-N] | 194 | 0xC2 | Universal Hardware Management |
| I/O Expansion Components | IEU | IEU[1~N] | 195 | 0xC3 | Universal Hardware Management |
| Heat dissipation component | CLU | CLU[1~N] | 196 | 0xC4 | Energy Efficiency Management |
| Ascend software alarm | Ascend Software Events | Ascend software alarms (such as MindIE and MindCluster alarms) | 252 | 0xFC | Ascend |
| PoDManager system software | PoDManager | This alarm is generated when the PoDManager software is detected. | 253 | 0xFD | Cluster |
| Reserved | Reserved | Reserved. It is used for extension or special scenario definition and cannot be used as a valid device type. | 255 | 0xFF |