DEVM/1/hwBoardFail_active

Message

DEVM/1/hwBoardFail_active: The board partially 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 board experienced a partial failure.

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.
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: board(7) -255: other(255)
EntityTrapFaultID	Indicates the error code.
Reason	Indicates the description of the cause of the trap.

Possible Causes

Cause 132096: Power supply for a board was abnormal.
Cause 132097: The monitor bus of the board is abnormal.
Cause 132098: The sc chip failed.
Cause 132100: The slotid check of the board is abnormal.
Cause 132101: The supply voltage 48V of the board is abnormal.
Cause 132102: The board cannot be properly powered on or powered off.
Cause 132103: The batteries are invalid.
Cause 132104: The act signal of the MPU Board is abnormal.
Cause 132105: The sensor of the board is abnormal.
Cause 132108: The clock signal of the clock board is abnormal.
Cause 132109: The voltage exceeded the upper limit of the fatal threshold.
Cause 132110: The voltage exceeded the upper limit of the major threshold.
Cause 132111: The voltage was lower than the lower limit of the fatal threshold.
Cause 132112: The voltage was lower than the lower limit of the major threshold.
Cause 132117: Clock signals on the board were faulty.
Cause 132118: The in-positon signal of the board were faulty.
Cause 132120: The IIC bus of the board is abnormal.
Cause 132121: The USB controller on the board failed.
Cause 132122: The CFcard of the MPU board is abnormal.
Cause 132127: The board clock malfunctions.
Cause 132128: The board PLL malfunctions.
Cause 132129: The FE PHY chip malfunctions.
Cause 132131: The keychip of the clock board is abnormal.
Cause 132134: LANSWITCH is abnormal.
Cause 132137: The CMAC chip failed the self check.
Cause 132139: The voltage of the subcard exceeded the fatal upper threshold.
Cause 132140: The voltage of the subcard exceeded the upper threshold.
Cause 132141: The voltage of the subcard was below the lower fatal threshold.
Cause 132142: The voltage of the subcard was below the warning lower threshold.
Cause 132150: The idle space on the CF card is lower than the threshold.
Cause 132152: The CPU of the board partially failed.
Cause 132155: The link between the CMAC chip and the NP chip was detected faulty.
Cause 132157:
Cause1: Capability of the traffic management chip was insufficient.

Cause2: The chip is abnormal.
Cause 132161: Board temperature sensors fault.
Cause 132163: The core of the board is abnormal.
Cause 132164: Too many sensor points failed.
Cause 132169: The communication channel failed and change into another channel.
Cause 132170: The RTC on the board failed.
Cause 132173: The Security Acceleration Engine is abnormal.
Cause 132174: PCB Corrosive.
Cause 132177: Interface MAC CRC error.
Cause 132178: E-label CRC error.
Cause 132180: The first 48V power supply of the board is fault.
Cause 132181: The second 48V power supply of the board is fault.
Cause 132182: Board voltage sensors fault.
Cause 132183: Voltage A/D Fault.
Cause 132184: SPI Bus fault.
Cause 132187: The cp2np-phy on the board is abnormal.
Cause 132188: The link between CPU and NP was detected faulty.
Cause 132191: The slave MPU reset signal of the board is abnormal.
Cause 132192: Board hardware encounters a chip single- or multi-channel failure or complete failure, poor resistor soldering, or sulphuration failure. As a result, a board ID single- or multi-bit failure occurs, causing the system to fail to read the correct board ID.
Cause 132193: The storage life cycle is approaching the maximum value.
Cause 132198: The encryption and decryption acceleration engine is abnormal.
Cause 132204: The cpu frequency of the board is abnormal.
Cause 132248: Failed to enable secure boot.
Cause 132255: The board working clock signal malfunctions.
Cause 132273: The management network port receives more than 2000 packets per second for 10 consecutive seconds.
Cause 132274: The Ethernet interface of Forward Engine is abnormal.
Cause 132305: Device certificate verify fail.
Cause 132307: An exception occurred due to the CPU MCU heartbeat loss exception.
Cause 132425: The FPGA1 logic of the board is abnormal.
Cause 132426: The FPGA2 logic of the board is abnormal.
Cause 132427: The FPGA3 logic of the board is abnormal.
Cause 132428: The FPGA4 logic of the board is abnormal.
Cause 132429: The FPGA5 logic of the board is abnormal.
Cause 132638: The number of lost intelligent heartbeats reached the alarm threshold.
Cause 132665: The NP chip is under back pressure status, this may cause traffic drop.

Procedure

Cause 132096: Power supply for a board was abnormal.
Collect trap, log, and configuration information, and contact technical support.
Cause 132097: The monitor bus of the board is abnormal.
1. If the board is neither reset nor powered off, and services on the board are normal, go to Step 4.

2. Power off the faulty board, 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 132098: The sc chip failed.
1. Run the reset slot command to reset the faulty SFU and check whether the alarm is cleared after the SFU is registered.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 2.
2. Replace the SFU and 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 132100: The slotid check of the board is abnormal.
1. If the board is neither reset nor powered off, and services on the board are normal, go to Step 4.

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 132101: The supply voltage 48V of the board is abnormal.
1. Run the display device command in the user view to check whether the device is installed with two power modules. If not, install the additional 48 V power module that is required to ensure normal power supply.

2. If the power supply for the board is abnormal and there is an alarm about faulty power modules, first handle the alarm. If the power supply for the board is normal but the alarm persists, go to Step 3.

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

4. End.
Cause 132102: The board cannot be properly powered on or powered off.
1. If the board is neither reset nor powered off, and services on the board are normal, go to Step 4.

2. Power off the faulty board, 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 132103: The batteries are invalid.
1. If an installed board has no services on it, check whether the board is properly installed, pins have bent, and the board connectors are faulty.

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

3. If the pins on the backplane have bent, do not install a new board into the improper slot. Contact technical support.

4. If only the board connectors are found to be faulty, replace the board.

5. If services on the board are normal, collect trap, log, and configuration information, and contact technical support.

6. End.
Cause 132104: The act signal of the MPU Board is abnormal.
Collect trap, log, and configuration information, and contact technical support.
Cause 132105: The sensor of the board is abnormal.
Collect trap, log, and configuration information, and contact technical support.
Cause 132108: The clock signal of the clock board is abnormal.
1. Check whether the two main control boards are securely installed. If not, install the them securely.

2. If an installed board has no services on it, check whether the board is properly installed, pins have bent, and the board connectors are faulty.

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

4. If the pins on the backplane have bent, do not install a new board into the improper slot. Contact technical support.

5. If only the board connectors are found to be faulty, replace the board.

6. If service have run on the faulty board but the alarm persists, collect trap, log, and configuration information, and contact technical support.

7. End.
Cause 132109: The voltage exceeded the upper limit of the fatal threshold.
1. If the power module fails, rectify the fault.

2. Run the display voltage slot slot-id command in the user view to check whether the actual voltage exceeds the upper critical threshold.

3. If the actual voltage exceeds the upper critical threshold, collect trap, log, and configuration information, and contact technical support.

4. End.
Cause 132110: The voltage exceeded the upper limit of the major threshold.
1. If the power module fails, first rectify the fault.

2. Run the display voltage slot slot-id command in the user view to check whether the actual voltage exceeds the upper major threshold.

3. If the actual voltage exceeds the upper major threshold, collect trap, log, and configuration information, and contact technical support.

4. End.
Cause 132111: The voltage was lower than the lower limit of the fatal threshold.
1. Run the display voltage slot slot-id command in the user view to check whether the actual voltage is lower than the lower critical threshold.

2. Check that the voltage of the external power supplier is adequate. Otherwise, increase the voltage of the external power supplier and check whether the alarm is cleared.
- If the alarm is cleared, no action is required.
- If the alarm persists, go to Step 3.
3. Replace the board and check whether the alarm is cleared.
- If the alarm is cleared, no action is required.
- If the alarm persists, go to Step 4.
4. Collect trap, log, and configuration information, and contact technical support.
Cause 132112: The voltage was lower than the lower limit of the major threshold.
1. Run the display voltage slot slot-id command in the user view to check whether the actual voltage is lower than the lower major threshold.

2. Check that the voltage of the external power supplier is adequate. Otherwise, increase the voltage of the external power supplier and check whether the alarm is cleared.
- If the alarm is cleared, no action is required.
- If the alarm persists, go to Step 3.
3. Replace the board and check whether the alarm is cleared.
- If the alarm is cleared, no action is required.
- If the alarm persists, go to Step 4.
4. Collect trap, log, and configuration information, and contact technical support.
Cause 132117: Clock signals on the board were faulty.
Collect trap, log, and configuration information, and contact technical support.
Cause 132118: The in-positon signal of the board were faulty.
1. If an installed board has no services on it, check whether the board is properly installed, pins have bent, and the board connectors become faulty.

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

3. If the pins on the backplane have bent, do not install a new board into the improper slot. Collect trap, log, and configuration information, and contact technical support.

4. If only the board connectors are found to be faulty, replace the board.

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

6. End.
Cause 132120: The IIC bus of the board is abnormal.
1. If the board is neither reset nor powered off, and services on the board are normal, go to Step 4.

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 132121: The USB controller on the board failed.
1. If the USB interface does not have the external memory, services are not affected, and no action is required.

2. If a USB interface is needed, use another USB interface on the faulty board or the USB interface on another main control board.

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

4. End.
Cause 132122: The CFcard of the MPU board is abnormal.
1. Remove and install the CF card and restart the board where the CF card resides as the standby main control board.

2. If the board is not registered, replace the faulty CF card and then restart the board.

3. If the board fails to be registered, replace the board.

4. Replace the faulty CF card and then restart the board. If the board is not registered or the alarm persists after the board is registered, replace the board where the faulty CF card resides.

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

6. End.
Cause 132127: The board clock malfunctions.
1. Replace the board in the corresponding slot and check whether the alarm is cleared.
- If the alarm is cleared, go to Step 3.
- If the alarm persists, go to Step 2.
2. Collect trap, log, and configuration information, and contact technical support.

3. End.
Cause 132128: The board PLL malfunctions.
1. Replace the board in the corresponding slot and check whether the alarm is cleared.
- If the alarm is cleared, go to Step 3.
- If the alarm persists, go to Step 2.
2. Collect trap, log, and configuration information, and contact technical support.

3. End.
Cause 132129: The FE PHY chip malfunctions.
1. Replace the board in the corresponding slot and check whether the alarm is cleared.
- If the alarm is cleared, go to Step 3.
- If the alarm persists, go to Step 2.
2. Collect trap, log, and configuration information, and contact technical support.

3. End.
Cause 132131: The keychip of the clock board is abnormal.
Collect trap, log, and configuration information, and contact technical support.
Cause 132134: LANSWITCH is abnormal.
1. Replace the board in the corresponding slot and check whether the alarm is cleared.
- If the alarm is cleared, go to Step 3.
- If the alarm persists, go to Step 2.
2. Collect trap, log, and configuration information, and contact technical support.

3. End.
Cause 132137: The CMAC chip failed the self check.
1. Restart the board. If the alarm persists, replace the board.

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

3. End.
Cause 132139: The voltage of the subcard exceeded the fatal upper threshold.
1. Run the display voltage lpu slot slot-id command to check the voltage information about the subcards. If the fault cannot be rectified within a short period of time, replace the subcard.

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

3. End.
Cause 132140: The voltage of the subcard exceeded the upper threshold.
1. Run the display voltage lpu slot slot-id command in the user view to check the voltage information about the subcards. If the fault cannot be rectified within a short period of time, replace the subcard.

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

3. End.
Cause 132141: The voltage of the subcard was below the lower fatal threshold.
1. Run the display voltage lpu slot slot-id command in the user view to check the voltage information about the subcards. If the fault cannot be rectified within a short period of time, replace the subcard.

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

3. End.
Cause 132142: The voltage of the subcard was below the warning lower threshold.
1. Run the display voltage lpu slot slot-id command in the user view to check the voltage information about the subcards. If the fault cannot be rectified within a short period of time, replace the subcard.

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

3. End.
Cause 132150: The idle space on the CF card is lower than the threshold.
1. Delete unwanted files on the device and check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
2. Collect trap, log, and configuration information, and contact technical support.

3. End.
Cause 132152: The CPU of the board partially failed.
Collect trap, log, and configuration information, and contact technical support.
Cause 132155: The link between the CMAC chip and the NP chip was detected faulty.
1. Reset the CMAC board. If the alarm persists, replace the board.

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

3. End.
Cause 132157:
Cause1: Capability of the traffic management chip was insufficient.

Cause2: The chip is abnormal.

Collect trap, log, and configuration information, and contact technical support.
Cause 132161: Board temperature sensors fault.
Collect trap, log, and configuration information, and contact technical support.
Cause 132163: The core of the board is abnormal.
1. If the user decides not to use the web fast reply and Netstream services, the alarm does not need to be concerned and no action is required.

2. If the user uses the web fast reply and Netstream services, replace the board.

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

4. End.
Cause 132164: Too many sensor points failed.
Collect trap, log, and configuration information, and contact technical support.
Cause 132169: The communication channel failed and change into another channel.
1. Replace the board.

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

3. End.
Cause 132170: The RTC on the board failed.
Collect trap, log, and configuration information, and contact technical support.
Cause 132173: The Security Acceleration Engine is abnormal.
Collect trap, log, and configuration information, and contact technical support.
Cause 132174: PCB Corrosive.
Collect trap, log, and configuration information, and contact technical support.
Cause 132177: Interface MAC CRC error.
1. Replace the board and check whether the alarm is cleared.
- If the alarm is cleared, go to Step 3.
- If the alarm persists, go to Step 2.
2. Collect trap, log, and configuration information, and contact technical support.

3. End.
Cause 132178: E-label CRC error.
1. Replace the board and check whether the alarm is cleared.
- If the alarm is cleared, go to Step 3.
- If the alarm persists, go to Step 2.
2. Collect trap, log, and configuration information, and contact technical support.

3. End.
Cause 132180: The first 48V power supply of the board is fault.
1. Replace the board.

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

3. End.
Cause 132181: The second 48V power supply of the board is fault.
1. Replace the board.

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

3. End.
Cause 132182: Board voltage sensors fault.
Collect trap, log, and configuration information, and contact technical support.
Cause 132183: Voltage A/D Fault.
Collect trap, log, and configuration information, and contact technical support.
Cause 132184: SPI Bus fault.
Collect trap, log, and configuration information, and contact technical support.
Cause 132187: The cp2np-phy on the board is abnormal.
Collect trap, log, and configuration information, and contact technical support.
Cause 132188: The link between CPU and NP was detected faulty.
Collect trap, log, and configuration information, and contact technical support.
Cause 132191: The slave MPU reset signal of the board is abnormal.
Collect trap, log, and configuration information, and contact technical support.
Cause 132192: Board hardware encounters a chip single- or multi-channel failure or complete failure, poor resistor soldering, or sulphuration failure. As a result, a board ID single- or multi-bit failure occurs, causing the system to fail to read the correct board ID.
1. If this is an FPIC, replace the FPIC. If this is a fixed-configuration device, replace the device. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 3.
- If the alarm persists, go to Step 2.
2. Collect trap, log, and configuration information, and contact technical support.

3. End.
Cause 132193: The storage life cycle is approaching the maximum value.
1. Replace the board and check whether the alarm is cleared.
- If the alarm is cleared, go to Step 3.
- If the alarm persists, go to Step 2.
2. Collect trap, log, and configuration information, and contact technical support.

3. End.
Cause 132198: The encryption and decryption acceleration engine is abnormal.
Collect trap, log, and configuration information, and contact technical support.
Cause 132204: The cpu frequency of the board is abnormal.
1. Perform an active/standby board switchover. Then check whether the alarm is cleared.
- If the alarm is cleared, go to Step 2.
- If the alarm persists, go to Step 3.
2. Check whether the alarm is generated again within 24 hours.
- If so, go to Step 3.
- If not, go to Step 4.
3. Collect trap, log, and configuration information, and contact technical support.

4. End.
Cause 132248: Failed to enable secure boot.
1. Reconfigure the secure boot flag.

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

3. End.
Cause 132255: The board working clock signal malfunctions.
1. Replace the board in the corresponding slot and check whether the alarm is cleared.
- If the alarm is cleared, go to Step 3.
- If the alarm persists, go to Step 2.
2. Collect trap, log, and configuration information, and contact technical support.

3. End.
Cause 132273: The management network port receives more than 2000 packets per second for 10 consecutive seconds.
Collect trap, log, and configuration information, and contact technical support.
Cause 132274: The Ethernet interface of Forward Engine is abnormal.
Collect trap, log, and configuration information, and contact technical support.
Cause 132305: Device certificate verify fail.
Reset the board and check whether the fault is rectified. If the fault persists, replace the board.
Cause 132307: An exception occurred due to the CPU MCU heartbeat loss exception.
Collect trap, log, and configuration information, and contact technical support.
Cause 132425: The FPGA1 logic of the board is abnormal.
1. If the board is not reset or powered off and services are running properly, collect alarm, log, and configuration information and contact technical support. 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, replace the faulty board.

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

5. End.
Cause 132426: The FPGA2 logic of the board is abnormal.
1. If the board is not reset or powered off and services are running properly, collect alarm, log, and configuration information and contact technical support. 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, replace the faulty board.

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

5. End.
Cause 132427: The FPGA3 logic of the board is abnormal.
1. If the board is not reset or powered off and services are running properly, collect alarm, log, and configuration information and contact technical support. 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, replace the faulty board.

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

5. End.
Cause 132428: The FPGA4 logic of the board is abnormal.
1. If the board is not reset or powered off and services are running properly, collect alarm, log, and configuration information and contact technical support. 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, replace the faulty board.

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

5. End.
Cause 132429: The FPGA5 logic of the board is abnormal.
1. If the board is not reset or powered off and services are running properly, collect alarm, log, and configuration information and contact technical support. 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, replace the faulty board.

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

5. End.
Cause 132638: The number of lost intelligent heartbeats reached the alarm threshold.
Collect trap, log, and configuration information, and contact technical support.
Cause 132665: The NP chip is under back pressure status, this may cause traffic drop.
Collect trap, log, and configuration information, and contact technical support.