[BGPCEP-457] Transitive Unrecognized Attribute not transiting Created: 06/May/16  Updated: 03/Mar/19  Resolved: 25/Jul/16

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

Type: Bug
Reporter: Sidhant Hasija Assignee: Ajay L
Resolution: Done 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 Processed-pcrpt-objects.png     File ipv4-bgproute.json    
External issue ID: 5855

 Description   

Hello ODL-BGPCEP

I inserted the following route with unrecognized attributes into the app-rib using RESTCONF :

"ipv4-route": [
{
"prefix": "9.9.9.9/32",
"attributes": {
"ipv4-next-hop":

{ "global": "11.11.11.11" }

,
"unrecognized-attributes": [

{ "partial": "true", "transitive": "true", "type": "101", "value": "0101010101010101" }

,

{ "partial": "true", "transitive": "true", "type": "102", "value": "0101010111111111" }

]
}
}]

While these unrecognized attributes are visible in loc-rib of the same bgp router, they are not appearing in the adj-rib-out of the neighboring bgp peer,
or in other words they are not being transmitted with the bgp update message of the bgp route.

I believe it is not the normal behavior and should be transmitted in the BGP update message for the prefix as transitive flag is set to true. (ipv4-route json object is also attached with the mail).

I am using bgp project version 0.5.2-SNAPSHOT and the peering is between two SDN controllers. I will be glad to provide more information, and sorry if I have missed out on some.

Regards
Sidhant

 Comments   
Comment by Sidhant Hasija [ 06/May/16 ]

Attachment ipv4-bgproute.json has been added with description: json object to insert bgp route with unrecognized attribute

Comment by Ajay L [ 17/May/16 ]

Hi Sidhant

I am looking into this issue. When I tried this on my setup, noticed that the unrecognized attribute is set in the adj-rib-out of the BGP peer, but it is not included in the Update message which is sent to the peer. This is happening due to a missing serializer and I am fixing that. Can you please check again in your setup about the attributes showing in the peer's adj-rib-out?

Regards
Ajay

Comment by Ajay L [ 17/May/16 ]

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

Comment by Sidhant Hasija [ 18/May/16 ]

Hello Ajay

Yes,I can confirm that unrecognized attributes show up in adj-rib-out of the peers in odl speaker.

Thanks and Regards
Sidhant

Comment by Milos Fabian [ 19/May/16 ]

stable/beryllium: https://git.opendaylight.org/gerrit/#/c/39086/

Comment by Ajay L [ 25/Jul/16 ]

Attachment Processed-pcrpt-objects.png has been added with description: Processed PCRpt objects

Comment by Ajay L [ 25/Jul/16 ]

(In reply to Ajay L from comment #5)
> Created attachment 1107 [details]
> Processed PCRpt objects

Attachment created erroneously. Please ignore

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