ALM-135463001 hwOpticalInvalid

Description

Optical Module is invalid. (EntPhysicalIndex=[EntPhysicalIndex], EntPhysicalName=[EntPhysicalName], EntityTrapFaultID=[EntityTrapFaultID], Reason=[Reason])

An optical module was faulty.

Attribute

Parameters

Impact on the System

• Cause 2: Output Optical Power Too High.

  Services on the optical module may be affected, which may cause bit errors, error packets, or even service interruption.

• Cause 3: Output Optical Power Too Low.

  Services on the optical module may be affected, which may cause bit errors, error packets, or even service interruption.

• Cause 4: Input Optical Power Too High.

  Services on the optical module may be affected, which may cause bit errors, error packets, or even service interruption.

• Cause 5: Input Optical Power Too Low.

  Services on the optical module may be affected, which may cause bit errors, error packets, or even service interruption.

• Cause 7: The IIC of the optical module failed.

  Services on the optical module may be affected, which may cause bit errors, error packets, or even service interruption.

• Cause 8: The optical signals received by the optical module were lost.

  Services on the optical module may be affected, which may cause bit errors, error packets, or even service interruption.

• Cause 9: The electrical signals sent by the optical module were lost.

  Services on the optical module may be affected, which may cause bit errors, error packets, or even service interruption.

• Cause 10: Loss of lock was detected in the receive direction by the optical module.

  Services on the optical module may be affected, which may cause bit errors, error packets, or even service interruption.

• Cause 11: Loss of lock was detected in the transmit direction by the optical module.

  Services on the optical module may be affected, which may cause bit errors, error packets, or even service interruption.

• Cause 12: The optical module failed to send signals.

  Services on the optical module may be affected, which may cause bit errors, error packets, or even service interruption.

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

  Services may be interrupted.

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

  Services may be interrupted.

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

  Services may be interrupted.

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

  Services may be interrupted.

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

  Services may be interrupted.

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

  Services may be interrupted.

• Cause 19: The power current of the optical module is too high.

  Services might be interrupted.

Possible Causes

• Cause 2: Output Optical Power Too High.
• Cause 3: Output Optical Power Too Low.
• Cause 4: Input Optical Power Too High.
• Cause 5: Input Optical Power Too Low.
• Cause 7: The IIC of the optical module failed.
• Cause 8: The optical signals received by the optical module were lost.
• Cause 9: The electrical signals sent by the optical module were lost.
• Cause 10: Loss of lock was detected in the receive direction by the optical module.
• Cause 11: Loss of lock was detected in the transmit direction by the optical module.
• Cause 12: The optical module failed to send signals.
• Cause 13: The voltage of the optical module was too high.
• Cause 14: The voltage of the optical module was too low.
• Cause 15: The bias current of the optical module was too high.
• Cause 16: The bias current of the optical module was too low.
• Cause 17: The temperature of the optical module was too high.
• Cause 18: The temperature of the optical module was too low.
• Cause 19: The power current of the optical module is too high.

Procedure

• Cause 2: Output Optical Power Too High.

  1. Run the display interface command in the user view to check whether the Tx power of the interface is within the allowed range.

  • If so, collect alarm, log, and configuration information, and contact technical support personnel.
  • If not, replace the optical module.

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

• Cause 3: Output Optical Power Too Low.

  1. Run the display interface command in the user view to check whether the Tx power of the interface is within the allowed range.

  • If so, go to step 2.
  • If not, replace the optical module.

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

• Cause 4: Input Optical Power Too High.

  1. Run the display interface command in the user view to check whether the Rx power of the interface is within the allowed range.

  • If so, collect trap, log, and configuration information, and contact technical support personnel.
  • If not, go to step 2.

  2. Check whether an alarm indicating that the Tx power is too high is generated on the remote interface.

  • If so, clear the alarm on the remote interface first.
  • If not, go to step 3.

  3. Check whether the peer optical module matches the local optical module.

  • If not, replace the optical module with one that matches the peer optical module.
  • If so, go to step 4.

  4. Add an optical attenuator to the local end. It is recommended that the attenuation be increased by -5 dB.

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

  6. If the alarm still persists, collect alarm, log, and configuration information, and contact technical support personnel.

• Cause 5: Input Optical Power Too Low.

  1. Run the display interface command in the user view to check whether the Rx power of the interface is within the allowed range.

  • If so, collect trap, log, and configuration information, and contact technical support personnel.
  • If not, go to step 2.

  2. If the peer interface is not Down and no alarm is generated, go to step 4.

  3. Rectify the fault and clear the alarm on the peer interface. If the alarm is cleared, no further action is required.

  4. Check whether the optical fiber is faulty. If so, replace the optical fiber.

  5. Check whether an alarm is generated on the local interface. If so, replace the optical module to rectify the fault.

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

• Cause 7: The IIC of the optical module failed.

  1. Check whether the optical module is securely installed. If so, remove the optical module and check whether the port has bent pins or is damaged. Try replacing the optical module. If the fault persists, contact technical support personnel.

• Cause 8: The optical signals received by the optical module were lost.

  Check whether the optical fiber is faulty. If so, replace the optical fiber. If the fault persists, collect alarm, log, and configuration information, and contact technical support personnel.

• Cause 9: The electrical signals sent by the optical module were lost.

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

• Cause 10: Loss of lock was detected in the receive direction by the optical module.

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

• Cause 11: Loss of lock was detected in the transmit direction by the optical module.

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

• Cause 12: The optical module failed to send signals.

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

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

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

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

  2. Handle the power alarm and 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 voltage of the board where the optical module resides and check whether a voltage alarm is generated on the NMS.

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

  4. Handle the voltage alarm and 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 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 where the optical module resides and 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 alarm, log, and configuration information, and contact technical support engineers.

  8. End.

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

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

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

  2. Handle the power alarm and 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 voltage of the board where the optical module resides and check whether a voltage alarm is generated on the NMS.

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

  4. Handle the voltage alarm and 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 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 where the optical module resides and 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 alarm, log, and configuration information, and contact technical support engineers.

  8. End.

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

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

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

  2. Handle the power alarm and 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 of the board where the optical module resides and check whether a current alarm is generated on the NMS.

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

  4. Handle the current alarm and 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 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 where the optical module resides and 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 alarm, log, and configuration information, and contact technical support engineers.

  8. End.

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

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

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

  2. Handle the power alarm and 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 of the board where the optical module resides and check whether a current alarm is generated on the NMS.

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

  4. Handle the current alarm and 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 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 where the optical module resides and 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 alarm, log, and configuration information, and contact technical support engineers.

  8. End.

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

  1. Run the display alarm all command to check whether the hwBoardInvalid alarm is generated.

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

  2. Handle the alarm and 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 temperature of the board where the optical module resides and check whether a board temperature alarm is generated on the NMS.

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

  4. Handle the board temperature 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 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 where the optical module resides and 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 alarm, log, and configuration information, and contact technical support engineers.

  8. End.

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

  1. Run the display alarm all command to check whether a temperature alarm is generated.

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

  2. Handle the temperature alarm and 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 temperature of the board where the optical module resides and check whether a board temperature alarm is generated on the NMS.

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

  4. Handle the board temperature 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 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 where the optical module resides and 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 alarm, log, and configuration information, and contact technical support engineers.

  8. End.

• Cause 19: The power current of the optical module is too high.

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

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

  2. Handle the power alarm and 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 of the board where the optical module resides and check whether a current alarm is generated on the NMS.

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

  4. Handle the current alarm and 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 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 where the optical module resides and 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 alarm, log, and configuration information, and contact technical support engineers.

Related Information

None.