PIC/1/hwOpticalFail_active

Procedure

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

  1. Replace the unmatched optical module with the one that matches the interface.

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

• Cause 135937: The output optical power was too high

  1. Run the display interface command in the user view to check whether the output optical power (Tx power) on the current interface is in the normal range.

  • If the Tx power is in the normal range, collect the alarm information, log information, and configuration information, and then contact technical support personnel.
  • If the Tx power is beyond the normal range, replace the optical module.
• Cause 135938: The output optical power of the optical module was too low

  1. Run the display interface command in the user view to check whether the output optical power (Tx power) on the current interface is in the normal range.

  • If the Tx power is in the normal range, collect the alarm information, log information, and configuration information, and then contact technical support personnel.
  • If the Tx power is beyond the normal range, replace the optical module.
• Cause 135939: The input optical power was 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, collect the alarm information, log information, and configuration information, and then contact technical support personnel.

  2. Check whether the alarm indicating high output optical power is generated on the remote end. If so, handle the alarm on the remote end first.

  3. Check whether the model of the optical module on the remote end matches that of the optical module on the local end. If not, replace the optical module on the local end and ensure that this optical module matches the optical module on the remote end.

  4. Add an optical attenuator.

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

• Cause 135940: The input optical power was 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, collect the alarm information, log information, and configuration information, and then contact technical support personnel.

  • 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.

  4. If the alarm persists after the optical module is replaced, collect the alarm information, log information, and configuration information, and then contact technical support personnel.

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

  1. Check whether a power supply alarm is generated in the NMS.

  • If a power supply alarm is generated, go to step 2.
  • If a power supply alarm is not generated, go to step 3.

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

  • If the alarm is cleared, go to step 8.
  • If the alarm is not cleared, go to step 3.

  3. Check whether a voltage alarm is generated on the board where the optical module resides in the NMS.

  • If a voltage alarm is generated, go to step 4.
  • If a voltage alarm is not generated, go to step 5.

  4. Clear the voltage alarm, and check whether the alarm is cleared.

  • If the alarm is cleared, go to step 8.
  • If the alarm is not cleared, go to step 5.

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

  • If the alarm is cleared, go to step 8.
  • If the alarm is not cleared, go to step 6.

  6. Replace the board where the optical module resides, and check whether the alarm is cleared.

  • If the alarm is cleared, go to step 8.
  • If the alarm is not cleared, go to step 7.

  7. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.

  8. End.

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

  1. Check whether a power supply alarm is generated in the NMS.

  • If a power supply alarm is generated, go to step 2.
  • If a power supply alarm is not generated, go to step 3.

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

  • If the alarm is cleared, go to step 8.
  • If the alarm is not cleared, go to step 3.

  3. Check whether a voltage alarm is generated on the board where the optical module resides in the NMS.

  • If a voltage alarm is generated, go to step 4.
  • If a voltage alarm is not generated, go to step 5.

  4. Clear the voltage alarm, and check whether the alarm is cleared.

  • If the alarm is cleared, go to step 8.
  • If the alarm is not cleared, go to step 5.

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

  • If the alarm is cleared, go to step 8.
  • If the alarm is not cleared, go to step 6.

  6. Replace the board where the optical module resides, and check whether the alarm is cleared.

  • If the alarm is cleared, go to step 8.
  • If the alarm is not cleared, go to step 7.

  7. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.

  8. End.

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

  1. Check whether a power supply alarm is generated in the NMS.

  • If a power supply alarm is generated, go to step 2.
  • If a power supply alarm is not generated, go to step 3.

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

  • If the alarm is cleared, go to step 8.
  • If the alarm is not cleared, go to step 3.

  3. Check whether a current alarm is generated on the board where the optical module resides in the NMS.

  • If a current alarm is generated, go to step 4.
  • If a current alarm is not generated, go to step 5.

  4. Clear the current alarm, and check whether the alarm is cleared.

  • If the alarm is cleared, go to step 8.
  • If the alarm is not cleared, go to step 5.

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

  • If the alarm is cleared, go to step 8.
  • If the alarm is not cleared, go to step 6.

  6. Replace the board where the optical module resides, and check whether the alarm is cleared.

  • If the alarm is cleared, go to step 8.
  • If the alarm is not cleared, go to step 7.

  7. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.

  8. End.

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

  1. Check whether a power supply alarm is generated in the NMS.

  • If a power supply alarm is generated, go to step 2.
  • If a power supply alarm is not generated, go to step 3.

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

  • If the alarm is cleared, go to step 8.
  • If the alarm is not cleared, go to step 3.

  3. Check whether a current alarm is generated on the board where the optical module resides in the NMS.

  • If a current alarm is generated, go to step 4.
  • If a current alarm is not generated, go to step 5.

  4. Clear the current alarm, and check whether the alarm is cleared.

  • If the alarm is cleared, go to step 8.
  • If the alarm is not cleared, go to step 5.

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

  • If the alarm is cleared, go to step 8.
  • If the alarm is not cleared, go to step 6.

  6. Replace the board where the optical module resides, and check whether the alarm is cleared.

  • If the alarm is cleared, go to step 8.
  • If the alarm is not cleared, go to step 7.

  7. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.

  8. End.

• Cause 135947: The Smart-Clock module frequency lock state is failed.

  1. Adjust the GPS antenna. Then, check whether the alarm is cleared.

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

  2. Replace the antenna system. Then, check whether the alarm is cleared.

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

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

  4. End.

• Cause 135948: The Smart-Clock module time lock state is failed.

  1. Adjust the GPS antenna. Then, check whether the alarm is cleared.

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

  2. Replace the antenna system. Then, check whether the alarm is cleared.

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

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

  4. End.