Today, I’d like to share a case.
Problem description
Partial MA5616 cannot be synchronized to the U2000 topology, and the ONU is in normal state.
Version information:
U2000: V100R002C01SPC100 (no patch)
MA5680T: V800R008C01SPC200 SPH307 HP2107
MA5616: V800R306C01B053 SPH009
Handling process
1. Version mapping fault.
2. Data configuration fault.
3. Synchronization fault.
4. NE management IP addresses conflict.
5. The number of NEs managed by the U2000 exceeds the limit.
6. Data in the memory table is incomplete.
root cause
Error in the U2000 memory table data.
Solution
1. Check the related version documents and the version mapping information. The version mapping is correct.
2. Log in to MA5680T and MA5616 from the U2000, and check the configuration of SNMP parameters. The configuration is correct. After the operator chooses File > Auto Discovery, the MA5616 can be added to the main topology, and the operator can manage it. The SNMP parameter configuration of the MA5616 is correct.
Right-click the MA5616 in the ONU list on the U2000 and choose the modification option. Check whether the IP address information on the page displayed is the same as the information queried by running display ont ipconfig on MA5680T. The IP address set on the U2000 and IP address of the device are the same.
3. Verify that the FTP settings of the U2000 are correct, and the FTP status is normal. The file backup from the MA5680T using FTP succeeds, which indicates that the FTP is in normal state. Delete the .poz file in the FTP root directory, restart the topology process and device management process, and synchronize the MA5680T to topology. The fault still exists. The FTP synchronization is not the cause.
4. On the U2000, press Ctrl+F and search for the management IP address of the MA5616. No NE is searched out. The IP addresses conflict is not the cause.
5. Run the following SQL statement to check whether the number of the NEs managed by the U2000 exceeds 4,000.
select (select count (ID) from BMSDB..bms_gdm_DeviceTab) + (select count (ID) from BMSDB..bms_gdm_Ne)
6. Import the memory table again, and synchronize the xPON module again. The fault is rectified.
The procedure is as follows:
a. Stop the U2000. (U2000\server\bin\stopnms)
b. Import the memory table again by running U2000\server\nemgr\nemgr_access\scriptsinstall\Init_cache.bat (Init_cache.sh for Solaris)
c. Start the U2000. (U2000\server\bing\startnms)
d. Synchronize data of the xPON to the U2000 by right-clicking the ONU list and choosing Synchronize.
Welcome to leave a message below.
We’ll study together.
Thank you!
