DEVM/1/hwEntityInvalid_active

Message

DEVM/1/hwEntityInvalid_active: Physical entity failed. (BaseTrapSeverity=[BaseTrapSeverity], BaseTrapProbableCause=[ProbableCause], BaseTrapEventType=[BaseTrapEventType], EntityPhysicalIndex=[EntityPhysicalIndex], EntPhysicalContainedIn=[EntContainedIn], EntPhysicalName=[EntPhysicalName], RelativeResource=[RelativeResource], ReasonDescription=[ReasonDescription])

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

Description

Physical entity failed.

Parameters

Parameter Name Parameter Meaning

BaseTrapSeverity

To describe the level of trap.

ProbableCause

To describe the probable cause of trap.

BaseTrapEventType

To describe the type of trap.

EntityPhysicalIndex

The index of the physical entity.

EntContainedIn

The value of entPhysicalIndex for the physical entity.

EntPhysicalName

The textual name of the physical entity.

RelativeResource

This object may contain a key word to indicate the relative resource of an entity.

ReasonDescription

To describe the reason of trap in DisplayString style.

Possible Causes

  • Cause 1: A link port on the MPU became Down.
  • Cause 2: An inter-chasssis channel between MPUs or between an MPU and an ICU became faulty.
  • Cause 3: The channel between ICUs became faulty.
  • Cause 4: The channel between pannel eth0 of ICUs became faulty.
  • Cause 5: A port on the ICU became Down.
  • Cause 6: A loop is formed between ICU(s), either because two connections are established between ICUs or two ports of the same ICU are interconnected.
  • Cause 7: Two MPUs of a CLC were connected to the same ICU.
  • Cause 8: Two MPUs of a CCC were incorrectly connected to ICUs.
  • Cause 9: An unauthorized device has connected with the cluster system.
  • Cause 65541: Vsr slot-id is failed,the optical module was removed.
  • Cause 66048: The board in-position signal was faulty.
  • Cause 67587: The clock signal of clock board is abnormal.
  • Cause 67590: The temperature sensor was faulty.
  • Cause 67591: The hardware of the fan was faulty.
  • Cause 67592: The hardware of the fan was faulty.
  • Cause 67593:

    Cause1:A power module failed.A fault occurred on the power module.

    Cause2:Internal communication failed for a power module. Communication between the power module and main processing unit in the same chassis failed.

  • Cause 67594:

    Cause1:A PMU was not detected. A PMU was removed or insecurely inserted.

    Cause2:The power supply module was not properly installed.The power supply module is absent.

  • Cause 67595: The fan frame was absent.
  • Cause 67596: slotid%s is failed, LCD is absent.
  • Cause 67597: slotid%s is failed, LCD screen is failed.
  • Cause 67598: slotid%s is failed, LCD hardware is abnormal.
  • Cause 67599: The cables of the fan frame were absent.
  • Cause 67600: slotid%s is failed, LCD cable is unplugged.
  • Cause 67601: The power cables were absent.
  • Cause 67602: The EEPROM component fails.
  • Cause 67603: The Monitor bus was faulty.
  • Cause 67604: The communication of the Monitor bus failed. This trap indicates that the Monitor bus was faulty.
  • Cause 67608: The output voltage of a power module exceeded a specified threshold.
  • Cause 67609: The output voltage of a power module exceeded a rated range.
  • Cause 67610: The output voltage of a power module was below a specified threshold.
  • Cause 67611: The output voltage of a power module was below a rated range.
  • Cause 67612: The output voltage of a power module exceeded the upper threshold.
  • Cause 67613: The current of a power module exceeded a rated range.
  • Cause 67614: The power module's output was cut off.
  • Cause 67615: The input voltage of a power module exceeded a specified threshold.
  • Cause 67616: The input voltage of a power module exceeded a rated range.
  • Cause 67617: The input voltage of a power module was below a specified threshold.
  • Cause 67618: The input voltage of a power module was below a rated range.
  • Cause 67619: The input voltage of a power module fell below the lower threshold.
  • Cause 67620:

    Cause1:AC power: The module's internal temperature exceeded a rated range, and consequently its power output was cut off.

    Cause2:DC power: The module's internal temperature exceeded the rate range. As a result, its auxiliary output was cut off (the main output that supplies power to the board remains unaffected).

  • Cause 67621: A power module's internal temperature was too high and would reach the specified threshold.
  • Cause 67622: The power module received an incorrect instruction.
  • Cause 67623: The input data was not supported.
  • Cause 67624: A fault occurred on the internal processor of a power module.
  • Cause 67625: A power module failed to communicate with the MPU, which does not affect power supply.
  • Cause 67626: The fan of the AC or DC power module was faulty.
  • Cause 67627: The input fuse of a power module was faulty or the link was disconnected.
  • Cause 67628: The input fuse of a power module was faulty or the link was disconnected.
  • Cause 67629: One of the internal switches on a power module was not closed.
  • Cause 67630: One of the internal power supply arresters of the DC power supply module was faulty.
  • Cause 67631: Output voltage of the DC power supply module was abnormal.
  • Cause 67632: Input voltage of the DC power supply module was below the rated value.
  • Cause 67633:

    Cause 1: An internal submodule was not properly installed.

    Cause 2: An internal submodule failed.

  • Cause 67634: The AC power supply module was faulty.
  • Cause 67638: The power module was properly installed but was not powered on.
  • Cause 67642: The key chip clock board is abnormal.
  • Cause 67643: Slot slotID is failed, 2M Apll Unlock.
  • Cause 67644: Slot slotID is failed, the heart beat of clock board is loss.
  • Cause 67652: Slot %s is failed, the clock signal %s of the Board is abnormal.
  • Cause 67653: The reference clock source on the SFU was faulty.
  • Cause 67654: LPU slot slotID is failed,the memory QDR of the TMtmID is abnormal.
  • Cause 67656: LPU slot slotID is failed,the key chip of the TMtmID is abnormal.
  • Cause 67657: LPU slot slotID is failed,the data link status to PE of the TMtmID is abnormal.
  • Cause 67659: The signal carrying the information about the slot where the interface board resided was disturbed.
  • Cause 67660:

    Cause1:The second 48 V power supply failed:

    The second power module was not installed or The second power module failed.

    Cause2:One or both power supplies failed,No external power supply was available for one or both power modules.

    Cause3:The two PMU monitor buses failed.

  • Cause 67661: The signal carrying the slot information sent from the MPU to the interface board was abnormal.
  • Cause 67669: Slot slotID is failed, PEPEID is abnormal.
  • Cause 67688: The optical module temperature is too high.
  • Cause 67689: The optical module temperature is too low.
  • Cause 67690: Optical module voltage is too high.
  • Cause 67691: The optical module voltage is too low.
  • Cause 67692: The optical module bias is too low.
  • Cause 67693: The optical module bias is too high.
  • Cause 67694: The output power of the optical module was too high.
  • Cause 67695: The transmitting power of the optical module is too low.
  • Cause 67696: The receiving power of the optical module is too high.
  • Cause 67697: The receiving power of the optical module is too low.
  • Cause 67701: The possible cause may be that the hardware of the MPU was faulty.
  • Cause 67708: The power of the FCB was faulty.
  • Cause 67709:

    Cause 1: The board PCI bus was abnormal.

    Cause 2: The NSE PCI was abnormal.

  • Cause 67721: LPU slot slotIDis failed,the link number to fabric of the TMtmID is not enough.
  • Cause 67722: Slot slotID is failed, the mpu act signal of the Board is abnormal.
  • Cause 67726: The batteries on the MPU failed to function normally.
  • Cause 67727: LPU slotID is failed, the data link to PIC of PEPEID is abnormal
  • Cause 67734: Slot slotID is failed, the mpu act signal of the Board is abnormal.
  • Cause 67735: Obtaining the manufacture information about the power supply module failed.
  • Cause 67737: The I2C channel was faulty
  • Cause 67739: The sensor on the subcard(or board) is faulty.
  • Cause 67740:

    Cause1:The board power was insufficient.

    Cause2:The device power was insufficient.

    Cause3:The number of power modules was less than required.

    Cause4:A power supply plane was unable to supply power with high reliability.

  • Cause 67743: Vsr VsrId is failed, the optical module of the OFC is abnormal.
  • Cause 67744:

    Cause1: The 125 MHz clock source failed.

    Cause2.:The differential transmission line failed.

  • Cause 67745: LPU slot slotID is failed,the memory ZBT of the TMtmID is abnormal.
  • Cause 67746: Vsr VsrId is failed,the optic connection is abnormal.
  • Cause 67755: The flash in slot slotid is abnormal.
  • Cause 67762: SFU is failed, SFU in chassis chassisid is not full.
  • Cause 67763: MPU is failed, MPU in chassis chassisid is not full.
  • Cause 67765:

    Cause 1: The software of the board is faulty.

    Cause 2: The hardware of the TCAM is faulty.

  • Cause 67771:

    Cause 1:The EPLD logic file was faulty.

    Cause 2: The EPLD hardware was faulty.

    Cause 3: The EPLD version is different from that of the system.

  • Cause 67796:

    Cause1: PCI BUS: indicates errors related to the PCI BUS.

    Cause2: Clock check: indicates errors related to the logic clock.

    Cause3: Tcam BUS: indicates errors related to the TCAM BUS.

    Cause4: Tcam ID: indicates errors related to the ASE TCAM ID.

    Cause5: Tcam array parity: indicates errors related to the Tcam array entry.

    Cause6: Ddr Parity: indicates errors related to the Ddr entry.

    Cause7: LA-1 Parity: indicates parity errors of the QDR interface.

  • Cause 67837: The PE hardware or NSE chip hardware on the board was faulty.
  • Cause 67838: A hardware fault occurs on the TCAM chip.
  • Cause 67840: ECC detected faults when the memory read and wrote DDR SDRAM of the CPU.
  • Cause 67842: The signal for the board being properly installed was incorrect.
  • Cause 67900: LPU slot slotID is failed,the key chip StatLogic of the TMtmID is abnormal.
  • Cause 67905: LPU slot slotID is failed,the key chip IftLogic of the TMtmID is abnormal.
  • Cause 67921: SWF slot slot-id is failed, all the links of the board are unavailable.
  • Cause 67922: Power slotid, %s is failed, the pem type does not match the type of the backplane.
  • Cause 67923: Fan slotid is failed, the fan type does not match the type of the backplane.
  • Cause 67924: Slot slotID did not match the device.
  • Cause 67952: Logic 1 of the board failed.
  • Cause 67953: Logic 2 of the board failed.
  • Cause 67969: The interface board is failed, the adaptive clock translator's output of the Board is abnormal.
  • Cause 67970: A fault occurred in 33 MHz clock signals on the board.
  • Cause 67971: A communication failure occurred on the fan module.
  • Cause 67995: The air filter inside the chassis chassisid was not cleaned.
  • Cause 67999: Slot slotid is failed, the slotID check is failed.
  • Cause 68006: Slot slotid is failed, the clock signal level3Clock of clock board is abnormal.
  • Cause 68007: Slot slotid is failed, the clock signal 3Clock of board is abnormal.
  • Cause 68008: Slot slotid is failed, the first erode-protect unit is break.
  • Cause 68010: Slot slotid is failed, the control bus PCIE of board is abnormal.
  • Cause 68011: Slot slotid is failed, the cpu internal module of the Board is abnormal.
  • Cause 68015:

    Cause 1:The PCI was abnormal.

    Cause 2:The internal clock of the PE or NSE was out of lock.

    Cause 3:The clock of the TCAM was out of lock.

  • Cause 68016: LPU slotID is failed, , the data link to TM of PEPEID is abnormal.
  • Cause 68017: LPU slotID is failed, the clock signals of the PEPEID is abnormal.
  • Cause 68018: LPU slotID is failed, PLLOUT of PE is abnormal.
  • Cause 68035: The clock component of a board failed.
  • Cause 68040: The FPGA fault was detected on the PIC card.
  • Cause 68043: SFU clock check fault.
  • Cause 68049: The BSP module detected a fault on the key chip EEPROM or IIC bus on a board.
  • Cause 68050:

    Cause 1:The management channel of the USB controller was faulty.

    Cause 2:The PCIE bridge was faulty.

  • Cause 68051:

    Cause 1:The management channel of the GE LSW was abnormal.

    Cause 2:The PCIE bridge was faulty.

  • Cause 68052:

    Cause 1:The management channel of the FE LSW was abnormal.

    Cause 2:The PCIE bridge was faulty.

  • Cause 68054: Cause 1: The hardware of the MDC/MDIO channel to the PHY is faulty. Cause 2: The PHY chip is abnormal
  • Cause 68055: The SFU clock synchronization is abnormal.
  • Cause 68056: The Board is failed, the mdio bus of this port is not ok.
  • Cause 68057: The clock unit on the subcard was faulty.
  • Cause 68059: The optical transceiver of the PIC card was found abnormal.
  • Cause 68060: The fault in the key chip of the PIC card was detected.
  • Cause 68062: The NP fault was detected on the PIC card.
  • Cause 68064: The NP fault was detected on the PIC card.
  • Cause 68065: The data channel fault was detected on the PIC card.
  • Cause 68067: The Heartbeat of PIC is abnormal.
  • Cause 68074: The output voltage of slot slotid failed.
  • Cause 68085: Too many SFU links were shut down for crc, loopback, FDR, updown.
  • Cause 68095: The optical module type did not match the interface type.
  • Cause 68130: Power current not average.
  • Cause 68131: Power canbus is abnormal.
  • Cause 68132: Power current exceed the max value.
  • Cause 68133: Power module merge current fail.
  • Cause 68134: slotid%s is failed, the RTC clock is abnormal.
  • Cause 68135: The PMU was faulty.
  • Cause 68136: slotid%s is failed, the MonitorBUS is abnormal.
  • Cause 68137: Powerbackplane failed Because of the cable is disconnected.
  • Cause 68138: Fan link board offline.
  • Cause 68140: The CPU on the interface board was faulty.
  • Cause 68143: The fast switchover port %d of MPU %s was connected incorrectly.
  • Cause 68144: The fast switchover port %d of MPU %s became disconnected.
  • Cause 68147: The link-heartbeat detection packet was modified on the link.
  • Cause 68148: The link-heartbeat detection packet was dropped on the link.
  • Cause 68153:

    Cause 1: The PE's chip failed.

    Cause 2: An error occurred on the PE's forwarding table read-write processing program.

  • Cause 68154: The PMU was offline.
  • Cause 68155:

    Cause 1: The external power supply was insufficient.

    Cause 2: The PM was either faulty or removed.

  • Cause 68156: The PM was either faulty or removed.
  • Cause 68157:

    Cause1: External power inputs are needed.

    Cause2: A fault occurred on the power module.

  • Cause 68160: The PLD or Flash initializatiaon fault.
  • Cause 68161: The power supply fault .
  • Cause 68162: The CFP checksum fault.
  • Cause 68163: The fan frame was present.
  • Cause 68165: In a CCC-0 system consisting of an NE5000E-X16A and a CLC of other types, the NE5000E-X16A functioned as the slave chassis.
  • Cause 68166:

    Cause1: The 100G/400G OFC has plugged in 25G CXP.

    Cause2: The 1T OFC in CLC chasis of cluster form has plugged in 10G CXP.

  • Cause 68167: The license item is not activated.
  • Cause 68168: The license item will expire.
  • Cause 68169: A power consumption limit was configured, resulting in inadequate system power supply.
  • Cause 68170: The app of the power module is abnormal.
  • Cause 68171: The cpu frequency of the board is abnormal.
  • Cause 68172: The CPU of the board partially failed.
  • Cause 68175: The fan was installed unstably.
  • Cause 68176: The communication between the CMUs is abnormal.
  • Cause 68177: The dustproof gate is not closed and has been opened for more than the detection time.
  • Cause 68178: The CMU is not registered.
  • Cause 68179: Fan is failed, Fan in chassis chassisid is not full.
  • Cause 68180: CMU do not match with product brand.
  • Cause 68181: The CMU communication or signal is abnormal.
  • Cause 68182: The channel between the power module and the device failed.
  • Cause 68183: The power supply on the power module is faulty.
  • Cause 68184: The power type does not match the type of the backplane.
  • Cause 68185: CMUs were not fully configured.
  • Cause 68187: Fan slotid is failed, the fan type does not match the type of the sfu.
  • Cause 68190: The PTN mode of the master chassis in a virtual cluster device is different from that of the slave chassis.
  • Cause 68191: The actual power-on status of the chip is not as expected.
  • Cause 68197: Abnormal temperature of the secondary CDU
  • Cause 68198: The secondary CDU pressure is abnormal.
  • Cause 68205: Liquid leakage fault
  • Cause 68206: Valve fault
  • Cause 68214: AC fault
  • Cause 68218: CDU communication failure.
  • Cause 68224: The SMI serial of the board is abnormal.
  • Cause 68225: IPUs with different forwarding capabilities were inserted on the device.
  • Cause 68226: SFU MPI control bus check fault.
  • Cause 68227: Device certificate verify fail.
  • Cause 68229: An exception occurred due to the CPU MCU heartbeat loss exception.
  • Cause 68232: The fan power fails to be unlocked.
  • Cause 69131: The board was powered off.
  • Cause 69501: A power input channel for the filtering box of the fan was interrupted.
  • Cause 69502: The filtering box of the fan was missing or improperly installed.
  • Cause 69503: CMU switch is abnormal.
  • Cause 69505: LPU slotID is failed, the control bus of PEPEID is abnormal.
  • Cause 69507: LPU slotID is failed, the data link of the PE IntfLogic is abnormal.
  • Cause 69510: LPU slot slotID is failed,the interlaken to PIC of the PE is abnormal.
  • Cause 69512: The voltage status of the subcard is abnormal.
  • Cause 69517: Fuse slotid%s is failed, Fuse is absent.
  • Cause 69632: LPU slotID is failed, the memory QDR of PE PEID is abnormal.
  • Cause 69634: LPU slot slotID is failed,the inner status of the TMtmID is abnormal.
  • Cause 132631: The packet loss count of TM on slot slotid exceeded the alarm threshold.
  • Cause 132648: SFU MPI control bus check fault.

Procedure

  • Cause 1: A link port on the MPU became Down.

    1. Check whether the signal of the corresponding port of the main control board is flashing. If the interframe connection is plugged in but the semaphore still does not blink, replace it with a new network cable and check whether the alarm is cleared.

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

    2. Change the main control board 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 2: An inter-chasssis channel between MPUs or between an MPU and an ICU became faulty.

    1. Replace the main control 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 3: The channel between ICUs became faulty.

    1. Check whether the signal of the corresponding port of the ICU board is flashing. If the interframe connection is plugged in but the semaphore still does not blink, replace it with a new network cable and check whether the alarm is cleared.

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

    2. Change the main control board 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 4: The channel between pannel eth0 of ICUs became faulty.

    1. Check whether the signal of the corresponding port of the ICU board is flashing. If the interframe connection is plugged in but the semaphore still does not blink, replace it with a new network cable and check whether the alarm is cleared.

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

    2. Change the main control board 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 5: A port on the ICU became Down.

    1. Check whether the signal of the corresponding port of the ICU board is flashing. If the interframe connection is plugged in but the semaphore still does not blink, replace it with a new network cable and check whether the alarm is cleared.

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

    2. Change the main control board 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 6: A loop is formed between ICU(s), either because two connections are established between ICUs or two ports of the same ICU are interconnected.

    1. Check the EntPhysicalName field in the alarm information to determine which two interfaces form a ring and remove the cable from the corresponding port. 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 7: Two MPUs of a CLC were connected to the same ICU.

    1. Check the EntPhysicalName field in the alarm information to determine the access chassis in which two main control boards are connected to the same ICU. Connect one of the main control board in the access chassis to another ICU. 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 8: Two MPUs of a CCC were incorrectly connected to ICUs.

    1. Check the EntPhysicalName field in the alarm information to determine which main control board is connected incorrectly. Connect the main control board properly. 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 9: An unauthorized device has connected with the cluster system.

    1. Remove the illegal 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 65541: Vsr slot-id is failed,the optical module was removed.

    1. Check whether the optical module is in position.

    • If so, go to Step 3.
    • If not, go to Step 2.

    2. Insert the optical module 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 66048: The board in-position signal was faulty.

    1. Check whether the board is in position. Remove and insert the board again to ensure that the board is in position. Then, check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67587: The clock signal of clock board is abnormal.

    1. Check whether the board is reset or powered off.

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. Power on the board 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 67590: The temperature sensor was faulty.

    1. Run the power on and the power off commands on the faulty board. After the board is registered, check whether the alarm is cleared.

    • If so, go to Step 2.
    • If not, go to Step 5.

    2. Insert and remove the board. After the board is re-registered, check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 5.

    3. Replace the board and check whether the alarm is cleared.

    • If so, go to step 5.
    • If not, go to Step 4.

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

    5. End.

  • Cause 67591: The hardware of the fan was faulty.

    1. Check whether the fan frame is installed well. Remove and insert the fan frame to ensure that it is installed well. Run the display fan command to check the status of the fan. Then, check whether the fan works properly and the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the fan 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 67592: The hardware of the fan was faulty.

    1. Check whether the fan frame is installed well. Remove and insert the fan frame to ensure that it is installed well. Run the display fan command to check the status of the fan. Then, check whether the fan works properly and the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the fan 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 67593:

    Cause1:A power module failed.A fault occurred on the power module.

    Cause2:Internal communication failed for a power module. Communication between the power module and main processing unit in the same chassis failed.

    1. Check whether the power module is connected properly and the power switch is off. If so, switch on the power. Check whether the input of the power module is normal. If not, install the power module properly. Then, check whether the alarm is cleared after the external input is complete.

    • If so, go to Step 5.
    • If not, go to Step 2.

    2. Check whether the power module is inserted completely. Then, check whether the alarm is cleared after the power module is removed and inserted again.

    • If so, go to Step 5.
    • If not, go to Step 3.

    3. Replace the power module and check whether the alarm is cleared.

    • If so, go to Step 5.
    • If not, go to Step 4.

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

    5. End.

  • Cause 67594:

    Cause1:A PMU was not detected. A PMU was removed or insecurely inserted.

    Cause2:The power supply module was not properly installed.The power supply module is absent.

    1. Check whether the power module is inserted completely. If the power module is in position, remove and insert the power module. Then, check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    3. Replace the power module and check whether the alarm is cleared.

    • If so, go to Step 5.
    • If not, go to Step 4.

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

    5. End.

  • Cause 67595: The fan frame was absent.

    1. Check whether the fan frame is removed. If so, insert the fan frame. Then, check whether the trap is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the fan frame and check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 3.

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

    4. End.

  • Cause 67596: slotid%s is failed, LCD is absent.

    1. Check whether the LCD is removed or the cables are not connected well.

    • If so, go to step 2.
    • If not, go to step 3.

    2. If the LCD is installed, open the LCD. Remove the cables connecting the serial interfaces and re-connect the cables. Then, check whether the trap is cleared.

    • If so, go to Step 5.
    • If not, go to Step 3.

    3. Replace the LCD and check whether the trap is cleared.

    • If so, go to Step 5.
    • If not, go to Step 4.

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

    5. End.

  • Cause 67597: slotid%s is failed, LCD screen is failed.

    1. Check whether the LCD is removed or the cables are not connected well.

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. If the LCD is installed, open the LCD. Remove the cables connecting the serial interfaces and re-connect the cables. Then, check whether the alarm is cleared.

    • If so, go to Step 5.
    • If not, go to Step 3.

    3. Replace the LCD and check whether the alarm is cleared.

    • If so, go to Step 5.
    • If not, go to Step 4.

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

    5. End.

  • Cause 67598: slotid%s is failed, LCD hardware is abnormal.

    1. Check whether the LCD is removed or the cables are not connected well.

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. If the LCD is installed, open the LCD. Remove the cables connecting the serial interfaces and re-connect the cables. Then, check whether the alarm is cleared.

    • If so, go to Step 5.
    • If not, go to Step 3.

    3. Replace the LCD and check whether the alarm is cleared.

    • If so, go to Step 5.
    • If not, go to Step 4.

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

    5. End.

  • Cause 67599: The cables of the fan frame were absent.

    1. Remove and insert the faulty fan again. Then, check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67600: slotid%s is failed, LCD cable is unplugged.

    1. Reinstall the LCD cable and check whether the fault is rectified.

    • If yes, go to step 3.
    • If no, go to step 2.

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

    3. End.

  • Cause 67601: The power cables were absent.

    1. Reconnect the power cable, and then check whether the alarm is cleared.

    • If yes, go to step 3.
    • If no, go to step 2.

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

    3. End.

  • Cause 67602: The EEPROM component fails.

    1. Replace the faulty board and then check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67603: The Monitor bus was faulty.

    1. Run the power off and power on commands on the faulty board. After the board is registered, check whether the alarm is cleared.

    • If so, go to Step 7.
    • If not, go to Step 2.

    2. Remove the board and check whether the pinch board of the Monitor bus is installed well. Reinsert the board. Then, check whether the alarm is cleared.

    • If so, go to Step 7.
    • If not, go to Step 3.

    3. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 7.
    • If not, go to Step 4.

    4. Check whether multiple boards report the alarm.

    • If so, go to Step 5.
    • If not, go to Step 6.

    5. Remove the main control board and check whether the pinch board of the Monitor bus is installed well. Reinsert the main control board. Then, check whether the alarm is cleared.

    • If so, go to Step 7.
    • If not, go to Step 6.

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

    7. End.

  • Cause 67604: The communication of the Monitor bus failed. This trap indicates that the Monitor bus was faulty.

    1. Run the power off and power on commands on the involved board. After the board is registered, check whether the alarm is cleared.

    • If so, go to Step 5.
    • If not, go to Step 2.

    2. Remove the board and check whether the pinch board of the Monitor bus is installed well. Reinsert the board. Then, check whether the alarm is cleared.

    • If so, go to Step 5.
    • If not, go to Step 3.

    3. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 5.
    • If not, go to Step 4.

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

    5. End.

  • Cause 67608: The output voltage of a power module exceeded a specified threshold.

    1. Check whether the external power supply is normal. Check whether the external input of the power supply is within the input range of the power supply. If not, replace the external input of the power supply to ensure that the input of the power supply is within the normal range (180 V AC to 264 V AC). Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 2.

    2. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it.

    Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 3.

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

    4. End.

  • Cause 67609: The output voltage of a power module exceeded a rated range.

    1. Check whether the external power supply is normal. Check whether the external input of the power supply is within the input range of the power supply. If not, replace the external input of the power supply to ensure that the input of the power supply is within the normal range (180 V AC to 264 V AC). Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 2.

    2. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it.

    Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 3.

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

    4. End.

  • Cause 67610: The output voltage of a power module was below a specified threshold.

    1. Check whether the external power supply is normal. Check whether the external input of the power supply is within the input range of the power supply. If not, replace the external input of the power supply to ensure that the input of the power supply is within the normal range (180 V AC to 264 V AC). Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 2.

    2. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it.

    Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 3.

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

    4. End.

  • Cause 67611: The output voltage of a power module was below a rated range.

    1. Check whether the external power supply is normal. Check whether the external input of the power supply is within the input range of the power supply. If not, replace the external input of the power supply to ensure that the input of the power supply is within the normal range (180 V AC to 264 V AC). Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 2.

    2. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it.

    Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 3.

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

    4. End.

  • Cause 67612: The output voltage of a power module exceeded the upper threshold.

    1. Check whether the external power supply is normal. Check whether the external input of the power supply is within the input range of the power supply. If not, replace the external input of the power supply to ensure that the input of the power supply is within the normal range (180 V AC to 264 V AC). Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 2.

    2. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it.

    Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 3.

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

    4. End.

  • Cause 67613: The current of a power module exceeded a rated range.

    1. Check whether the external power supply is normal. Check whether the external input of the power supply is within the input range of the power supply. If not, replace the external input of the power supply to ensure that the input of the power supply is within the normal range (180 V AC to 264 V AC). Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 2.

    2. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it.

    Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 3.

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

    4. End.

  • Cause 67614: The power module's output was cut off.

    1. Check whether the external power supply is normal. Check whether the external input of the power supply is within the input range of the power supply. If not, replace the external input of the power supply to ensure that the input of the power supply is within the normal range (180 V AC to 264 V AC). Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 2.

    2. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it.

    Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 3.

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

    4. End.

  • Cause 67615: The input voltage of a power module exceeded a specified threshold.

    1. Check whether the external power supply is normal. Check whether the external input of the power supply is within the input range of the power supply. If not, replace the external input of the power supply to ensure that the input of the power supply is within the normal range (180 V AC to 264 V AC). Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 2.

    2. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it.

    Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 3.

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

    4. End.

  • Cause 67616: The input voltage of a power module exceeded a rated range.

    1. Check whether the external power supply is normal. Check whether the external input of the power supply is within the input range of the power supply. If not, replace the external input of the power supply to ensure that the input of the power supply is within the normal range (180 V AC to 264 V AC). Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 2.

    2. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it.

    Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 3.

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

    4. End.

  • Cause 67617: The input voltage of a power module was below a specified threshold.

    1. Check whether the external power supply is normal. Check whether the external input of the power supply is within the input range of the power supply. If not, replace the external input of the power supply to ensure that the input of the power supply is within the normal range (180 V AC to 264 V AC). Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 2.

    2. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power module before replacing it.

    Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 3.

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

    4. End.

  • Cause 67618: The input voltage of a power module was below a rated range.

    1. Check whether the external power supply is normal. Check whether the external input of the power supply is within the input range of the power supply. If not, replace the external input of the power supply to ensure that the input of the power supply is within the normal range (180 V AC to 264 V AC). Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 2.

    2. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power module before replacing it.

    Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 3.

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

    4. End.

  • Cause 67619: The input voltage of a power module fell below the lower threshold.

    1. Check whether the external power supply is normal. Check whether the external input of the power supply is within the input range of the power supply. If not, replace the external input of the power supply to ensure that the input of the power supply is within the normal range (180 V AC to 264 V AC). Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 2.

    2. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it. Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 3.

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

    4. End.

  • Cause 67620:

    Cause1:AC power: The module's internal temperature exceeded a rated range, and consequently its power output was cut off.

    Cause2:DC power: The module's internal temperature exceeded the rate range. As a result, its auxiliary output was cut off (the main output that supplies power to the board remains unaffected).

    1. Check whether the fans of the power supply unit (PSU) are ventilated properly. Check the air exhaust vent of the power module. If the ventilation is abnormal, clean the air exhaust vent and wait for about 1 minute to check whether the fault is rectified.

    • If yes, go to step 4.
    • If no, go to step 3.

    2. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it. Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 3.

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

    4. End.

  • Cause 67621: A power module's internal temperature was too high and would reach the specified threshold.

    1. Check whether the external power supply is normal. Check whether the external input of the power supply is within the input range of the power supply. If not, replace the external input of the power supply to ensure that the external input of the power supply is within the normal range (180 V AC to 264 V AC). Then, check whether the fault is rectified.

    • If yes, go to step 4.
    • If no, go to step 2.

    2. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it.

    Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 3.

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

    4. End.

  • Cause 67622: The power module received an incorrect instruction.

    1. Perform an active/standby switchover. Then, check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the power supply module 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 67623: The input data was not supported.

    1. Perform an active/standby switchover. Then, check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the power supply module 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 67624: A fault occurred on the internal processor of a power module.

    1. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it. Check whether the alarm is cleared.

    • If yes, go to step 3.
    • If no, go to step 2.

    2. Collect alarm, log, and configuration information and contact Huawei technical support.

    3. End.

  • Cause 67625: A power module failed to communicate with the MPU, which does not affect power supply.

    1. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it. Check whether the alarm is cleared.

    • If yes, go to step 3.
    • If no, go to step 2.

    2. Collect alarm, log, and configuration information and contact Huawei technical support.

    3. End.

  • Cause 67626: The fan of the AC or DC power module was faulty.

    1. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it. Check whether the alarm is cleared.

    • If yes, go to step 3.
    • If no, go to step 2.

    2. Collect alarm, log, and configuration information and contact Huawei technical support.

    3. End.

  • Cause 67627: The input fuse of a power module was faulty or the link was disconnected.

    1. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it. Check whether the alarm is cleared.

    • If yes, go to step 3.
    • If no, go to step 2.

    2. Collect alarm, log, and configuration information and contact Huawei technical support.

    3. End.

  • Cause 67628: The input fuse of a power module was faulty or the link was disconnected.

    1. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it. Check whether the alarm is cleared.

    • If yes, go to step 3.
    • If no, go to step 2.

    2. Collect alarm, log, and configuration information and contact Huawei technical support.

    3. End.

  • Cause 67629: One of the internal switches on a power module was not closed.

    1. Check whether the switches on the power panel are off.

    • If one or more switches are not off, go to Step 2.
    • If all switches are off, go to Step 3.

    2. Turn off the switches and check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 3.

    3. Run the slave switchover command to perform an active/standby switchover.

    Check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 4.

    4. Replace the power module. Power off the faulty power module before replacing it.

    Then, check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 5.

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

    6. End.

  • Cause 67630: One of the internal power supply arresters of the DC power supply module was faulty.

    1. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it. Check whether the alarm is cleared.

    • If yes, go to step 3.
    • If no, go to step 2.

    2. Collect alarm, log, and configuration information and contact Huawei technical support.

    3. End.

  • Cause 67631: Output voltage of the DC power supply module was abnormal.

    1. Check whether the power supply is powered on.

    • If yes, go to step 3.
    • If no, go to step 2.

    2. Set the switch to ON and check whether the alarm persists.

    • If yes, go to step 3.
    • If no, go to step 5.

    3. Replace the power module. Power off the faulty power module before replacing it.

    Check whether the alarm is cleared.

    • If yes, go to step 5.
    • If no, go to step 4.

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

    5. End.

  • Cause 67632: Input voltage of the DC power supply module was below the rated value.

    1. View the power input information. Run the display power environment-info slot command to check the input voltage of the power supply. If the input voltage is too low, adjust the input voltage so that the power supply works normally. After the power supply works normally, check whether the alarm persists.

    • If yes, go to step 4.
    • If no, go to step 2.

    2. Replace the power supply device. Then, check whether the alarm is cleared. Power off the faulty power supply module before replacing it.

    Check whether the alarm is cleared.

    • If yes, go to step 4.
    • If no, go to step 3.

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

    4. End.

  • Cause 67633:

    Cause 1: An internal submodule was not properly installed.

    Cause 2: An internal submodule failed.

    1. Check whether the power module is correctly installed.

    • If so, go to Step 3.
    • If not, go to Step 2.

    2. Remove and reinstall the power module and check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 4.

    3. Perform an active/standby switchover and check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 4.

    4. Replace the power module. Power off the faulty power module before replacing it. Then, check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 5.

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

    6. End.

  • Cause 67634: The AC power supply module was faulty.

    1. Check whether the power supply module is well installed.

    • If so, go to Step 3.
    • If not, go to Step 2.

    2. Re-install the power supply module and then check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 4

    3. Perform an active/standby switchover, and then check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 4.

    4. Replace the power supply module and check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 5.

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

    6. End.

  • Cause 67638: The power module was properly installed but was not powered on.

    1. Check whether the power supply module is stably installed.

    • If so, go to Step 2.
    • If not, go to Step 6.

    2. Check whether the power supply module is powered on. If the power supply module is not powered on, power on it. Then, check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 4.

    3. Perform an active/standby switchover. Then, check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 4.

    4. Replace the power supply module. Power off the faulty power module before replacing it. Then, check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 5.

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

    6. End.

  • Cause 67642: The key chip clock board is abnormal.

    1. Check whether the board is reset or powered off.

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. Power on the board 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 67643: Slot slotID is failed, 2M Apll Unlock.

    1. Check whether the board is reset or powered off.

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. Power on the board 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 67644: Slot slotID is failed, the heart beat of clock board is loss.

    1. Check whether the board is reset or powered off.

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. Power on the board 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 67652: Slot %s is failed, the clock signal %s of the Board is abnormal.

    1. Run the reset slot slot-id command to reset the faulty board. After the board is registered, check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the board 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 67653: The reference clock source on the SFU was faulty.

    1. Run the reset slotslot-id command in the user view 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 trap 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 67654: LPU slot slotID is failed,the memory QDR of the TMtmID is abnormal.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67656: LPU slot slotID is failed,the key chip of the TMtmID is abnormal.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67657: LPU slot slotID is failed,the data link status to PE of the TMtmID is abnormal.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67659: The signal carrying the information about the slot where the interface board resided was disturbed.

    1. Run the reset slot slot-id command to reset the faulty board. After the board is registered, check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the board 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 67660:

    Cause1:The second 48 V power supply failed:

    The second power module was not installed or The second power module failed.

    Cause2:One or both power supplies failed,No external power supply was available for one or both power modules.

    Cause3:The two PMU monitor buses failed.

    The second 48 V power supply failed.

    1. Run the display device command and check whether the second power supply is unavailable.

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. Install an additional power module and check whether the trap is cleared.

    • If so, go to Step 6.
    • If not, go to Step 3.

    3. Run the display device command and check whether the power module works properly.

    • If so, go to Step 5.
    • If not, go to Step 4.

    4. Replace the faulty power module and check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 4.

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

    6. End.

  • Cause 67661: The signal carrying the slot information sent from the MPU to the interface board was abnormal.

    1. Run the reset slot slot-id command to reset the faulty board and then check whether the board can be normally registered.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the faulty interface board 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 67669: Slot slotID is failed, PEPEID is abnormal.

    1. Replace the board and check whether the fault is rectified.

    • If so, go to Step 3.
    • If no, go to Step 2.

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

    3. The procedure ends.

  • Cause 67688: The optical module temperature is too high.

    1. Replace the optical module and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67689: The optical module temperature is too low.

    1. Replace the optical module and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67690: Optical module voltage is too high.

    1. Check the environmental power supply information. Run the display alarm all command to check whether the power supply voltage alarm hwVoltFallingAlarm is generated on the port.

    • If so, go to Step 3.
    • If not, go to Step 2.

    2. Handle the power supply alarm, and then check whether the alarm is cleared.

    • If so, go to Step 8.
    • If not, go to Step 3.

    3. Check the voltage information of the board where the optical module is located, and check whether the voltage alarm information appears on the NMS.

    • If so, go to Step 4.
    • If not, go to Step 5.

    4. Handle the voltage alarm, and then check whether the alarm is cleared.

    • If so, go to Step 8.
    • If not, go to Step 5.

    5. Replace the optical module to check whether the alarm is cleared.

    • If so, go to Step 8.
    • If not, go to Step 6.

    6. Replace the optical module board to check whether the alarm is cleared.

    • If so, go to Step 8.
    • If not, go to Step 7.

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

    8. End.

  • Cause 67691: The optical module voltage is too low.

    1. Replace the optical module and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67692: The optical module bias is too low.

    1. Replace the optical module and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67693: The optical module bias is too high.

    1. Replace the optical module and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67694: The output power of the optical module was too high.

    1. Add an optical attenuator and check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the optical module 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 67695: The transmitting power of the optical module is too low.

    1. Replace the optical module and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67696: The receiving power of the optical module is too high.

    1. Replace the optical module or increase the optical attenuation. Then, check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67697: The receiving power of the optical module is too low.

    1. Check whether the optical fiber is inserted in the port (that is, whether the optical fiber is in use).

    • If so, go to Step 3.
    • If not, go to Step 2.

    2. Remove the optical module and check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 5.

    3. Replace the optical fiber and check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to step 4.

    4. Replace the optical module and check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 5.

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

    6. End.

  • Cause 67701: The possible cause may be that the hardware of the MPU was faulty.

    1. Replace the faulty main control board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67708: The power of the FCB was faulty.

    1. Remove and insert the faulty fan module. Then, check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the fan module 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 67709:

    Cause 1: The board PCI bus was abnormal.

    Cause 2: The NSE PCI was abnormal.

    1. Run the reset slot command to reset the board. After the board is registered, check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the board 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 67721: LPU slot slotIDis failed,the link number to fabric of the TMtmID is not enough.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67722: Slot slotID is failed, the mpu act signal of the Board is abnormal.

    1. Replace the main control board in the corresponding slot according to the alarm information. Then, check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67726: The batteries on the MPU failed to function normally.

    1. Replace the main control board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67727: LPU slotID is failed, the data link to PIC of PEPEID is abnormal

    1. Replace the board and check whether the fault is rectified.

    • If so, go to Step 3.
    • If no, go to Step 2.

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

    3. The procedure ends.

  • Cause 67734: Slot slotID is failed, the mpu act signal of the Board is abnormal.

    1. Run the reset slot slot-id command to reset the faulty SFU and check whether the alarm is cleared after the SFU is registered.

    • 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 67735: Obtaining the manufacture information about the power supply module failed.

    1. Run the display device command to check whether the power supply module functions normally.

    • If so, go to Step 3.
    • If not, go to Step 2.

    2. Replace the power supply module 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 67737: The I2C channel was faulty

    1. Check whether the board is reset or powered off.

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. Power on the board 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 67739: The sensor on the subcard(or board) is faulty.

    1. Check whether the board is reset or powered off.

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. Power on the board 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 67740:

    Cause1:The board power was insufficient.

    Cause2:The device power was insufficient.

    Cause3:The number of power modules was less than required.

    Cause4:A power supply plane was unable to supply power with high reliability.

    1. If boards cannot be replaced, replace the power module with a high-power one. Then, check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 3.

    2. If boards can be replaced, replace the power module with a low-power one, or remove the unused boards. Then 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 67743: Vsr VsrId is failed, the optical module of the OFC is abnormal.

    1. Replace with a new optical fiber and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67744:

    Cause1: The 125 MHz clock source failed.

    Cause2.:The differential transmission line failed.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67745: LPU slot slotID is failed,the memory ZBT of the TMtmID is abnormal.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67746: Vsr VsrId is failed,the optic connection is abnormal.

    1. Check whether the fiber connection is incorrect.

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. Correct the fiber connection 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 67755: The flash in slot slotid is abnormal.

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

    2. End.

  • Cause 67762: SFU is failed, SFU in chassis chassisid is not full.

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

    2. End.

  • Cause 67763: MPU is failed, MPU in chassis chassisid is not full.

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

    2. End.

  • Cause 67765:

    Cause 1: The software of the board is faulty.

    Cause 2: The hardware of the TCAM is faulty.

    1. Upgrade the system software or install a patch on the faulty board.

    2. Run the display device command to check whether the faulty board is registered successfully. Then, check whether the alarm is cleared.

    • If so, go to Step 5.
    • If not, go to Step 3.

    3. Replace the board and then check whether the alarm is cleared.

    • If so, go to Step 5.
    • If not, go to step 4.

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

    5. End.

  • Cause 67771:

    Cause 1:The EPLD logic file was faulty.

    Cause 2: The EPLD hardware was faulty.

    Cause 3: The EPLD version is different from that of the system.

    1. Run the corresponding command to upgrade the board EPLD by board type in the diagnostic view. After the upgrade is finished and the board is registered, check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the board and then 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 67796:

    Cause1: PCI BUS: indicates errors related to the PCI BUS.

    Cause2: Clock check: indicates errors related to the logic clock.

    Cause3: Tcam BUS: indicates errors related to the TCAM BUS.

    Cause4: Tcam ID: indicates errors related to the ASE TCAM ID.

    Cause5: Tcam array parity: indicates errors related to the Tcam array entry.

    Cause6: Ddr Parity: indicates errors related to the Ddr entry.

    Cause7: LA-1 Parity: indicates parity errors of the QDR interface.

    1. Replace the board. After the new board is registered, check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67837: The PE hardware or NSE chip hardware on the board was faulty.

    1. Run the reset slot command to reset the board. After the board is registered, check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the board 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 67838: A hardware fault occurs on the TCAM chip.

    1. Run the reset slot command to reset the board. After the board is registered, check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the board 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 67840: ECC detected faults when the memory read and wrote DDR SDRAM of the CPU.

    1. Run the reset slot command to reset the board. After the board is registered, check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the board 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 67842: The signal for the board being properly installed was incorrect.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67900: LPU slot slotID is failed,the key chip StatLogic of the TMtmID is abnormal.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67905: LPU slot slotID is failed,the key chip IftLogic of the TMtmID is abnormal.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67921: SWF slot slot-id is failed, all the links of the board are unavailable.

    1. Check whether the interface board is in position.

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. Check the inter-chassis fiber connections.

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

    4. End.

  • Cause 67922: Power slotid, %s is failed, the pem type does not match the type of the backplane.

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

    2. End.

  • Cause 67923: Fan slotid is failed, the fan type does not match the type of the backplane.

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

    2. End.

  • Cause 67924: Slot slotID did not match the device.

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

  • Cause 67952: Logic 1 of the board failed.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67953: Logic 2 of the board failed.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67969: The interface board is failed, the adaptive clock translator's output of the Board is abnormal.

    1. Remove and reinstall the board. Check whether the alarm is cleared after the board is registered. If the alarm persists, the clock on the PHY chip fails. In this case, replace the board. If the alarm is cleared after the board is registered, a software error occurs.

    2. Upgrade system software .Download the system software with the version later than the source version to the CF card of the active and standby main control boards. Run the startup system-software command to specify the system software to be loaded for the next startup. Then, restart the router.

    3. Run the display device command and check whether the faulty board can be successfully registered.

    • If so, go to Step 5.
    • If not, go to Step 4.

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

    5. End.

  • Cause 67970: A fault occurred in 33 MHz clock signals on the board.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 67971: A communication failure occurred on the fan module.

    1. Run the reset slot command to reset the faulty fan module. Then, check whether the alarm is cleared. If the alarm persists after the fan module is registered, replace the faulty fan module. If the alarm is cleared after the fan module is reset and can be registered, a software error occurs.

    2. Upgrade system software .Download the system software with the version later than the source version to the CF card of the active and standby main control boards. Run the startup system-software command to specify the system software to be loaded for the next startup. Then, restart the router.

    3. Run the display device command and check whether the faulty board can be successfully registered.

    • If so, go to Step 5.
    • If not, go to Step 4.

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

    5. End.

  • Cause 67995: The air filter inside the chassis chassisid was not cleaned.

    1. Run the display dustproof command to check whether the air filter cleanup cycle has expired.

    2. If the air filter cleanup cycle has expired, clean the air filter. After the cleaned air filter is reinstalled, run the reset dustproof run-time command to re-set the parameters for the air filter. Ensure that the parameters are set successfully.

    3. End.

  • Cause 67999: Slot slotid is failed, the slotID check is failed.

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

    2. End.

  • Cause 68006: Slot slotid is failed, the clock signal level3Clock of clock board is abnormal.

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

    2. End.

  • Cause 68007: Slot slotid is failed, the clock signal 3Clock of board is abnormal.

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

    2. End.

  • Cause 68008: Slot slotid is failed, the first erode-protect unit is break.

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

    2. End.

  • Cause 68010: Slot slotid is failed, the control bus PCIE of board is abnormal.

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

    2. End.

  • Cause 68011: Slot slotid is failed, the cpu internal module of the Board is abnormal.

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

  • Cause 68015:

    Cause 1:The PCI was abnormal.

    Cause 2:The internal clock of the PE or NSE was out of lock.

    Cause 3:The clock of the TCAM was out of lock.

    1. Replace the board. After the new board is registered, check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68016: LPU slotID is failed, , the data link to TM of PEPEID is abnormal.

    1. Replace the board and check whether the fault is rectified.

    • If so, go to Step 3.
    • If no, go to Step 2.

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

    3. The procedure ends.

  • Cause 68017: LPU slotID is failed, the clock signals of the PEPEID is abnormal.

    1. Replace the board and check whether the fault is rectified.

    • If so, go to Step 3.
    • If no, go to Step 2.

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

    3. The procedure ends.

  • Cause 68018: LPU slotID is failed, PLLOUT of PE is abnormal.

    1. Replace the board and check whether the fault is rectified.

    • If so, go to Step 3.
    • If no, go to Step 2.

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

    3. The procedure ends.

  • Cause 68035: The clock component of a board failed.

    1. Check whether the board is reset or powered off.

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. Power on the board 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 68040: The FPGA fault was detected on the PIC card.

    1. Check whether the faulty board is an FPIC.

    • If so, go to Step 3.
    • If not, go to Step 2.

    2. Run the reset slot slotID card cardID command to reset the FPIC, and then check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 3.

    3. Run the reset slot slotID command to reset the faulty board and then check whether the board can function properly.

    • If so, go to Step 6.
    • If not, go to Step 4.

    4. Replace the faulty board. After the new board is registered, check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 5.

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

    6. End.

  • Cause 68043: SFU clock check fault.

    1. Run the reset slot command to reset the faulty SFU. After the SFU is registered, check whether the alarm is cleared.

    • 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 68049: The BSP module detected a fault on the key chip EEPROM or IIC bus on a board.

    1. Run the reset slot command to reset the faulty board. Then, check whether the board can function properly.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68050:

    Cause 1:The management channel of the USB controller was faulty.

    Cause 2:The PCIE bridge was faulty.

    1. Run the reset slot command to reset the faulty board. Then, check whether the board can function properly.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68051:

    Cause 1:The management channel of the GE LSW was abnormal.

    Cause 2:The PCIE bridge was faulty.

    1. Run the reset slot command to reset the faulty board. Then, check whether the board can function properly.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68052:

    Cause 1:The management channel of the FE LSW was abnormal.

    Cause 2:The PCIE bridge was faulty.

    1. Run the reset slot command to reset the faulty board. Then, check whether the board can function properly.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68054: Cause 1: The hardware of the MDC/MDIO channel to the PHY is faulty. Cause 2: The PHY chip is abnormal

    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 68055: The SFU clock synchronization is abnormal.

    1. Run the reset slot command to reset the faulty board. Then, check whether the board can function properly.

    • If so, go to Step 4.
    • If not, go to Step 3.

    2. Replace the board. After the board is registered, 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 68056: The Board is failed, the mdio bus of this port is not ok.

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

    2. End.

  • Cause 68057: The clock unit on the subcard was faulty.

    1. Run the reset slot command to reset the board. After the board is registered, check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the board 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 68059: The optical transceiver of the PIC card was found abnormal.

    1. Replace the optical fiber, and then check whether the alarm is cleared.

    • If so, go to Step 7.
    • If not, go to Step 2.

    2. Check whether any alarm is generated on the peer interface.

    • If so, go to Step 3.
    • If not, go to Step 4.

    3. Replace the optical transceiver of the peer interface, and then check whether the alarm is cleared.

    • If so, go to Step 7.
    • If not, go to Step 4.

    4. Check whether any alarm is generated on the local interface.

    • If so, go to Step 5.
    • If not, go to Step 7.

    5. Replace the optical transceiver of the local interface, and then check whether the alarm is cleared.

    • If so, go to Step 7.
    • If not, go to Step 6.

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

    7. End.

  • Cause 68060: The fault in the key chip of the PIC card was detected.

    1. Check whether the faulty board is an FPIC.

    • If so, go to Step 3.
    • If not, go to Step 2.

    2. Run the reset slot slotID card cardID command to reset the FPIC, and then check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 3.

    3. Run the reset slot slotID command to reset the faulty board and then check whether the board can function properly.

    • If so, go to Step 6.
    • If not, go to Step 4.

    4. Replace the faulty board. After the new board is registered, check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 5.

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

    6. End.

  • Cause 68062: The NP fault was detected on the PIC card.

    1. Check whether the faulty board is an FPIC.

    • If so, go to Step 3.
    • If not, go to Step 2.

    2. Run the reset slot slotID card cardID command to reset the FPIC, and then check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 3.

    3. Run the reset slot slotID command to reset the faulty board and then check whether the board can function properly.

    • If so, go to Step 6.
    • If not, go to Step 4.

    4. Replace the faulty board. After the new board is registered, check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 5.

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

    6. End.

  • Cause 68064: The NP fault was detected on the PIC card.

    1. Check whether the faulty board is an FPIC.

    • If so, go to Step 3.
    • If not, go to Step 2.

    2. Run the reset slot slotID card cardID command to reset the FPIC, and then check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 3.

    3. Run the reset slot slotID command to reset the faulty board and then check whether the board can function properly.

    • If so, go to Step 6.
    • If not, go to Step 4.

    4. Replace the faulty board. After the new board is registered, check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 5.

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

    6. End.

  • Cause 68065: The data channel fault was detected on the PIC card.

    1. Check whether the faulty board is an FPIC.

    • If so, go to Step 3.
    • If not, go to Step 2.

    2. Run the reset slot slotID card cardID command to reset the FPIC, and then check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 3.

    3. Run the reset slot slotID command to reset the faulty board and then check whether the board can function properly.

    • If so, go to Step 6.
    • If not, go to Step 4.

    4. Replace the faulty board. After the new board is registered, check whether the alarm is cleared.

    • If so, go to Step 6.
    • If not, go to Step 5.

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

    6. End.

  • Cause 68067: The Heartbeat of PIC is abnormal.

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

    2. End.

  • Cause 68074: The output voltage of slot slotid failed.

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

    2. End.

  • Cause 68085: Too many SFU links were shut down for crc, loopback, FDR, updown.

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

    2. End.

  • Cause 68095: The optical module type did not match the interface type.

    1. Use another type of optical module that matches the interface type. Then, check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68130: Power current not average.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68131: Power canbus is abnormal.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68132: Power current exceed the max value.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68133: Power module merge current fail.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68134: slotid%s is failed, the RTC clock is abnormal.

    1. Replace the board and check whether the fault is rectified.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68135: The PMU was faulty.

    1. Insert and remove the PMU, and re-power on the PMU. Check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68136: slotid%s is failed, the MonitorBUS is abnormal.

    1. Replace the board and check whether the fault is rectified.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68137: Powerbackplane failed Because of the cable is disconnected.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68138: Fan link board offline.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68140: The CPU on the interface board was faulty.

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

    2. End.

  • Cause 68143: The fast switchover port %d of MPU %s was connected incorrectly.

    1. Modify the connection using rapid sensing cables and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68144: The fast switchover port %d of MPU %s became disconnected.

    1. After the board resets automatically, run the display device command to check whether the board works properly.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the faulty board 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 68147: The link-heartbeat detection packet was modified on the link.

    1. Run the power off slot slot-id and power on slot slot-id commands on the boards at both ends of the direct link. After the boards are registered, check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the board, and then 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 68148: The link-heartbeat detection packet was dropped on the link.

    1. Run the power off slot slot-id and power on slot slot-id commands on the boards at both ends of the direct link. After the boards are registered, check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the board, and then 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 68153:

    Cause 1: The PE's chip failed.

    Cause 2: An error occurred on the PE's forwarding table read-write processing program.

    1. Replace the faulty LPU. After the new LPU is registered, check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68154: The PMU was offline.

    1. Check whether the PMU is properly installed. If the PMU is properly installed, remove and reinstall the PMU and then check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the PMU 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 68155:

    Cause 1: The external power supply was insufficient.

    Cause 2: The PM was either faulty or removed.

    1. Install enough PMs into the power slot. Then, check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68156: The PM was either faulty or removed.

    1. Install enough PMs into the power slot so that the number of installed PMs reaches or exceeds the threshold. Then, check whether the alarm is cleared. (The minimum number of DC PMs is 5 and the minimum number of AC PMs is 4.)

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68157:

    Cause1: External power inputs are needed.

    Cause2: A fault occurred on the power module.

    1. Check whether the external power input is lacked.

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. Add external power input and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 5.

    3. Replace the PM that reports the alarm and check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 5.

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

    5. End.

  • Cause 68160: The PLD or Flash initializatiaon fault.

    1. Replace the optical module and then check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68161: The power supply fault .

    1. Replace the optical module and then check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68162: The CFP checksum fault.

    1. Replace the optical module and then check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68163: The fan frame was present.

    1. Check whether the fan frame is in position. If the fan frame is in position, remove the fan fram and then check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68165: In a CCC-0 system consisting of an NE5000E-X16A and a CLC of other types, the NE5000E-X16A functioned as the slave chassis.

    1. Reconfigure the chassis IDs, run the following commands in order:

    set chassis clc1 chassis-id 2

    set chassis clc2 chassis-id 1

    2. Restart the device and then 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 68166:

    Cause1: The 100G/400G OFC has plugged in 25G CXP.

    Cause2: The 1T OFC in CLC chasis of cluster form has plugged in 10G CXP.

    1. Replace with the CXPs matching the optical subcard. Then, check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68167: The license item is not activated.

    1. Check whether license control items are activated.

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. Re-apply for and activate the license control items. Then, 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 68168: The license item will expire.

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

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. Re-apply for and activate the license control items. Then, 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 68169: A power consumption limit was configured, resulting in inadequate system power supply.

    1. Check whether the power modules configured are adequate for the system.

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. Check whether the power consumption limit configured is too low for system power supply. Reconfigure the capping power of the power supply. Then, check whether the alarm is cleared.

    • If so, go to Step 5.
    • If not, go to Step 3.

    3. Insert the power module and check whether the alarm is cleared.

    • If so, go to Step 5.
    • If not, go to Step 4.

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

    5. End.

  • Cause 68170: The app of the power module is abnormal.

    1. Upgrade the PM module.

    2. Check whether the alarm is cleared.

    • If so, go to Step 5.
    • If not, go to Step 3.

    3. Replace the power module. Power off the faulty power module before replacing it. Then, check whether the alarm is cleared.

    • If so, go to Step 5.
    • If not, go to Step 4.

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

    5. End.

  • Cause 68171: The cpu frequency of the board is abnormal.

    1. Perform an active/standby switchover and then check whether the alarm is cleared.

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. Check whether the same alarm occurred 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 68172: The CPU of the board partially failed.

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

    2. End.

  • Cause 68175: The fan was installed unstably.

    1. Re-install the fan and check whether the alarm is cleared.

    • If so,go to Step 6.
    • If not,go to Step 2.

    2. Check whether the pins on the backplane have bent.

    • If so,go to Step 5.
    • If not,go to Step 3.

    3. Check whether the fan connector is faulty.

    • If so,go to Step 4.
    • If not,go to Step 5.

    4. Replace the fan with a new one and check whether the alarm is cleared.

    • If so,go to Step 6.
    • If not,go to Step 5.

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

    6. End.

  • Cause 68176: The communication between the CMUs is abnormal.

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

  • Cause 68177: The dustproof gate is not closed and has been opened for more than the detection time.

    1. Check whether the dustproof gate is opened.

    • If so,go to Step 2.
    • If not,go to Step 3.

    2. Close the dustproof gate 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 68178: The CMU is not registered.

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

  • Cause 68179: Fan is failed, Fan in chassis chassisid is not full.

    1. Install the standby fan, and then check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68180: CMU do not match with product brand.

    1. Replace the CMU to a new one matching the product and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 68181: The CMU communication or signal is abnormal.

    1. Reset the faulty CMU and check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Remove and re-install the faulty CMU and check whether the alarm is cleard.

    • 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 68182: The channel between the power module and the device failed.

    1. Replace the power supply module and check whether the alarm is cleared.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the main control board and check whether the alarm is cleard.

    • 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 68183: The power supply on the power module is faulty.

    1. Check whether the external power supply system works properly.

    • If so, go to Step 5.
    • If not, go to Step 2.

    2. Check whether a short circuit occurs on the power supply system.

    • If so, go to Step 5.
    • If not, go to Step 3.

    3. Replace the faulty power supply module and check whether the alarm is cleared.

    • If so, go to Step 5.
    • If not, go to Step 4.

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

    5. End.

  • Cause 68184: The power type does not match the type of the backplane.

    1. Check whether the power module and backplane types match.

    • If so, go to Step 4.
    • If not, go to Step 2.

    2. Replace the power module with one matching the backplane type and then 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 68185: CMUs were not fully configured.

    1. Check whether CMUs are fully configured.

    • If not, go to Step 2.
    • If so, go to Step 3.

    2. Install CMUs based on configuration requirements. 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 trap, log, and configuration information, and contact technical support.

    4. End.

  • Cause 68187: Fan slotid is failed, the fan type does not match the type of the sfu.

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

    2. End.

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

    1. Disconnect the standby chassis, configure the PTN mode of the standby chassis to be the same as that of the active chassis using the active mode-control license command, and then connect the standby chassis to the active chassis.

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

    3. End.

  • Cause 68191: The actual power-on status of the chip is not as expected.

    1. Power on the board again. Then, check whether the alarm is cleared.

    • If the alarm 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 68197: Abnormal temperature of the secondary CDU

    1. Check whether the water temperature at the water inlet on the primary side is within the range of 5°C to 33°C.

    • If yes, go to Step 2.
    • If no, go to Step 4.

    2. Check whether the primary side valve is faulty.

    • If yes, go to Step 3.
    • If no, go to Step 4.

    3. Rectify the valve fault.

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

    5. End.

  • Cause 68198: The secondary CDU pressure is abnormal.

    1. Check whether pipes are correctly connected.

    • If yes, go to Step 2.
    • If no, go to Step 3.

    2. Check whether the valve is faulty.

    • If yes, go to Step 4.
    • If no, go to Step 5.

    3. Connect the pipes correctly.

    4. Rectify the valve fault.

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

    6. End.

  • Cause 68205: Liquid leakage fault

    1. Check whether the electrolyte leaks.

    • If yes, go to Step 3.
    • If no, go to Step 2.

    2. Check whether the sensor cable and cable connection are normal.

    • If yes, go to Step 5.
    • If no, go to Step 4.

    3. Solve the problem of electrolyte leakage.

    4. Replace the sensor.

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

    6. End.

  • Cause 68206: Valve fault

    1. Check whether the valve cable is correctly connected.

    • If yes, go to Step 2.
    • If no, go to Step 3.

    2. Replace the valve, and go to Step 4.

    3. Correctly connect cables to the valve.

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

    5. End.

  • Cause 68214: AC fault

    1. Check whether the input power supply is normal.

    • If yes, go to Step 3.
    • If no, go to Step 2.

    2. Replace the PSU.

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

    4. End.

  • Cause 68218: CDU communication failure.

    1. Check whether the CDU is powered on.

    • If yes, go to Step 3.
    • If no, go to Step 2.

    2. Power on the CDU.

    3. Check whether the RS485 cable is properly connected.

    • If yes, go to Step 5.
    • If no, go to Step 4.

    4. Connect the RS485 cable correctly.

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

    6. End.

  • Cause 68224: The SMI serial of the board is abnormal.

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

  • Cause 68225: IPUs with different forwarding capabilities were inserted on the device.

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

    2. End.

  • Cause 68226: SFU MPI control bus check fault.

    1. Run the reset slot command to reset the faulty SFU. After the SFU is registered, check whether the alarm is cleared.

    • 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 68227: Device certificate verify fail.

    Reset the board and check whether the fault is rectified. If the fault persists, replace the board.

  • Cause 68229: An exception occurred due to the CPU MCU heartbeat loss exception.

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

    2. End.

  • Cause 68232: The fan power fails to be unlocked.

    1. Check whether the fan module can be unlocked.

    If yes, go to step 2.

    If no, go to step 3.

    2. Wait for the system to unlock the fan again. If the unlocking is successful, the alarm is automatically cleared.

    If the the unlocking fails, remove the fan module and go to Step 4.

    3. Replace the fan with one that supports power unlocking.

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

  • Cause 69131: The board was powered off.

    1. Check whether the board needs to be powered on again.

    • If so, go to Step 2.
    • If not, go to Step 4.

    2. Power on the board again 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 69501: A power input channel for the filtering box of the fan was interrupted.

    1. Check whether a power input channel for the filtering box of the fan is interrupted.

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. Repair the interrupted power input channel 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 69502: The filtering box of the fan was missing or improperly installed.

    1. Check whether the filtering box of the fan in the corresponding slot is properly installed.

    • If so, go to Step 3.
    • If not, go to Step 2.

    2. Reseat the filtering box 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 69503: CMU switch is abnormal.

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

    2. End.

  • Cause 69505: LPU slotID is failed, the control bus of PEPEID is abnormal.

    1. Replace the board and check whether the fault is rectified.

    • If so, go to Step 3.
    • If no, go to Step 2.

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

    3. The procedure ends.

  • Cause 69507: LPU slotID is failed, the data link of the PE IntfLogic is abnormal.

    1. Replace the board and check whether the fault is rectified.

    • If so, go to Step 3.
    • If no, go to Step 2.

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

    3. The procedure ends.

  • Cause 69510: LPU slot slotID is failed,the interlaken to PIC of the PE is abnormal.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 69512: The voltage status of the subcard is abnormal.

    1. Check whether the subboard is powered on.

    • If the subcard is powered on, no action is required.
    • If the subcard is not powered on, go to Step 2.

    2. Power on the subcard using commands. If the alarm persists, go to Step 3.

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

    4. End.

  • Cause 69517: Fuse slotid%s is failed, Fuse is absent.

    1. Determine the position where the fuse component is faulty.

    2. Check whether a new fuse component needs to be inserted into the position.

    • If so, go to Step 3.
    • If not, go to Step 5.

    3. Insert the fuse component into the corresponding position and check whether the alarm is cleared.

    • If so, go to Step 5.
    • If not, go to Step 4.

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

    5. End.

  • Cause 69632: LPU slotID is failed, the memory QDR of PE PEID is abnormal.

    1. Replace the board and check whether the fault is rectified.

    • If so, go to Step 3.
    • If no, go to Step 2.

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

    3. The procedure ends.

  • Cause 69634: LPU slot slotID is failed,the inner status of the TMtmID is abnormal.

    1. Replace the board and check whether the alarm is cleared.

    • If so, go to Step 3.
    • If not, go to Step 2.

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

    3. End.

  • Cause 132631: The packet loss count of TM on slot slotid exceeded the alarm threshold.

    1. Check whether the traffic exceeds the bandwidth of the port and board.

    • If so, go to Step 2.
    • If not, go to Step 3.

    2. Perform reasonable layout of the network topology to reduce traffic pressure on network nodes. 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 132648: SFU MPI control bus check fault.

    1. Run the reset slot command to reset the faulty SFU. After the SFU is registered, check whether the alarm is cleared.

    • 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.

Parent Topic: DEVM
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >