Device Type (Component Type)
更新时间: 2026/08/06
在Gitcode上查看源码

Device Type (Component Type)

Change History

iBMC 4-segment versionRevision DateDescriptionRevised By
3.10.02.332024-06-01The 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.032024-06-05The 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.032024-06-05The component type 94 is added as the event body type reported by the module (HiAM) object alarm.Xu Junlin
3.17.01.072024-11-07The component type 97 is added, which is used as the event body type for NP board alarm reporting.Sun Yuanxing
5.06.00.012024-12-26The 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.012024-02-17The component type 98 is added, which is used as the event type reported by the LCN board.He Shijie 00873585
Not involved2025-05-19The 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/A2025-11-03The 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

ItemBitFunctionDescription
Highestbit24-bit31Event subject typeSee Table 1.
-bit16-bit23Specifies the product ID.See Product ID allocation table.
-bit8-bit15Event offset, high byte-
Lowestbit0-bit7Event offset, low byteEvent 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 TypeType number (decimal)Type number (hexadecimal)
PCBAMotherBoard00x00
Mezzanine card-10x01
AMC-20x02
MMC-30x03
Power module-40x04

Table 3 Device type.

Component Type (Including Card Type)Displayed Component TypeComponent Name
Note: Items in [] are optional.
Type ID (decimal)Type ID (hexadecimal)Subsystem
CPUCPUCPU[1~N]00x00Heterogeneous computing power management
MemoryMemoryDIMM### and ### indicate the CPU ID, channel ID, and DIMM ID respectively.10x01Heterogeneous computing power management
Hard diskDiskDisk[0-N] or Disk[A-Z]20x02Universal Hardware Management
Power supply unit (PSU)PSUPSU[1~N]30x03Energy Efficiency Management
FanFanFan[1~N]40x04Energy Efficiency Management
Hard Drive BackplaneDisk BackplaneDisk BP[1~N], first used by the RH8100 V5.50x05Universal Hardware Management
Screw-in RAID controller cardRAID CardRAID Card[1~N]60x06Universal Hardware Management
Undefined (undefined or unknown)UNKNOWNUNKNOWN70x07NA
PCIe cardsPCIe CardPCIe 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
80x08Universal Hardware Management
AMC boardAMCAMC[1~N]90x09Universal Hardware Management
HBA Controller CardHBAHBA[1~N]100x0AUniversal Hardware Management
mezzanine cardMezz CardMezz Card[1~N]110x0BUniversal Hardware Management
Undefined (undefined or unknown)UNKNOWNUNKNOWN120x0CNA
NICNICNIC[1~N]130x0DUniversal Hardware Management
Memory boardMemory BoardMemory Board[1~N]140x0EHeterogeneous computing power management
PCIe riser cardPCIe Riser
Riser Card
PCIe Riser[1~N]150x0FUniversal Hardware Management
PCBAMainboardMainboard[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"
160x10Universal Hardware Management
LCDLCDLCD[1~N]170x11Universal Hardware Management
ChassisChassisChassis[1~N]180x12Universal Hardware Management
Node controller module (NCM)NCMNCM[1~N]190x13Universal Hardware Management
Switch moduleSwitch ModuleSwitch Module[1~N]200x14Universal Hardware Management
Storage boardStorage BoardStorage Board[1~N]210x15Universal Hardware Management
Chassis backplaneChassis BackplaneChassis BP[1–N]. The RH8100 V5 is used first, and other models will be used later.220x16Universal Hardware Management
SMM/CMCHMM/CMCHMM/CMC[1~N]: centralized management module.230x17TCE
Fan backplaneFan BackplaneFan BP[1~N], first used in the RH8100 V5.240x18Energy Efficiency Management
PSU backplanePower BackplanePSU BP[1~N], first used in the RH8100 V5. Used for iBMC V2.250x19Energy Efficiency Management
Power Adapter BoardPower Transfer BoardPower Transfer Board[1~N]. Used in iBMC V3 and later versions250x19Energy Efficiency Management
BMC boardBMC
BMCCard
BMC[1~N]260x1AUniversal Hardware Management
MMC/MM boardMM/MMCMMC/MM[1–N]: peripheral component management board, which manages power supply and fan modules.270x1BTCE
Twin node backplaneTwin Node BackplaneTwin Node Backplane[1~N]280x1CNA
Base (switching plane)Base PlaneBase Plane[1~N]290x1DCluster
Fabric (switching plane)Fabric PlaneFabric Plane[1~N]300x1ECluster
Switch mezzanine card (such as FC GW, FCoE, or M8PA)Switch MezzSwitch Mezz[1~N]: mezz modules on OSCA switch boards.310x1FUniversal Hardware Management
LEDLEDLED[1~N]320x20Universal Hardware Management
SD cardSD CardSD Card[1~N]330x21Universal Hardware Management
TPM/TCM cardSecurity ModuleSecurity Module[1~N]340x22Security management
I/O boardI/O BoardI/O Board[1~N]
FIO Board[1~N]
BIO Board[1~N]
350x23Universal Hardware Management
Processor board/CPU boardCPU BoardCPU Board[1~N]360x24Heterogeneous computing power management
RMC boardRMCRMC[1–N]: X8000 rack management module.370x25Universal Hardware Management
PCIe SSD adapterPCIe AdapterPCIe 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.380x26Universal Hardware Management
PCHPCHPCH[1~N]390x27Heterogeneous computing power management
Cable/Internal connectionCableCable[1~N]400x28Universal Hardware Management
PortPortPort[1~N]410x29Universal Hardware Management
LSWLSWLSW[1~N]420x2AUniversal Hardware Management
PHYPHYPHY[1~N]430x2BUniversal Hardware Management
Service system/productSystemSystem440x2CUniversal Hardware Management
M.2 adapterM.2 Transfer CardM.2 Transfer Card[1~N]
M.2 adapter
450x2DUniversal Hardware Management
ExpanderExpanderExpander[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.
450x2DUniversal Hardware Management
LED boardLED BoardLED Board[1~N]460x2EUniversal Hardware Management
LPM (or PBI board, that is, the PCH, BMC, and I/O combination board)LPMLPM[1–N]: used by the RH8100 V3.470x2FUniversal Hardware Management
PIC (flexible)PIC CardPIC Card[1~N]: used on the XCUK switch board.480x30Universal Hardware Management
ButtonButton### Buttons, such as power button and UID button490x31Universal Hardware Management
Universal expansion boardExpanderExpander[1–N]: universal expansion board, for example, the expander of the expansion hard disk. Generally, the expander is located on the hard disk backplane.500x32Universal Hardware Management
CPI (Centralized Control Partition Unit, Central Partition Interconnect Module)CPICPI[1–N]: applies to the 9032 and is managed by the CMC.510x33Cluster
Advanced clock module (ACM)ACMACM[1–N]: applies to the 9032 and is managed by the CMC.520x34Cluster
Central interface module (CIM)CIMCIMs 1 to N are used in the 9032 and are managed by the CMC.530x35Cluster
Power and fan integrity module (PFM)PFMPFM[1~N]: a component of the KunLun 9032, managed by the CMC.540x36Cluster
KPAR (multi-partition system)KPARKPAR (multi-partition system)550x37Cluster
JCJCJC[1–N]: For example, the JC chip is on the mainboard or memory riser.560x38Heterogeneous computing power management
System compute module (SCM), which is the computing unit of the CPU and memorySCMSCM[1~N]570x39Heterogeneous computing power management
MINISAS HD channelMinisas HD channelARM product, used for fault diagnosis.580x3ARAS Fault Management
SATADOM channelSATA DOM channelARM product, used for fault diagnosis.590x3BRAS Fault Management
GE channelGE channelARM product, used for fault diagnosis.600x3CRAS Fault Management
XGE channelXGE channelARM product, used for fault diagnosis.610x3DRAS Fault Management
PCIe SwitchPCIe SwitchPCIe Switch[1~N]620x3EUniversal Hardware Management
Interface component/interface boardInterface DeviceInterface Device[1-N]: for example, the optical module on the E9000 rear board, DAC cable, or UB interface board630x3FCluster
xPU carrier board/xPUxPU Carrier Board/xPU BoardxPU Board[1~N], such as GPU and VPU640x40Heterogeneous computing power management
Disk baseboard (CH222V3 SESA)Disk BaseBoardDisk BaseBoard650x41Universal Hardware Management
VGA adapterVGA Interface CardVGA Intf Card660x42Universal Hardware Management
Pass-through card (for example, SAS pass-through card)Pass-Through CardPass-Through Card670x43Universal Hardware Management
Logical DiskLogical DriverLogical Driver[1~N]680x44Universal Hardware Management
PCIe RetimerPCIe RetimerPCIe Retimer[1~N]690x45Universal Hardware Management
PCIe ReperterPCIe RepeaterPCIe Repeater1~N]700x46Universal Hardware Management
SASSASSAS[1~N]710x47Universal Hardware Management
Memory channelMemory ChannelMemory Channel[1~N]720x48Heterogeneous computing power management
BMABMABMA730x49Universal Hardware Management
LOMsLOMLOM[1~N]
Note: This type is not used currently. The value 0x0D is used to query LOM information.
740x4AUniversal Hardware Management
Signal transfer boardSignal Adapter BoardSignal Adapter Board750x4BUniversal Hardware Management
Horizontal adapterHorizontal Connection BoardHorizontal Connection Board760x4CUniversal Hardware Management
NodeNodeNodes 1 to N, for example, front boards and switch boards on the E9000.770x4DCluster
Asset management and control boardAsset Locate BoardAsset Locate Board[1~N]780x4ECluster
Installation PositionUnitUnit[1~N]790x4FCluster
Cabinet management moduleRMMRMM stands for rack management module.800x50Cluster
CabinetRackRack810x51Cluster
Backup power supply moduleBBUBBU[1-N], Taishan: backup power module of the 2280 V2.820x52Cluster
OCP cardOCP CardOCP Card[1~N]830x53Universal Hardware Management
Leakage detection cardLeakage Detection CardLeakage Detection Card[1~N]840x54Cluster
Mesh cardMESH CardMESH Card[1~N]850x55TCE
Neural network computing chipNPUNPU[1-N], AtlasA 800 neural network computing chip.860x56Heterogeneous computing power management
Converged interface card,
Converged Interface Card
CIC CardConverged Interface Card[1~N]870x57Storage
Expansion ModuleExpansion ModuleExpansion Module[1~N]880x58Universal Hardware Management
Fan moduleFan ModuleFan Module[0-N]890x59Energy Efficiency Management
AR cardAR CardAR Card[1~N]900x5AStorage
Convergence boardConverge BoardConverge Board[1~N]910x5BStorage
SoC PCBASoC BoardSoC Board[1~N],
Small SoC inference mainboard , for example, Atlas 200I SoC A1
920x5CUniversal Hardware Management
Extension boardExpand BoardExpBoard[1-N]930x5DUniversal Hardware Management
HiAMHiAMHiAM [1~N]940x5ERAS Fault Management
Optical ModuleOpticalModuleOpticalModule[1-N]950x5FRAS Fault Management
HDUHDUHDU[1~N]960x60Cluster
Network accelerator cardNPNetwork Process Board970x61TCE
Regional computer networkLCNLocal Computer Network980x62Ascend, LingQu network
Basic Computing UnitBCUBCU[1~N]1920xC0Heterogeneous computing power management
System Extension UnitEXUEXU[1~N]1930xC1Universal Hardware Management
Storage Expansion ComponentsSEUSEU[1-N]1940xC2Universal Hardware Management
I/O Expansion ComponentsIEUIEU[1~N]1950xC3Universal Hardware Management
Heat dissipation componentCLUCLU[1~N]1960xC4Energy Efficiency Management
Ascend software alarmAscend Software EventsAscend software alarms (such as MindIE and MindCluster alarms)2520xFCAscend
PoDManager system softwarePoDManagerThis alarm is generated when the PoDManager software is detected.2530xFDCluster
ReservedReservedReserved. It is used for extension or special scenario definition and cannot be used as a valid device type.2550xFF