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-671] BGP RIB's not responding well when configured more than one using Open Config https://jira.opendaylight.org/browse/BGPCEP-671 bgpcep <p>Unable to get all active BGP sessions up in 3-node clustering using Open Config.</p> <p>Operating System: All<br/> Platform: All</p> BGPCEP-671

BGP RIB's not responding well when configured more than one using Open Config

Bug Resolved Cannot Reproduce Unassigned Ajay Chhabria Fri, 12 May 2017 07:13:24 +0000 Sun, 3 Mar 2019 11:50:03 +0000 Wed, 4 Oct 2017 18:10:37 +0000 Bugzilla Migration Bugzilla Migration BGP 0 5 <p>Attachment multiple_ribs.txt has been added with description: Karaf Snapshot showing peer not configured</p> <p>Attachment Config_datastore.txt has been added with description: Config Datastore showing peer is configured</p> <p>Steps To Reproduce:</p> <p>1. Configure 3-Node clustering and install BGP extension.</p> <p>2. Configure protocol defining BGP RIB ID. Make sure the RIB-ID's are different for all 3 nodes using Open Config.</p> <p><a href="http://CONTROLLER:PORT/restconf/config/openconfig-network-instance:network-instances/network-instance/global-bgp/openconfig-network-instance:protocols" class="external-link" target="_blank" rel="nofollow noopener">http://CONTROLLER:PORT/restconf/config/openconfig-network-instance:network-instances/network-instance/global-bgp/openconfig-network-instance:protocols</a></p> <p>3. Configure Neighbor using the same RIB-ID as configured above for all the 3-node controllers.</p> <p><a href="http://CONTROLLER:PORT/restconf/config/openconfig-network-instance:network-instances/network-instance/global-bgp/openconfig-network-instance:protocols/protocol/openconfig-policy-types:BGP/bgp-example/bgp/neighbors" class="external-link" target="_blank" rel="nofollow noopener">http://CONTROLLER:PORT/restconf/config/openconfig-network-instance:network-instances/network-instance/global-bgp/openconfig-network-instance:protocols/protocol/openconfig-policy-types:BGP/bgp-example/bgp/neighbors</a></p> <p>Note: There is a chance this problem get triggered. But not always.</p> <p>Hi guys, please add ODL version and some logs. So we can clarify where might be the issue coming from, if its duplicated but, etc..</p> <p>Regards,</p> <p>Attachment karaf.zip has been added with description: Karaf Logs</p> <p>(In reply to Claudio D. Gasparini from comment #4)<br/> > Hi guys, please add ODL version and some logs. So we can clarify where might<br/> > be the issue coming from, if its duplicated but, etc..<br/> > <br/> > <br/> > Regards,</p> <p>Hi Claudio,</p> <p>I have attached the karaf logs. The ODL version that we found this issue is 0.6.3-Boron-SR3. Please let me know if you need any further information.</p> <p>Hi Ajay, would be better to have some logs with trace. <br/> Since I don't see any Exception or Error on logs.</p> <p>Regards,</p> <p>(In reply to Claudio D. Gasparini from comment #7)<br/> > Hi Ajay, would be better to have some logs with trace. <br/> > Since I don't see any Exception or Error on logs.<br/> > <br/> > Regards,</p> <p>Hi Claudio,</p> <p>If you see the config data store shows the rib configuration making 10.18.132.202 as the peer but the karaf logs was continuously saying that 10.18.132.202 has not been configured. Check the following snapshot:</p> <p>##############################################################################<br/> 2017-05-12 08:39:15,267 | ERROR | tLoopGroup-10-14 | BGPDocumentedException | 89 - org.opendaylight.bgpcep.bgp-parser-api - 0.6.3.Boron-SR3 | Error = CONNECTION_REJECTED<br/> org.opendaylight.protocol.bgp.parser.BGPDocumentedException: BGP peer with ip: IpAddress [_ipv4Address=Ipv4Address <span class="error">[_value=10.18.132.202]</span>] not configured. <br/> ##############################################################################</p> <p>Shouldn't the BGP RIB respond correctly and establish second session when in reality it has been configured and showing up in the config data store ?</p> <p>Let me know if you need to know anything else.</p> <p>Thanks,<br/> Ajay Chhabria</p> <p>In this use-case the intention was to use 3 nodes in the cluster as 3 separate BGP speakers with their own RIB. For this to work, OpenConfig model which carries the BGP RIB and peer information needs to be configured on a separate shard and replication disabled for the same</p> <p>Sample config in configuration/initial/modules.conf file:</p> { name = "openconfig_network_instance" namespace = "http://openconfig.net/yang/network-instance" shard-strategy = "module" } <p>Sample config in configuration/initial/module-shards.conf file:</p> <p> {<br/> name = "openconfig_network_instance"<br/> shards = [</p> { name="openconfig_network_instance" replicas = [ "member-1" ] } <p> ]<br/> }</p> Development External issue ID 8426 External issue URL Rank 0|i02dq7: