DEVM/1/hwOpticalInvalid_active

Procedure

• Cause 136192: The optical module worked abnormally.

  1. Check whether the optical fiber works properly.

  • If not, replace the faulty optical fiber.

  2. Check whether an alarm is generated on the local interface. If so, replace the local optical module.

  3. Check whether an alarm is generated on the peer interface. If so, replace the peer optical module.

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

  5. End.

• Cause 136193: The output optical power was too high.

  1. Run the display interface command in the user view to check the current transmit optical power (Tx Power) of the local interface. If yes, go to Step 4.

  • If the peer port is not in the down state and no alarm is generated, go to Step 4.
  • Rectify the fault that the peer port is down and clear the alarm.

  2. Check whether the optical fiber is faulty. If yes, replace the optical fiber.

  3. Check whether an alarm is generated on the local interface. If an alarm is generated, replace the optical module to rectify the fault. If the alarm persists after the optical module is replaced, go to Step 4.

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

  5. End.

• Cause 136194: The output optical power was too low.

  1. Run the display interface command in the user view to check the current transmit optical power (Tx Power) of the local interface. If yes, go to Step 4.

  • If the peer port is not in the down state and no alarm is generated, go to Step 4.
  • Rectify the fault that the peer port is down and clear the alarm.

  2. Check whether the optical fiber is faulty. If yes, replace the optical fiber.

  3. Check whether an alarm is generated on the local interface. If an alarm is generated, replace the optical module to rectify the fault. If the alarm persists after the optical module is replaced, go to Step 4.

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

  5. End.

• Cause 136195: The input optical power was too high.

  1. Run the display interface command in the user view to check the current transmit optical power (Tx Power) of the local interface. If yes, go to Step 4.

  • If the peer port is not in the down state and no alarm is generated, go to Step 4.
  • Rectify the fault that the peer port is down and clear the alarm.

  2. Check whether the optical fiber is faulty. If yes, replace the optical fiber.

  3. Check whether an alarm is generated on the local interface. If an alarm is generated, replace the optical module to rectify the fault. If the alarm persists after the optical module is replaced, go to Step 4.

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

  5. End.

• Cause 136196: The input optical power was too low.

  1. Run the display interface command in the user view to check the current transmit optical power (Tx Power) of the local interface. If yes, go to Step 4.

  • If the peer port is not in the down state and no alarm is generated, go to Step 4.
  • Rectify the fault that the peer port is down and clear the alarm.

  2. Check whether the optical fiber is faulty. If yes, replace the optical fiber.

  3. Check whether an alarm is generated on the local interface. If an alarm is generated, replace the optical module to rectify the fault. If the alarm persists after the optical module is replaced, go to Step 4.

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

  5. End.

• Cause 136197: The voltage of the optical module was too high.

  1. Run the display alarm all command to check whether hwPowerInvalid is generated on the interface.

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

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

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

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

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

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

  • If the alarm is cleared, go to Step 8.
  • If the alarm persists, go to Step 5.

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

  • If the alarm is cleared, go to Step 8.
  • If the alarm persists, go to Step 6.

  6. Replace the board on which the optical module is installed, and then check whether the alarm is cleared.

  • If the alarm is cleared, go to Step 8.
  • If the alarm persists, go to Step 7.

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

  8. End.

• Cause 136198: The voltage of the optical module was too low.

  1. Run the display alarm all command to check whether hwPowerInvalid is generated on the interface.

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

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

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

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

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

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

  • If the alarm is cleared, go to Step 8.
  • If the alarm persists, go to Step 5.

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

  • If the alarm is cleared, go to Step 8.
  • If the alarm persists, go to Step 6.

  6. Replace the board on which the optical module is installed, and then check whether the alarm is cleared.

  • If the alarm is cleared, go to Step 8.
  • If the alarm persists, go to Step 7.

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

  8. End.

• Cause 136199: The bias current of the optical module was too high.

  1. Run the display alarm all command to check whether hwPowerInvalid is generated on the interface.

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

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

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

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

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

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

  • If the alarm is cleared, go to Step 8.
  • If the alarm persists, go to Step 5.

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

  • If the alarm is cleared, go to Step 8.
  • If the alarm persists, go to Step 6.

  6. Replace the board on which the optical module is installed, and then check whether the alarm is cleared.

  • If the alarm is cleared, go to Step 8.
  • If the alarm persists, go to Step 7.

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

  8. End.

• Cause 136200: The bias current of the optical module was too low.

  1. Run the display alarm all command to check whether hwPowerInvalid is generated on the interface.

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

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

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

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

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

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

  • If the alarm is cleared, go to Step 8.
  • If the alarm persists, go to Step 5.

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

  • If the alarm is cleared, go to Step 8.
  • If the alarm persists, go to Step 6.

  6. Replace the board on which the optical module is installed, and then check whether the alarm is cleared.

  • If the alarm is cleared, go to Step 8.
  • If the alarm persists, go to Step 7.

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

  8. End.

• Cause 136201: The temperature of the optical module was too high.

  1. Run the display alarm all command to check whether hwPowerInvalid is generated on the interface.

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

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

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

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

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

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

  • If the alarm is cleared, go to Step 8.
  • If the alarm persists, go to Step 5.

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

  • If the alarm is cleared, go to Step 8.
  • If the alarm persists, go to Step 6.

  6. Replace the board on which the optical module is installed, and then check whether the alarm is cleared.

  • If the alarm is cleared, go to Step 8.
  • If the alarm persists, go to Step 7.

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

  8. End.

• Cause 136202: The temperature of the optical module was too low.

  1. Run the display alarm all command to check whether hwPowerInvalid is generated on the interface.

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

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

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

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

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

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

  • If the alarm is cleared, go to Step 8.
  • If the alarm persists, go to Step 5.

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

  • If the alarm is cleared, go to Step 8.
  • If the alarm persists, go to Step 6.

  6. Replace the board on which the optical module is installed, and then check whether the alarm is cleared.

  • If the alarm is cleared, go to Step 8.
  • If the alarm persists, go to Step 7.

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

  8. End.

• Cause 136204: The service life of the optical module laser was about to expire.

  1. Replace the module, 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 136205: The PLD or Flash initializatiaon fault.

  1. Replace the module, 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 136206: The power supply fault.

  1. Replace the module, 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 136207: The CFP checksum fault.

  1. Replace the module, 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 136208: The I2C interface of the Smart-Clock module was faulty.

  1. Reset the Smart-Clock module and check if the alarm is cleared.

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

  2. Replace the Smart-Clock module and check if 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 136209: The phase-locked loop chip of the Smart-Clock module was faulty.

  1. Reset the Smart-Clock module and check if the alarm is cleared.

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

  2. Replace the Smart-Clock module and check if 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 136210: The GPS chip of the Smart-Clock module was faulty.

  1. Reset the Smart-Clock module and check if the alarm is cleared.

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

  2. Replace the Smart-Clock module and check if 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 136211: The memory chip of the Smart-Clock module was faulty.

  1. Reset the Smart-Clock module and check if the alarm is cleared.

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

  2. Replace the Smart-Clock module and check if 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 136212: The SerDes interface of the Smart-Clock module was faulty.

  1. Reset the Smart-Clock module and check if the alarm is cleared.

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

  2. Replace the Smart-Clock module and check if 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 136213: The internal 1PPS signals of the Smart-Clock module were abnormal.

  1. Reset the Smart-Clock module and check if the alarm is cleared.

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

  2. Replace the Smart-Clock module and check if 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 136214: The internal clock source signals of the Smart-Clock module were abnormal.

  1. Reset the Smart-Clock module and check if the alarm is cleared.

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

  2. Replace the Smart-Clock module and check if 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 136215: The system clock of the Smart-Clock module was faulty.

  1. Reset the Smart-Clock module and check if the alarm is cleared.

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

  2. Replace the Smart-Clock module and check if 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 136216: The voltage of the Smart-Clock module was abnormal.

  1. Reset the Smart-Clock module and check if the alarm is cleared.

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

  2. Replace the Smart-Clock module and check if 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 136217: The temperature sensor of the Smart-Clock module was faulty.

  1. Reset the Smart-Clock module and check if the alarm is cleared.

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

  2. Replace the Smart-Clock module and check if 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 136218: The antenna of the Smart-Clock module was abnormal.

  1. Reset the Smart-Clock module and check if the alarm is cleared.

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

  2. Replace the Smart-Clock module and check if 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 136219: The temperature of the Smart-Clock module exceeded the limit.

  1. Reset the Smart-Clock module and check if the alarm is cleared.

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

  2. Replace the Smart-Clock module and check if 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 136225: The receiving total power of the optical module is too high.

  1. Run the display interface command in the user view to check whether the input optical power (Rx Power) on the current interface is in the normal range. If the Rx power is in the normal range, go to Step 4.

  • If the remote interface is physically Up and no alarm indicating low output optical power is generated on the remote interface, go to Step 5.
  • If the remote interface is physically Down and an alarm indicating interface Down is generated on the remote interface, rectify the fault on the remote interface.

  2. Check whether the fiber is faulty. If so, replace the fiber.

  3. Replace the optical module on the local interface. If the alarm persists after the optical module is replaced, go to Step 4.

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

  5. End.

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

  1. Run the display interface command in the user view to check whether the input optical power (Rx Power) on the current interface is in the normal range. If the Rx power is in the normal range, go to Step 4.

  • If the remote interface is physically Up and no alarm indicating low output optical power is generated on the remote interface, go to Step 5.
  • If the remote interface is physically Down and an alarm indicating interface Down is generated on the remote interface, rectify the fault on the remote interface.

  2. Check whether the fiber is faulty. If so, replace the fiber.

  3. Replace the optical module on the local interface. If the alarm persists after the optical module is replaced, go to Step 4.

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

  5. End.

• Cause 136227: A component on the MSA's private register module fails.

  1. Replace the module, 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 136228: A severe fault occurs on a module.

  1. Replace the module, 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 136229: The fiber or optical module on card is abnormal.

  1. Check whether the optical fiber fails. If the optical fails, replace it.

  2. Check whether the local wavelength and remote wavelength are the same. If they are different, change the channel number.

  3. Check whether alarm information exists on the local interface. If alarm information exists, replace the optical module of the local interface.

  4. Check whether alarm information exists on the remote interface. If alarm information exists, replace the optical module of the remote interface.

  5. If the alarm persists after the optical module is replaced, collect trap, log, and configuration information, and contact technical support.

  6.End.

• Cause 136230: The optical module connected abnormally.

  1. Check whether the optical module is properly inserted. If the optical module is not properly inserted, re-insert it and tighten the screws.

  2. If the alarm persists, replace the optical module.

  3. If the alarm persists, check whether the FEC mode and wavelength configurations are consistent between directly connected interfaces. Run the display this command to check the FEC mode configuration, and run the display this interface command to check the wavelength configuration. If either configuration is inconsistent, reconfigure the FEC mode or change the wavelength channel ID accordingly.

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

  5. End.

• Cause 136232: After an optical module that supports FEC-ETH was inserted in to an interface, the interface did not start the FEC-ETH function.

  1. Enable FEC-ETH on the interface and check if 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 136233: The Smart-Clock module failed to obtain leap second information in Single-GLONASS mode or GPS-GLONASS mode.

  1. Run the smart-clock gnss-model command in the GE-interface view to switch to the other mode(GPS, BEIDOU, GPS-BEIDOU). Then check whether the alarm is cleared.

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

  2. Run the smart-clock leap command in the GE-interface view to configure leap second information. 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 136234: The start-up of GNSS chip in Smart-Clock module was abnormal.

  1. Replace the Smart-Clock module. 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.