No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Alarm Handling

CloudEngine 12800 and 12800E V200R005C00

This document provides the explanations, causes, and recommended actions of alarms on the product.
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).
DEVM_1.3.6.1.4.1.2011.5.25.219.2.2.3 hwBoardFail

DEVM_1.3.6.1.4.1.2011.5.25.219.2.2.3 hwBoardFail

Description

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

The board partially failed.

Attribute

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Alert

Mnemonic Code

hwBoardFail

Trap OID

1.3.6.1.4.1.2011.5.25.219.2.2.3

Alarm ID

0x08130054

Alarm Type

equipmentAlarm

Raise or Clear

Raise

Match trap

DEVM_1.3.6.1.4.1.2011.5.25.219.2.2.4 hwBoardFailResume

Parameters

Name Meaning

EntPhysicalIndex

Indicates the index of an entity.

EntPhysicalName

Indicates the name of an entity.

EntityType

Indicates the entity type.
  • 1: MPU
  • 2: LPU
  • 3: SFU
  • 4: subcard
  • 5: storage medium

EntityTrapFaultID

Indicates the error code.
  • 132137

  • 132128

  • 132134

  • 132107

  • 132167

  • 132097

  • 132102

  • 132105
  • 132103
  • 132106
  • 132096
  • 132189
  • 132190
  • 132194
  • 132195
  • 132196
  • 132197
  • 132202
  • 132203
  • 132205
  • 132206
  • 132207
  • 132210
  • 132211
  • 132214
  • 132216
  • 132221
  • 132222

Reason

Indicates a possible cause.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.219.1.1

hwEntityPhysicalIndex

N/A

1.3.6.1.2.1.47.1.1.1.1.7

entPhysicalName

entPhysicalIndex

1.3.6.1.4.1.2011.5.25.219.1.2

hwEntityTrapEntType

N/A

1.3.6.1.4.1.2011.5.25.219.1.3

hwEntityTrapFaultID

N/A

Impact on the System

Services on the board may be affected or interrupted.

Possible Causes

  • Cause 1 (EntityTrapFaultID=[132137]): Chip instability.

  • Cause 2 (EntityTrapFaultID=[132167]): The memory size is different from the standard configuration.

  • Cause 3 (EntityTrapFaultID=[132128]): Board PLL instability.

  • Cause 4 (EntityTrapFaultID=[132134]): LANSWITCH chip instability.

  • Cause 5 (EntityTrapFaultID=[132107]): Phy instability.

  • Cause 6 (EntityTrapFaultID=[132097]): Board CANBUS failed.

  • Cause 7 (EntityTrapFaultID=[132106]): Flash memory failed.

  • Cause 8 (EntityTrapFaultID=[132105]): The sensor on the board was faulty.

  • Cause 9 (EntityTrapFaultID=[132103]): Board RTC fault.

  • Cause 10 (EntityTrapFaultID=[132102]): Board cannot be powered on or powered off properly.

  • Cause 11 (EntityTrapFaultID=[132096]): Power supply abnormal.

  • Cause 12 (EntityTrapFaultID=[132189]): A data channel fault occurred on the forwarding engine.

  • Cause 13 (EntityTrapFaultID=[132190]): The forwarding engine failed.

  • Cause 14 (EntityTrapFaultID=[132194]): Inter-card broadcast traffic failed to be forwarded.

  • Cause 15 (EntityTrapFaultID=[132195]): Fabric interface input or output bandwidth usage exceeded 90% continuously.

  • Cause 16 (EntityTrapFaultID=[132196]): Ingress clock signals channel failed.

  • Cause 17 (EntityTrapFaultID=[132197]): Egress clock signals channel failed.

  • Cause 18 (EntityTrapFaultID=[132202]): The 38M clock fails.

  • Cause 19 (EntityTrapFaultID=[132203]): A packet reassembly error occurred.

  • Cause 20 (EntityTrapFaultID=[132205]): The HiGig link on the board failed.

  • Cause 21 (EntityTrapFaultID=[132206]): A logic error occurs in the LPM table of the forwarding engine.

  • Cause 22 (EntityTrapFaultID=[132207]): The board clock fails.

  • Cause 23 (EntityTrapFaultID:132210): The PLL inside the forwarding engine is not ready.

  • Cause 24 (EntityTrapFaultID:132211): An internal modular of the forwarding engine is abnormal.

  • Cause 25 (EntityTrapFaultID:132214): The active and standby MPUs cannot communicate with each other.

  • Cause 26 (EntityTrapFaultID:132216): An exception occurs when the forwarding engine accesses the external TCAM.

  • Cause 27 (EntityTrapFaultID:132221): The board type cannot be identified.

  • Cause 28 (EntityTrapFaultID:132222): The chip cannot synchronize signals with the system and is isolated.

Procedure

  • Cause 1: Chip instability.
    1. Reset the board. If the fault cannot be rectified, go to step 2.
    2. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 2: The memory size is different from the standard configuration.
    1. Run the display version command to check the memory size of the board. If the memory size is different from the standard configuration, contact technical support personnel.
  • Cause 3: Board PLL instability.
    1. Reset the board. If the fault cannot be rectified, replace the board.
  • Cause 4: LANSWITCH chip instability.
    1. Reset the board. If the fault cannot be rectified, go to step 2.
    2. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 5: Phy instability.
    1. If the faulty board is not reset or powered off and services are running normally, go to step 3.
    2. Power off and then power on the faulty board. If the fault persists, go to step 3.
    3. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 6: Board CANBUS failed.
    1. If the faulty board is not reset or powered off and services are running normally, go to step 3.
    2. Power off and then power on the faulty board. If the fault persists, go to step 3.
    3. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 7: Flash memory failed.
    1. Reset the board. If the fault cannot be rectified, go to step 2.
    2. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 8: The sensor on the board was faulty.
    1. Reset the board. If the fault cannot be rectified, go to step 2.
    2. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 9: Board RTC fault.
    1. If the faulty board is not reset or powered off and services are running normally, go to step 3.
    2. Power off and then power on the faulty board. If the fault persists, go to step 3.
    3. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 10: 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. Remove and reinstall the board. If the fault persists, go to step 3.
    3. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 11: Power supply abnormal.
    1. If the faulty board is not reset or powered off and services are running normally, go to step 3.
    2. Power off and then power on the faulty board. If the fault persists, go to step 3.
    3. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 12: A data channel fault occurred on the forwarding engine.
    1. If the faulty board is not reset or powered off and services are running normally, go to step 3.
    2. Reset the board. If the fault cannot be rectified, go to step 3.
    3. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 13: The forwarding engine failed.
    1. If the faulty board is not reset or powered off and services are running normally, go to step 3.
    2. Reset the board. If the fault cannot be rectified, go to step 3.
    3. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 14: Inter-card broadcast traffic failed to be forwarded.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 15: Fabric interface input or output bandwidth usage exceeded 90% continuously.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 16: Ingress clock signals channel failed.
    1. Collect the display device alarm hardware command output, alarm information, log information, and configuration information, and contact technical support personnel.
  • Cause 17: Egress clock signals channel failed.
    1. Collect the display device alarm hardware command output, alarm information, log information, and configuration information, and contact technical support personnel.
  • Cause 18: The 38M clock fails.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 19: A packet reassembly error occurred.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 20: The HiGig link on the board failed.
    1. Reset the board. If the fault cannot be rectified, go to step 2.
    2. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 21: A logic error occurs in the LPM table of the forwarding engine.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 22: The board clock fails.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 23: The PLL inside the forwarding engine is not ready.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 24: An internal modular of the forwarding engine is abnormal.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 25: The active and standby MPUs cannot communicate with each other.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 26: An exception occurs when the forwarding engine accesses the external TCAM.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 27: The board type cannot be identified.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 28: The chip cannot synchronize signals with the system and is isolated.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039527

Views: 70291

Downloads: 21

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next