Uploaded image for project: 'transportpce'
  1. transportpce
  2. TRNSPRTPCE-575

Improve OR to TAPI XPDR node mapping

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • Phosphorus
    • None
    • None
    • None

      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

            errea Javier Errea
            errea Javier Errea
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 4 days
                4d