[BGPCEP-445] Attempted PCEP Update for a non-delegated LSP sets delegation to true in operational datastore Created: 19/Apr/16  Updated: 03/Mar/19  Resolved: 05/May/16

Status: Resolved
Project: bgpcep
Component/s: PCEP
Affects Version/s: Bugzilla Migration
Fix Version/s: Bugzilla Migration

Type: Bug
Reporter: Ajay Chhabria Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: PNG File Attempted_PCEP_Update_non_delegated_LSP.PNG     File type_bug_5765_PCC_initiated.pcap     File type_bug_5765_pce_initiated.pcap    
Issue Links:
Duplicate
duplicates BGPCEP-444 Attempted PCEP Update for a non-deleg... Resolved
External issue ID: 5765

 Description   

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.

Symbolic Path name is read from the GET Operation and included as a part of LSP.

Refer the snapshot of the payload sent.



 Comments   
Comment by Ajay Chhabria [ 19/Apr/16 ]

Attachment Attempted_PCEP_Update_non_delegated_LSP.PNG has been added with description: Attempted PCEP Update for a non-delegated LSP

Comment by Milos Fabian [ 20/Apr/16 ]

The ODL PCE is reporting data from received PcRpt messages.
Is the LSP PCC-initiated or PCE-initiated?

Comment by Ajay Chhabria [ 20/Apr/16 ]

The behavior was the same on both PCC and PCE initiated cases.

Comment by Milos Fabian [ 20/Apr/16 ]

If possible, could you please attach packet capture?

Comment by Ajay Chhabria [ 20/Apr/16 ]

Hi Milos,

Please find the PCAP files both with PCC and PCE initiated tunnels.

I would like to correct that with PCE initiated tunnels I saw something different:

1. PCE initiated tunnel
2. send an update with delegate flag set to false.
3. Read the operational data the delegation flag was set to false.
4. Send another update with delegate flag set to false and included symbolic path name.
5. It threw error type 6 and value 13. The tunnel got DELETED.

Was this behavior expected in the PCE initiated tunnels ? Comments? Thoughts ?

Comment by Ajay Chhabria [ 20/Apr/16 ]

Attachment type_bug_5765_PCC_initiated.pcap has been added with description: PCC initiated tunnels PCAP

Comment by Ajay Chhabria [ 20/Apr/16 ]

Attachment type_bug_5765_pce_initiated.pcap has been added with description: PCE initiated tunnels PCAP

Comment by Kevin Wang [ 21/Apr/16 ]

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.

Comment by Milos Fabian [ 22/Apr/16 ]

(In reply to Ajay Chhabria from comment #4)
> Hi Milos,
>
> Please find the PCAP files both with PCC and PCE initiated tunnels.
>
> I would like to correct that with PCE initiated tunnels I saw something
> different:
>
> 1. PCE initiated tunnel
> 2. send an update with delegate flag set to false.
> 3. Read the operational data the delegation flag was set to false.
> 4. Send another update with delegate flag set to false and included symbolic
> path name.
> 5. It threw error type 6 and value 13. The tunnel got DELETED.
>
> Was this behavior expected in the PCE initiated tunnels ? Comments? Thoughts
> ?

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 https://tools.ietf.org/html/draft-ietf-pce-pce-initiated-lsp-00#section-6

Comment by Kevin Wang [ 04/May/16 ]

I believe this has the same root cause as https://bugs.opendaylight.org/show_bug.cgi?id=5763 ?

Comment by Milos Fabian [ 05/May/16 ]

(In reply to Kevin Wang from comment #9)
> I believe this has the same root cause as
> https://bugs.opendaylight.org/show_bug.cgi?id=5763 ?

Yes, this one can be closed as a duplicate of 5763.

Comment by Kevin Wang [ 05/May/16 ]

The root cause of this one and bug-5763 are the same, that the retake of delegation is not successfully processed by PCC.

Generated at Wed Feb 07 19:13:05 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.