Customers use analyzer to test CES service on OSN3500, using typical networking and configuration.
They found that the analyzer report one alarm every 49 or 50 minutes.
CES service was down in a fixed time interval. That is a typical problem caused by clock not synchronized. It can be confirmed by the following two aspects.
1. Enable CES PW performance monitoring. After the error occurs several times, view historical performance. We found the remote NE, i.e. OSN3500 B in the figure, has the buffer underflow records in the same time period as CES service down.
3
From the buffer underflow records, it is more clearly that clock not synchronized leading to the service down.
2. By viewing the clock tracing relationship, we found that two OSN3500s are synchronized by using the Synchronous Ethernet Clock Protocol. But the analyzer is not synchronized with the two NEs.
After modifying the clock mode of the analyzer to trace with the OSN3500 A, all equipment of in the network are synchronized, and the service become stable.
Analyzer clock and NE clock is not synchronized.
To synchronize all equipment clock, including the analyzer clock.
CES service down by fixed time intervals, is a typical problem caused by clock not synchronized. It can be confirmed by viewing the CES PW performance and to find whether there are buffer overflow or underflow records by the same interval. Synchronizing all equipment clock, including the analyzer clock, to solve this problem.
Thunder-link.com now have Huawei OSN series, MERO series, PTN/TRN series equipment, GPON products, datacom products and various board on promotion, more than 86% off list price, please come to visit www.thunder-link.com; or just email for inquire: sales@thunder-link.com
Comments are closed