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

Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs 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/hwBoardInvalid_active

DEVM/1/hwBoardInvalid_active

Message

DEVM/1/hwBoardInvalid_active: The board totally failed. (EntPhysicalIndex=[EntPhysicalIndex], EntPhysicalName=[EntPhysicalName], EntityType=[EntityType], EntityTrapFaultID=[EntityTrapFaultID], Reason=[Reason])

Description

The board completely failed.

Parameters

Parameter Name Parameter 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

  • 132666

  • 132613

  • 132674

  • 132677

Reason

Indicates a possible cause.

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=[132666]): The in-position board type conflicts with the pre-configured board type.

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

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

  • Cause 8 (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.

    Power off and then power on the faulty device. If the faulty device cannot be registered, replace the faulty device.

  • Cause 4: TCAM chip failed.

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

  • Cause 5: 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 6: 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 7: 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 8: 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: EDOC1100039602

Views: 136864

Downloads: 90

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