DEVM/1/hwBoardInvalid_active

Message

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

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

Description

The overall function of the board does not take effect.

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 entity such as a chassis.
EntityType	Indicates the type of the physical entity. The value can be one of the following: 1: mpu(1) 2: lpu(2) 3: sfu(3) 4: pic(4) 5: cfcard(5) 6: ofc(6) 7: npu(7)
EntityTrapFaultID	Indicates the error code.
Reason	Indicates the description of the cause of the trap.

Possible Causes

Cause 1: The link between the TM chip and the NP chip was detected faulty.
Cause 3: The number of links between the TM chip and the SFU was too small.
Cause 4: The board failed the self check.
Cause 17: SFU Fabric chip fault.
Cause 20: FABRIC SRD CRC check fault.
Cause 29: The SD5000 self-check failed.
Cause 32: The EEPROM of the board is fauty.
Cause 63: The board power supply failed.
Cause 69: The crosspoint of the board faulty.
Cause 131843: The board info of the mpu conflicted.
Cause 131844: The MPU system master conflicted.
Cause 132609: The board reset because of the heart beat loss.
Cause 132610: The board did not match the device.
Cause 132612: The sync clock of the board is abnormal.
Cause 132613: The FPGA logic of the board failed.
Cause 132614: The EPLD logic of the board failed.
Cause 132616: The clock signal of the board was incorrect.
Cause 132617: The TM chip failed the self check.
Cause 132618: Board NP fault.
Cause 132619: The master or slave ACT signal of the MPU board is abnormal.
Cause 132620: The supply power of the board is insufficient.
Cause 132621: The control bus of the board is abnormal.
Cause 132623: NSE on the board fault.
Cause 132624: The memory of the board failed.
Cause 132625: The Lanswitch chip of the board failed.
Cause 132626: The board was powered off.
Cause 132627: The board is register.
Cause 132628: The board reset because of the exception.
Cause 132629: The PHY chip of the board failed.
Cause 132630: The clock signals of the SFU fabric is abnormal.
Cause 132632: The control bus failed.
Cause 132654: The board is uncompatible with system software.
Cause 132657: The combination of cards is not compatible with the capabity of linked FE.
Cause 132660: A board was reset because its temperature was overhigh.
Cause 132661: The board is reset by command.
Cause 132670: The user-input supply power of the board is insufficient.
Cause 132671: The EPLD2 logic of the board failed.
Cause 132672: The clock signals 125M of the board is abnormal.
Cause 132673: The data link of the board is abnormal.
Cause 132676: Power supply is insufficient to improve the fan power.
Cause 132679: The ETM chip failed the self check.
Cause 132680: A fatal interrupt occurs in the TM chip.
Cause 132685: The board failed to be inserted tightly.
Cause 132686: The SMI serial of the board is abnormal.
Cause 132687: The board is not running the PAT.
Cause 132690: The FPGA1 logic of the board failed.
Cause 132691: The FPGA2 logic of the board failed.
Cause 132692: The FPGA3 logic of the board failed.
Cause 132693: The FPGA4 logic of the board failed.
Cause 132694: The FPGA5 logic of the board failed.

Procedure

Cause 1: The link between the TM chip and the NP chip was detected faulty.
1. If the faulty board is neither reset nor powered off, and services on the board are normal, go to Step 4. Otherwise, go to Step 2.

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

3. If the board cannot be registered or the alarm persists after the board is registered, go to Step 4.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 3: The number of links between the TM chip and the SFU was too small.
1. If the faulty board is neither reset nor powered off, and services on the board are normal, go to Step 4. Otherwise, go to Step 2.

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

3. If the board cannot be registered or the alarm persists after the board is registered, go to Step 4.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 4: The board failed the self check.
1. If the faulty board is neither reset nor powered off, and services on the board are normal, go to Step 4. Otherwise, go to Step 2.

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

3. If the board cannot be registered or the alarm persists after the board is registered, go to Step 4.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 17: SFU Fabric chip fault.
1. If the faulty board is neither reset nor powered off, and services on the board are normal, go to Step 4. Otherwise, go to Step 2.

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

3. If the board cannot be registered or the alarm persists after the board is registered, go to Step 4.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 20: FABRIC SRD CRC check fault.
1. If the faulty board is neither reset nor powered off, and services on the board are normal, go to Step 4. Otherwise, go to Step 2.

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

3. If the board cannot be registered or the alarm persists after the board is registered, go to Step 4.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 29: The SD5000 self-check failed.
Collect trap, log, and configuration information, and contact technical support.
Cause 32: The EEPROM of the board is fauty.
Collect trap, log, and configuration information, and contact technical support.
Cause 63: The board power supply failed.
Collect trap, log, and configuration information, and contact technical support.
Cause 69: The crosspoint of the board faulty.
Collect trap, log, and configuration information, and contact technical support.
Cause 131843: The board info of the mpu conflicted.
1. Run the display chassis-id all command in the system view to check whether the current and peer chassis have the same ID.
- If they have the same chassis ID, go to Step 2.
- If they have different chassis IDs, go to Step 3.
2. Run the set chassis-id command in the system view of the current or peer chassis to set a different chassis ID. Restart the device and check whether the alarm is cleared.
- If the alarm persists, go to Step 3.
- If the alarm is cleared, go to Step 5.
3. Run the display version slot command in the system view to check whether the current and peer chassis have the same MPU type and memory size.
- If they have the same MPU type and memory size, go to Step 4.
- If they have different MPU types or memory sizes, replace one of the MPUs.
4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 131844: The MPU system master conflicted.
Collect trap, log, and configuration information, and contact technical support.
Cause 132609: The board reset because of the heart beat loss.
Collect trap, log, and configuration information, and contact technical support.
Cause 132610: The board did not match the device.
1. Remove the board that does not match the device, and then install a board that matches the device.

2. If the alarm persists, collect trap, log, and configuration information, and contact technical support.

3. End.
Cause 132612: The sync clock of the board is abnormal.
1. If only the faulty board reports this alarm, replace the faulty board.

2. If the alarm persists, collect alarm, log, and configuration information and contact technical support engineers.

3. End.
Cause 132613: The FPGA logic of the board failed.
1. If the faulty board is neither reset nor powered off, and services on the board are normal, go to Step 4. Otherwise, go to Step 2.

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

3. If the board cannot be registered or the alarm persists after the board is registered, go to Step 4.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 132614: The EPLD logic of the board failed.
1. Go to Step 2 if the faulty board is not the main control board.

2. If the faulty board is registered, run the EPlD upgrade command in the user view: upgrade mpu/lpu/sfu slotid startup firmware. Then, go to Step 4.

3. If the faulty board is not registered, power off and then power on the faulty board.

4. If the faulty board cannot be registered or the fault persists after the board is registered, replace the faulty board.

5. If the alarm persists, collect alarm, log, and configuration information and contact technical support engineers.

6. End.
Cause 132616: The clock signal of the board was incorrect.
1. If the faulty board is neither reset nor powered off, and services on the board are normal, go to Step 4. Otherwise, go to Step 2.

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

3. If the board cannot be registered or the alarm persists after the board is registered, go to Step 4.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 132617: The TM chip failed the self check.
1. If the faulty board is neither reset nor powered off, and services on the board are normal, go to Step 4. Otherwise, go to Step 2.

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

3. If the board cannot be registered or the alarm persists after the board is registered, go to Step 4.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 132618: Board NP fault.
1. If the faulty board is neither reset nor powered off, and services on the board are normal, go to Step 4. Otherwise, go to Step 2.

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

3. If the board cannot be registered or the alarm persists after the board is registered, go to Step 4.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 132619: The master or slave ACT signal of the MPU board is abnormal.
1. Check whether other boards have low-power-related alarms or power-related alarms. If so, handle these alarms first.

2. Remove and reinstall the current standby main control board and check whether the standby main control board is securely installed, whether any bent pins exist, and whether the connectors of the standby main control board are normal. Then, go to Step 4.

3. If the device is reset, remove the other main control board and check whether the main control board is securely installed, whether any bent pins exist, and whether the connectors of the main control board are normal. Then, go to Step 4.

4. If the board is not securely installed, install it securely.

5. If the backplane has bent pins, avoid installing a new board into the faulty slot. Contact technical support.

6. If only the connectors of the board are found to be faulty, replace the board and go to Step 8.

7. If the standby main control board is still not registered or the alarm persists, contact technical support.

8. End.
Cause 132620: The supply power of the board is insufficient.
Collect trap, log, and configuration information, and contact technical support.
Cause 132621: The control bus of the board is abnormal.
1. Run the reset slot slot-id command to reset the faulty SFU. After the SFU is registered, check whether the alarm is cleared.
- If so, go to Step 4.
- If not, go to Step 2.
2. Replace the SFU and check whether the alarm is cleared.
- If so, go to Step 4.
- If not, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support.

4. End.
Cause 132623: NSE on the board fault.
1. If the faulty board is neither reset nor powered off, and services on the board are normal, go to Step 4. Otherwise, go to Step 2.

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

3. If the board cannot be registered or the alarm persists after the board is registered, go to Step 4.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 132624: The memory of the board failed.
1. If the faulty board is neither reset nor powered off, and services on the board are normal, go to Step 4. Otherwise, go to Step 2.

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

3. If the board cannot be registered or the alarm persists after the board is registered, go to Step 4.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 132625: The Lanswitch chip of the board failed.
1. Run the display device command to check the status of all the boards on the current device.

2. If all the boards are in the Registered state, contact technical support.

3. If several boards are in the non-Registered state after the alarm occurs, replace the faulty boards.

4. If only one board is in the non-Registered state, collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 132626: The board was powered off.
1. Replace the faulty board and check whether the alarm is cleared. If the alarm is not cleared, go to Step 2.

2. Collect trap, log, and configuration information, and contact technical support.

3. End.
Cause 132627: The board is register.
This trap message is informational only, and no action is required.
Cause 132628: The board reset because of the exception.
Collect trap, log, and configuration information, and contact technical support.
Cause 132629: The PHY chip of the board failed.
1. Run the display device command to view the status of the faulty board.

2. If the faulty board is in the Registered state, collect trap, log, and configuration information, and contact technical support.

3. If the faulty board is in the non-Registered state, replace the faulty board.
Cause 132630: The clock signals of the SFU fabric is abnormal.
1. Run the reset slot slot-id command to reset the faulty SFU. After the SFU is registered, check whether the alarm is cleared.
- If so, go to Step 4.
- If not, go to Step 2.
2. Replace the SFU and check whether the alarm is cleared.
- If so, go to Step 4.
- If not, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support.

4. End.
Cause 132632: The control bus failed.
1. If the faulty board is neither reset nor powered off, and services on the board are normal, go to Step 4. Otherwise, go to Step 2.

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

3. If the board cannot be registered or the alarm persists after the board is registered, go to Step 4.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 132654: The board is uncompatible with system software.
1. Change the type of boards supported by the current version. Check whether the alarm is cleared. If the alarm is not cleared, go to Step 2.

2. Update the system software and check whether the board is registered. If the board is not registered, go to Step 3.

3. Collect trap, log, and configuration information, and contact technical support.

4. End.
Cause 132657: The combination of cards is not compatible with the capabity of linked FE.
1. Remove some subcards connected to the FE until the bandwidth of subcards left is lower than that of the FE bandwidth available. Check whether the alarm is cleared.

2. Collect trap, log, and configuration information, and contact technical support.

3. End.
Cause 132660: A board was reset because its temperature was overhigh.
1. If fans are installed, check whether the fans work properly.

2. Check whether the ambient temperature is overhigh.

3. Wait for the board to be powered off. The board will automatically restart after it cools down. Alternatively, you can replace the faulty board.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 132661: The board is reset by command.
Collect trap, log, and configuration information, and contact technical support.
Cause 132670: The user-input supply power of the board is insufficient.
1. Check whether the device is equipped with sufficient power modules.
- If power modules are sufficient, go to Step 2.
- If power modules are not sufficient, go to Step 3.
2. Check whether the maximum power consumption allowed is too small.
- If the maximum power consumption allowed is too small, change it to a proper value and then go to Step 4.
- If the maximum power consumption allowed is not too small, go to Step 5.
3. Install extra power modules.

4. Check whether the alarm is cleared.
- If the alarm is cleared, go to Step 6.
- If the alarm persists, go to Step 5.
5. Collect trap, log, and configuration information, and contact technical support.

6. End.
Cause 132671: The EPLD2 logic of the board failed.
1. Go to Step 2 if the faulty board is not the main control board.

2. If the faulty board is registered, run the EPlD2 upgrade command in the user view: upgrade mpu/lpu/sfu slotid startup firmware. Then go to Step 4.

3. If the faulty board is not registered, power off and then power on the faulty board.

4. If the faulty board cannot be registered or the fault persists after the board is registered, replace the faulty board.

5. If the alarm persists, collect alarm, log, and configuration information and contact technical support engineers.

6. End.
Cause 132672: The clock signals 125M of the board is abnormal.
Collect trap, log, and configuration information, and contact technical support.
Cause 132673: The data link of the board is abnormal.
Collect trap, log, and configuration information, and contact technical support.
Cause 132676: Power supply is insufficient to improve the fan power.
1. Check whether the device is equipped with sufficient power modules.
- If power modules are sufficient, go to Step 3.
- If power modules are not sufficient, go to Step 2.
2. Install extra power modules.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 trap, log, and configuration information, and contact technical support.

4. End.
Cause 132679: The ETM chip failed the self check.
1. Check whether the faulty board is reset or powered off.
- If the faulty board is reset or powered off, go to Step 3.
- If the faulty board is not reset or powered off, go to Step 2.
2. Power off the faulty board and then power it on. 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, log, and configuration information, and contact technical support.

4. End.
Cause 132680: A fatal interrupt occurs in the TM chip.
1. If the board is neither reset nor powered off, and services on the board are normal, go to Step 4. Otherwise, go to Step 2.

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

3. If the board cannot be registered or the alarm persists after the board is registered, go to Step 4.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 132685: The board failed to be inserted tightly.
1. Remove the board.

2. Push the board into the slot until it is fully seated. Then, fasten the board.

3. End.
Cause 132686: The SMI serial of the board is abnormal.
Collect the trap information, log information, and configuration information, and contact Huawei technical personnel.
Cause 132687: The board is not running the PAT.
1. Load the PAT file with the corresponding version.

2. Wait about 10 minutes and check whether the alarm is cleared.
- If so, go to Step 4.
- If not, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support.

4. End.
Cause 132690: The FPGA1 logic of the board failed.
1. If the faulty board is neither reset nor powered off, and services on the board are normal, go to Step 4. Otherwise, go to Step 2.

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

3. If the board cannot be registered or the alarm persists after the board is registered, go to Step 4.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 132691: The FPGA2 logic of the board failed.
1. If the faulty board is neither reset nor powered off, and services on the board are normal, go to Step 4. Otherwise, go to Step 2.

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

3. If the board cannot be registered or the alarm persists after the board is registered, go to Step 4.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 132692: The FPGA3 logic of the board failed.
1. If the faulty board is neither reset nor powered off, and services on the board are normal, go to Step 4. Otherwise, go to Step 2.

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

3. If the board cannot be registered or the alarm persists after the board is registered, go to Step 4.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 132693: The FPGA4 logic of the board failed.
1. If the faulty board is neither reset nor powered off, and services on the board are normal, go to Step 4. Otherwise, go to Step 2.

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

3. If the board cannot be registered or the alarm persists after the board is registered, go to Step 4.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.
Cause 132694: The FPGA5 logic of the board failed.
1. If the faulty board is neither reset nor powered off, and services on the board are normal, go to Step 4. Otherwise, go to Step 2.

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

3. If the board cannot be registered or the alarm persists after the board is registered, go to Step 4.

4. Collect trap, log, and configuration information, and contact technical support.

5. End.