No relevant resource is found in the selected language.
Enterprise
Worldwide
Huawei Global - English
Support Documentation
FusionServer Pro High-Density Server iBMC (V250 or Later) Alarm Handling 24
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Event Alarms

Event Alarms

An event alarm indicates an event occurred during the running of a server. Generally, this type of alarms does not affect services and need to be handled immediately. Users can handle event alarms in off-peak hours. Table 10-1 lists the events of servers.

Table 10-1 Event list

Event Code

Event Description

Impact/Suggestions

0x00000015

CPU arg1 installed.

NOTE:

arg1 indicates the CPU No.

-

0x00000017

CPU arg1 removed.

NOTE:

arg1 indicates the CPU No.

Impact:The server may break down.

0x00000079

CPU arg1 health status degradation detected by PFAE.

NOTE:

arg1 indicates the CPU No.

Impact: The system reliability is affected.

Handling suggestions:

  1. Arrange planned maintenance. After the server is powered off, check whether the CPU or its socket is damaged or whether the CPU has poor contact with its socket.
  2. Replace the faulty part and check whether the alarm is cleared.
  3. Replace the mainboard.

0x00000081

arg1 CPU arg2 is replaced from SN(arg3) to SN(arg4).

NOTE:
  • arg1 indicates the slot No. of the memory board.
  • arg2 indicates the DIMM silkscreen or CPU socket number and memory channel No.
    • DIMM silkscreen, for example, DIMM020(A) or DIMM010(B).
    • CPU socket number and memory channel No.

      The number of DIMMs corresponding to a channel varies depending on the server model.

  • arg3 indicates the SN of the DIMM to be replaced.
  • arg4 indicates the SN of the new DIMM.

-

0x0100000D

[Memory board arg1] arg2 memory correctable ECC.

NOTE:
  • arg1 indicates the slot No. of the memory board.
  • arg2 indicates the DIMM silkscreen or CPU socket number and memory channel No.
    • DIMM silkscreen, for example, DIMM020(A) or DIMM010(B).
    • CPU socket number and memory channel No.

      The number of DIMMs corresponding to a channel varies depending on the server model.

Impact: The system performance is affected.

0x0100000F

[Memory board arg1] arg2 installed.

NOTE:
  • arg1 indicates the slot No. of the memory board.
  • arg2 indicates the DIMM silkscreen or CPU socket number and memory channel No.
    • DIMM silkscreen, for example, DIMM020(A) or DIMM010(B).
    • CPU socket number and memory channel No.

      The number of DIMMs corresponding to a channel varies depending on the server model.

-

0x01000011

[Memory board arg1] arg2 removed.

NOTE:
  • arg1 indicates the slot No. of the memory board.
  • arg2 indicates the DIMM silkscreen or CPU socket number and memory channel No.
    • DIMM silkscreen, for example, DIMM020(A) or DIMM010(B).
    • CPU socket number and memory channel No.

      The number of DIMMs corresponding to a channel varies depending on the server model.

Impact: The system performance is affected.

Handling suggestions:

  1. Install a DIMM in the slot indicated by the alarm.
  2. Reseat the DIMM.
  3. Replace the DIMM.
  4. Replace the mainboard or memory board.

0x0100002B

[arg1]arg2 memory initialization error. Error code: arg3.

NOTE:
  • arg1 indicates the Slot number of the memory board.
  • arg2 indicates the DIMM silkscreen or CPU socket number and memory channel No.
  • arg3 indicates the error code of the alarm.

-

0x0100002D

[arg1] arg2 health status degradation detected by PFAE.

NOTE:
  • arg1 indicates the slot No. of the memory board.
  • arg2 indicates the DIMM silkscreen or CPU socket number and memory channel No.
    • DIMM silkscreen, for example, DIMM020(A) or DIMM010(B).
    • CPU socket number and memory channel No.

      The number of DIMMs corresponding to a channel varies depending on the server model.

Impact: The system reliability is affected.

Handling suggestions:

  1. Arrange planned maintenance. After the server is powered off, check whether the CPU or its socket is damaged or whether the CPU has poor contact with its socket.
  2. Replace the faulty part and check whether the alarm is cleared.
  3. Replace the mainboard.

0x01000041

arg1 arg2 is replaced from SN(arg3) to SN(arg4).

NOTE:
  • arg1 indicates the slot No. of the memory board.
  • arg2 indicates the DIMM silkscreen or CPU socket number and memory channel No.
    • DIMM silkscreen, for example, DIMM020(A) or DIMM010(B).
    • CPU socket number and memory channel No.

      The number of DIMMs corresponding to a channel varies depending on the server model.

  • arg3 indicates the SN of the DIMM to be replaced.
  • arg4 indicates the SN of the new DIMM.

-

0x02000003

The [arg1] disk arg2 installed.

NOTE:
  • arg1 indicates the disk location, for example, rear or front.
  • arg2 indicates the disk slot No.

-

0x02000005

The [arg1] disk arg2 removed.

NOTE:
  • arg1 indicates the disk location, for example, rear or front.
  • arg2 indicates the disk slot No.

-

0x0200000D

RAID rebuild starts at the [arg1] disk arg2.

NOTE:
  • arg1 indicates the disk location, for example, rear or front.
  • arg2 indicates the disk slot No.

-

0x0200000F

RAID rebuild at the [arg1] disk arg2 stopped.

NOTE:
  • arg1 indicates the disk location, for example, rear or front.
  • arg2 indicates the disk slot No.
The stop of the rebuild does not mean a success of the rebuild. You still need to check for alarms related to the drives and RAID controller card.
  • If there is no alarm generated for the RAID controller card or drives, the RAID rebuild is successful.
  • If there are alarms generated for the RAID controller card or drives, the RAID rebuild has failed.

0x0200001F

The [arg1] disk arg2 health status degradation detected by PFAE.

NOTE:
  • arg1 indicates the disk location, for example, rear or front.
  • arg2 indicates the disk slot No.

Impact: The system reliability is affected.

Handling suggestions:

  1. Arrange planned maintenance. After the server is powered off, check whether the CPU or its socket is damaged or whether the CPU has poor contact with its socket.
  2. Replace the faulty part and check whether the alarm is cleared.
  3. Replace the mainboard.

0x02000023

The arg1 disk arg2 is replaced from SN(arg3) to SN(arg4).

NOTE:
  • arg1 indicates the disk location, for example, rear or front.
  • arg2 indicates the disk slot No.
  • arg3 indicates the SN of the disk to be replaced.
  • arg4 indicates the SN of the new disk.

-

0x02000033

The [arg1] disk arg2 disconnected temporarily.

NOTE:
  • arg1 indicates the disk location, for example, rear or front.
  • arg2 indicates the disk slot No.

-

0x03000003

PSU arg1 installed.

NOTE:

arg1 indicates the PSU slot No.

-

0x03000005

PSU arg1 removed.

NOTE:

arg1 indicates the PSU slot No.

Impact: The power supply redundancy is affected.

0x03000021

High output voltage detected on PSU arg1.

NOTE:

arg1 indicates the PSU slot No.

Impact: The output power voltage is high.

0x03000023

Low output voltage detected on PSU arg1.

NOTE:

arg1 indicates the PSU slot No.

Impact: The output power voltage is low.

0x03000025

High output current detected on PSU arg1.

NOTE:

arg1 indicates the PSU slot No.

Impact: The PSU is about to fail.

0x03000027

High input voltage detected on PSU arg1.

NOTE:

arg1 indicates the PSU slot No.

Impact: The input voltage is too high, and the PSU is about to fail.

0x0300001D

Low input voltage detected on PSU arg1.

NOTE:

arg1 indicates the PSU slot No.

Impact: The input voltage is too low, and the PSU is about to fail.

0x03000029

High temperature detected on PSU arg1.

NOTE:

arg1 indicates the PSU slot No.

Impact: The PSU internal temperature is too high, and the PSU is about to fail.

0x0300002B

Fan alarm detected on PSU arg1.

NOTE:

arg1 indicates the PSU slot No.

Impact: A PSU fan alarm is generated, and the PSU is about to fail.

0x04000001

Fan arg1 [arg2] installed.

NOTE:
  • arg1 indicates the slot No. of the fan module.
  • arg2 indicates the fan module location, for example, rear or front.

-

0x04000003

Fan arg1 [arg2] removed.

NOTE:
  • arg1 indicates the slot No. of the fan module.
  • arg2 indicates the fan module location, for example, rear or front.

Impact: The fan redundancy is affected.

0x06000001

The RAID controller card arg1 installed.

NOTE:

arg1 indicates the slot No. of the RAID controller card.

-

0x06000003

The RAID controller card arg1 removed.

NOTE:

arg1 indicates the slot No. of the RAID controller card.

Impact: The services related to the RAID controller card will be interrupted.

0x06000013

arg1 RAID card arg2 BBU is absent.

NOTE:
  • arg1 indicates the slot No. of the RAID controller card.
  • arg2 indicates the location of the RAID controller card.
    • FM: The RAID controller card is located in the front I/O module.
    • CMN: The RAID controller card is located in the compute node in slot N.

Impact: The cache function of the RAID controller card fails.

Handling suggestions: Replace the BBU.

0x06000015

arg2 RAID card arg1 BBU is present.

NOTE:
  • arg1 indicates the slot No. of the RAID controller card.
  • arg2 indicates the location of the RAID controller card.
    • FM: The RAID controller card is located in the front I/O module.
    • CMN: The RAID controller card is located in the compute node in slot N.

-

0x06000023

The arg1 RAID controller card arg2 health status degradation detected by PFAE.

NOTE:
  • arg1 indicates the slot No. of the RAID controller card.
  • arg2 indicates the location of the RAID controller card.
    • FM: The RAID controller card is located in the front I/O module.
    • CMN: The RAID controller card is located in the compute node in slot N.

Impact: The system is still running properly, but the reliability is affected.

Handling suggestions:

  1. Arrange planned maintenance. After the server is powered off, check whether the CPU or its socket is damaged or whether the CPU has poor contact with its socket.
  2. Replace the faulty part and check whether the alarm is cleared.
  3. Replace the mainboard.

0x08000019

The [arg1] PCIe card arg2 (arg3) starting arg4.

NOTE:

  • arg1 indicates the PCIe card location, for example, front, inner, or rear.

  • arg2 indicates the PCIe card slot No.

  • arg3 indicates the PCIe card type, for example, M60 GPU.
  • arg4 indicates the system startup phase, for example, BIOS POST successful or OS load successful.

-

0x0800003D

The [arg1] PCIe card arg2 (RAID) BBU is absent.

NOTE:

  • arg1 indicates the PCIe card location, for example, front, inner, or rear.

  • arg2 indicates the PCIe card slot No.

Impact: The cache function of the PCIe card fails.

Handling suggestions: Replace the BBU.

0x0800003F

The [arg1] PCIe card arg2 (RAID) BBU is present.

NOTE:

  • arg1 indicates the PCIe card location, for example, front, inner, or rear.

  • arg2 indicates the PCIe card slot No.

-

0x08000065

arg1 arg2 [arg3] health status degradation detected by PFAE.

NOTE:

  • arg1 indicates the PCIe card location, for example, front, inner, or rear.

  • arg2 indicates the PCIe card slot No.

  • arg3 indicates the PCIe card type, for example, PCIe Card or SDI Card.

Impact: The system reliability is affected.

Handling suggestions:

  1. Arrange planned maintenance. After the server is powered off, check whether the CPU or its socket is damaged or whether the CPU has poor contact with its socket.
  2. Replace the faulty part and check whether the alarm is cleared.
  3. Replace the mainboard.

0x0800008F

The arg1 PCIe card arg2 (arg3) arg4 chip was reset. [arg5] [arg6]

NOTE:
  • arg1 indicates the device holding the PCIe card, for example, GpuBoard or Riser.

  • arg2 indicates the PCIe card slot No.

  • arg3 indicates the PCIe card type, for example, NIC or SDI.
  • arg4 indicates the device name, for example, NetCard or TransformCard.
  • arg5 indicates the supplementary information about the alarm, for example, Error Code.
  • arg6 indicates the error code of the alarm, for example, (7168) or (7177).

-

0x0D000007

The NIC arg1 health status degradation detected by PFAE.

NOTE:

arg1 indicates the NIC slot No.

Impact: The system reliability is affected.

Handling suggestions:

  1. Arrange planned maintenance. After the server is powered off, check whether the CPU or its socket is damaged or whether the CPU has poor contact with its socket.
  2. Replace the faulty part and check whether the alarm is cleared.
  3. Replace the mainboard.

0x0F000001

PCIe riser card arg1 installed.

NOTE:

arg1 indicates the slot No. of the PCIe riser card.

-

0x0F000003

PCIe riser card arg1 removed.

NOTE:

arg1 indicates the slot No. of the PCIe riser card.

Impact: The services related to the PCIe card will be interrupted.

0x100000C3

Failed to obtain the RTC Time on the mainboard.

Impact: The log time on the iBMC is inaccurate.

Suggestions:

  1. Restart the iBMC.
  2. Replace the RTC battery.
  3. If the problem persists, replace the mainboard.

0x100000CD

The LOM [arg1] health status degradation detected by PFAE.

NOTE:

arg1 indicates the LOM slot No.

Impact: The system reliability is affected.

Handling suggestions:

  1. Arrange planned maintenance. After the server is powered off, check whether the CPU or its socket is damaged or whether the CPU has poor contact with its socket.
  2. Replace the faulty part and check whether the alarm is cleared.

0x12000005

Chassis cover opened.

Impact: Heat dissipation and component protection will be affected.

Handling suggestions: Close the chassis cover.

0x1A00000B

arg1 changed.

NOTE:

arg1 indicates the SDR or FR information and iBMC version.

-

0x1A00000D

iBMC is restarted after AC power supply is restored.

-

0x1A00000F

iBMC event records are cleared.

-

0x1A000011

iBMC event record has reached 90% space capacity.

Impact: If this alarm is not handled in time, the event records will overflow.

Handling suggestions: Clear event records.

0x1A00001B

iBMC operation log has reached 90% space capacity.

Impact: If this alarm is not handled in time, the operation logs will overflow and some historical operation logs may be lost.

Handling suggestions:

  1. Export the operation logs.
  2. Enable the remote syslog dumping function.

0x1A00001D

iBMC security log has reached 90% space capacity.

Impact: If this alarm is not handled in time, the security logs will overflow and some historical security logs may be lost.

Handling suggestions:

  1. Export the security logs.
  2. Enable the remote syslog dumping function.

0x1A000021

iBMC is reset and started.

-

0x1A000023

arg1 certificate is about to expire or has expired.

NOTE:
  • arg1 indicates the certificate type.
  • In iBMC V370 and later versions, the alarm severity is Minor. In other versions, the alarm severity is Normal.

Handling suggestions: Import a new certificate.

0x1A000025

Heartbeat signals between the iBMC and the system management software (iBMA) are lost.

Impact: The in-band management and monitoring information cannot be obtained or updated on a realtime basis.

Handling suggestions: Reinstall the iBMA.

0x1A000029

iBMC time is stepped by more than arg1 minutes.

NOTE:

arg1 indicates the time stepped.

Impact: The iBMC log time is inaccurate.

Handling suggestions: Restart the iBMC.

0x1A00002B

iBMC failed to synchronize time with the NTP server.

NOTE:

The event code of this alarm is 0x1A000031 in versions earlier than iBMC V256 and 0x1A00002B in iBMC V256 or later.

Impact: The iBMC system time is inaccurate.

Handling suggestions:

  1. Check whether the NTP server is configured correctly.
  2. Check whether the communication between the iBMC and the NTP server is normal.
  3. Restart the NTP service of the iBMC.

0x1A000039

The iBMC license enters the grace period and can still be used. It will expire in arg1 days.

NOTE:

arg1 indicates the remaining days in the grace period.

Impact: Advanced features of the iBMC cannot be implemented.

Handling suggestions:

  1. Install a valid license.
  2. Delete the current license.

0x1A00003B

The iBMC license has expired.

Impact: Advanced features of the iBMC cannot be implemented.

Handling suggestions:

  1. Install a valid license.
  2. Delete the current license.

0x27000033

PCH health status degradation detected by PFAE.

Impact: The system reliability is affected.

Handling suggestions:

  1. Arrange planned maintenance. After the server is powered off, check whether the mainboard is damaged.
  2. Replace the mainboard and check whether the alarm is cleared.

0x28000015

CPU arg1 QPI/UPI arg2 link health status degradation detected by PFAE.

NOTE:

  • arg1 indicates the CPU No.

  • arg2 indicates the QPI/UPI channel No.

Impact: The system reliability is affected.

Handling suggestions:

  1. Arrange planned maintenance. After the server is powered off, check whether the CPU or its socket is damaged or whether the CPU has poor contact with its socket.
  2. Replace the faulty part and check whether the alarm is cleared.
  3. Replace the mainboard.

0x29000001

arg1 [arg2] portarg3 disconnected.

NOTE:
  • arg1 indicates the NIC status.
    • NIC N: Ethernet NIC N (N indicates the slot No.)
    • PCIe Card N: standard PCIe NIC N (N indicates the slot No.)
    • LOM: LAN on motherboard.
  • arg2 indicates the NIC type, for example, (NIC) or (FC).
  • arg3 indicates the network port No.

Impact: The network port services will be interrupted.

Handling suggestions:

  1. Remove and reconnect the network cable.
  2. Check whether the network cable is properly connected to the peer device.
  3. Check whether the peer device is operating properly.

0x2B000003

arg1

NOTE:

arg1 indicates Alarm message:

  • RAID card (RAID Card1) PHY0 bit error increased too fast.
  • RAID card (RAID Card1) expander 1 PHY0 bit error increased too fast.

Impact: The performance of the drive connected to the corresponding slot may deteriorate, or the drive may even become offline.

Handling suggestions:

  1. If an expander backplane is used, replace the cables, RAID controller card, and backplane in sequence.
  2. If a pass-through backplane is used, replace the cables, drives, RAID controller card, and backplane in sequence.

0x2C000001

The CPU usage (arg1) exceeds the threshold (arg2).

NOTE:
  • arg1 indicates the current CPU usage.
  • arg2 indicates the CPU usage threshold.

Impact: The system performance is affected.

Handling suggestions:

  1. Check whether the CPU usage threshold is set improperly (too low).
  2. Stop services to release CPU resources.

0x2C000003

The memory usage (arg1) exceeds the threshold (arg2).

NOTE:
  • arg1 indicates the current memory usage.
  • arg2 indicates the memory usage threshold.

Impact: The system performance is affected.

Handling suggestions:

  1. Check whether the memory usage threshold is set improperly (too low).
  2. Stop services to release memory resources.

0x2C000009

ACPI is in the working state.

-

0x2C00000B

ACPI is in the soft-off state.

Impact: The server fails to power on.

0x2C000063

The host was restarted by BMC arg1.

NOTE:

arg1 indicates the cause of the restart, for example, "due to an IERR diagnosis failure" or "due to PCIe switch or retimer upgrade".

Impact: Services will be interrupted.

Handling suggestions: Restart the iBMC as soon as possible.

0x2C00000F

The host was restarted due to unrecognized reason.

Impact: Services running on the server will be interrupted.

0x2C000011

The host was restarted by command.

Impact: Services running on the server will be interrupted.

0x2C000013

The host was restarted by power button.

Impact: Services running on the server will be interrupted.

0x2C000015

The host was restarted due to watchdog timeout.

Impact: Services running on the server will be interrupted.

0x2C000017

The host is restarted after being powered on (Power strategy is "Turn On").

Impact: Services running on the server will be interrupted.

0x2C000019

The host is restarted after being powered on (Power strategy is "Restore Previous State").

Impact: Services running on the server will be interrupted.

0x2C00001B

The OS cannot start without a boot device.

Impact: The server OS fails to start.

0x2C00001D

The OS cannot start without a bootable disk.

Impact: The server OS fails to start.

0x2C00001F

The OS cannot start because the PXE service is unavailable.

Impact: The server OS fails to start.

0x2C000021

The OS cannot start due to the invalid boot partition.

Impact: The server OS fails to start.

0x2C000023

The watchdog(arg1) timed out.

NOTE:

arg1 indicates the watch dog type, which can be BIOS FRB2, BIOS/POST, OS Load, SMS/OS, or OEM.

-

0x2C00002D

Power capping failed.

Impact: The server automatically powers off, which interrupts services.

Handling suggestions:

  1. Check whether the mains supply meets power consumption requirements of the server. If no, adjust the power supply.
  2. Increase the power cap value.

0x2C00002F

The server system crashes or is abnormally reset.

Impact: The server OS is abnormal, and related services are interrupted.

0x2C000051

arg1 arg2 arg3 arg4 memory initialization error. Error code: 0xarg5.

NOTE:

arg1 indicates the Slot number of the memory board.

arg2 indicates the DIMM silkscreen or CPU socket number and memory channel No.

arg3 indicates the error code of the alarm.

arg4 indicates the Memory serial number.

arg5 indicates the BOM code.

Impact: The server performance is affected, or the server fails to start.

0x2C000053

The hard disk partition (arg1) usage (arg2) exceeds the threshold (arg3).

NOTE:
  • arg1 indicates the disk partition No.
  • arg2 indicates the current disk partition usage.
  • arg3 indicates the disk partition usage threshold.

Impact: The system performance is affected.

Handling suggestions:

  1. Check whether the disk partition usage threshold is set improperly (too low).
  2. Clear disk partition to release resources.

0x2C000059

System power is abnormal, reading value:arg1,threshold value:arg2.

NOTE:

arg1 indicates the Current reading of the sensor.

arg2 indicates the Alarm threshold.

Impact: The management software cannot correctly report the total system power consumption in real time.

Handling suggestions:

1.Restart the iBMC.

2.Replace the PSU.

0x2C000061

Network arg1 [arg2] arg3 bandwidth usage (arg4) exceeds the threshold (arg5).

NOTE:
  • arg1 indicates the NIC status.
    • NIC N: Ethernet NIC N (N indicates the slot No.)
    • PCIe Card N: standard PCIe NIC N (N indicates the slot No.)
    • LOM: LAN on motherboard.
  • arg2 indicates the NIC type, for example, (NIC) or (FC).
  • arg3 indicates the network port No.
  • arg4 indicates the current bandwidth.
  • arg5 indicates the bandwidth threshold.

Impact: The packet loss rate of the NIC port increases, and the communication quality deteriorates.

Handling suggestions:

  1. Check for and stop the services that cause abnormal packet transmission.
  2. Replace the NIC with a NIC that provides higher bandwidth.
  3. Check for network storm.

0x31000001

The power button on the panel is pressed.

Impact: The server will be powered off.

0x31000003

The UID button on the panel is pressed.

-

0x2C000085

After the AC is powered on, the host is restarted because the SP information collection is completed.

-

0x05000015

The disk backplane arg1 is replaced from SN(arg2) to SN(arg3).

NOTE:
  • arg1: Slot number of the drive backplane related to the alarm.
  • arg2: SN of the drive backplane before replacement.
  • arg3: SN of the drive backplane after replacement.

-

0x080000BD

arg1 is replaced from SN(arg2) to SN(arg3).

NOTE:
  • arg1: Name of the PCIe card related to the alarm, for example, FPGA or NIC.
  • arg2: SN of the PCIe card before replacement.
  • arg3: SN of the PCIe card after replacement.

-

0x03000043

PSU arg1 is replaced from SN(arg2) to SN(arg3).

NOTE:
  • arg1: Slot number of the PSU.
  • arg2: SN of the PSU before replacement.
  • arg3: SN of the PSU after replacement.

-
Translation
日本語 简体中文
Download
Updated: 2021-08-04

Document ID: EDOC1000157054

Views: 302218

Downloads: 149

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Digital Signature File

Digital Signature Authentication Mode
Share
Previous Next
Huawei e+ App Huawei e+

Copyright © 2022 Huawei Technologies Co., Ltd. All rights reserved.

You are going to visit :