svachhani isn't it already fixed ? 

Yes it is already fixed. 

thanks , we can close it then, orenais can you update it and excel sheet after review.

Sorry missed it. Could you point to the gerrit changes associated to that. We had several discussions about this, and my feeling was that we had a workaround , but that at the end the status was not modified. Expected behavior is the following. 1) we create a link with in the OMS attributes a clfi and spanloss-base according to the info we have in an external database that gives the inventory of links. 2) The Controller finds the source and LLDP info on neighbors during topology building. It shall then check consistency between measured span loss and spanloss-base and fills what misses (spanloss-current) if consistent. 3) if a link is broken, from a notification on LLDP status change, it shall only change the admin or operationnal-state of the link, but not delete it, so that we don't need to repopulate the spanloss-base (used for the link engineering) as in first step.

The opened issue was addressed by the merge request. Current version of code is adding a new link into network model based on LLDP notification and deleting it from network model based on LLDP notification which was agreed  at that tine. Code is already merged into Master. I think we can close this issue and open another one if you think it needs more features. 

This bug highlighted prior to integration in Fluorine has been resolved. However proposed solution leads to other issues. Created TRNSPRTPCE-46 to address the corresponding issue