Hello everyone! Today I'll introduce you a diagnosis method for NE disconnection from OMC server.
Symptom:
In the topology view, select the disconnected NE and click Connect to NE. The NE displays that the connection is not successful.
Possible Cause:
1. The device communication IP address of the eOMC cannot be pinged from the NE communication IP address.
2. The two-way authentication between the eOMC and the NE fails.
3. The NE is locked because an incorrect password is entered consecutively.
4. The eOMC and NE certificates fail to be authenticated.
5. It has been connected to another NMS.
Locating Process:
1. The message center displays "Network communication error", "NE no response", "SNMP connection failure", or "IP unreachable". The keywords "UNREACHABLE", "I_O_ERROR", and "RVI_OP_EMPTY_RET" are found in the med.log log, indicating that the network communication is normal.
log in to the eOMC server as user eoss in SSH mode.
Switch to user root. (su - root)
run the following command: ping -I IP address of the NE communication IP address. If the IP address cannot be pinged, change the communication IP address of the device or check whether the communication between the and the NE is normal.
if the NE is a base station or 2U, run the following command: Telnet to the IP 6007 of the NE to check whether the 6007 port of the NE can be connected. If the test port fails, check whether the communication between the NMS and the NE is faulty and whether the route is correctly configured.
2. Check the message center. If the message "Authentication error" is displayed and the keywords "SND_CRG_ERROR" and "zmq login error" are found in the med.log log, or the NE does not return any packet, the two-way authentication between the eOMC and the NE fails.
check whether the authentication password of the NE on the eOMC is correct.
Check whether the NE is connected to another NMS.
3. Check the message center. If the message "The NE has been locked" is displayed, search the med.log file for the keyword "RETCODE = 939589671 Internal error", which indicates that the NE is locked due to multiple login failures.
delete the NE from the eOMC, wait for 30s, and use the correct password to add the NE again.
4. The message "SSL authentication failure suggestion" is displayed in the message center. 1. Enable the eOMC compatible mode. 2. Update the NE certificate. Search the med.log file for the keyword "ssl connect failed", indicating that the certificate authentication between the NMS and the NE fails.
enable the eOMC compatibility switch. For details, see the eOMC product documentation.
update the NE certificate. For details, see the related product documentation of the NE.
5. Check the message center. If the message "Other NMS has logged in" is displayed and the keyword "U2000 already connected" is found in the med.log log, it indicates that the NE is connected to another NMS.
