[BGPCEP-753] bgp session should negotiate supported address-family capabiltiy Created: 31/Jan/18 Updated: 16/Nov/21 Resolved: 16/Nov/21 |
|
| Status: | Resolved |
| Project: | bgpcep |
| Component/s: | BGP |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | chen dongfang | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
in RFC4760 page 9 To have a bi-directional exchange of routing information for a particular <AFI, SAFI> between a pair of BGP speakers, each such speaker MUST advertise to the other (via the Capability Advertisement mechanism) the capability to support that particular <AFI, SAFI> route.
when session up，create database listener should used negotiated adress-family。
otherwise，if peer advertised address-family which ODL bgp not support，ex：afi--BGP-LS(16388)/safi–UNICAST(1)，ODL BGP will occur nullpointerException |
| Comments |
| Comment by Robert Varga [ 15/Mar/19 ] |
|
Do you have the NPE stack trace, please? |
| Comment by Robert Varga [ 16/Nov/21 ] |
|
No feedback from reporter, closing as cannot reproduce. |