https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/TRNSPRTPCE-348 transportpce <p>We noticed that there are cases where, xponder subtree may not have all the connection map details. Below is an example:</p> <p> </p> <p> </p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>&lt;xponder&gt; &lt;xpdr-number&gt;2&lt;/xpdr-number&gt; &lt;xpdr-port&gt; &lt;index&gt;2&lt;/index&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;eqpt-srg-id&gt;1&lt;/eqpt-srg-id&gt; &lt;circuit-pack-name&gt;1-1-4&lt;/circuit-pack-name&gt; &lt;/xpdr-port&gt; &lt;xpdr-port&gt; &lt;index&gt;1&lt;/index&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;eqpt-srg-id&gt;1&lt;/eqpt-srg-id&gt; &lt;circuit-pack-name&gt;1-1-3&lt;/circuit-pack-name&gt; &lt;/xpdr-port&gt; &lt;xpdr-type&gt;tpdr&lt;/xpdr-type&gt; &lt;/xponder&gt; &lt;xponder&gt; &lt;xpdr-number&gt;1&lt;/xpdr-number&gt; &lt;xpdr-port&gt; &lt;index&gt;2&lt;/index&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;eqpt-srg-id&gt;1&lt;/eqpt-srg-id&gt; &lt;circuit-pack-name&gt;1-1-2&lt;/circuit-pack-name&gt; &lt;/xpdr-port&gt; &lt;xpdr-port&gt; &lt;index&gt;1&lt;/index&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;eqpt-srg-id&gt;1&lt;/eqpt-srg-id&gt; &lt;circuit-pack-name&gt;1-1-1&lt;/circuit-pack-name&gt; &lt;/xpdr-port&gt; &lt;recolor&gt;false&lt;/recolor&gt; &lt;xpdr-type&gt;tpdr&lt;/xpdr-type&gt; &lt;/xponder&gt; &lt;connection-map&gt; &lt;connection-map-number&gt;16843777&lt;/connection-map-number&gt; &lt;destination&gt; &lt;circuit-pack-name&gt;1-1-3&lt;/circuit-pack-name&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;/destination&gt; &lt;source&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;circuit-pack-name&gt;1-1-4&lt;/circuit-pack-name&gt; &lt;/source&gt; &lt;/connection-map&gt; &lt;connection-map&gt; &lt;connection-map-number&gt;16843521&lt;/connection-map-number&gt; &lt;destination&gt; &lt;circuit-pack-name&gt;1-1-4&lt;/circuit-pack-name&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;/destination&gt; &lt;source&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;circuit-pack-name&gt;1-1-3&lt;/circuit-pack-name&gt; &lt;/source&gt; &lt;/connection-map&gt; &lt;connection-map&gt; &lt;connection-map-number&gt;16843265&lt;/connection-map-number&gt; &lt;destination&gt; &lt;circuit-pack-name&gt;1-1-1&lt;/circuit-pack-name&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;/destination&gt; &lt;source&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;circuit-pack-name&gt;1-1-2&lt;/circuit-pack-name&gt; &lt;/source&gt; &lt;/connection-map&gt; &lt;connection-map&gt; &lt;connection-map-number&gt;16843009&lt;/connection-map-number&gt; &lt;destination&gt; &lt;circuit-pack-name&gt;1-1-2&lt;/circuit-pack-name&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;/destination&gt; &lt;source&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;circuit-pack-name&gt;1-1-1&lt;/circuit-pack-name&gt; &lt;/source&gt; &lt;/connection-map&gt; &lt;connection-map&gt; &lt;connection-map-number&gt;16909313&lt;/connection-map-number&gt; &lt;destination&gt; &lt;circuit-pack-name&gt;1-2-3&lt;/circuit-pack-name&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;/destination&gt; &lt;source&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;circuit-pack-name&gt;1-2-4&lt;/circuit-pack-name&gt; &lt;/source&gt; &lt;/connection-map&gt; &lt;connection-map&gt; &lt;connection-map-number&gt;16909057&lt;/connection-map-number&gt; &lt;destination&gt; &lt;circuit-pack-name&gt;1-2-4&lt;/circuit-pack-name&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;/destination&gt; &lt;source&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;circuit-pack-name&gt;1-2-3&lt;/circuit-pack-name&gt; &lt;/source&gt; &lt;/connection-map&gt; &lt;connection-map&gt; &lt;connection-map-number&gt;16908801&lt;/connection-map-number&gt; &lt;destination&gt; &lt;circuit-pack-name&gt;1-2-1&lt;/circuit-pack-name&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;/destination&gt; &lt;source&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;circuit-pack-name&gt;1-2-2&lt;/circuit-pack-name&gt; &lt;/source&gt; &lt;/connection-map&gt; &lt;connection-map&gt; &lt;connection-map-number&gt;16908545&lt;/connection-map-number&gt; &lt;destination&gt; &lt;circuit-pack-name&gt;1-2-2&lt;/circuit-pack-name&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;/destination&gt; &lt;source&gt; &lt;port-name&gt;1&lt;/port-name&gt; &lt;circuit-pack-name&gt;1-2-1&lt;/circuit-pack-name&gt; &lt;/source&gt; &lt;/connection-map&gt; </pre> </div></div> <p>In the this case the circuit-packs 1-2-1, 1-2-2, 1-2-3, 1-2-4 does not have xponder substree. While we can manually create xponder subtree in the device for these missing circuit-packs. It would be better if the code throws error for such scenarios, while continue to build the port-mapping.</p> TRNSPRTPCE-348

Portmapping fails when xponder subtree is not fully populated

Bug Medium Verified Done Balagangadhar Bathula Balagangadhar Bathula Wed, 11 Nov 2020 20:00:52 +0000 Fri, 18 Jun 2021 13:34:10 +0000 Wed, 28 Apr 2021 15:19:32 +0000 Aluminium Silicon 0 1 0 minutes 0 minutes 3 days Development Rank 0|i03v91:9zzzzzx Sprint Sprint 18 Sprint 19 Sprint 20 Sprint 21 Sprint 22