DEVM/1/hwChassisInvalid_active

Message

DEVM/1/hwChassisInvalid_active: The chassis totally failed.(EntityPhysicalIndex=[EntityPhysicalIndex], EntityPhysicalIndex=[EntPhysicalIndex], EntPhysicalName=[EntPhysicalName], EntityTrapFaultID=[EntityTrapFaultID],Reason=[Reason])

In VS mode, this log is supported only by the admin VS.

Description

The chassis totally failed.

Parameters

Parameter Name Parameter Meaning

EntityPhysicalIndex

Indicates the index of the physical entity.

EntPhysicalIndex

Indicates the index of the physical entity.

EntPhysicalName

Indicates the name of the physical entity, such as "chassis"

EntityTrapFaultID

Indicates the error code.

Reason

Indicates the description of the cause of the trap.

Possible Causes

  • Cause 131560: The PTN mode of the master chassis in a virtual cluster device is different from that of the slave chassis.
  • Cause 131586: The type of SFU dismatch with the device
  • Cause 131587: The board types of the master and slave MPUs are different.
  • Cause 131588: Software Test Right license is not activated, the boards or cards will be reset after 72 hours.
  • Cause 131589: Software Test Right license will expire. After it expires, the boards or cards will be reset once every 24 hours.
  • Cause 131590: Software Test Right license is not activated or expired, the boards or cards will be reset once every 24 hours.

Procedure

  • Cause 131560: The PTN mode of the master chassis in a virtual cluster device is different from that of the slave chassis.

    1. Disconnect the slave chassis from the master chassis, configure the PTN mode of the slave chassis to be the same as that of the master chassis using the active mode-control license command or its undo form, and then connect the slave chassis to the master chassis.

    2. If the alarm still exists, collect trap, log, and configuration information, and contact technical support personnel.

    3. End.

  • Cause 131586: The type of SFU dismatch with the device

    1. Change the sfu match with the device.

    2. If the alarm still exists, collect trap, log, and configuration information, and contact technical support personnel.

    3. End.

  • Cause 131587: The board types of the master and slave MPUs are different.

    1. Install master and slave MPUs of the same board type.

    2. If the alarm still exists, collect trap, log, and configuration information, and contact technical support personnel.

    3. End.

  • Cause 131588: Software Test Right license is not activated, the boards or cards will be reset after 72 hours.

    1. Check whether license control items are activated.

    • If they are not activated, go to Step 2.
    • If they are activated, go to Step 3.

    2. Re-apply for and activate the license control items. Then, check whether the alarm is cleared.

    • If the alarm is cleared, go to Step 4.
    • If the alarm persists, go to Step 3.

    3. Collect alarm information, log information and configuration information, and then contact technical support personnel.

    4. End.

  • Cause 131589: Software Test Right license will expire. After it expires, the boards or cards will be reset once every 24 hours.

    1. Check whether license control items are about to expire.

    • If they are about to expire, go to Step 2.
    • If they are not about to expire, go to Step 3.

    2. Re-apply for and activate the license control items. Then, check whether the alarm is cleared.

    • If the alarm is cleared, go to Step 4.
    • If the alarm persists, go to Step 3.

    3. Collect alarm information, log information and configuration information, and then contact technical support personnel.

    4. End.

  • Cause 131590: Software Test Right license is not activated or expired, the boards or cards will be reset once every 24 hours.

    1. Check whether license control items are activated.

    • If they are not activated, go to Step 2.
    • If they are activated, go to Step 3.

    2. Re-apply for and activate the license control items. Then, check whether the alarm is cleared.

    • If the alarm is cleared, go to Step 4.
    • If the alarm persists, go to Step 3.

    3. Collect alarm information, log information and configuration information, and then contact technical support personnel.

    4. End.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >