Hello, everyone!
This post will tell you one issue for How to Handle A_LOC reported by OSN 3500.
Problem description:
There was A_LOC alarm appeared on the 6th port of PD3 board,due to which the E3 service was down .Two other E3's configured on the same PD3 board were working normal .
A_LOC (Loss of clock) alarm was reported which is major alarm and by monitoring the performance it was obsserved there were some errors E3_LCV_SDH (Line code violation ) in quite large number E3_LES_SDH,E3_LSES_SDH .
392086 15 A_LOC MJ start 2007-09-23 20:13 None 0x01 0x00 0x06 0xff 0xff
:per-get-curdata:15,0,0,0,perall,15m;
15 15m 2007-09-23 20:13 e3_lcv_sdh 1 6 84933870
15 15m 2007-09-23 20:13 e3_les_sdh 1 1 649
15 15m 2007-09-23 20:13 e3_les_sdh 1 4 649
15 15m 2007-09-23 20:13 e3_lses_sdh 1 1 649
Handling procedure:
The alarm was reported due to the patching issue of E3 at DDF on customer end.
Root cause:
NA.
Solution:
We make a local loop at site where the alarm was reported, towards other vendor equipment and they were not getting local loop as well. After that the customer patching patching was removed from DDF and it was observed that A_LOC alarm was disappeared .Than we make the Hard loop towards system side again the A_LOC alarm was disappeared and there was no alarm no the trail as well. So after that patching was redone by the customer end ,alarm was cleared and E3 service was up .
That's all, I welcome everyone to leave a message and exchange in the comment area!
Thank you！
