[TRNSPRTPCE-575] Improve OR to TAPI XPDR node mapping Created: 25/Nov/21  Updated: 20/Sep/23  Resolved: 10/Dec/21

Status: Verified
Project: transportpce
Component/s: None
Affects Version/s: None
Fix Version/s: Phosphorus

Type: Story Priority: Medium
Reporter: Javier Errea Assignee: Javier Errea
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 4 days
Original Estimate: Not Specified

Epic Link: T-API extended support

 Description   

The conversion of an XPDR device into TAPI node has a mistake. The eODU nep should be generated based on the CLIENT ports of the XPDR. At this moment it is based on the NETWORK port. This is wrong becase the eODU represents the LO_ODU and the iODU represents the HO_ODU, meaning that the iODU could aggregate the traffic from multiple LO_ODU.

To cope with the implementation of T0 Multilayer Topology, the SIP of the eODU is moved to the iODU.

The corresponding modifications in the Topology and Connectivity services are also adressed here


Generated at Wed Feb 07 20:43:27 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.