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/BGPCEP-490 bgpcep <p>Bug exists since Beryllium at least.</p> <p>Reproduce:</p> <p>1. Create a PCC-inited LSP<br/> 2. Observe the network topology, ipv4 under reported-lsp/path/lsp/tlvs/lsp-identifiers is displayed like this:</p> <p> &lt;ipv4&gt;<br/> &lt;ipv4-tunnel-endpoint-address&gt;192.168.254.3&lt;/ipv4-tunnel-endpoint-address&gt;<br/> &lt;ipv4-tunnel-sender-address&gt;192.168.254.1&lt;/ipv4-tunnel-sender-address&gt;<br/> &lt;ipv4-extended-tunnel-id&gt;192.168.254.3&lt;/ipv4-extended-tunnel-id&gt;<br/> &lt;/ipv4&gt;</p> <p>3. Make the LSP operational down<br/> 4. Check the network topology again, now the ipv4 is showing like this</p> <p> &lt;ipv4&gt;<br/> &lt;ipv4-tunnel-endpoint-address&gt;192.168.254.6&lt;/ipv4-tunnel-endpoint-address&gt;<br/> &lt;ipv4-tunnel-sender-address&gt;192.168.254.1&lt;/ipv4-tunnel-sender-address&gt;<br/> &lt;ipv4-extended-tunnel-id&gt;6.254.168.192&lt;/ipv4-extended-tunnel-id&gt;<br/> &lt;/ipv4&gt;</p> <p>5. The ipv4-extended-tunnel-id is recovered to correct value when operational is back to UP.</p> <ul> <li>Tested with Cisco XRV 5.3 as router</li> </ul> <p>Is this behavior expected?</p> <p>Operating System: All<br/> Platform: All</p> BGPCEP-490

ipv4-extended-tunnel-id showing backwards when LSP is operational down

Bug Resolved Cannot Reproduce Claudio David Gasparini Kevin Wang Fri, 1 Jul 2016 00:49:56 +0000 Sun, 3 Mar 2019 11:49:48 +0000 Sat, 2 Jul 2016 00:03:58 +0000 Bugzilla Migration Bugzilla Migration PCEP 0 2 <p>Hi Kevin, could you please attach logs, and package captures?<br/> Thanks</p> <p>Attachment ip-extended.up.pcap has been added with description: pcap when lsp is up</p> <p>Attachment ip-extended.down.pcap has been added with description: pcap when the lsp is going down</p> <p>Hi Claudio,</p> <p>I double checked the pcap (uploaded). the extended tunnel id is showing backwards in the PCRpt. I think it is a Cisco XRV bug.</p> Development External issue ID 6138 External issue URL Rank 0|i02clz: