OpenDaylight JIRA

OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us

8.20.10

820010

22-06-2022

[BGPCEP-690] BGP session does not get established when send-max flag is not included in configuration https://jira.opendaylight.org/browse/BGPCEP-690 bgpcep <p>From the protocols-config.xml file, remove the line send-max and try to peer with other BGP speaker.</p> <p>Operating System: All<br/> Platform: All</p> BGPCEP-690

BGP session does not get established when send-max flag is not included in configuration

Bug Verified Won't Do Ajay Lele Ajay Chhabria Tue, 19 Sep 2017 18:03:02 +0000 Wed, 18 Apr 2018 07:59:16 +0000 Tue, 16 Jan 2018 19:16:56 +0000 Oxygen Bugzilla Migration BGP 0 5 <p>Attachment karaf.log has been added with description: Karaf Log</p> <p>Master: <a href="https://git.opendaylight.org/gerrit/#/c/63464/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/63464/</a></p> <p><a href="https://git.opendaylight.org/gerrit/#/q/topic:Bug-9186" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/q/topic:Bug-9186</a></p> <p>Hi Ajay, please extend the issue, scenario and what you are trying to achieve and its failing.</p> <p>After check the patch, from my point of view what you are doing is a missconfiguration and therefore you are hitting the NPE.</p> <p>Regards,</p> <p>Claudio</p> <p>When Configuring ADD PATH capabilty. </p> <ul class="alternate" type="square"> <li>global/rib it should be configured per AFI/SAFI if its supported and what strategy will be used. send-max field is mandatory</li> <li>peer here send-max is not mandatory, from doc:</li> </ul> <p>Note<br/> The path selection strategy is not configurable on per peer basis. The send-max presence indicates a willingness to send ADD-PATH NLRIs to the neighbor. </p> <p>Regards, </p> <p>Claudio</p> <p>(In reply to Claudio D. Gasparini from comment #3)<br/> > Hi Ajay, please extend the issue, scenario and what you are trying to<br/> > achieve and its failing.<br/> > <br/> > After check the patch, from my point of view what you are doing is a<br/> > missconfiguration and therefore you are hitting the NPE.<br/> > <br/> > Regards,<br/> > <br/> > Claudio</p> <p>The issue was found while testing add-path capability modes (ref. <a href="https://tools.ietf.org/html/rfc7911#page-4" class="external-link" target="_blank" rel="nofollow noopener">https://tools.ietf.org/html/rfc7911#page-4</a>). In version of OpenConfig model currently used by ODL BGP code, there is no separate provision to specify that send capability should not be advertised. Only value associated with send is send-max. If it is not specified, it was causing NPE. This patch adds check to prevent NPE. So now for send capability not to be advertised, send-max can be skipped</p> <p>BGP OpenConfig model has been updated recently to add a boolean flag for specifying if send capability should be advertised (ref. <a href="https://github.com/openconfig/public/commit/e020ce4b7e94482a9bbcf8dfb73f3d01dbdda5e6#diff-0d759af0e8ee335a03ba94fd5055d69cL312" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/openconfig/public/commit/e020ce4b7e94482a9bbcf8dfb73f3d01dbdda5e6#diff-0d759af0e8ee335a03ba94fd5055d69cL312</a>) which is the correct way of doing this and once we update to this version above will not be required</p> <p>(In reply to Claudio D. Gasparini from comment #4)<br/> > When Configuring ADD PATH capabilty. <br/> > - global/rib it should be configured per AFI/SAFI if its supported and what<br/> > strategy will be used. send-max field is mandatory</p> <p>where is send-max mentioned as mandatory and how do we enforce it? I don't see it as mandatory in the yang</p> <p>> - peer here send-max is not mandatory, from doc:<br/> > <br/> > Note<br/> > The path selection strategy is not configurable on per peer basis. The<br/> > send-max presence indicates a willingness to send ADD-PATH NLRIs to the<br/> > neighbor. <br/> > </p> <p>I don't understand this doc note. Generally per neighbor config should override the global config</p> <p>> <br/> > <br/> > Regards, <br/> > <br/> > <br/> > Claudio</p> <p>(In reply to Ajay Lele from comment #6)<br/> > (In reply to Claudio D. Gasparini from comment #4)<br/> > > When Configuring ADD PATH capabilty. <br/> > > - global/rib it should be configured per AFI/SAFI if its supported and what<br/> > > strategy will be used. send-max field is mandatory<br/> > <br/> > where is send-max mentioned as mandatory and how do we enforce it? I don't<br/> > see it as mandatory in the yang<br/> > <br/> > > - peer here send-max is not mandatory, from doc:<br/> > > <br/> > > Note<br/> > > The path selection strategy is not configurable on per peer basis. The<br/> > > send-max presence indicates a willingness to send ADD-PATH NLRIs to the<br/> > > neighbor. <br/> > > <br/> > <br/> > I don't understand this doc note. Generally per neighbor config should<br/> > override the global config<br/> > <br/> > > <br/> > > <br/> > > Regards, <br/> > > <br/> > > <br/> > > Claudio</p> <p>Hi Ajay, global configuration is used to defined the path selection strategy to be used when supporting add-path(only configurable per RIB).<br/> Then neighbor config is used to define the additional capability per neighbor(receive flag and send flag). As you mentioned send flag is not present therefore send-max presence is used as flag.</p> <p>All this is mentioned in documentation, if you thing that it can be improved, feel free to provide some improvement and we can go through it.</p> <p><span class="error">[0]</span> <a href="http://docs.opendaylight.org/en/stable-nitrogen/user-guide/bgp-user-guide.html#additional-path" class="external-link" target="_blank" rel="nofollow noopener">http://docs.opendaylight.org/en/stable-nitrogen/user-guide/bgp-user-guide.html#additional-path</a></p> <p>Could you close the bug as wont be fixed.</p> <p>Thanks</p> <p>Hi Claudio</p> <p>Ok I see what you are saying. So to achieve what is intended, config required is:<br/> 1. config add-path (both receive and send-max params) at global level<br/> 2. exclude send-max param under neighbor config</p> <p>I tried it out and confirm that it works. Fine to close this issue</p> <p>Regards<br/> Ajay</p> Development External issue ID 9186 External issue URL Rank 0|i02duf: