No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


IF board mismatch caused MW_LOF alarm even after achieved the RX level

Publication Date:  2012-07-25 Views:  131 Downloads:  0
Issue Description
In x country with y customer in Backbone project  a link achieved his RX level  but still display alarm MW LOF which prevent us to carry any traffic on this link and for the whole project we use XPIC links and Hybrid board like IFH2

Alarm Information
MW LOF :microwave loss of fram which mean that frame aligment A1 byte didnt achieved the frame

Handling Process
So after we got this trial we realize that the solution is be sure between the IF boards in both sites is the same
IFH2 at Site A=iFH2 at Site B  (√)
IFX2 at Site A=iFX at Site B  (√)
IFH2 at Site A=iFX at Site B  (*) WHICH IS WRONG coz both board is Inconsistent ,

Root Cause
After Change in planning and the design of the links due to customer requirement we found the alarm MW LOF,LOS, after changing some board to use it in another sites ,so we analysis a lot of trials :

1-reset the RTN
2-cold rest and pull off the IF board and return back
3- check the configuration is the same in both sites
4-ODU type in both Site

1 -check the confiduration and the ODU board type both is the Same
2 - check whether the IF board type is the same even if u got the RSL
3 3-make sure that the alarm MW LOF Disappear to be ready link for traffic