Message text

Dropped below the lower minor threshold.---Current reading:$1---Threshold reading:$2

Variable fields

$1: Current reading of the temperature sensor.

$2: Value of the lower minor temperature alarm threshold.

Severity level

Minor

Example

Dropped below the lower minor threshold.---Current reading:2---Threshold reading:10

Impact

Performance degradation and unstable operation might occur on the device components if the temperature is too low.

If the temperature does not rise and the alarm persists, it might result in further temperature reduction and produce alarms of the major level. Therefore, it is important to detect potential issues that might lead to low temperature alarms as early as possible to avoid escalation of the issues.

Cause

The temperature is too low.

Recommended action

1.     Verify that the temperature of the equipment room is as required.

2.     Log in to HDM, access the Fans page, and verify if the fan speed is too high. If yes, adjust the fan speed mode or fan speed level.

3.     If the issue persists, contact Technical Support.

Message text

Dropped below the lower major threshold.---Current reading:$1---Threshold reading:$2

Variable fields

$1: Current reading of the temperature sensor.

$2: Value of the lower major temperature alarm threshold.

Severity level

Major

Example

Dropped below the lower major threshold.---Current reading:2---Threshold reading:5

Impact

Performance degradation and unstable operation might occur on the device components if the temperature is too low.

If the temperature does not rise and the alarm persists, it might result in further temperature reduction and generate alarms of the critical level. Therefore, it is important to detect potential issues that might lead to low temperature alarms as early as possible in order to avoid issue escalation.

Cause

The temperature is too low.

Recommended action

1.     Verify that the temperature of the equipment room is as required.

2.     Log in to HDM, access the Fans page, and verify if the fan speed is too high. If yes, adjust the fan speed mode or fan speed level.

3.     If the issue persists, contact Technical Support.

Message text

Dropped below the lower critical threshold.---Current reading:$1---Threshold reading:$2

Variable fields

$1: Current reading of the temperature sensor.

$2: Value of the lower critical temperature alarm threshold.

Severity level

Critical

Example

Dropped below the lower critical threshold.---Current reading:2---Threshold reading:3

Impact

Operating devices in ultra-low temperature environments can reduce device performance, impact device lifespan, disrupt business operations, and lead to system downtime.

Cause

The temperature is too low.

Recommended action

1.     Verify that the temperature of the equipment room is as required.

2.     Log in to HDM, access the Fans page, and verify if the fan speed is too high. If yes, adjust the fan speed mode or fan speed level.

3.     If the issue persists, contact Technical Support.

Message text

Exceeded the upper minor threshold.---Current reading:$1---Threshold reading:$2

Variable fields

$1: Current reading of the temperature sensor.

$2: Value of the minor overtemperature alarm threshold.

Severity level

Minor

Example

Exceeded the upper minor threshold.---Current reading:100---Threshold reading:80

Impact

Performance degradation and unstable operation might occur on the device components if the temperature is too high.

If the temperature does not decrease and the alarm persists, it might result in further temperature rise and generate major-level alarms. Therefore, it is important to detect potential issues that might lead to high temperature alarms as early as possible in order to avoid problem escalation.

Cause

High ambient temperature, blockage of air intake or exhaust, and low fan speed.

Recommended action

1.     Verify that the temperature of the equipment room is as required.

2.     Verify that the server's air inlet and outlet are not blocked.

3.     Log in to HDM, access the Fans page, and verify that all the fans are operating correctly, and the fan speed is not too low. If the fan speed is low, adjust the fan speed mode or fan speed level.

4.     If the issue persists, contact Technical Support.

Message text

Exceeded the upper major threshold.---Current reading:$1---Threshold reading:$2

Variable fields

$1: Current reading of the temperature sensor.

$2: Value of the major overtemperature alarm threshold.

Severity level

Major

Example

Exceeded the upper major threshold.---Current reading:100---Threshold reading:85

Impact

Performance degradation and unstable operation might occur on the device components if the temperature is too high.

If the temperature does not decrease and the alarm persists, it might result in further temperature rise and generate critical-level alarms. Therefore, it is important to detect potential issues that might lead to high temperature alarms as early as possible in order to avoid problem escalation.

Cause

High ambient temperature, blocked air intake or exhaust, and low fan speed.

Recommended action

1.     Verify that the temperature of the equipment room is as required.

2.     Verify that the server's air inlet and outlet are not blocked.

3.     Log in to HDM, access the Fans page, and verify that all the fans are operating correctly, and the fan speed is not too low. If the fan speed is low, adjust the fan speed mode or fan speed level.

4.     If the issue persists, contact Technical Support.

Message text

Exceeded the upper critical threshold.---Current reading:$1---Threshold reading:$2

Variable fields

$1: Current reading of the temperature sensor.

$2: Value of the critical overtemperature alarm threshold.

Severity level

Critical

Example

Exceeded the upper critical threshold.---Current reading:100---Threshold reading:90

Impact

Operating devices in high-temperature environments can reduce device performance, impact device lifespan, increase energy consumption, disrupt business operations, and cause system crashes.

Cause

High ambient temperature, blocked air intake or exhaust, and low fan speed.

Recommended action

1.     Verify that the temperature of the equipment room is as required.

2.     Verify that the server's air inlet and outlet are not blocked.

3.     Log in to HDM, access the Fans page, and verify that all the fans are operating correctly, and the fan speed is not too low. If the fan speed is low, adjust the fan speed mode or fan speed level.

4.     If the issue persists, contact Technical Support.

Message text

Abnormal Temperature---GPU Card Temperature Error---Register location:$1--- GPU location:$2

Variable fields

$1: State register.

$2: GPU slot number.

Severity level

Major

Example

Abnormal Temperature---GPU Card Temperature Error---Register location:0x6--- GPU location:11

Impact

Cause

Recommended action

1.     Verify that the temperature of the equipment room is as required.

2.     Verify that the server's air inlet and outlet are not blocked.

3.     Log in to HDM, access the Fans page, and verify that all the fans are operating correctly, and the fan speed is not too low. If the fan speed is low, adjust the fan speed mode or fan speed level.

4.     If the issue persists, contact Technical Support.

Message text

State Asserted

Variable fields

N/A

Severity level

Critical

Example

State Asserted

Impact

Performance degradation and unstable operation might occur on the device components if the voltage is too high.

Cause

Overvoltage was detected on the system board. To locate the alarm triggering component, see the sensor name on the Event Log page from the HDM Web interface.

Recommended action

1.     Power off and then restart the server.

2.     If the issue persists, contact Technical Support.

Message text

Dropped below the lower major threshold.---Current reading:$1---Threshold reading:$2

Variable fields

$1: Current value of the total input voltage.

$2: Lower major voltage alarm threshold.

Severity level

Major

Example

Dropped below the lower major threshold.---Current reading:2.58---Threshold reading:2.60

Impact

Performance degradation and unstable operation might occur on the device components if the voltage is too low.

Cause

Abnormal board voltage.

Recommended action

1.     Verify that the external power supply is operating correctly.

2.     Log in to HDM and verify that the power supply is operating correctly.

3.     Power off and then restart the server.

4.     If the issue persists, contact Technical Support.

Message text

Exceeded the upper major threshold.---Current reading:$1---Threshold reading:$2

Variable fields

$1: Current value of the total input voltage.

$2: Upper major voltage alarm threshold.

Severity level

Major

Example

Exceeded the upper major threshold.---Current reading:2.58---Threshold reading:2.56

Impact

Performance degradation and unstable operation might occur on the device components if the voltage is too low.

Cause

Abnormal board voltage.

Recommended action

1.     Verify that the external power supply is operating correctly.

2.     Log in to HDM and verify that the power supply is operating correctly.

3.     Power off and then restart the server.

4.     If the issue persists, contact Technical Support.

Message text

State Asserted

Variable fields

N/A

Severity level

Critical

Example

State Asserted

Impact

The system might be shut down and powered off.

Cause

Overcurrent was detected for a component on the system board.

Recommended action

1.     Log in to HDM, access the Logs page, and verify that no alarm is present for the power supply or system board.

2.     Verify that power can be supplied to the server correctly and the voltage is within the normal range.

3.     If the issue persists, contact Technical Support.

Message text

Transition to Running.

Variable fields

N/A

Severity level

Info

Example

Transition to Running

Impact

No negative impact.

Cause

The fan is operating correctly.

Recommended action

1.     Verify that the fan is present.

2.     Re-install the fan.

3.     If the issue persists, contact Technical Support.

Message text

Fully Redundant.

Variable fields

N/A

Severity level

Major

Example

Fully Redundant

Impact

Depending on the severity of redundancy loss, it might affect the normal heat dissipation of the server.

Cause

A fan redundancy error is present because a fan is absent, or a fan was removed or failed.

Recommended action

1.     Re-install the removed fans.

2.     Remove and re-install the fans, and make sure the fans are in good contact.

3.     If a fan status sensor reports an error, replace the faulty fan.

4.     If the issue persists, contact Technical Support.

Message text

Non-redundant:Sufficient Resources from Redundant

Variable fields

N/A

Severity level

Major

Example

Non-redundant:Sufficient Resources from Redundant

Impact

This issue does not affect system heat dissipation.

Cause

The fan is invalid or is absent.

Recommended action

1.     Re-install the removed fans.

2.     Remove and re-install the fans, and make sure the fans are in good contact.

3.     If a fan status sensor reports an error, replace the faulty fan.

4.     If the issue persists, contact Technical Support.

Message text

Transition to Off Line.

Variable fields

N/A

Severity level

Info

Example

Transition to Off Line

Impact

This affects system heat dissipation and reduces the performance of the system board components.

Cause

The fan module has been unplugged or the fan module and the system board have poor contact.

Recommended action

1.     Re-install the removed fans.

2.     Remove and re-install the fans, and make sure the fans are in good contact.

3.     If a fan status sensor reports an error, replace the faulty fan.

4.     If the issue persists, contact Technical Support.

Message text

Non-redundant:Insufficient Resources

Variable fields

N/A

Severity level

Major

Example

Non-redundant:Insufficient Resources

Impact

This affects system heat dissipation, causing the system to overheat and automatically shut down.

Cause

The fan is invalid or is absent.

Recommended action

1.     Re-install the removed fans.

2.     If a fan status sensor reports an error, replace the faulty fan.

3.     Remove and re-install the fans, and make sure the fans are in good contact.

4.     If the issue persists, contact Technical Support.

Message text

Transition to Degraded.

Variable fields

N/A

Severity level

Major

Example

Transition to Degraded

Impact

This affects system heat dissipation and reduces the performance of the system board components.

Cause

The fan speed is abnormal.

Recommended action

1.     Log in to HDM and view the fan speed. If the speed is low, a fan might have aged. If the speed is almost zero, a fan might be blocked or have failed.

2.     Verify that the fans are not blocked.

3.     If a fan status sensor reports an error, replace the faulty fan.

4.     Replace the aged fans.

5.     If the issue persists, contact Technical Support.

Message text

Install Error.

Variable fields

N/A

Severity level

Minor

Example

Install Error

Impact

The system might fail to be powered on.

Cause

The fan was incorrectly installed.

Recommended action

1.     Verify that the fans are installed as instructed. For more information about the installation principles, see the user guide for the server.

2.     If the issue persists, contact Technical Support.

Event code

0x0a5000de

Message text

Liquid Cooler is not present.

Variable fields

N/A

Severity level

Minor

Example

Liquid Cooler is not present

Impact

This affects system heat dissipation and system performance.

Cause

The liquid-cooled module is installed incorrectly. This message is available only for liquid-cooled servers.

Recommended action

1.     Verify that the liquid-cooled module is present.

2.     Verify that the liquid leakage sensor is installed correctly.

3.     Replace the liquid-cooled module.

4.     If the issue persists, contact Technical Support.

Event code

0x0a6000de

Message text

Liquid Cooler is leakage.

Variable fields

N/A

Severity level

Critical

Example

Liquid Cooler is leakage

Impact

This might cause system crashes.

Cause

Liquid leakage occurred to the liquid-cooled module. This message is available only for liquid-cooled servers.

Recommended action

1.     Verify that the liquid-cooled module is operating correctly and liquid leakage does not occur.

2.     Replace the liquid-cooled module.

3.     If the issue persists, contact Technical Support.

Event code

0x0a7000de

Message text

Liquid Cooler is leakage.

Variable fields

N/A

Severity level

Critical

Example

Liquid Cooler is leakage

Impact

This might cause system crashes.

Cause

Liquid leakage occurred to the liquid-cooled module. This message is available only for liquid-cooled servers.

Recommended action

1.     Verify that the liquid-cooled module is operating correctly and liquid leakage does not occur.

2.     Replace the liquid-cooled module.

3.     If the issue persists, contact Technical Support.

Message text

General Chassis Intrusion.

Variable fields

N/A

Severity level

Minor

Example

General Chassis Intrusion

Impact

No negative impact.

Cause

The access panel was removed from the server.

Recommended action

1.     Verify that the access panel was removed.

2.     Verify that the access panel is installed correctly.

3.     Verify that the chassis-open alarm module has a good contact with the chassis ear.

4.     If the issue persists, contact Technical Support.

Message text

LAN Leash Lost.

Variable fields

N/A

Severity level

Info

Example

LAN Leash Lost

Impact

No negative impact.

Cause

The NCSI channel detection of BMC detected that the network is disconnected at the physical layer.

Recommended action

1.     Verify that an Ethernet adapter was disabled in the OS.

2.     Verify that the message was reported on a power-on or power-off operation.

3.     Verify that the Ethernet cable is connected correctly to the shared network port.

4.     Disable the shared network port if the shared network port is not necessary.

5.     If the issue persists, contact Technical Support.

Message text

Intel:

$1 $2 err---Socket $3

AMD:

GMI/xGMI err---Socket$1 Die$2 LinkID$3

Variable fields

·     Intel:

¡     $1: Signal type. Options include MSMI and CATERR.

¡     $2: Error type. Options include IERR and MCERR.

¡     $3: CPU number.

·     AMD:

¡     $1: CPU number.

¡     $2: Die number.

¡     $3: Link number.

Severity level

Critical

Example

Intel:

CATERR IERR err---Socket 1

AMD:

GMI/xGMI err---Socket1 Die1 LinkID1

Impact

This can cause system crashes. By default, the system will then automatically restart.

Cause

A processor internal error, such as a Package Control Unit (PCU) uncorrectable error, occurred.

Recommended action

1.     Upgrade the BIOS and HDM firmware to the latest version.

2.     Review logs to troubleshoot the issue as instructed.

3.     If the issue persists, contact Technical Support.

Message text

State Asserted.

Variable fields

N/A

Severity level

Major

Example

State Asserted

Impact

This might cause system crashes.

Cause

A processor was overheated.

Recommended action

1.     Log in to HDM and verify that the fans are operating correctly.

2.     If low-speed alarms are present, re-install or replace the faulty fans.

3.     View resource summary to identify system service loads. If the system is overloaded, close uncritical services to reduce service loads.

4.     Verify that the ambient temperature of the server is within the normal operation range.

5.     Verify that the air inlets and outlets are not blocked.

6.     Power off the server, and verify that the processor heatsink has a good contact. Smear the thermal grease onto the heatsink, install the heatsink, and power on the server.

7.     If the issue persists, contact Technical Support.

Message text

CPU Critical Temperature.

Variable fields

N/A

Severity level

Critical

Example

CPU Critical Temperature

Impact

This might cause system crashes.

Cause

The temperature of a processor exceeded the critical overtemperature alarm threshold.

Recommended action

1.     Log in to HDM and verify that the fans are operating correctly.

2.     If a low-speed alarm is present, re-install or replace the faulty fan.

3.     View resource summary to identify system service loads. If the system is overloaded, close uncritical services to reduce service loads.

4.     Verify that the temperature in the equipment room is within the normal range.

5.     Verify that the air inlets and outlets are not blocked.

6.     Power off the server, and verify that the processor heatsink has a good contact. Smear the thermal grease onto the heatsink, install the heatsink, and power on the server.

7.     If the issue persists, contact Technical Support.

Message text

Thermal Trip

Variable fields

N/A

Severity level

Critical

Example

Thermal Trip

Impact

This might cause system crashes.

Cause

A processor was overheated, which might cause system power-off.

Recommended action

1.     Log in to HDM and verify that all fans are operating correctly.

2.     If a low-speed alarm is present, re-install or replace the faulty fan.

3.     View resource summary to identify system service loads. If the system is overloaded, close uncritical services to reduce service loads.

4.     Verify that the temperature in the equipment room is within the normal range.

5.     Verify the air inlets and outlets are not blocked.

6.     Power off the server, and verify that the processor heatsink has a good contact. Smear the thermal grease onto the heatsink, install the heatsink, and power on the server.

7.     If the issue persists, contact Technical Support.

Message text

FRB1/BIST failure

Variable fields

N/A

Severity level

Minor

Example

FRB1/BIST failure

Impact

It might result in the operating system failing to start up normally and hardware being downgraded.

Cause

The processor core BIST failed.

Recommended action

1.     Power off and power on the server to clear the alarm.

2.     If the issue persists, replace the processors.

3.     If the issue persists, contact Technical Support.

Message text

Processor Presence detected.

Variable fields

N/A

Severity level

Info/Critical

Example

Processor Presence detected

Impact

The system cannot start up if the primary processor is absent.

Cause

The system detected the absence or misinstallation of the primary processor.

Recommended action

1.     Verify that the primary processor is installed correctly.

2.     Replace the faulty primary processor.

3.     If the issue persists, contact Technical Support.

Message text

Processor Automatically Throttled---due to fan error.

Variable fields

N/A

Severity level

Minor

Example

Processor Automatically Throttled---due to fan error

Impact

CPU underclocking causes a decrease in system performance.

Cause

The processor was underclocked because a fan fails.

Recommended action

1.     Verify that the heat dissipation setting meets the requirements of the running services.

2.     Verify that the temperature in the equipment room is within the normal range and the air inlet and outlet are not blocked.

3.     Verify that the fans are not blocked and are operating correctly.

4.     Replace the faulty fans.

5.     If the issue persists, contact Technical Support.

Message text

Machine Check Exception---$1---$2---Location: Socket:$3

Variable fields

$1: Error type.

$2: Indicates whether the error occurred during this system boot. Options include:

¡     Current Boot Error.

¡     Last Boot Error.

$3: CPU number.

Severity level

Critical

Example

Machine Check Exception---SMN---Last Boot Error---Location: Socket:1

Impact

The system stops responding.

Cause

An uncorrectable error occurred.

Recommended action

1.     Upgrade the BIOS and HDM firmware to the latest version.

2.     Review event logs to locate the failed processor or other components.

3.     Reboot the device.

4.     Verify that the processor and memories are operating correctly.

5.     If the issue persists, contact Technical Support.

Message text

CPU $1 triggered an uncorrectable error.

Variable fields

$1: CPU number.

Severity level

Critical

Example

CPU 1 triggered an uncorrectable error.

Impact

The system stops responding.

Cause

An IERR or MCERR error occurred. The BMC diagnostic result is "CPU uncorrectable error."

Recommended action

1.     Upgrade the BIOS and HDM firmware to the latest version.

2.     Review event logs to locate the failed memory, PCIe module, or processor.

3.     Power off the server, and replace the failed component.

4.     Replace the system board.

5.     If the issue persists, contact Technical Support.

Message text

Machine Check Error ---Location: Processor:$1 ---IIO Stack number:$2 ---$3---$4

Variable fields

$1: CPU number.

$2: IIO Stack number (IIO port number).

$3: Current boot or last boot.

$4: Error type.

Severity level

Critical

Example

Machine Check Exception---Location: Processor:1 ---IIO Stack number:1 --Last Boot---ITC Error:ECC uncorrectable error in the ITC dat_dword RF

Impact

The system stops responding.

Cause

Internal uncorrectable errors were detected on the processor, such as VT-d errors, ITC errors, OTC errors, DMA errors, IRP errors, and Ring errors.

This error also triggers other alarms.

Recommended action

1.     Review event logs.

2.     If the issue persists, contact Technical Support.

Message text

Machine Check Error ---CPU core errors --- ErrorType:$1---Location: Processor:$2  core MCA bank: $(3)

Variable fields

$1: General error type.

$2: CPU number.

$3: Error type.

Severity level

Critical

Example

Machine Check Exception---CPU core errors--ErrorType:Unknow--Fatal Error--Last Boot---Location: Processor:1 core MCA bank: instruction fetch unit

Impact

The system stops responding.

Cause

Internal uncorrectable errors were detected on the processor, such as CPU core errors.

Recommended action

1.     Review event logs.

2.     If the issue persists, contact Technical Support.

Message text

CPU $1 triggered a correctable error.

Variable fields

$1: CPU number.

Severity level

Minor

Example

CPU 1 triggered a correctable error.

Impact

No negative impact.

Cause

An IERR or MCERR error occurred. The BMC diagnostic result is "CPU uncorrectable error."

Recommended action

1.     Upgrade the BIOS and HDM firmware to the latest version.

2.     Review event logs to locate the failed CPU or other components.

3.     Power off the server, and replace the failed component.

4.     Replace the system board.

5.     If the issue persists, contact Technical Support.

Message text

Correctable Machine Check Error ---location: Processor:$1 ---IIO Stack number:$2 ---$3---$4

Variable fields

$1: CPU number.

$2: IIO Stack number.

$3: Current boot or last boot.

$4: Error type.

Severity level

Minor

Example

Correctable Machine Check Error---Location: Processor:1 ---IIO Stack number:1 --Last Boot---DMA Error:Descriptor Count Error

Impact

No negative impact.

Cause

Internal correctable errors were detected on the processor, such as VT-d errors, ITC errors, OTC errors, DMA errors, IRP errors, and Ring errors.

Recommended action

1.     Review event logs and troubleshoot the present errors.

2.     If the issue persists, contact Technical Support.

Message text

Correctable Machine Check Error ---CPU UPI errors ---Location: Processor:$1  UPI port number:$2

Variable fields

$1: CPU number.

$2: UPI port.

Severity level

Minor

Example

Correctable Machine Check Error---CPU UPI errors---Location: Processor:2 UPI port number:0x1

Impact

No negative impact.

Cause

Internal correctable errors were detected on the processor, such as CPU UPI errors.

Recommended action

1.     Review event logs and troubleshoot the present errors.

2.     If the issue persists, contact Technical Support.

Message text

Correctable Machine Check Error ---IOH UPI errors ---Location: Processor:$1  UPI port number:$2 ---Coherent interface (IRP) local group error code:$3

Variable fields

$1: CPU number.

$2: UPI port.

$3: Error code.

Severity level

Minor

Example

Correctable Machine Check Error---IOH UPI errors---Location: Processor:1 UPI port number:0x1---Coherent interface (IRP) local group error code:0x6

Impact

No negative impact.

Cause

Internal correctable errors were detected on the processor, such as IOH UPI errors.

Recommended action

1.     Review event logs and troubleshoot the present errors.

2.     If the issue persists, contact Technical Support.

Message text

Correctable Machine Check Error ---IOH core errors ---Location:Processor:$1  ---IIO core local group error code:$2

Variable fields

$1: CPU number.

$2: Error code.

Severity level

Minor

Example

Correctable Machine Check Error---IOH core errors---Location: Processor:2---IIO core local group error code:0x6

Impact

No negative impact.

Cause

Internal correctable errors were detected on the processor, such as IOH core errors.

Recommended action

1.     Review event logs and troubleshoot the present errors.

2.     If the issue persists, contact Technical Support.

Message text

Correctable Machine Check Error ---VT-d errors ---Location: Processor:$1  ---VT-d local group error code:$2

Variable fields

$1: CPU number.

$2: Error code.

Severity level

Minor

Example

Correctable Machine Check Error---VT-d errors---Location: Processor:2---VT-d local group error code:0x6

Impact

No negative impact.

Cause

Internal correctable errors were detected on the processor, such as VT-d errors.

Recommended action

1.     Review event logs and troubleshoot the present errors.

2.     If the issue persists, contact Technical Support.

Message text

Correctable Machine Check Error ---CPU core errors ---ErrorType:$1 ---Location: Processor:$2  core MCA bank: $3

Variable fields

$1: General error type.

$2: CPU number.

$3: Error type.

Severity level

Minor

Example

Correctable Machine Check Error---CPU core errors--ErrorType:Unknow--Current Boot---Location: Processor:2 core MCA bank: mid level cache

Impact

No negative impact.

Cause

Internal correctable errors were detected on the processor, such as CPU core errors.

Recommended action

1.     Review event logs and troubleshoot the present errors.

2.     If the issue persists, contact Technical Support.

Message text

Correctable Machine Check Error ---Cbo error--location: CPU core ID:$1  thread ID:$2 caching agent MCA bank: Cbo$3

Variable fields

$1: Core number.

$2: Thread number.

$3: Cbo number.

Severity level

Minor

Example

Correctable Machine Check Error---Cbo error---Location: CPU core ID:0x0 thread ID:0x0 caching agent MCA bank: Cbo0

Impact

No negative impact.

Cause

Internal correctable errors were detected on the processor, such as Cbo error.

Recommended action

1.     Review event logs and troubleshoot the present errors.

2.     If the issue persists, contact Technical Support.

Message text

Configuration Error---System is operating in KTI Link Slow Speed Mode- Location:CPU:$1

Variable fields

$1: Core number.

Severity level

Minor

Example

Configuration Error---System is operating in KTI Link Slow Speed Mode- Location:CPU:1

Impact

No negative impact.

Cause

The system is operating in Keizer Technology Interconnect (KTI) low speed mode.

Recommended action

1.     Verify that the processors are installed correctly as instructed. For more information about the installation principles, see the user guide for the server.

2.     If the issue persists, contact Technical Support.

Message text

Fully Redundant

Variable fields

N/A

Severity level

Info

Example

Fully Redundant

Impact

No negative impact.

Cause

Power redundancy.

Recommended action

No action is required.

Message text

Fully Redundant

Variable fields

N/A

Severity level

Major

Example

Fully Redundant

Impact

Power redundancy failure reduces the reliability of device power supply.

Cause

The power supply redundancy was lost.

Recommended action

1.     Verify that the environment is normal.

2.     Verify that no power supply is removed.

3.     Verify that the power supplies have good contacts with the power cords.

4.     Verify that all power supplies are operating correctly.

5.     If the issue persists, contact Technical Support.

Message text

Presence detected.

Variable fields

N/A

Severity level

Info

Example

Presence detected

Impact

No negative impact.

Cause

0x080000de: When the power supply is detected as being inserted, this event is triggered, indicating a transition from the power supply not being in place to being in place.

0x080000df: When the power supply is detected as being removed, this event is cleared, indicating a transition from the power supply being in place to not being in place.

Recommended action

1.     Verify that the power module is not removed.

2.     Verify that the power module is installed correctly.

3.     If the issue persists, contact Technical Support.

Message text

Redundancy Lost.

Variable fields

N/A

Severity level

Major

Example

Redundancy Lost

Impact

Power redundancy failure reduces the reliability of device power supply.

Cause

The power supply redundancy was lost.

Recommended action

1.     Verify that the environment is normal.

2.     Verify that no power supply is removed.

3.     Verify that the power supplies have good contacts with the power cords.

4.     Verify that all power supplies are operating correctly.

5.     If the issue persists, contact Technical Support.

Message text

Power Supply Failure detected.

Variable fields

N/A

Severity level

Major

Example

Power Supply Failure detected

Impact

It affects system power supply and may result in abnormal system power-off.

Cause

A power supply fault was detected.

Recommended action

1.     Verify that the power supply fans are operating correctly.

2.     Re-install the power supplies.

3.     Verify that the input voltage of the power supply is normal.

4.     Replace the faulty power supply.

5.     If the issue persists, contact Technical Support.

Message text

Power Supply Predictive Failure---PSU Self Check Failed---Id: $1

Variable fields

$1: Number of a power supply.

Severity level

Minor

Example

Power Supply Predictive Failure---PSU Self Check Failed---Id: 1

Impact

The power supply may have malfunctions that affect system power supply.

Cause

Power supply self-check failed.

Recommended action

1.     Verify that the power supply LED is operating correctly.

2.     Verify that the power supply fans are operating correctly.

3.     Verify that the power supply is compatible with the server.

4.     If the issue persists, contact Technical Support.

Message text

Power Supply Predictive Failure.

Variable fields

N/A

Severity level

Minor

Example

Power Supply Predictive Failure

Impact

The power supply may have malfunctions that affect system power supply.

Cause

A predictive power supply fault is detected.

Recommended action

1.     Verify that the power supply LED is operating correctly.

2.     Verify that the power supply fans are operating correctly.

3.     Verify that the input voltage of the power supply is normal.

4.     If the issue persists, contact Technical Support.

Message text

Power Supply input lost (AC/DC).

Variable fields

N/A

Severity level

Major

Example

Power Supply input lost (AC/DC)

Impact

It may cause the server to power off abnormally.

Cause

The AC power cable of the power supply is unplugged or the AC input is abnormal.

Recommended action

1.     Verify that all power cords are not damaged and are correctly connected.

2.     Verify that all power supplies are correctly installed.

3.     Verify that the power supply fans are operating correctly.

4.     Verify that the power input is normal.

5.     If the issue persists, contact Technical Support.

Message text

Power Supply input lost or out-of-range.

Variable fields

N/A

Severity level

Major

Example

Power Supply input out-of-range

Impact

This might cause the server to be powered off abnormally.

Cause

The input voltage of the power supply exceeded the rated range.

Recommended action

1.     Verify that the power supply has not been cut off manually.

2.     Verify that the input voltage of the power supply is normal.

3.     Verify that the power cords and power modules are installed correctly.

4.     Re-install the power supplies. Make sure the power supplies have a good contact.

5.     Verify that the power supply fans are operating correctly.

6.     If the issue persists, contact Technical Support.

Message text

Power Supply input out-of-range - but present.

Variable fields

N/A

Severity level

Major

Example

Power Supply input out-of-range - but present

Impact

Abnormal power input beyond the supported range might cause the server to be powered off.

Cause

The input voltage was too high.

Recommended action

1.     Verify that the input voltage of the power supply is normal.

2.     Verify that the power cords and power modules are installed correctly.

3.     Re-install the power supplies. Make sure the power supplies have a good contact.

4.     Verify that the power supply fans are operating correctly.

5.     If the issue persists, contact Technical Support.

Message text

Configuration error ---Vendor mismatch.

Variable fields

N/A

Severity level

Minor

Example

Configuration error ---Vendor mismatch

Impact

An unknown risk exists due to the use of non-originally certified components.

Cause

Non-originally certified power supplies are installed.

Recommended action

1.     Verify that all power supplies are compatible with the server.

2.     If the issue persists, contact Technical Support.

Message text

Configuration error---Power supply rating mismatch:PSU$1,POUT:$2

Variable fields

$1: Power supply ID.

$2: Output power of the power supply.

Severity level

Minor

Example

Configuration error---Power supply rating mismatch:PSU1,POUT:2000

Impact

This might result in unstable power supply and abnormal system shutdown.

Cause

Originally certified power supplies are installed, but the models of the two power supplies do not match.

Recommended action

1.     If the rated power of the installed power supplies is consistent, remove and install the power supplies in sequence.

2.     If the rated power of the installed power supplies is inconsistent, replace the power supplies to make sure they are of the same rated power.

3.     If the issue persists, contact Technical Support.

Message text

Exceeded the upper minor threshold. ---Current reading:$1---Threshold reading:$2

Variable fields

$1: Current reading.

$2: Total power alarm threshold.

Severity level

Minor

Example

Exceeded the upper minor threshold.---Current reading:2030---Threshold reading:493

Impact

The power exceeded the upper limit and will cause system shutdown.

Cause

The power exceeded the threshold.

Recommended action

1.     Log in to HDM and verify that the alarm threshold is appropriate.

2.     Log in to HDM and verify that the total power is not too high.

3.     Verify that the total power of the power supplies can meet service requirements.

4.     If the issue persists, contact Technical Support.

Message text

Power Supply Inactive/standby state.

Variable fields

N/A

Severity level

Info

Example

Power Supply Inactive/standby state

Impact

No negative impact.

Cause

A power supply exited the cold standby state.

If power redundancy is configured, a standby power supply automatically exits the cold standby state and supplies power to the server when the system power consumption is too high.

Recommended action

1.     Log in to HDM and verify if the total power of the server is too high.

2.     If the issue persists, contact Technical Support.

Message text

Interlock Power Down

Variable fields

N/A

Severity level

Critical

Example

Interlock Power Down

Impact

This might lead to a system crash.

Cause

Fluctuations in the power grid can cause an AC momentary interruption.

Recommended action

1.     Verify that the external power supply environment of the server is in normal state.

2.     Press and hold the power button until the UID LED stops flashing.

3.     If the issue persists, contact Technical Support.

Event code

0x08a000de

Message text

Power Supply Pwok abnormal

Variable fields

N/A

Severity level

Major

Example

Power Supply Pwok abnormal

Impact

This might affect the system power supply and eventually leads to system crashes.

Cause

Power output is normal but the Pwok signal on the system board is abnormal and the health LED is on.

Recommended action

1.     Verify that the power input is correct.

2.     Verify that the system board is in operating correctly.

3.     Verify that power supplies are connected correctly to the system board.

4.     If the issue persists, contact Technical Support.

Message text

Power limit is exceeded over correction time limit---Current Power: $1W.

Variable fields

$1: Current power threshold value.

Severity level

Minor

Example

Power limit is exceeded over correction time limit---Current Power: 2000W.

Impact

The specified action will be taken if power capping fails.

Cause

This alarm is generated if the power exceeds the cap value for a period of time.

Recommended action

1.     Adjust the power cap value or the server work load.

2.     If the issue persists, contact Technical Support.

Message text

Power limit is exceeded over correction time limit---GPU Current Power: $1W.

Variable fields

$1: Configured power threshold value.

Severity level

Minor

Example

Power limit is exceeded over correction time limit---GPU Current Power: 2000W.

Impact

The specified action will be taken if power capping fails.

Cause

This alarm is generated if the power exceeds the cap value for a period of time.

Recommended action

1.     Adjust the power cap value or the GPU work load.

2.     If the issue persists, contact Technical Support.

Message text

Correctable ECC or other correctable memory error--$1-Location:CPU:$2 MEM CTRL:$3 CH:$4 DIMM:$5 $6

Variable fields

$1: Indicates whether the error occurred during this system boot. Options include:

·     Current Boot Error.

·     Last Boot Error.

$2: CPU number.

$3: Memory controller number.

$4: Channel number.

$5: DIMM number.

$6: DIMM mark.

Severity level

Minor

Example

Correctable ECC or other correctable memory error---Current Boot Error-Location:CPU:1 MEM CTRL:1 CH:1 DIMM:0 A1

Impact

No negative impact.

Cause

A correctable memory error occurred.

Recommended action

No action is required.

Message text

CPU $1 $2 triggered a correctable error

Variable fields

$1: CPU number.

$2: DIMM number.

Severity level

Minor

Example

CPU 1 A0 triggered a correctable error

Impact

No negative impact.

Cause

An IERR or MCERR error was triggered. The error was identified by HDM as a correctable error.

Recommended action

No action is required.

Message text

Uncorrectable ECC or other uncorrectable memory error--$1-Location:CPU:$2 MEM CTRL:$3 CH:$4 DIMM:$5 $6

Variable fields

$1: Indicates whether the error occurred during this system boot. Options include:

·     Current Boot Error.

·     Last Boot Error.

$2: CPU number.

$3: Memory controller number.

$4: Channel number.

$5: DIMM number.

$6: DIMM mark.

Severity level

Major

Example

Uncorrectable ECC or other uncorrectable memory error---Current Boot Error-Location:CPU:1 MEM CTRL:1 CH:1 DIMM:0 A1

Impact

It can cause the system to stop sending responses, unless the memory is in certain RAS modes, such as mirror or MCA recovery.

Cause

A non-correctable (multiple bit flip) ECC error has occurred.

Recommended action

1.     Verify that the ambient temperature and humidity are as required.

2.     Re-install the DIMM. Verify that the gold contacts on the DIMM are not contaminated and the DIMM slot does not contain any foreign objects.

3.     Verify that the pins in the processor socket are not bent. If any pins are bent, replace the system board.

4.     Replace the DIMM.

5.     If the issue persists, contact Technical Support.

Message text

CPU$1 $2 triggered an uncorrectable error

Variable fields

$1: CPU number.

$2: DIMM number.

Severity level

Major

Example

CPU1 A0 triggered an uncorrectable error

Impact

It can cause the system to restart or stop sending responses.

Cause

An IERR or MCERR error was triggered. The error was identified by BMC as a memory uncorrectable error.

Recommended action

1.     Verify that the ambient temperature and humidity are as required.

2.     Re-install the DIMM. Verify that the gold contacts on the DIMM are not contaminated and the DIMM slot does not contain any foreign objects.

3.     Verify that the pins in the CPU socket are not bent. If any pins are bent, replace the system board.

4.     Replace the DIMM.

5.     If the issue persists, contact Technical Support.

Message text

Parity---$1---Location: Location:CPU:$2 MEM CTRL:$3  CH:$4 DIMM:$5 $6

Variable fields

$1: Indicates whether the error occurred during this system boot. Options include:

·     Current Boot Error.

·     Last Boot Error.

$2: CPU number.

$3: Memory controller number.

$4: Channel number.

$5: DIMM number.

$6: DIMM mark.

Severity level

Minor

Example

Parity---Current Boot Error-Location:CPU:1 MEM CTRL:1 CH:1 DIMM:0 A0

Impact

No negative impact.

Cause

This error message is generated when a failure occurs in data parity on the command/address lines while the system is reading the memory cell data, resulting in abnormal data access to the memory.

Recommended action

1.     Verify that the ambient temperature and humidity are as required.

2.     Re-install the DIMM. Verify that the gold contacts on the DIMM are not contaminated and the DIMM slot does not contain any foreign objects.

3.     Verify that the pins in the processor socket are not bent. If any pins are bent, replace the system board.

4.     Replace the DIMM.

5.     If the issue persists, contact Technical Support.

Message text

Parity---Memory Training Faulty Part Tracking Uncorrectable Error-Location:CPU:$1 CH:$2 DIMM:$3 Rank:$4

Variable fields

$1: CPU number.

$2: Channel number.

$3: DIMM number.

$4: Rank number.

Severity level

Minor

Example

Parity---Memory Training Faulty Part Tracking Uncorrectable Error-Location:CPU:2 CH:1 DIMM:B1 Rank:0

Impact

No negative impact.

Cause

A Faulty Parts Tracking error occurred because of an uncorrectable error.

Recommended action

1.     Verify that the ambient temperature and humidity are as required.

2.     Re-install the DIMM. Verify that the gold contacts on the DIMM are not contaminated and the DIMM slot does not contain any foreign objects.

3.     Verify that the pins in the processor socket are not bent. If any pins are bent, replace the system board.

4.     Replace the DIMM.

5.     If the issue persists, contact Technical Support.

Message text

Parity---Memory Sense Amp Training Error-Location:CPU:$1 CH:$2 DIMM:$3 Rank:$4

Variable fields

$1: CPU number.

$2: Channel number.

$3: DIMM number.

$4: Rank number.

Severity level

Minor

Example

Parity---Memory Sense Amp Training Error-Location:CPU:1 CH:1 DIMM:A1 Rank:0

Impact

This might lead to a decrease in system performance.

Cause

Sense Amp Training failed because a voltage input error occurred.

Recommended action

1.     Verify that the ambient temperature and humidity are as required.

2.     Re-install the DIMM. Verify that the gold contacts on the DIMM are not contaminated and the DIMM slot does not contain any foreign objects.

3.     Verify that the pins in the processor socket are not bent. If any pins are bent, replace the system board.

4.     Replace the DIMM.