iBMC Introduction and Log Analysis
What is BMC?
Platform management monitors and controls hardware such as temperature sensors, voltages, fans and power supplies. It also records hardware information and logs for alerts and troubleshooting. These functions can be integrated in a Baseboard Management Controller (BMC), an independent embedded system with its own processor, software and management functions. BMCs are common in servers and can operate independently of the host OS. The diagram below shows a BMC in the system.
The source guide covers two iBMC generations based on the 1710 and 1711 processors. Its screenshots and defaults are examples from the shown platforms; they do not describe every current iBMC firmware version.
Device Management
Out-of-band Management (out-of-band)
Network management is implemented through a dedicated network management channel, separating management data from business data and establishing a
dedicated channel for management data. In this channel, only management data is transmitted. Separating management data from business data can improve management efficiency and reliability, and also enhance the security of
management data.
In-band Management (in-band)
Network management control information and user data information are transmitted using the same physical channel.
Introduction to iBMC Web Login
Step 1: Open a supported browser and enter the configured iBMC address. The source example lists 192.168.2.10 as its default; use the address configured for your device.
Step 2: If the browser displays the certificate warning shown below, verify the intended management address and certificate before deciding whether to continue.
English explanatory illustration of the source certificate warning; the address and error code are retained.
Step 3: Select the interface language and enter the credentials configured for the device. The source platform lists Admin / Admin@123 as legacy defaults; these values are platform-specific. Choose the local iBMC or user domain and click Log In. First login or an unchanged initial password may trigger a security prompt.
English explanatory illustration of the KunTai R722 iBMC login page; the serial number is masked and input fields are empty.
Basic Information View
English explanatory illustration of the source iBMC home page. Device identifiers are masked; source hardware counts, IP address and versions are retained.
iBMC Log Collection Methods
In the iBMC web interface, choose Quick Access > One-Click Collection. After collection, download the diagnostic package; the source example creates dump_info.tar.gz.
English explanatory illustration of Quick Access: One-Click Collection. Alarm counts remain zero; device identity text is masked.
Alternatively, connect to iBMC over SSH and run ipmcget -d diaginfo. When collection completes, retrieve dump_info.tar.gz from /tmp using an SFTP or SCP client.
Obtain server basic information from the one-click collection data
Obtain server model and serial number
dump_info\RTOSDump\versioninfo\fruinfo.txt
Obtain iBMC IP address
dump_info\AppDump\NetConfig\net_info.txt
Obtain server firmware version information
dump_info\RTOSDump\versioninfo\app_revision.txt
Obtain server board information
dump_info\AppDump\card_manage\card_info
Obtain server memory information
dump_info\AppDump\CpuMem\mem_info
Obtain CPU information
dump_info\AppDump\CpuMem\CPU_info
Obtain fan information
dump_info\AppDump\cooling_app\fan_info.txt
Obtain sensor information
dump_info\AppDump\sensor_alarm\sensor_info.txt
If a sensor value crosses a threshold, the server can raise an alarm.
lnr: Lower Non-Recoverable
lc: Lower Critical
lnc: Lower Non-Critical
unc: Upper Non-Critical
uc: Upper Critical
unr: Upper Non-RecoverableObtain hard disk information
dump_info\AppDump\StorageMgnt\RAID_Controller_Info.txt
Obtain server system power consumption information
In dump_info\OptPme\pram, view ps_web_view.dat
English explanatory illustration; source power, energy and timestamp values are retained without an added timezone.
English explanatory excerpt of the final power-history row: current, average and maximum. Earlier repeated rows are omitted; the source timestamp is unchanged.
Obtain server configuration summary information
dump_info\RTOSDump\versioninfo\server_config.txt
Common files requiring event record analysis
dump_info\LogDump
dump_info\OSDump
dump_info\AppDump\sensor_alarm\sel.tar
System Event Log (SEL)
Judging Hardware Faults Based on SEL Logs:
dump_info\AppDump\sensor_alarm\sel.tar
SEL logs mainly record hardware alarms occurring on the server and timestamps of these alarms.
A summary of various restart actions recorded in the SEL log is as follows:
English explanatory rendering of the source restart-event reference table. Event tokens and diagnostic cases are retained.
Operation Log Analysis
(dump_info\LogDump\operate_log)
Records changes made under BMC and BIOS, which can be used to analyze the scenario when issues occur alongside SEL logs. For example: Was abnormal power-off manual operation? Settings made under BIOS
When operations were performed, etc.
Common operation logs are divided into several types as follows:
IPMI,N/A@HOST,BMC,Set XXXXXX successfully Server reboot self-test prompt
IPMI,bmcUSER@bmcip,BMC,Set XXXX successfully Actions triggered using tools such as ipmitool
KVM, bmcUSER@bmcip,KVM,XXXXX Accessed via KVM remote console
WEB, bmcUSER@bmcip,User,XXXXX Accessed via BMC web interface
CLI, bmcUSER@bmcip:49680,CLI,root(10.44.88.148:49680) xxxx successfully Accessed via BMC CLI interface,
SNMP, bmcUSER@bmcip,sensor_alarm,Set SNMP xxx successfully Accessed via SNMP protocol to BMC
Maintenance Log Analysis
(dump_info\LogDump\maintenance_log)
Key Focus: Power On/Off, Power Supply, RAID. Maintenance logs generally contain current and voltage alarms related to the motherboard, which can be used to locate abnormal power-down issues. The logs typically include power module alarms (occurring outside of power on/off events). When such alarms appear accompanied by abnormal system power on/off, it usually indicates a motherboard or power module fault.
Maintenance logs also record server hardware exception information
FDM Fault Diagnosis Log Analysis
(dump_info\LogDump)
English explanatory illustration of the FDM-related files; filenames, modification times and sizes are retained.
fdm Log File Function Description:
1. The fdm_log file records the occurrence time of errors received by iBMC, collection source, original error information, and parsing information of some registers (such as error level).
2. fdm_output generally records diagnostic results and some auxiliary positioning information. Whenever an alarm is generated by FDM, there will be a record in fdm_output.
FDM Fault Diagnosis Log (dump_info\LogDump\fdmlog) - Fault Example: DIMM
English reference rendering of the annotated DIMM error: field mappings and raw register values are retained, including the original GMT timestamp.
Serial Port Log
In dump_info\OSDump, examine systemcom and the last three screen captures. Serial-console logs record POST/restart information and activity before shutdown. The three captures preserve screen states before shutdown or restart.
English reference rendering of all 45 source BIOS initialization markers. Line numbers and diagnostic meanings are retained; unrelated sample addresses are omitted.
English reference rendering of the source BIOS-log annotations. Line references and diagnostic meanings are retained; example memory addresses and MAC values are omitted. This is an explanatory table, not a raw log capture.
English explanatory rendering of the source legacy BIOS/MBR, GRUB and SysV init boot diagram. This workflow is version-specific; modern UEFI/systemd systems differ.
English reference rendering of the source keyword and time-correlation notes; unrelated stack frames are omitted. The shown captures are separate examples: correlate records using a common boot/time anchor, without directly subtracting these unrelated sample timestamps.