The NodeB receives IP Clock data from IPCLK1000 with very large deviation when it is connected directly to the NE40 optic port. The NodeB can not synchronize. All alarm and trace information is in attachment. But it is OK if it is connected to the NE40 through PTN950
NE40E Version: V600R001C00
PTN910 Version: V100R001C01SPC500
NodeB DBS3900 WCDMA Version: V200R011C00SPC230
In this project most NodeBs are connected to the IP Clock in the following way: (NodeB <---> PTN910 <---> PTN950 <---> NE40E <---> IPCLK1000)
Only 1 NodeB is connected to NE40E directly using optical FE port:
( NodeB Optical FE <---> Optical FE NE40E Electrical FE <---> Electrical FE IPCLK1000)
Reference Clock Source Abnormal
Need to connect NodeB to PTN first. Connect NodeB to IPCLK1000 in the following way: NodeB Optical FE <---> Opical FE Quidway3500 Electrical FE <---> Electrical FE PTN950 <---> NE40E <---> IPCLK1000
After alarm "Reference Clock Source Abnormal"( see attachment " ALM-10-02-22-17-20-40.csv")
was appeared we started related traces in NodeB:
1. IP Clock Data Gather Monitor. The execution results are in the following attachments: IP Clock Data Gather Monitoring_2010-02-22-15-24-58_Cabinet No.-Master cabinet_Subrack No.-0_Slot No.-7.txt; Large offset.JPG. The results show the IP Clock source unstability for NodeB connected directly to NE40E.
2. IP trace in NodeB LMT. The execution results are in the following attachment: IP_Trace.rar. The result shows that there are no any other PTP 1588v2 packets received by NodeB except for IPCLK1000 (Source IP 10.46.2.124).
3. Packet loss of IP level in NodeB LMT. The execution results are in the following attachment: Packets Loss of IP Level_2010-02-22-17-28-33_Rack No.-Master cabinet_Subrack No.-0_Slot No.-7_SubBoard Type-BASE_BOARD_Port Type-ETH_Port No.-0_Report Period(s)-1.txt. The result shows that there are no lost IP packets.
Then we checked NE40E configuration: attachment NE40E cfg.txt. The NodeB is connected to Optical FE port 11. The PTP function on this port is not activated.