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-445 bgpcep <p>Attempted PCEP Update (with delegate flag=false and explicit inclusion of symbolic path name in the payload) for a non-delegated LSP sets delegation to true in the operational datastore.</p> <p>Symbolic Path name is read from the GET Operation and included as a part of LSP.</p> <p>Refer the snapshot of the payload sent.</p> <p>Operating System: All<br/> Platform: All</p> BGPCEP-445

Attempted PCEP Update for a non-delegated LSP sets delegation to true in operational datastore

Bug Resolved Duplicate Unassigned Ajay Chhabria Tue, 19 Apr 2016 19:53:38 +0000 Sun, 3 Mar 2019 11:49:44 +0000 Thu, 5 May 2016 13:52:14 +0000 Bugzilla Migration Bugzilla Migration PCEP 0 3 <p>Attachment Attempted_PCEP_Update_non_delegated_LSP.PNG has been added with description: Attempted PCEP Update for a non-delegated LSP</p> <p>The ODL PCE is reporting data from received PcRpt messages.<br/> Is the LSP PCC-initiated or PCE-initiated?</p> <p>The behavior was the same on both PCC and PCE initiated cases.</p> <p>If possible, could you please attach packet capture?</p> <p>Hi Milos,</p> <p>Please find the PCAP files both with PCC and PCE initiated tunnels. </p> <p>I would like to correct that with PCE initiated tunnels I saw something different:</p> <p>1. PCE initiated tunnel <br/> 2. send an update with delegate flag set to false.<br/> 3. Read the operational data the delegation flag was set to false.<br/> 4. Send another update with delegate flag set to false and included symbolic path name.<br/> 5. It threw error type 6 and value 13. The tunnel got DELETED.</p> <p>Was this behavior expected in the PCE initiated tunnels ? Comments? Thoughts ?</p> <p>Attachment type_bug_5765_PCC_initiated.pcap has been added with description: PCC initiated tunnels PCAP</p> <p>Attachment type_bug_5765_pce_initiated.pcap has been added with description: PCE initiated tunnels PCAP</p> <p>This bug has the same behavior, after PCE received the report with delegation flag set to false, the tunnel get deleted in PCE after a while. As the 2nd update doesn't have ENDPOINT object in the request, and PCE try to initialize a new tunnel instead of updating an existing tunnel, it throws the exception mandatory object is missing.</p> <p>(In reply to Ajay Chhabria from comment #4)<br/> &gt; Hi Milos,<br/> &gt; <br/> &gt; Please find the PCAP files both with PCC and PCE initiated tunnels. <br/> &gt; <br/> &gt; I would like to correct that with PCE initiated tunnels I saw something<br/> &gt; different:<br/> &gt; <br/> &gt; 1. PCE initiated tunnel <br/> &gt; 2. send an update with delegate flag set to false.<br/> &gt; 3. Read the operational data the delegation flag was set to false.<br/> &gt; 4. Send another update with delegate flag set to false and included symbolic<br/> &gt; path name.<br/> &gt; 5. It threw error type 6 and value 13. The tunnel got DELETED.<br/> &gt; <br/> &gt; Was this behavior expected in the PCE initiated tunnels ? Comments? Thoughts<br/> &gt; ?</p> <p>The "END-POINT Object missing" error is really strange. The second updateLsp (PCInitiate message is send) request should have meaning of "retake delegation" request as described in <a href="https://tools.ietf.org/html/draft-ietf-pce-pce-initiated-lsp-00#section-6" class="external-link" target="_blank" rel="nofollow noopener">https://tools.ietf.org/html/draft-ietf-pce-pce-initiated-lsp-00#section-6</a></p> <p>I believe this has the same root cause as <a href="https://bugs.opendaylight.org/show_bug.cgi?id=5763" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=5763</a> ?</p> <p>(In reply to Kevin Wang from comment #9)<br/> &gt; I believe this has the same root cause as<br/> &gt; <a href="https://bugs.opendaylight.org/show_bug.cgi?id=5763" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=5763</a> ?</p> <p>Yes, this one can be closed as a duplicate of 5763.</p> <p>The root cause of this one and bug-5763 are the same, that the retake of delegation is not successfully processed by PCC.</p> Duplicate BGPCEP-444 Development External issue ID 5765 External issue URL Rank 0|i02cbz: