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.30 hwBoardWarning

DEVM_1.3.6.1.4.1.2011.5.25.219.2.2.30 hwBoardWarning

Description

The board experienced a minor fault. (EntPhysicalIndex=[EntPhysicalIndex], EntPhysicalName=[EntPhysicalName], EntityType=[EntityType], EntityTrapFaultID=[EntityTrapFaultID], Reason=[Reason])

A minor fault occurred on the board.

Attribute

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Warning

Mnemonic Code

hwBoardWarning

Trap OID

1.3.6.1.4.1.2011.5.25.219.2.2.30

Alarm ID

0x081321c3

Alarm Type

equipmentAlarm

Raise or Clear

Raise

Match trap

DEVM_1.3.6.1.4.1.2011.5.25.219.2.2.31 hwBoardWarningResume

Parameters

Parameter Description

EntPhysicalIndex

Indicates the entity index.

EntPhysicalName

Indicates the entity name.

EntityType

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

EntityTrapFaultID

Indicates the error code.
  • 147200
  • 147201
  • 147202
  • 147203
  • 147204
  • 147205
  • 147206
  • 147207
  • 147208
  • 147209
  • 147210
  • 147211

Reason

Indicates the alarm reason.

VB Parameters

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.

Possible Causes

  • Cause 1 (EntityTrapFaultID=[147200]): A small number of internal CRC error packets are generated on the SFU.

  • Cause 2 (EntityTrapFaultID=[147201]): Packet loss occurred in a queue on an SFU.

  • Cause 3 (EntityTrapFaultID=[147202]): Packet loss occurred in a queue on the FDR module of an LPU.

  • Cause 4 (EntityTrapFaultID=[147203]): The buffer usage of the SFU is high. Check its bandwidth.

  • Cause 5 (EntityTrapFaultID=[147204]): All links on the SFU are down.

  • Cause 6 (EntityTrapFaultID=[147205]): Packet loss occurs on forward engine ingress interface.

  • Cause 7 (EntityTrapFaultID=[147206]): Link access to the forwarding engine is abnormal.

  • Cause 8 (EntityTrapFaultID=[147207]): The volume of forwarded traffic is close to the maximum forwarding capability of the device.

  • Cause 9 (EntityTrapFaultID=[147208]): The CPU failed to send packets.

  • Cause 10 (EntityTrapFaultID=[147209]): The XFI port connecting the LSW to the FPGA is Down.

  • Cause 11 (EntityTrapFaultID=[147210]): The PLL status is unlocked on the XFI port connecting the LSW to the FPGA.

  • Cause 12 (EntityTrapFaultID=[147211]): CRC error packets are generated on the XFI port connecting the LSW to the FPGA.

Procedure

  • Cause 1: A small number of internal CRC error packets are generated on the SFU.
    1. If the fault cannot be rectified for a long period of time, collect trap, log, and configuration information, and contact technical support personnel.
  • Cause 2: Packet loss occurred in a queue on an SFU.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 3: Packet loss occurred in a queue on the FDR module of an LPU.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 4: The buffer usage of the SFU is high. Check its bandwidth.
    1. Add an SFU. If the fault cannot be rectified, collect trap, log, and configuration information, and contact technical support personnel.
  • Cause 5: All links on the SFU are down.
    1. Remove and then insert the SFU. If the fault cannot be rectified, collect trap, log, and configuration information, and contact technical support personnel.
  • Cause 6: Packet loss occurs on forward engine ingress interface.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 7: Link access to the forwarding engine is abnormal.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 8: The volume of forwarded traffic is close to the maximum forwarding capability of the device.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 9: The CPU failed to send packets.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 10:The XFI port connecting the LSW to the FPGA is Down.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 11:The PLL status is unlocked on the XFI port connecting the LSW to the FPGA.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
  • Cause 12:CRC error packets are generated on the XFI port connecting the LSW to the FPGA.
    1. Collect traps, logs, and configurations, and contact technical support personnel.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039527

Views: 70338

Downloads: 21

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