Got it

Causes and how to troubleshoot a unreachable NE on a OSN 3500 Highlighted

Latest reply: Dec 5, 2021 10:26:14 1209 14 9 0 1

Hello, everyone!

In this post, I would like to share with you the causes and how to troubleshoot an unreachable NE on an OSN 3500

Fault symptom

A single NE being unreachable. This topic describes the symptoms, impact, and possible causes of a single unreachable NE. In addition, this topic describes the required tools, precautions, and procedures for rectifying the fault.

Symptom

 On the U2000, a single NE is unreachable and the other NEs of the same site are reachable.

Impact on System 

The unreachable NE cannot be managed.

Possible Causes

  • Cause 1: The hardware is faulty.

  • Cause 2: The IP address or the ID of the NE is incorrectly set.

  • Cause 3: The fibers are faulty.

  • Cause 4: The DCC of the optical interface is disabled.

  • Cause 5: The NE software fails.


Tools, Equipment, and Materials

  • U2000 LCT

  • U2000


Procedure

  • Cause 1: The hardware is faulty. As a result, the NE is unreachable.

    • Check whether the external power supply device is working in its normal state.

      If...Then...The external power supply device is faculty refer to Service Interruptions Caused by Power Supply Failures to rectify the fault of the external power supply device. Check whether the NE recovers. If the NE does not recover, proceed to the next step. The external power supply device is working in the normal state proceed to the next step.

    • Check whether the power board is working in its normal state.

      If...Then...The power board is faulty see the Parts Replacement to replace the faulty board. Check whether the NE recovers. If the NE does not recover, proceed to the next step. The power board is working in the normal state proceed to the next step.

    • Log in to the NE through the U2000 LCT.

      If...Then...You fail to log in to the NE through the U2000 LCTThe SCC board or CXL board of the NE is faulty. See the Parts Replacement to replace the faulty board. Check whether the NE recovers. If the NE does not recover, check whether the fault is due to other causes. You successfully log in to the NE through the U2000 LCTCheck whether the fault is due to other causes.


  • Cause 2: The IP address or the ID of the NE is incorrectly set. As a result, the NE is unreachable.

    • Log in to the NE through the U2000 LCT and restore the original IP address and ID of the NE according to the record.

    • Check whether the NE recovers. If the NE does not recover, check whether the fault is due to other causes.

  • Cause 3: The fibers are faulty. As a result, the NE is unreachable.

    • Use the OTDR meter to test the fiber. Analyze the line attenuation curve displayed by the meter to determine whether fiber cut occurs on the line. For how to use the meter, see the OTDR user guide.

      If...Then...Fiber cut occurs on the line to replace the faulty fiber. Then, check whether the service is restored. If not, check whether the fault is due to other causes. Fiber cut does not occur on the line check whether the fault is due to other causes.


  • Cause 4: The DCC of the optical interface is disabled.

    • On the U2000, check whether the DCC of the optical interface is disabled or enabled.

      If...Then...The DCC of the optical interface is disabled to enable the DCC of the optical interface. Then, check whether the NE recovers. If not, proceed to the next step. The DCC of the optical interface is enabled to check whether the fault is due to other causes.

  • Cause 5: The NE software fails. As a result, the NE is unreachable.

    • Browse alarms by using the U2000, and determine the board that reports the alarm.

    • Load the NE software to the board, and perform a warm reset on the board by using the U2000 tool. Then, check whether the alarm is cleared.

    • Check whether the NE recovers. If not, proceed to other causes.



That's all, I hope you like it.

Thank you!


The post is synchronized to: Transmission O&M World

Very helpful in troubleshooting! Thanks for sharing this!
View more
  • x
  • convention:

good document for troubleshooting
View more
  • x
  • convention:

Is there any alarms reported by U2000 when a NE is unreachable?
View more
  • x
  • convention:

Posted by Anca at 2018-07-05 15:43 Is there any alarms reported by U2000 when a NE is unreachable?
Yes, you will see alarms .

1. GNE_CONNECT_FAIL : The Gateway NE Communication Fault
2. NE_COMMU_BREAK : NE Communication Fault
3.NE_NOT_LOGIN : The use logs out or fails to login
View more
  • x
  • convention:

Let me share my experience of "unreachable NE on a OSN 3500" .
DCC disabled . Accessing OSN 3500 via DCN.

My DCN network as below :- U2000 Server Located in Head Quarters <> LAN Switch <> DCN Router in Head Quarters<> MPLS Network <> DCN Router <> LAN Switch <> OSN 3500 GNE


Problem Description :- Observed below alarms in U2000
1. GNE_CONNECT_FAIL : The Gateway NE Communication Fault
2. NE_COMMU_BREAK : NE Communication Fault
3.NE_NOT_LOGIN : The use logs out or fails to login

Initial Action Taken : -

1. Tried soft reset and hard reset of AUX card, check settings of DCN communication of Gateway, changed phsyical cabling AUX card ETH port & swtich port. However, alarm still persists.

AUX Board :- AUX is the system auxillary interface board . AUX provides system with interfaces 10M/100M Lanswitch ,F&F, OAM , orderwire etc etc.

2. Connected Laptop to ETH port with IP address and subnet mask with same network of U2000 , not able to ping.

3. Switch over from the main control board (GSCC Board ) to the stand by and try to connect locally from NMS port to the NE. Still alarm persists.

Final Action :-
Tried switch over from the main control board to the stand by and try to connect locally from NMS port to the NE. No changes. Hence proceeded with replacement of AUX Board
View more
  • x
  • convention:

Posted by AbdulRauf at 2018-07-08 09:42 Let me share my experience of "unreachable NE on a OSN 3500" . DCC disabled . Accessing OSN 3500 via ...
thank you very much Abdul for sharing with us ur hands on experience. Keep up the good work :D
View more
  • x
  • convention:

Posted by AlexandruS at 2018-07-09 14:26 thank you very much Abdul for sharing with us ur hands on experience. Keep up the good work :D
you are welcome..
View more
  • x
  • convention:

interesting content.
View more
  • x
  • convention:

VinceD
VinceD Created Nov 10, 2021 18:37:22 (0) (0)
 
BAZ
MVE Author Created Nov 10, 2021 19:19:16

Very helpful in troubleshooting!
View more
  • x
  • convention:

12
Back to list

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.