ALM-135462996 hwBoardFail

Description

The board partially failed. (EntPhysicalIndex=[EntPhysicalIndex], EntPhysicalName=[EntPhysicalName], EntityType=[EntityType], EntityTrapFaultID=[EntityTrapFaultID], Reason=[Reason])

The card experienced a partial failure.

Attribute

AlarmID	Alarm OID	Alarm Severity	Alarm Type
135462996	1.3.6.1.4.1.2011.5.25.219.2.2.3	Critical	Equipment alarm

Parameters

Name	Meaning
EntPhysicalIndex	Entity index.
EntPhysicalName	Entity name.
EntityType	Entity type.
EntityTrapFaultID	Alarm cause.
Reason

Impact on the System

Cause 1: Power supply abnormal.
Services on the card may be affected or even interrupted.
Cause 2: A voltage drop occurred on the board.
Services on the card may be affected or even interrupted.
Cause 3: The serial management bus of the board malfunctions.
Services on the card may be affected or even interrupted.
Cause 6: Board RTC fault.
Services on the card may be affected or even interrupted.
Cause 8: The fan is not full.
As a result, fan information cannot be obtained.
Cause 11: A data channel fault occurred on the forwarding engine.
Services on the card may be affected or even interrupted.
Cause 12: The forwarding engine failed.
Services on the card may be affected or even interrupted.
Cause 13: Inter-card broadcast traffic failed to be forwarded.
Services on the card may be affected or even interrupted.
Cause 15: Fabric interface input or output bandwidth usage exceeded 90% continuously.
Services on the card may be affected or even interrupted.
Cause 16: Ingress clock signals channel failed.
Services on the card may be affected or even interrupted.
Cause 17: The sensor on the board was faulty.
Services on the card may be affected or even interrupted.
Cause 18: Chip instability.
Services on the card may be affected or even interrupted.
Cause 19: Egress clock signals channel failed.
Services on the card may be affected or even interrupted.
Cause 20: A packet reassembly error occurred.
Services on the card may be affected or even interrupted.
Cause 21: Board CANBUS failed.
Services on the card may be affected or even interrupted.
Cause 23: Board cannot be powered on or powered off properly.
Services on the card may be affected or even interrupted.
Cause 24: EEPROM is abnormal.
The current services are not affected, but the services after the next startup of the board are affected.
Cause 25: The fan model does not match the device.
Services on the card may be affected or even interrupted.
Cause 26: The power supply model does not match the device.
Services on the card may be affected or even interrupted.
Cause 27: The PHY chip is abnormal.
Services on the card may be affected or even interrupted.
Cause 29: Board PLL instability.
Services on the card may be affected or even interrupted.
Cause 30: Phy instability.
Services on the card may be affected or even interrupted.
Cause 36: USB overcurrent occurred.
Services on the card may be affected or even interrupted.
Cause 37: IIC failed.
Services on the card may be affected or even interrupted.
Cause 38: LANSWITCH chip instability.
Services on the card may be affected or even interrupted.
Cause 39: The link of the XFI interface is faulty.
Services on the card may be affected or even interrupted.
Cause 40: A CRC error occurred on the XFI interface.
Services on the card may be affected or even interrupted.
Cause 43: The memory size is different from the standard configuration.
Services on the card may be affected or even interrupted.
Cause 44: Flash memory failed.
Services on the card may be affected or even interrupted.
Cause 50: CMU on the MPU is not registered.
Services on the card may be affected or even interrupted.
Cause 51: The 38M clock fails.
Services on the card may be affected or even interrupted.
Cause 52: The 19M clock fails.
Services on the card may be affected or even interrupted.
Cause 53: The board clock fails.
Services on the card may be affected or even interrupted.
Cause 54: The PLLA inside the forwarding engine is not ready.
Services on the card may be affected or even interrupted.
Cause 55: The Serdes on the board failed.
Services on the card may be affected or even interrupted.
Cause 56: An internal modular of the forwarding engine is abnormal.
Services on the card may be affected or even interrupted.
Cause 58: The active and standby MPUs cannot communicate with each other.
Services on the card may be affected or even interrupted.
Cause 59: The board type cannot be identified.
Services on the card may be affected or even interrupted.
Cause 60: The board clock(156M) failed.
Services on the card may be affected or even interrupted.
Cause 65: Storage media is abnormal.
Services on the card may be affected or even interrupted.
Cause 70: CANBUS communications between the monitor chips failed.
Services on the card may be affected or even interrupted.
Cause 71: A DDR fault occurs on the board.
Services on the card may be affected or even interrupted.
Cause 72: The slot ID of the board fails to be checked.
Services on the card may be affected or even interrupted.
Cause 73: Access to the flash memory of the board fails.
Services on the card may be affected or even interrupted.
Cause 74: The FULLIN signal of the board is abnormal.
Services on the card may be affected or even interrupted.
Cause 75: The slot ID signal from the CANBUS is abnormal.
Services on the card may be affected or even interrupted.
Cause 76: A SerialCpldLocalbus fault occurs on the board.
Services on the card may be affected or even interrupted.
Cause 77: The micro switch of the board fails.
Services on the card may be affected or even interrupted.
Cause 78: The frequency synthesizer failed.
Services on the card may be affected or even interrupted.
Cause 80: A CPU fault occurred.
Services on the card may be affected or even interrupted.
Cause 82: A CPU-side CRC fault occurred.
Services on the card may be affected or even interrupted.
Cause 83: A PHY-side CRC fault occurred.
Services on the card may be affected or even interrupted.
Cause 84: The disk will soon become invalid.
Services on the card may be affected or even interrupted.
Cause 88: The Chip is failed.
Services on the card may be affected or even interrupted.
Cause 90: Overcurrent occurred on the board.
Services on the card may be affected or even interrupted.
Cause 91: The FPGA is abnormal.
Services on the card may be affected or even interrupted.
Cause 92: The sensor chip on the board was faulty.
Services on the card may be affected or even interrupted.
Cause 96: A HTM chip fault occurred.
Services on the card may be affected or even interrupted.
Cause 99: Failed to check the voltage of the board.
Services on the card may be affected or even interrupted.
Cause 102: The currently used hard disk is not certified by Huawei.
Services on the card may be affected or even interrupted.
Cause 103: The hard disk was pulled out.
Services on the card may be affected or even interrupted.
Cause 104: The device certificate verification failed.
The key components of the board may have been replaced, which affects system reliability and security.
Cause 105: Failed to access backplane IIC.
Services on the card may be affected or even interrupted.
Cause 106: Failed to check backplane ID.
Services on the card may be affected or even interrupted.
Cause 107: The IIC of MCU module is abnormal.
Services on the card may be affected or even interrupted.

Possible Causes

Cause 1: Power supply abnormal.
Cause 2: A voltage drop occurred on the board.
Cause 3: The serial management bus of the board malfunctions.
Cause 6: Board RTC fault.
Cause 8: The fan is not full.
Cause 11: A data channel fault occurred on the forwarding engine.
Cause 12: The forwarding engine failed.
Cause 13: Inter-card broadcast traffic failed to be forwarded.
Cause 15: Fabric interface input or output bandwidth usage exceeded 90% continuously.
Cause 16: Ingress clock signals channel failed.
Cause 17: The sensor on the board was faulty.
Cause 18: Chip instability.
Cause 19: Egress clock signals channel failed.
Cause 20: A packet reassembly error occurred.
Cause 21: Board CANBUS failed.
Cause 23: Board cannot be powered on or powered off properly.
Cause 24: EEPROM is abnormal.
Cause 25: The fan model does not match the device.
Cause 26: The power supply model does not match the device.
Cause 27: The PHY chip is abnormal.
Cause 29: Board PLL instability.
Cause 30: Phy instability.
Cause 36: USB overcurrent occurred.
Cause 37: IIC failed.
Cause 38: LANSWITCH chip instability.
Cause 39: The link of the XFI interface is faulty.
Cause 40: A CRC error occurred on the XFI interface.
Cause 43: The memory size is different from the standard configuration.
Cause 44: Flash memory failed.
Cause 50: CMU on the MPU is not registered.
Cause 51: The 38M clock fails.
Cause 52: The 19M clock fails.
Cause 53: The board clock fails.
Cause 54: The PLLA inside the forwarding engine is not ready.
Cause 55: The Serdes on the board failed.
Cause 56: An internal modular of the forwarding engine is abnormal.
Cause 58: The active and standby MPUs cannot communicate with each other.
Cause 59: The board type cannot be identified.
Cause 60: The board clock(156M) failed.
Cause 65: Storage media is abnormal.
Cause 70: CANBUS communications between the monitor chips failed.
Cause 71: A DDR fault occurs on the board.
Cause 72: The slot ID of the board fails to be checked.
Cause 73: Access to the flash memory of the board fails.
Cause 74: The FULLIN signal of the board is abnormal.
Cause 75: The slot ID signal from the CANBUS is abnormal.
Cause 76: A SerialCpldLocalbus fault occurs on the board.
Cause 77: The micro switch of the board fails.
Cause 78: The frequency synthesizer failed.
Cause 80: A CPU fault occurred.
Cause 82: A CPU-side CRC fault occurred.
Cause 83: A PHY-side CRC fault occurred.
Cause 84: The disk will soon become invalid.
Cause 88: The Chip is failed.
Cause 90: Overcurrent occurred on the board.
Cause 91: The FPGA is abnormal.
Cause 92: The sensor chip on the board was faulty.
Cause 96: A HTM chip fault occurred.
Cause 99: Failed to check the voltage of the board.
Cause 102: The currently used hard disk is not certified by Huawei.
Cause 103: The hard disk was pulled out.
Cause 104: The device certificate verification failed.
Cause 105: Failed to access backplane IIC.
Cause 106: Failed to check backplane ID.
Cause 107: The IIC of MCU module is abnormal.

Procedure

Cause 1: Power supply abnormal.
1. If the faulty board is not reset or powered off and services are running properly, go to step 3.

2. Power off and then power on the faulty board. If the fault persists, go to step 3.

3. Collect trap, log, and configuration information, and contact technical support personnel.
Cause 2: A voltage drop occurred on the board.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 3: The serial management bus of the board malfunctions.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 6: Board RTC fault.
1. If the faulty board is not reset or powered off and services are running properly, go to step 3.

2. Power off and then power on the faulty board. If the fault persists, go to step 3.

3. Collect trap, log, and configuration information, and contact technical support personnel.
Cause 8: The fan is not full.
Insert the fan module into the corresponding slot.
Cause 11: A data channel fault occurred on the forwarding engine.
1. Reset the board. If the fault persists, go to step 2.

2. Collect trap, log, and configuration information, and contact technical support personnel.
Cause 12: The forwarding engine failed.
1. Reset the board. If the fault persists, go to step 2.

2. Collect trap, log, and configuration information, and contact technical support personnel.
Cause 13: Inter-card broadcast traffic failed to be forwarded.
1. Collect alarm and log information, and contact technical support personnel.
Cause 15: Fabric interface input or output bandwidth usage exceeded 90% continuously.
1. Collect alarm and log information, and contact technical support personnel.
Cause 16: Ingress clock signals channel failed.
1. Collect alarm and log information, and contact technical support personnel.
Cause 17: The sensor on the board was faulty.
1. Reset the board. If the fault persists, go to step 2.

2. Collect trap, log, and configuration information, and contact technical support personnel.
Cause 18: Chip instability.
1. Reset the board. If the fault persists, go to step 2.

2. Collect trap, log, and configuration information, and contact technical support personnel.
Cause 19: Egress clock signals channel failed.
1. Collect alarm and log information, and contact technical support personnel.
Cause 20: A packet reassembly error occurred.
1. Collect alarm and log information, and contact technical support personnel.
Cause 21: Board CANBUS failed.
1. Reset the faulty board. If the fault persists, go to step 2.

2. Collect trap, log, and configuration information, and contact technical support personnel.
Cause 23: Board cannot be powered on or powered off properly.
1. Power off and then power on the faulty board. If the fault persists, go to step 2.

2. Collect trap, log, and configuration information, and contact technical support personnel.
Cause 24: EEPROM is abnormal.
1. Check whether the services on the board are normal.
- If so, go to step 4.
- If not, go to step 2.
2. Securely insert the board, and then check whether the alarm is cleared.
- If so, go to step 5.
- If not, go to step 3.
3. Replace the faulty board, and then check whether the alarm is cleared.
- If so, go to step 5.
- If not, go to step 4.
4. Collect alarm, log, and configuration information, and contact technical support engineers.

5. End.
Cause 25: The fan model does not match the device.
1. Replace the fan module with one that matches the device model.
Cause 26: The power supply model does not match the device.
1. Replace the fan or power module with a new one that matches the device model.
Cause 27: The PHY chip is abnormal.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 29: Board PLL instability.
1. Reset and restart the system.

2. If the fault persists, replace the board.
Cause 30: Phy instability.
1. If the faulty board is not reset or powered off and services are running properly, go to step 3.

2. Power off and then power on the faulty board. If the fault persists, go to step 3.

3. Collect trap, log, and configuration information, and contact technical support personnel.
Cause 36: USB overcurrent occurred.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 37: IIC failed.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 38: LANSWITCH chip instability.
1. Reset the board. If the fault persists, go to step 2.

2. Collect trap, log, and configuration information, and contact technical support personnel.
Cause 39: The link of the XFI interface is faulty.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 40: A CRC error occurred on the XFI interface.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 43: The memory size is different from the standard configuration.
1. Run the display version command to check whether the board memory meets the specifications. If the board memory does not meet the specifications, contact technical support personnel.
Cause 44: Flash memory failed.
1. Reset the board. If the fault persists, go to step 2.

2. Collect trap, log, and configuration information, and contact technical support personnel.
Cause 50: CMU on the MPU is not registered.
Collect alarm, log, and configuration information and contact Huawei technical support.
Cause 51: The 38M clock fails.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 52: The 19M clock fails.
Collect alarm, log, and configuration information and contact Huawei technical support.
Cause 53: The board clock fails.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 54: The PLLA inside the forwarding engine is not ready.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 55: The Serdes on the board failed.
1. Reset the board. If the fault persists, go to step 2.

2. Collect trap, log, and configuration information, and contact technical support personnel.
Cause 56: An internal modular of the forwarding engine is abnormal.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 58: The active and standby MPUs cannot communicate with each other.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 59: The board type cannot be identified.
1. Collect alarm and log information, and contact technical support personnel.
Cause 60: The board clock(156M) failed.
Collect alarm and log information and contact Huawei technical support.
Cause 65: Storage media is abnormal.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 70: CANBUS communications between the monitor chips failed.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 71: A DDR fault occurs on the board.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 72: The slot ID of the board fails to be checked.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 73: Access to the flash memory of the board fails.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 74: The FULLIN signal of the board is abnormal.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 75: The slot ID signal from the CANBUS is abnormal.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 76: A SerialCpldLocalbus fault occurs on the board.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 77: The micro switch of the board fails.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 78: The frequency synthesizer failed.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 80: A CPU fault occurred.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 82: A CPU-side CRC fault occurred.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 83: A PHY-side CRC fault occurred.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 84: The disk will soon become invalid.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 88: The Chip is failed.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 90: Overcurrent occurred on the board.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 91: The FPGA is abnormal.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 92: The sensor chip on the board was faulty.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 96: A HTM chip fault occurred.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 99: Failed to check the voltage of the board.
1. Collect alarm, log, and configuration information, and contact technical support personnel.
Cause 102: The currently used hard disk is not certified by Huawei.
Remove non-Huawei-certified hard disks and insert Huawei-certified hard disks.
Cause 103: The hard disk was pulled out.
Insert a hard disk.
Cause 104: The device certificate verification failed.
Reset the board and check whether the fault is rectified. If the fault persists, replace the board.
Cause 105: Failed to access backplane IIC.
Collect alarm, log, and configuration information and contact Huawei technical support.
Cause 106: Failed to check backplane ID.
Collect alarm, log, and configuration information and contact Huawei technical support.
Cause 107: The IIC of MCU module is abnormal.
Collect alarm, log, and configuration information and contact Huawei technical support.