ALM-135462958 hwBoardInvalid

Attribute

Parameters

Procedure

• Cause 1: The power supplied to the board is insufficient.
  1. Collect trap, log, and configuration information, and contact technical support.
• Cause 6: The EPLD logic of the board failed.
  1. Check whether the faulty board is the active board.
     • If yes, perform the active/standby switchover when the standby board is normal.
     • If not, go to 2.
  2. 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 7: The in-position board type conflicts with the pre-configured board type.
  1. Change the pre-configured conflict policy to be based on the physical configuration.
  2. Delete the pre-configured board configuration at the position.
  3. Remove the board.
  4. Clear the offline configuration of the slot.
• Cause 8: The clock signals of the board were incorrect.
  1. Check whether the faulty board is reset or powered off and whether services are running properly.
     • If the board is not reset or powered off and services are running properly, go to 4.
     • If the board is reset or powered off, or services are abnormal, go to 2.
  2. Power off and then power on the faulty board.
     • If the board registers successfully and the fault is rectified after the registration, go to 5.
     • If the board cannot be registered or the alarm persists after the board is registered, go to 3.
  3. Replace the fault board.
     • If the board registers successfully and the fault is rectified after the registration, go to 5.
     • If the board cannot be registered or the alarm persists after the board is registered, go to 4.
  4. Contact technical support personnel.
  5. End.
• Cause 9: The board does not support some configurations and cannot register.
  1. The current system does not support the board. Remove the board.
• Cause 10: The board does not match the device.
  1. The current subrack does not support the board. Remove the board.
• Cause 11: The FPGA local bus self-check failed.
  1. If the faulty board is not the active main control board, go to 3.
  2. If the slave main control board is normal, run the slave switchover command in the system view to perform a master/slave main control board switchover. Then go to 1.
  3. Power off and then power on the faulty board.
  4. If the fault persists, replace the faulty board.
• Cause 12: The SD5K communication failed.
  1. Collect alarm, log, and configuration information, and contact technical support personnel.
• Cause 13: The board obtained abnormal signals from the master and slave MPUs.
  1. Check whether the two MPUs are installed properly. If not, install them 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 services are not running on the faulty board, perform the following operations. If the fault is rectified, go to step 4. Otherwise, go to step 3.
     • If the board is not properly installed, install it properly.
     • If the backplane has bent pins, do not insert the new board into the faulty slot and contact Huawei technical support personnel.
     • If the board connector is faulty, replace the board.
  3. If services are running on the faulty board or the fault persists, contact technical support personnel.
  4. End.
• Cause 14: The device hardware verification failed.
  1. Reset the board and check whether the fault is rectified. If the fault persists, replace the board.
• Cause 19: TCAM chip failed.
  1. Check whether the faulty board is reset or powered off and whether services are running properly.
     • If the board is not reset or powered off and services are running properly, go to 4.
     • If the board is reset or powered off, or services are abnormal, go to 2.
  2. Power off and then power on the faulty board.
     • If the board registers successfully and the fault is rectified after the registration, go to 5.
     • If the board cannot be registered or the alarm persists after the board is registered, go to 3.
  3. Replace the faulty board.
     • If the board registers successfully and the fault is rectified after the registration, go to 5.
     • If the board cannot be registered or the alarm persists after the board is registered, go to 4.
  4. Contact technical support.
  5. End
• Cause 20: The FPGA entry of the board may be faulty.
  1. Check whether the faulty board is reset or powered off and whether services are running properly.
     • If the board is not reset or powered off and services are running properly, go to 4.
     • If the board is reset or powered off, or services are abnormal, go to 2.
  2. Power off and then power on the faulty board.
     • If the board registers successfully and the fault is rectified after the registration, go to 5.
     • If the board cannot be registered or the alarm persists after the board is registered, go to 3.
  3. Replace the faulty board.
     • If the board registers successfully and the fault is rectified after the registration, go to 5.
     • If the board cannot be registered or the alarm persists after the board is registered, go to 4.
  4. Contact technical support.
  5. End.
• Cause 21: The PCIE of the board was faulty.
  1. Check whether the faulty board is reset or powered off and whether services are running properly.
     • If the board is not reset or powered off and services are running properly, go to 4.
     • If the board is reset or powered off, or services are abnormal, go to 2.
  2. Power off and then power on the faulty board.
     • If the board registers successfully and the fault is rectified after the registration, go to 5.
     • If the board cannot be registered or the alarm persists after the board is registered, go to 3.
  3. Replace the faulty board.
     • If the board registers successfully and the fault is rectified after the registration, go to 5.
     • If the board cannot be registered or the alarm persists after the board is registered, go to 4.
  4. Contact technical support.
  5. End.
• Cause 22: The board is not installed properly.
  1. Check whether the line card is installed properly. If not, install the line card properly and check whether the fault is rectified. If the alarm persists, go to 2.
  2. Collect trap, log, and configuration information, and contact technical support.
• Cause 23: The PCIE link of the FPGA and slave CXP is faulty.
  1. Collect alarm, log, and configuration information, and contact technical support personnel.
• Cause 24: Board burnt due to high PoE power.
  1. Collect trap and log information, and contact Huawei technical support.
• Cause 26: The master or slave ACT signal of the MPU board is abnormal.
  1. Check whether other boards have low voltage alarms or power-related alarms. If so, clear the alarms first.
  2. Remove and reinstall the current standby main control board. Check whether the board is properly installed, whether there are bent pins, and whether the board connector is faulty. If so, go to step 4.
  3. If the device is reset, remove the other main control board and check whether the main control board is properly installed, whether there are bent pins, and whether the board connector is faulty. If so, go to step 4.
  4. If the board is not properly inserted, insert the board properly.
  5. If the backplane has bent pins, do not insert a new board into the slot and contact the technical support personnel.
  6. If only the connector of the faulty board is faulty, replace the board and go to step 8.
  7. If the standby main control board is not registered or the alarm persists, contact the technical support personnel.
  8. End.
• Cause 33: The board was not registered.
  1. Collect trap, log, and configuration information, and contact technical support.
• Cause 66: The board failed to register after three registration attempts.
  1. Collect alarm, log, and configuration information, and contact technical support.
• Cause 67: A board was powered off.
  1. Replace the board and check whether the alarm is cleared. If the alarm persists, go to 2.
  2. Collect trap, log, and configuration information, and contact technical support.
• Cause 68: The board was powered on.
  1. The board is powered on.
• Cause 69: The FPGA of the board failed.
  1. Determine the slot ID of the faulty board based on EntPhysicalName. The first digit after fpga indicates the FPGA chip ID, and the second and subsequent digits indicate the slot ID of the board. For example, EntPhysicalName=fpga1 3 indicates that FPGA1 in slot 3 is faulty.
  2. If the faulty board cannot be registered after being restarted or the alarm cannot be cleared after being registered, replace the faulty board.
  3. If the faulty board is not restarted or powered off and services are running properly, contact technical support personnel.
• Cause 70: The board does not match the slot.
  1. The current slot does not support the board. Remove the board.
• Cause 80: The power supply self-check failed.
  1. Collect trap, log, and configuration information, and contact technical support.
• Cause 85: The smi serial of the board is abnormal.
  1. Collect alarm, log, and configuration information, and contact technical support personnel.
• Cause 87: The card failed to be registered.
  1. Remove and then insert the subcard. If the faulty subcard still cannot be registered, replace the faulty subcard and check whether the fault is rectified. If the alarm persists, go to step 2.
  2. Collect alarm, log, and configuration information, and contact technical support.
• Cause 98: The EPLD logic of the board failed.
  1. If the faulty board is not the active main control board, go to Step 3.
  2. If the standby main control board is normal, perform an active/standby switchover in the system view and go to Step 1.
  3. If the faulty board is already registered, run the upgrade mpu/lpu/sfu <slotid> startup firmware command in the user view to upgrade the CPID, and go to Step 5.
  4. If the faulty board is not registered, power off and then power on the board.
  5. If the faulty board cannot be registered or the fault persists after registration, replace the faulty board.
• Cause 99: The FPGA local bus self-check failed.
  1. Collect alarm, log, and configuration information, and contact technical support.
• Cause 123: The board voltage exceeded the major alarm threshold.
  1. Collect trap, log, and configuration information, and contact technical support.
• Cause 124: The board voltage fell below the major alarm threshold.
  1. Collect trap, log, and configuration information, and contact technical support.
• Cause 125: The board voltage exceeds the fatal alarm threshold.
  1. Collect alarm, log, and configuration information, and contact technical support personnel.
• Cause 126: The board voltage fell below the fatal alarm threshold.
  1. Collect alarm, log, and configuration information, and contact technical support personnel.
• Cause 127: The board is incompatible with the software version.
  1. Collect alarm, log, and configuration information, and contact technical support.
• Cause 128: Different SFUs were installed in the same chassis.
  1. Run the clear inactive-configuration command to clear the offline configuration.
  2. Remove and then insert the faulty board or power on the faulty board. Then, check whether the fault is rectified.
     • If the fault is rectified, go to Step 4.
     • If the fault persists, go to Step 3.
  3. Collect alarm, log, and configuration information, and contact technical support.
  4. End.
• Cause 130: The card is incompatible with board.
  1. Remove the subcard and install a subcard that is compatible with the board type.