Hi guys!!
I would like to share with you a "Communication between the NCE and a GNE fails" issue on the OptiX OSN 8800 transmission network.
Description:
The network topology is similar as follows:
And the DCN Management Configuration is shows below:
The customer report about the appearance of some alarms regarding communication between NCE and some NEs fails on the network.
Alarms on GNE1 (node C)
Alarms on NEs (nodes A, B, D, E, G, H* and I)
*in this case shows the node H alarms, identical in the other nodes (NEs)
The alarms description is as follows:
NE_COMMU_BREAK and NE_NOT_LOGIN alarms cleared in a few seconds because an automatic switching from Primary GNE1 to GNE2 occurs.
Now all the nodes of the network are being managed through GNE2 (node F).
The question is: Why does the communication between NCE and GNE1 (node C) fail?
Solution:
The possible causes of the GNE_CONNECT_FAIL alarm are as follows:
Cause 1: The parameter settings about DCN communicacion of the gateway NE are incorrect.
a) Open the Network Management app and choose Topology > NE Onboarding > DCN Management for Transport NEs from the main menu. Click the GNE tab.
b) Check whether the IP address and port number of the faulty gateway NE are correct.
If correct, proceed to Steps 1.c to 1.e.
If incorrect, proceed to Step 2.
c) Optional: Right-click the faulty gateway NE and choose Modify GNE. In the displayed Modify GNE dialog box, correctly set the communication parameters, and then click Apply.
d) The Warning dialog box is displayed to indicate that this operation may interrupt communication, click OK.
e) If the alarm persists, proceed with the next step.
<<< These points are verified and all parameters are correct >>>
Cause 2: The parameter settings about DCN communication of a non-gateway NE connected to the gateway NE are incorrect.
a) In NE Explorer, select the non-gateway NE and choose Communication > Communication Parameters from Function Tree.
b) Check whether the subnet mask of the non-gateway NE is the same as the subnet mask of the gateway NE. If not, proceed with the next step.
c) Set the subnet masks of the non-gateway NE and gateway NE to the same. Then click Apply.
d) If the alarm persists, proceed with the next step.
<<< These points are verified and all parameters are correct >>>
Cause 3: The physical link between the NCE and the gateway NE is broken.
a) Check whether the STAT or Run indicator on the SCC of the gateway NE blinks. If not, power on the equipment.
<<< This point is verified and SCC is fine >>>
b) Set the communication parameters (IP address and subnet mask) on a laptop computer the same as the communication parameters on the NCE. Run the ping IP address of the NE command at the four detection points in the following figure in turn to locate the faulty point of the physical link.
<<< Our maintenance technicians find the network cable between switch and GNE1 (node C) disconnected in the switch port. Third-party communications staff disconnect this network cable by mistake >>>
After connect the network cable again correctly, the communication between NCE and GNE1 (node C) is reestablished, an automatic switching occurs from GNE2 (node F) to Primary GNE1 (node C) due to the revertive mode setting.
GNE_CONNECT_FAIL and NE_COMMU_GNE_SWITCH alarms clears.
Cause 4: GNE Disconnected due to Mismatched SSL Certificates.
<<< Does not apply >>>
References:
- HedEx
BR
