[#BGPCEP-318] Withdrawn routes missing in UPDATE message from controller to BGP peer

[BGPCEP-318] Withdrawn routes missing in UPDATE message from controller to BGP peer Created: 26/Nov/15 Updated: 03/Mar/19 Resolved: 01/Dec/15
Status:	Resolved
Project:	bgpcep
Component/s:	BGP
Affects Version/s:	Bugzilla Migration
Fix Version/s:	Bugzilla Migration

Type:

Bug

Reporter:

Radovan Sajben

Assignee:

Unassigned

Resolution:

Cannot Reproduce

Votes:

Labels:

None

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified

Environment:

Operating System: All
Platform: All

External issue ID:

4682

Description

UPDATE message sent by controller to BGP peer intended for the 8.0.1.0/28 prefix withdrawal does not contain Withdrawn Routes at all

bgp peer log (play.py)

2015-11-26 11:27:49,433 DEBUG: UPDATE message received: 0xffffffffffffffffffffffffffffffff0045020000002e40010100400200800404000000004005040000006480090429292929800a0428282828800f080001011c08000100
2015-11-26 11:27:49,433 DEBUG: Decoding update message:
2015-11-26 11:27:49,433 DEBUG: Message header marker: 0xffffffffffffffffffffffffffffffff
2015-11-26 11:27:49,433 DEBUG: Message lenght: 0x0045 (69)
2015-11-26 11:27:49,433 DEBUG: Message type: 0x02 (update)
2015-11-26 11:27:49,433 DEBUG: Withdrawn routes lenght: 0x0000 (0)
2015-11-26 11:27:49,433 DEBUG: Withdrawn routes: 0x
2015-11-26 11:27:49,433 DEBUG: Withdrawn routes prefix list: []
2015-11-26 11:27:49,434 DEBUG: Total path attribute lenght: 0x002e (46)
2015-11-26 11:27:49,434 DEBUG: Path attributes: 0x40010100400200800404000000004005040000006480090429292929800a0428282828800f080001011c08000100
2015-11-26 11:27:49,434 DEBUG: Calculated NLRI length: 0
2015-11-26 11:27:49,434 DEBUG: NLRI: 0x
2015-11-26 11:27:49,434 DEBUG: NLRI prefix list: []

karaf log for distribution-karaf-0.3.2-Lithium-SR2 temporary at https://jenkins.opendaylight.org/sandbox/job/bgpcep-csit-1node-userfeatures-only-stable-lithium/19/artifact/karaf.log

Comments

Comment by Milos Fabian [ 01/Dec/15 ]

Since the peering supports BGP Multi-Protocol for IPv4 Unicast, routing information, in this case withdrawing, is kept in Path Attribute "MP_UNREACH_NLRI" and "Withdrawn routes" field is left empty.
Ref.: https://tools.ietf.org/html/rfc4760#section-4

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

[BGPCEP-318] Withdrawn routes missing in UPDATE message from controller to BGP peer Created: 26/Nov/15 Updated: 03/Mar/19 Resolved: 01/Dec/15