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 8800, 7800, 6800, and 5800 V200R005C10

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 device 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

  • 132120

  • 132162

  • 132128

  • 132134

  • 132107

  • 132105
  • 132103
  • 132106
  • 132096
  • 132186
  • 132189
  • 132190
  • 132205
  • 132206
  • 132207

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 device may be affected or interrupted.

Possible Causes

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

  • Cause 2 (EntityTrapFaultID=[132162]): The fan model or power supply model does not match the device.

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

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

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

  • Cause 6 (EntityTrapFaultID=[132120]): IIC instability.

  • 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=[132096]): Power supply abnormal.

  • Cause 11 (EntityTrapFaultID=[132186]): The forwarding engine buffer failed.

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

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

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

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

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

Procedure

  • Cause 1: Chip instability.
    1. Reset the device. If the fault cannot be rectified, go to step 2.
    2. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 2: The fan model or power supply model does not match the device.
    1. Replace existing fans or power modules with ones that match the device.
  • Cause 3: Board PLL instability.
    1. Reset the device. If the fault cannot be rectified, replace the device.
  • Cause 4: LANSWITCH chip instability.
    1. Reset the device. 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 device is not reset or powered off and services are running normally, go to step 3.
    2. Power off and then power on the faulty device. If the fault persists, go to step 3.
    3. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 6: IIC instability.
    1. Reset the device. If the fault cannot be rectified, go to step 2.
    2. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 7: Flash memory failed.
    1. Reset the device. 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 device. 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 device is not reset or powered off and services are running normally, go to step 3.
    2. Power off and then power on the faulty device. If the fault persists, go to step 3.
    3. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 10: Power supply abnormal.
    1. If the faulty device is not reset or powered off and services are running normally, go to step 3.
    2. Power off and then power on the faulty device. If the fault persists, go to step 3.
    3. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 11: The forwarding engine buffer failed.
    1. If the faulty device is not reset or powered off and services are running normally, go to step 3.
    2. Reset the device. If the fault cannot be rectified, 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 device is not reset or powered off and services are running normally, go to step 3.
    2. Reset the device. 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 device is not reset or powered off and services are running normally, go to step 3.
    2. Reset the device. If the fault cannot be rectified, go to step 3.
    3. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 14: The HiGig link on the board failed.
    1. Reset the device. If the fault cannot be rectified, go to step 2.
    2. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 15: A logic error occurs in the LPM table of the forwarding engine.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 16: The board clock fails.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
Translation
Download
Updated: 2019-04-02

Document ID: EDOC1100074754

Views: 17126

Downloads: 25

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