Signal failure because of LSX substitution limitation
Hi ,
Dear Community , today I have a case related of LSX version substitution limitation problem .
- Description
-As we were doing expansion for 10G-LAN signal in OSN6800 link consist of 2 OTM NEs and 3 OLA NEs in the middle , through a distance over 250km , we started with adding new LSX boards in OSN 6800 terminal NEs then commissioning the power of added channels , But we found out that U2000 rises an alarm (ODU2_DEG & ODU_PM_DEG) in one side of the terminal NEs .
- The problem cause
- We checked the signal path using OSA spectrum analyzer in both Source and Destination NEs and found that the signal goes normally .
- Then after checking Version of boards we found that one site has 12LSX while the other has 13LSX both boards support AFEC and FEC forward error correction , when setting FEC Mode the alarm get cleared and the service goes normally but when setting AFEC in both sides the service got cut and the alarm raised again in the NE which has the 12LSX Board .
- When checking Hedex we got this substitution limitation , we got this knowledge
- The 12LSX uses different AFEC type than 13LSX , and so 12LSX doesn’t work with 13LSX when using AFEC .
- The solution
-The solution was using FEC in both boards , and according to this new knowledge we planned the distribution of the boards , so we will use links with mixed LSX boards in short distance to use FEC .
I hope to be useful experience .
Regards
