Product Classification Description and Precautions
| Category | Models |
|---|---|
| V3/V5 rack servers | RH1288 V3, RH2288 V3, RH2288H V3, XH310 V3, RH8100 V3, RH5885 V3, RH5885H V3, 5288 V3, 1288H V5, 2288H V5, 2288C V5, 5288 V5, 2288 V5(JDM), 5885H V5, 2488 V5, 2488H V5, 1288X V5, 2288X V5, 5288X V5, 2298 V5 |
| V6 rack servers | 1288H V6, 2288H V6, 2488H V6, DP1210, DP2210, DP4210 |
| V3/V5 blade servers | CH121 V3, CH121H V3, CH121L V3, CH140 V3, CH140L V3, CH220 V3, CH222 V3, CH242 V3, CH226 V3, CH225 V3, CH121 V5, CH242 V5, CH121L V5, CH225 V5, CH221 V5, FD Controller |
| V3/V5 switch modules | CX220, CX620, CX621, CX320, CX318, CX710, CX712, CX820, CX916, CX920, CX930 |
| Management module | MM630, MM810, MM650, MM920, MM921, MM510, RM110, RM210 |
| High-density V3/V5 servers | XH622 V3, XH628 V3, XH620 V3, XH310 V3, XH321 V3, XH321 V5, XH321L V5, XH628 V5 |
| KunLun servers | 9008, 9016, 9032, RH8100 V3, 9008 V5 Base, 9008 V5 Advance, 8100 V5 |
| TaiShan 100 server | Taishan 100 2180, TaiShan 100 2280, TaiShan 100 5280, TaiShan 100 XR320 |
| TaiShan 200 server | TaiShan 200 1280, TaiShan 200 2180, TaiShan 200 2280, TaiShan 200 5280, TaiShan 200 2480, TaiShan 200 2280E, TaiShan 200 5290, TaiShan 200 XA320, TaiShan 200 2280H, TaiShan 200 2280 Pro, TS200-2280K, TS200-5280K, S920X20, S920X21, S920S10, S920S10K, S920X10, S920X10K |
| Atlas GPU servers | G560, G2500, G560 V5, G530 V5 |
| Atlas NPU servers | Atlas 800 9000, A800-9000, Atlas 800 9010, A800-9010, Atlas 500 Pro, A500 Pro, Atlas 900 A3 SuperPoD, Atlas 800T A3, A800T A3, Atlas 800I A3, A800I A3, A200T A3 Box8, Atlas 800I A2 2UP, A800I 2UP, Atlas9000 RCK A3 A9000 RCK A3, Atlas 800I A2, Atlas 800T A2, Atlas 900 A2 PoD |
| FusionPod servers | DA120 V2, DA120C V2, DH120 V5, DH120C V5, DA140C V2, DH140C V6, DA121C V2 |
| E9000H series | CM221, CN221, CN221 V2, CN221S V2, CM221S, CM311T V2, CM211S V2, CM221S V2, SMM410, SMM420, SMM810, SMM820, CM221 V2, CM421 V2, CM411 V2 |
| Storage Series | OceanStor Pacific 9950 Data cluster module, OceanStor Pacific 9950 Node, FusionCube 500, OceanDisk 1300, OceanDisk1301 |
Note: The command sets supported by different products may be different. That is, the same command may not be supported by all models listed above.
[Precaution] Subsystem naming and division
| Subsystem Name (Zh) | Abbreviation | Note |
|---|---|---|
| Unified O&M Subsystem | om | 1. Interface, including northbound interfaces (including web interfaces) 2. O&M system in the BMC domain |
| Various Hardware Subsystems | hardware | hardware, hardware management |
| Energy efficiency management subsystem | energy | energy. No verb is presented. |
| RAS fault management subsystem | ras | ras is an abbreviation used in the industry to display all functions in the fault management domain. |
| Security Resilience Subsystem | security | Security-related apps |
| Platform Functional Subsystem | bmc_core | bmc_core: basic core function of the BMC software |
| Basic Framework Subsystem | framework | Framework, a pure software framework irrelevant to services |
[Note] iBMCBMC indicates the four-segment version number rule.
The rules for defining the BMC four-segment version number are as follows:
- The first segment has a fixed length of 1 byte, ranging from 3 to 9.
- The middle two segments are fixedly two bytes, ranging from 00 to 99. The prefix 0 cannot be omitted.
- The fourth field has a fixed length of 2 bytes, ranging from 00 to 97. The prefix 0 cannot be omitted. (In the equipment scenario, the fourth field value is increased by 1.)
- When the IPMI interface is used to query the version number, the four segments are interpreted as hexadecimal numbers and then returned. For example, 99 is interpreted as 0x99. The command is ipmitool raw 0x2C 0x2F 0x00 0x00 0x01.
[Precaution] Application Owner
General principles
IPMI commands implemented by the BMC software are preferentially reviewed by the BMC side.
IPMI commands implemented by the IMU software are preferentially reviewed by the IMU side.
Exceptional scenario: If some features are fully viewed in a certain domain or the corresponding requirement initiator, ask the owner of the corresponding domain to submit a topic for review.
[Precaution] Interface Modification Process
Step 1: Developers obtain the latest interface document.
Step 2: Developers update, modify, or add interfaces based on the latest document and pass the review by SEs in the team (review dimensions: interface integrity and interface requirement satisfaction).
Step 3: The development personnel ask the interface document maintenance SE to review the rationality, universality, and compatibility of the interface. After the review is passed, the development personnel submit the interface document to the subPC for review.
Step 4 After the subPC review is passed, the development personnel send the modification points and review minutes to the interface document maintenance SE by email for update.
[Precaution] Checklist of Common Problems in IPMI Interface Modification
The length field needs to be added to the content to be set and queried. If the content is too long, read and write by segment need to be considered.
After the subPC review is passed, the development personnel send the modification points and review minutes to the interface document maintenance SE by email. The test personnel perform acceptance based on the external IPMI interface document and do not update the external IPMI document. The test personnel submit a trouble ticket to track the acceptance.
The command word definition must not conflict with the existing IPMI.
If the commands of earlier versions are reused, the compatibility of the BMC in all scenarios must be considered, including but not limited to the new version, peripheral components, tools, production equipment, and live network scenarios.
If an interface is modified, the change history must be clearly described, including the software version, modification background, modification time, and modifier of iBMCBMC.
If the IPMI command is dedicated for a specific server model, specify the server model in the Applicable Server Model column.
Examples of IPMI commands must be accurate and executable.