Then, the engineer has to double check the logical fiber connection and tried. However after a few attempts, the same problem and error message occur. Thinking that it might be FOADM side design problem, the engineer has to logically pass through the ITL at both directions. But, the same problem exists. And then, the engineer revises the solution by changing the MO to IN and OUT to MI of the MR8V. Unfortunately, the problem is still unsolved. Lastly, the engineer has to collect all of the script file (Network Wide Configuration) and U2000 log (nemgr_OTN_XXX & Nml_otn_XXX )
and escalate it to R & D for analysis. After checking, R & D claim that the FOADM local add/drop lambda at A7/D7 has conflict with the pass through lambda. R & D has suggested below solution:
To modify the MR8V add/drop lambda to other lambda that is not same with the pass through lambda.
To modify the pass through lambda.
Pass through the conflict port (in this case A7/D7) with physical fiber and create logically at U2000.