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.5 hwBoardInvalid

DEVM_1.3.6.1.4.1.2011.5.25.219.2.2.5 hwBoardInvalid

Description

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

The board completely failed.

Attribute

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Alert

Mnemonic Code

hwBoardInvalid

Trap OID

1.3.6.1.4.1.2011.5.25.219.2.2.5

Alarm ID

0x0813002e

Alarm Type

equipmentAlarm

Raise or Clear

Raise

Match trap

DEVM_1.3.6.1.4.1.2011.5.25.219.2.2.6 hwBoardInvalidResume

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.
  • 132614

  • 132616

  • 132627

  • 132623

  • 132626

  • 132630

  • 132666

  • 132613

  • 132669

  • 132610

  • 132632

  • 132674

  • 132675

  • 132677

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

The board completely fails, and services are interrupted.

Possible Causes

  • Cause 1 (EntityTrapFaultID=[132614]): The EPLD logic of the board failed.

  • Cause 2 (EntityTrapFaultID=[132616]): The clock signals of the board were incorrect.

  • Cause 3 (EntityTrapFaultID=[132627]): The board was not registered.

  • Cause 4 (EntityTrapFaultID=[132623]): TCAM chip of the board failed.

  • Cause 5 (EntityTrapFaultID=[132626]): The board was powered off. (Possible causes include: The board was manually powered off; the current version does not support this board; the board temperature was too high; the board was not registered for a long period of time; the board was not working normally.)

  • Cause 6 (EntityTrapFaultID=[132630]): The board obtained abnormal signals from the master and slave MPUs.

  • Cause 7 (EntityTrapFaultID=[132666]): The in-position board type conflicts with the pre-configured board type.

  • Cause 8 (EntityTrapFaultID=[132613]): The FPGA entry may be incorrect.

  • Cause 9 (EntityTrapFaultID=[132669]): The board does not support some configurations and cannot register.

  • Cause 10 (EntityTrapFaultID=[132610]): The board does not match the device.

  • Cause 11 (EntityTrapFaultID=[132632]): PCI bus failed.

  • Cause 12 (EntityTrapFaultID=[132674]): The FPGA of the board failed.

  • Cause 13 (EntityTrapFaultID=[132675]): The LSW port connected to the MPU fails.

  • Cause 14 (EntityTrapFaultID=[132677]): The FPGA local bus self-check failed.

Procedure

  • Cause 1: The EPLD logic of the board failed.
    1. Check whether the faulty board is the active board.

      • If so, perform the active/standby switchover when the standby board works properly.

      • If not, go to step 2.

    2. Check whether the board has been successfully registered.

      • If so, go to step 3.

      • If not, go to step 4.

    3. Upgrade the EPLD in the user view and check whether the fault is rectified.

      • If so, no action is required.

      • If not, go to step 4.

    4. Power off and then power on the faulty board. If the faulty board cannot be registered or the fault persists after the board is registered, replace the faulty board.
  • Cause 2: The clock signals of the board were incorrect.
    1. Check whether the faulty board is reset or powered off and whether services are running normally.

      • If the board is not reset or powered off and services are running normally, go to step 4.
      • If the board is reset or powered off or services are not running normally, go to step 2.

    2. Power off and then power on the faulty board.

      • If the board can be registered successfully and the fault is rectified, go to step 5.
      • If the board cannot be registered and the fault persists, go to step 3.

    3. Replace the faulty board.

      • If the board can be registered successfully and the fault is rectified, go to step 5.
      • If the board cannot be registered and the fault persists, go to step 4.

    4. Contact technical support personnel.
    5. End
  • Cause 3: The board was not registered.

    Remove and reinstall the board. If the faulty board cannot be registered, replace the faulty board.

  • Cause 4: TCAM chip failed.

    The handling procedure is the same as that for cause 2.

  • Cause 5: The board was powered off.
    1. Check whether the board was manually powered off.

      • If so, check whether the power-off is expected. If so, no action is required. If not, power on the board.

      • If not, go to step 2.

    2. Check whether the current version supports this board.

      • If so, go to step 3.

      • If not, replace this board with the one supported by the current version.

    3. Check whether the board temperature is too high.

      • If so, reduce the temperature.

      • If not, go to step 4.

    4. Remove and then reinstall the board to check whether the fault is rectified. If the fault persists, go to step 5.
    5. Collect trap messages, log messages, and configurations, and then contact technical support personnel.
  • Cause 6: Abnormal signals were obtained from the active and standby MPUs.
    1. Check whether the two MPUs are installed properly. If not, install the two MPUs properly and check whether the fault is rectified.

      • If the fault is rectified, go to step 4.

      • If the fault persists, go to step 2.

    2. If no services are running on the faulty board, perform the following operations to rectify the fault. If the fault is rectified, go to step 4. If the fault persists, go to step 3.

      • If the board is not properly installed, install the board properly.
      • If there are bent pins on the backplane, this slot becomes unavailable and the fault cannot be rectified.
      • If the board connector fails, replace the board.

    3. If services are running on the board or the fault persists, contact technical support personnel.
    4. End
  • Cause 7: The in-position board conflicts with the logical board.

    • Run the undo device conflict-policy keep-config command to make the installed board work.
    • Delete the pre-configured logical board in the position.
    • Remove the conflicting physical board and then install a physical board that is the same as the pre-configured board.

  • Cause 8: The FPGA entry may be incorrect.

    • If the board fails to be registered after being reset or the fault persists after the board is registered, replace the board.
    • If the board is not reset or powered off and services are running normally, contact technical support personnel.

  • Cause 9: The board does not support some configurations and cannot register.

    Check whether the board is an LPU or SFU.

    • If the board is an LPU, run the undo set forward capability enhanced command in the system view to restore the board interoperability mode to non-enhanced mode and then restart the device.
    • If the board is an SFU, run the sfu maintenance mode enable command in the diagnostic view to enable the SFU maintenance mode and then reseat the board.

  • Cause 10: The board does not match the device.

    The device does not support this board or has FD, FD1, FG, FG1, SD, or FDA LPUs installed together with SFUAs, SFUBs, or SFUCs. You need to remove this board.

  • Cause 11: PCI bus failed.

    Power off and then power on the faulty board. If the fault persists, contact technical support personnel.

  • Cause 12: The FPGA of the board failed.

    • If the board fails to be registered after being reset or the fault persists after the board is registered, replace the board.
    • If the board is not reset or powered off and services are running normally, contact technical support personnel.

  • Cause 13: The LSW port connected to the MPU fails.

    Replace the faulty board.

  • Cause 14: The FPGA local bus self-check failed.
    1. If the faulty board is not the active MPU, go to step 3.

    2. If the standby MPU works properly, run the slave switchover command in the system view to perform an active/standby switchover, and go to step 1.

    3. Power off the faulty board and then power it on.
    4. If the fault persists, replace the faulty board.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039527

Views: 88220

Downloads: 21

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