https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/LACP-10 lacp <p>Mininet Topology: 32 Host &amp; Switches and 2 links connecting each host and switch. Configure the Hosts on LACP mode and check if the LAG groups are formed on the switch side. <br/> Openvswitch version: 2.3.1<br/> Build no: Integration build 2133</p> <p>Steps to recreate:<br/> 1. Bring up the controller and feature install the LACP module.<br/> 2. Once the controller is setup, create a mininet topology script as specified above and check if the group entries are formed on all the switches. &lt;&lt;&lt;Entries are formed as expected<br/> 3. Also, check the Karaf logs to see if there are any LACP specific errors being generated while scaling up to this number. &lt;&lt;&lt;&lt;RPC Exception issue seen now.</p> <p>Error message generated on Karaf log:</p> <p>2015-06-02 11:24:24,838 | ERROR | Thread-80 | LacpGroupTbl | 203 - org.opendaylight.lacp.main.lacp.main.impl - 1.0.0.SNAPSHOT | received interrupt {}java.util.concurrent.ExecutionException: org.opendaylight.controller.md.sal.dom.api.DOMRpcImplementationNotAvailableException: No implementation of RPC AbsoluteSchemaPath</p> {path=[(urn:opendaylight:group:service?revision=2013-09-18)update-group]} <p> available &lt;&lt;&lt;&lt;&lt;&lt;On looking at the message, the exception problem looks to be because of some issue with the LcpGroupTbl impl.</p> <p>Sometimes, the same message is slightly modified and displayed as below when you scale up the LAG numbers first and create the topology, then follow it up by starting the controller. <br/> 64 LAG's in the below case<br/> 2015-06-01 14:44:15,591 | ERROR | Thread-1073 | LacpFlow | 203 - org.opendaylight.lacp.main.lacp.main.impl - 1.0.0.SNAPSHOT | received </p> <p>interrupt in lacp flow removal java.util.concurrent.ExecutionException: org.opendaylight.controller.md.sal.dom.api.DOMRpcImplementationNotAvailableException: </p> <p>SchemaPath AbsoluteSchemaPath</p> {path=[(urn:opendaylight:flow:service?revision=2013-08-19)remove-flow]} <p> is not resolved to an RPC &lt;&lt;&lt;&lt;On looking at the message, the exception problem looks to be because of some issue with the LacpFlow impl.</p> <p>Please find the Karaf.log files attached along with this bug.</p> <p>Operating System: All<br/> Platform: All</p> LACP-10

RPC Exception messages are thrown while trying to scale the number of LAG's to 32 entries.

Bug Resolved Done Kalaiselvi Mahesh Manivasagam Tue, 2 Jun 2015 07:30:18 +0000 Tue, 9 Jun 2015 09:32:32 +0000 Tue, 9 Jun 2015 09:32:32 +0000 unspecified General 0 1 <p>Attachment karaf_logs.zip has been added with description: Karaf_logs</p> <p>The reported RPC exceptions are thrown because in the script, the set bridge command is used to specify the openflow version. This command causes the openflow connection to be reset and open a new connection.<br/> The flow programming or the group programming done at the moment the switch closes its connections to the controller the concurrent ExecutionException is thrown.<br/> As the switches are already started with the version openflow13, the set bridge command is not required to be configured.</p> <p>When the switches are teared down and then restarted, some additional node update notifications are received because LACP aggregator information is re-written for removed ports. This causes the switch to be available in memory and when the switches re-brought up again, the flow programming is skipped as the node is already available in the in-memory db.</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/22054/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/22054/</a><br/> On removal of ports from lag, md-sal data store write is avoided.<br/> Instead on the information deletion is done in the data-store.<br/> So this does not trigger node-update messages.</p> Development External issue ID 3539 External issue URL Rank 0|i034dz: