[BGPCEP-346] Routes not withdrawn when eBGP peers are disconnected (the same prefixes annonced) Created: 23/Dec/15 Updated: 03/Mar/19 Resolved: 09/Feb/16 |
|
| Status: | Resolved |
| Project: | bgpcep |
| Component/s: | BGP |
| Affects Version/s: | Bugzilla Migration |
| Fix Version/s: | Bugzilla Migration |
| Type: | Bug | ||
| Reporter: | Radovan Sajben | Assignee: | Claudio David Gasparini |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
| External issue ID: | 4835 |
| Description |
|
Routes not withdrawn when both eBGP peers (they previously announced these routes) are disconnected https://tools.ietf.org/html/rfc4271#section-3.1 3.1. Routes: Advertisement and Storage ... BGP provides mechanisms by which a BGP speaker can inform its peers ... c) the BGP speaker connection can be closed, which implicitly example-ipv4-topology eBGP-1 connected {"topology":[{"topology-id":"example-ipv4-topology","topology-types":{},"node":[{"node-id":"1.1.1.1","l3-unicast-igp-topology:igp-node-attributes":{"prefix":[ {"prefix":"8.0.0.0/28"}, {"prefix":"8.0.0.16/28"}]}}],"server-provided":true}]} both eBGPs connected {"topology":[{"topology-id":"example-ipv4-topology","topology-types":{},"node":[{"node-id":"1.1.1.1","l3-unicast-igp-topology:igp-node-attributes":{"prefix":[ {"prefix":"8.0.0.0/28"}, {"prefix":"8.0.0.16/28"}]}}],"server-provided":true}]} eBGP-1 disconnected {"topology":[{"topology-id":"example-ipv4-topology","topology-types":{},"node":[{"node-id":"2.2.2.2","l3-unicast-igp-topology:igp-node-attributes":{"prefix":[ {"prefix":"8.0.0.0/28"}, {"prefix":"8.0.0.16/28"}]}}],"server-provided":true}]} example-ipv4-topology stil contains routes after both eBGP peers disconnection ... 20151223 11:06:42.317 / 20151223 11:06:42.318 / 00:00:00.001 [ {"prefix":"8.0.0.0/28"}, {"prefix":"8.0.0.16/28"}]}}],"server-provided":true}]}' does not contain '{"topology":[{"topology-id":"example-ipv4-topology","server-provided":true,"topology-types":{}}]}' ========================================================== the BGP peer log does not contain any prefix withdrawals: ... 2015-12-23 12:20:38,223 DEBUG: UPDATE message received: 0xffffffffffffffffffffffffffffffff0035020000001e40010100400206020100008000800e0e0001010402020202001c08000000 ========================================================== see the attached karaf.log as well - from the ROBOT MESSAGE: Starting test Disconnect_eBGP_Peer2 |
| Comments |
| Comment by Radovan Sajben [ 23/Dec/15 ] |
|
Attachment karaf.log.txt has been added with description: see the scenario from the ROBOT MESSAGE: Starting test Disconnect_eBGP_Peer2 |
| Comment by Claudio David Gasparini [ 12/Jan/16 ] |
| Comment by Iveta Halanova [ 13/Jan/16 ] |
| Comment by Iveta Halanova [ 14/Jan/16 ] |
|
connected 2 eBGP peers with same route with diff. next hop. |
| Comment by Iveta Halanova [ 14/Jan/16 ] |
|
Attachment 08.2.1_karaf.log has been added with description: new logs |
| Comment by Claudio David Gasparini [ 21/Jan/16 ] |
| Comment by Claudio David Gasparini [ 25/Jan/16 ] |
| Comment by Claudio David Gasparini [ 09/Feb/16 ] |