Checking Network Connections Among NEs

Hi dear,

After the core network, eNodeB, and switch configurations are complete, you can run the Ping command to check whether the network communications are normal to rule out bottom-layer link faults.

Hello,

1.1 GNE Disconnection Symptom The icon of a GNE is gray. According to the GNE tab of the DCN Management window, the GNE is being connected. Possible Causes The U2000 fails to establish a TCP connection with the GNE or the established TCP connection is interrupted. Procedure    Step 1      Check whether the GNE has a reachable socket connection. 1.         Choose Administration > DCN Management from the main menu. 2.         In the DCN Management window, click the GNE tab and check the IP address and port of the GNE. 3.         Ping the IP address of the GNE from the U2000 server. −       If the ping test fails, the GNE may be running improperly or the network may be faulty. Then check the running status of the GNE and the network condition. −       If the ping test succeeds, the GNE may be disconnected due to high packet loss rate. Then go to step 4. 4.         On the U2000 server, run the telnet command to test the TCP connection. If the test fails, contact the device technical support.    Step 2      Check the ACL of the GNE. If the U2000 server IP address is prohibited in the ACL, the GNE will be disconnected.    Step 3      Check whether excess socket connections have been established. If the NE management process of the GNE has multiple instances, the number of socket connections may reach the maximum limit. Then no more socket connections can be established, rendering the GNE disconnected. In that event, save socket connections by shutting down unnecessary U2000s and other tools that connect to NEs.    Step 4      Check the firewall and antivirus software settings. Incorrect firewall or antivirus software settings will lead to data truncation. Shut down the firewall and antivirus software if disconnection occurs.    Step 5      Check the running status of the OS. If a large number of programs are running at the same time, the OS will have to close communications connections, rendering the GNE disconnected. In that event, stop unnecessary programs. 1.2 Non-gateway NE Disconnection Symptom The icon of a non-gateway NE is gray. Procedure    Step 1      Check the number of NEs connected to the related GNE. If more than 50 NEs are connected to the same GNE, the GNE will not be able to forward data correctly, rendering the non-gateway NEs disconnected. In that event, replan the network structure and adjust the DCN.    Step 2      Test the communications status of the NE. 1.         Choose Administration > DCN Management from the main menu. 2.         In the DCN Management window, click the NE tab. 3.         On the NE tab, right-click the disconnected NE and choose Test NE from the shortcut menu. The U2000 begins to send data to the NE. About 10 seconds later, a failure message is reported. In that event, check that the GNE is properly forwarding data. 1.3 NE Login Failure Symptom An NE is properly communicating with the U2000, but its login status shifts between Logged in and Not logged in at an interval of about 5 seconds. The NE_NOT_LOGIN alarm is generated and cleared repeatedly. Possible Causes The same NE user is used on another U2000. Procedure Shut down a U2000 or switch to another NE user.

Thanks

Hello,

1.1 GNE Disconnection Symptom The icon of a GNE is gray. According to the GNE tab of the DCN Management window, the GNE is being connected. Possible Causes The U2000 fails to establish a TCP connection with the GNE or the established TCP connection is interrupted. Procedure    Step 1      Check whether the GNE has a reachable socket connection. 1.         Choose Administration > DCN Management from the main menu. 2.         In the DCN Management window, click the GNE tab and check the IP address and port of the GNE. 3.         Ping the IP address of the GNE from the U2000 server. −       If the ping test fails, the GNE may be running improperly or the network may be faulty. Then check the running status of the GNE and the network condition. −       If the ping test succeeds, the GNE may be disconnected due to high packet loss rate. Then go to step 4. 4.         On the U2000 server, run the telnet command to test the TCP connection. If the test fails, contact the device technical support.    Step 2      Check the ACL of the GNE. If the U2000 server IP address is prohibited in the ACL, the GNE will be disconnected.    Step 3      Check whether excess socket connections have been established. If the NE management process of the GNE has multiple instances, the number of socket connections may reach the maximum limit. Then no more socket connections can be established, rendering the GNE disconnected. In that event, save socket connections by shutting down unnecessary U2000s and other tools that connect to NEs.    Step 4      Check the firewall and antivirus software settings. Incorrect firewall or antivirus software settings will lead to data truncation. Shut down the firewall and antivirus software if disconnection occurs.    Step 5      Check the running status of the OS. If a large number of programs are running at the same time, the OS will have to close communications connections, rendering the GNE disconnected. In that event, stop unnecessary programs. 1.2 Non-gateway NE Disconnection Symptom The icon of a non-gateway NE is gray. Procedure    Step 1      Check the number of NEs connected to the related GNE. If more than 50 NEs are connected to the same GNE, the GNE will not be able to forward data correctly, rendering the non-gateway NEs disconnected. In that event, replan the network structure and adjust the DCN.    Step 2      Test the communications status of the NE. 1.         Choose Administration > DCN Management from the main menu. 2.         In the DCN Management window, click the NE tab. 3.         On the NE tab, right-click the disconnected NE and choose Test NE from the shortcut menu. The U2000 begins to send data to the NE. About 10 seconds later, a failure message is reported. In that event, check that the GNE is properly forwarding data. 1.3 NE Login Failure Symptom An NE is properly communicating with the U2000, but its login status shifts between Logged in and Not logged in at an interval of about 5 seconds. The NE_NOT_LOGIN alarm is generated and cleared repeatedly. Possible Causes The same NE user is used on another U2000. Procedure Shut down a U2000 or switch to another NE user.

hanks

Hello,
Please refer to the link:
http://support.huawei.com/huaweiconnect/carrier/en/thread-139713-1-1.html
Thanks

On eNodeB, use DSP S1INTERFACE command to check the status ( optional execute DSP X2INTERFACE, if configured )
On core network side , use PING command to check connectivity on S5, S6 and S11 interfaces.
For trunking network, use PING to test connectivity over Tx and Rx interfaces

Hi dear, look here:

 Step 1     On the eNodeB side, run the Ping command to check whether the S1-U IP address of the core network can be pinged from the eNodeB.

l   Set Source IP to the S1 interface IP address of the eNodeB.

l   Set Destination IP to the S1-U IP address of the core network.

                              

 Step 2     On the eNodeB side, run the Ping command to check whether the S1-C IP address of the core network can be pinged from the eNodeB.

l   Set Source IP to the S1 interface IP address of the eNodeB.

l   Set Destination IP to the S1-C IP address of the core network.

                               

 

Step 3     On the eNodeB side, run the Ping command to check whether the O&M IP address of the NMS can be pinged from the eNodeB.

l   Set Source IP to the eNodeB IP address used for connecting the eNodeB to the NMS.

l   Set Destination IP to the O&M IP address of the NMS.

                             

 

Step 4     On the WebUI of an industry terminal, run the Ping command to check network connectivity.

1.         Choose System > Diagnosis.

2.         Select Ping for Diagnosis method.

3.         In the Target IP or domain text box, enter the IP address or domain name of the server PC.

4.         Specify Timeout.

5.         Click Ping.

The diagnosis results of the Ping command are displayed in the Result area at the bottom.

                             

Step 5     On the eSight, run the Ping command to check the network connectivity between the industry terminal and the eSight.

1.         Choose Resource > eLTE > Resource Monitor > Industry Terminal.

The Industry Terminal page is displayed.

2.         Click Ping.

The IP Ping window is displayed.

3.         In the IP Ping window, specify Pack Size(Byte) and Times(1-100).

4.         Click Ping.

The IP Ping results are displayed in the text box.