[BGPCEP-675] PCEP session remain registered when a PCEP CLOSE message is received Created: 01/Jun/17  Updated: 03/Mar/19  Resolved: 26/Jun/17

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

Type: Bug
Reporter: Kevin Wang Assignee: Kevin Wang
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 8577

 Description   

The PCEP CLOSE message was not handled correctly by ODL. Right now when a PCEP CLOSE message was received by the controller, it simply disconnect the PCEP peer without unregistering it from PCEP topology. Thus the closed PCEP session will stay in the topology and user can still see it in jolokia after the session is gone. As follow-up problem, when the PCEP session comes back again, it fails to register on PCEP topology again as previous registration was not removed, so ODL will not actively sends out keep-alive messages to remote peer, then the DEAD_TIMER problem was triggered.

This bug can only be triggered when the router sends out PCEP CLOSE message before it drops the PCEP session. However, route doesn't always do it, most of the time it just drop the TCP connection, and in this case the bug will not be triggered.



 Comments   
Comment by Kevin Wang [ 26/Jun/17 ]

https://git.opendaylight.org/gerrit/#/c/54331/

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