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/OPNFLWPLUG-118 OpenFlowPlugin <p>Hello,</p> <p>When I connect mininet(of10 &amp; of13) with the controller (using of13 option), I get the following error at the OSGi command line. Attached the links for the detailed error.</p> <p>Link 1 to mininet(of10) : <a href="http://pastebin.com/46hrz3yM" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/46hrz3yM</a></p> <p>Link 2 to mininet(of13) : <a href="http://pastebin.com/aczRP2M8" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/aczRP2M8</a></p> <p>Please let me know if you need any additional information.</p> <p>BR/Madhusudhan</p> <p>Operating System: Windows<br/> Platform: PC</p> OPNFLWPLUG-118

Error at OSGi log after starting mininet (of13 & of10)

Bug Resolved Done Madhusudhan Ananderi Madhusudhan Ananderi Mon, 21 Apr 2014 23:44:01 +0000 Mon, 27 Sep 2021 09:01:08 +0000 Wed, 14 May 2014 16:29:06 +0000 General 0 4 <p>Hi Madhusudhan,<br/> the of10 part looks like you managed to send some error messages during handshake - this is solid bug.</p> <p>The of13 part looks like you are pushing flows into disconnected device. Could you provide more details about you setup - which build are you using, OS?</p> <p>Thank you,<br/> Michal</p> <p>For OF13 part, I used the build from integration repo. </p> <p><a href="https://jenkins.opendaylight.org/integration/job/integration-project-centralized-integration/lastSuccessfulBuild/artifact/distributions/base/target/distributions-base-0.1.2-SNAPSHOT-osgipackage.zip" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/integration/job/integration-project-centralized-integration/lastSuccessfulBuild/artifact/distributions/base/target/distributions-base-0.1.2-SNAPSHOT-osgipackage.zip</a></p> <p>After running the controller using -of13 option, I started mininet, however it found to be working fine but I could see those errors in OSGi logs.</p> <p>Regarding OS, I used CentOS.</p> <p>Thanks,<br/> Madhusudhan</p> <p>regarding mininet(of10):<br/> <a href="https://git.opendaylight.org/gerrit/#/c/6513/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/6513/</a></p> <p>regarding mininet(of13):</p> <p>How many exceptions of this type are you getting? There should be none or only a few (sometimes the switch disconnects right after connecting - but happens only at the beginning). Also could you check if all expected switches are registered?</p> <p><a href="http://localhost:8080/restconf/operational/opendaylight-inventory:nodes/" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8080/restconf/operational/opendaylight-inventory:nodes/</a></p> <p>Thank you.</p> <p>Attachment OSGi_Errors.txt has been added with description: OSGi errors</p> <p>Hi Michel,</p> <p>I just picked the latest build from integration repo. The things are encountered during the testing and have attached the document(OSGi_Errors) for clear information.</p> <p>Please let me know if you need any additional information.</p> <p>Thanks,<br/> Madhusudhan</p> <p>java.lang.InterruptedException are kind of new issue - will be solved separately</p> <hr /> <p>ERROR o.o.o.protocol.impl.core.OFEncoder - Serializer for key: msgVersion: 1 msgType: org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.action.rev130731.actions.grouping.Action msgType2: org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.action.rev130731.DecNwTtl was not found</p> <p>This shows, that you are trying to use OF-1.3 feature on OF-1.0 device.</p> <hr /> <p>java.lang.IllegalArgumentException: Session for the cookie is invalid. Reason: the switch has been recently disconnected OR inventory provides outdated information.</p> <p>This comes after devices disconnected and probably ad-sal apps are still trying to add/remove flows on devices. Those will be covered by sal-compatibility bugs.</p> <hr /> <p>Could you please retest with either using OF-1.0 features in flow or with OF-1.3 device?</p> <p>Hi Michal,</p> <p>I tested the following using the latest controller. I still facing the same issues when I try to add a flow using mininet 0f10 simulation running with of13 option in controller. The issue is only using mininet of10 simulation with of13 option controller</p> <p>1. wget 'https://jenkins.opendaylight.org/integration/job/integration-project-centralized-integration/lastSuccessfulBuild/org.opendaylight.integration$distributions-base/artifact/org.opendaylight.integration/distributions-base/0.1.2-SNAPSHOT/distributions-base-0.1.2-SNAPSHOT-osgipackage.zip'<br/> -<del>2014-04-29 16:50:37</del>- <a href="https://jenkins.opendaylight.org/integration/job/integration-project-centralized-integration/lastSuccessfulBuild/org.opendaylight.integration$distributions-base/artifact/org.opendaylight.integration/distributions-base/0.1.2-SNAPSHOT/distributions-base-0.1.2-SNAPSHOT-osgipackage.zip" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/integration/job/integration-project-centralized-integration/lastSuccessfulBuild/org.opendaylight.integration$distributions-base/artifact/org.opendaylight.integration/distributions-base/0.1.2-SNAPSHOT/distributions-base-0.1.2-SNAPSHOT-osgipackage.zip</a></p> <p>2. Start the controller using ./run.sh -of13 -Xmx1G -start<br/> 3. Start the mininet: sudo mn --controller 'remote,ip=127.0.0.1,port=6633' --topo tree,2 <br/> 4. Add a flow: PUT <a href="http://localhost:8080/restconf/config/opendaylight-inventory:nodes/node/openflow:1/table/2/flow/152" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8080/restconf/config/opendaylight-inventory:nodes/node/openflow:1/table/2/flow/152</a></p> <p>Body: <a href="https://wiki.opendaylight.org/view/Flow_body" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/Flow_body</a><br/> 5. FLows are getting installed in config: <a href="http://localhost:8080/restconf/config/opendaylight-inventory:nodes/node/openflow:1/table/2/flow/152" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8080/restconf/config/opendaylight-inventory:nodes/node/openflow:1/table/2/flow/152</a><br/> 6. But not the same in operational : GET <a href="http://localhost:8080/restconf/operational/opendaylight-inventory:nodes/node/openflow:1/table/2/flow/152" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8080/restconf/operational/opendaylight-inventory:nodes/node/openflow:1/table/2/flow/152</a></p> <p>7. At the switch, I could not see the flows as well when dumping the flows at the switch:<br/> mininet@mininet-vm:~\&gt; sudo ovs-ofctl dump-flows s1<br/> NXST_FLOW reply (xid=0x4):</p> <p>8. I get this error in OSGi after adding a flow:</p> <p>2014-04-29 16:59:01.751 PDT <span class="error">&#91;nioEventLoopGroup-10-1&#93;</span> ERROR o.o.o.protocol.impl.core.OFEncoder - Message serialization failed<br/> 2014-04-29 16:59:01.751 PDT <span class="error">&#91;nioEventLoopGroup-10-1&#93;</span> ERROR o.o.o.protocol.impl.core.OFEncoder - Serializer for key: msgVersion: 1 msgType: org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.action.rev130731.actions.grouping.Action msgType2: org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.action.rev130731.DecNwTtl was not found<br/> java.lang.NullPointerException: Serializer for key: msgVersion: 1 msgType: org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.action.rev130731.actions.grouping.Action msgType2: org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.action.rev130731.DecNwTtl was not found<br/> at org.opendaylight.openflowjava.protocol.impl.serialization.SerializerRegistryImpl.getSerializer(SerializerRegistryImpl.java:68) ~<span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.openflowjava.protocol.impl.util.CodingUtils.serializeActions(CodingUtils.java:52) ~<span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.openflowjava.protocol.impl.serialization.factories.OF10FlowModInputMessageFactory.serialize(OF10FlowModInputMessageFactory.java:50) ~<span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.openflowjava.protocol.impl.serialization.factories.OF10FlowModInputMessageFactory.serialize(OF10FlowModInputMessageFactory.java:31) ~<span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.openflowjava.protocol.impl.serialization.SerializationFactory.messageToBuffer(SerializationFactory.java:36) ~<span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.openflowjava.protocol.impl.core.OFEncoder.encode(OFEncoder.java:40) <span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.openflowjava.protocol.impl.core.OFEncoder.encode(OFEncoder.java:25) <span class="error">&#91;bundlefile:na&#93;</span><br/> at io.netty.handler.codec.MessageToByteEncoder.write(MessageToByteEncoder.java:111) <span class="error">&#91;bundlefile:4.0.17.Final&#93;</span><br/> at io.netty.channel.DefaultChannelHandlerContext.invokeWrite(DefaultChannelHandlerContext.java:647) <span class="error">&#91;bundlefile:4.0.17.Final&#93;</span><br/> at io.netty.channel.DefaultChannelHandlerContext.access$2000(DefaultChannelHandlerContext.java:29) <span class="error">&#91;bundlefile:4.0.17.Final&#93;</span><br/> at io.netty.channel.DefaultChannelHandlerContext$AbstractWriteTask.write(DefaultChannelHandlerContext.java:914) <span class="error">&#91;bundlefile:4.0.17.Final&#93;</span><br/> at io.netty.channel.DefaultChannelHandlerContext$WriteAndFlushTask.write(DefaultChannelHandlerContext.java:968) <span class="error">&#91;bundlefile:4.0.17.Final&#93;</span><br/> at io.netty.channel.DefaultChannelHandlerContext$AbstractWriteTask.run(DefaultChannelHandlerContext.java:903) <span class="error">&#91;bundlefile:4.0.17.Final&#93;</span><br/> at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:354) <span class="error">&#91;bundlefile:4.0.17.Final&#93;</span><br/> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:353) <span class="error">&#91;bundlefile:4.0.17.Final&#93;</span><br/> at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) <span class="error">&#91;bundlefile:4.0.17.Final&#93;</span><br/> at java.lang.Thread.run(Thread.java:744) <span class="error">&#91;na:1.7.0_51&#93;</span></p> <p>I could see the same issue happening at jenkins as well:</p> <p><a href="https://jenkins.opendaylight.org/integration/job/integration-csit-base-of13/805/robot/report/log.html" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/integration/job/integration-csit-base-of13/805/robot/report/log.html</a> - Please check "Restconf Flows" after "restart mininet OF10" testcase.</p> <p>Please note: Issue is happening at FRM (after adding a flow) and Host Tracker (After adding a flow) as well. I can raise it separately to avoid confusion with this one.</p> <p>Please let me know if there is something wrong with my testing.</p> <p>Thanks,<br/> Madhusudhan</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/6660/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/6660/</a><br/> (unregistering of provided node services)</p> <p>Madhusudhan,<br/> regarding your testing there is one problem: when you start integration build with -of13 parameter then you get running controller with support for OF-1.0 and OF-1.3. But then you start mininet (a assume you are using ovs backend). And ovs uses by default OF-1.0. You need to pass 'protocols' parameter' in order to use OF-1.3 by ovs. </p> <p><a href="https://wiki.opendaylight.org/view/Openflow_Protocol_Library:OpenVirtualSwitch" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/Openflow_Protocol_Library:OpenVirtualSwitch</a></p> <p>Hi Michal,</p> <p>Yes. Thats right.</p> <p>1. If I want to use of13 mininet to the controller running of13 option, I should specify the protocols=OpenFlow13 i.e.,</p> <p>sudo mn --topo tree,2 --controller 'remote,ip=127.0.0.1,port=6633' --switch ovsk,protocols=OpenFlow13</p> <p>2. If I want to use of10 mininet to the controller running of13 option, I should specify the protocols=OpenFlow10 i.e.,</p> <p>(a)sudo mn --topo tree,2 --controller 'remote,ip=127.0.0.1,port=6633' --switch ovsk,protocols=OpenFlow10</p> <p>OR</p> <p>(b) sudo mn --topo tree,2 --controller 'remote,ip=127.0.0.1,port=6633'</p> <p>--------------------------------------------------------------------------------</p> <p>A quick question: What is the correct way for invoking mininet(of10)?</p> <p>Should it (a) or (b). I get different behaviors when I chose two of them.</p> <p>Different responses can be seen at <a href="https://jira.opendaylight.org/browse/OPNFLWPLUG-148" title="OSGi errors after connecting mininet to the controller" class="issue-link" data-issue-key="OPNFLWPLUG-148"><del>OPNFLWPLUG-148</del></a></p> <p>Thanks,<br/> Madhusudhan</p> <p>Hi Madhusudhan,<br/> it does not matter, id you explicitly specify OF10 protocol parameter for ovs (via mininet) because OF-1.0is the default. </p> <p>Regarding different behavior - those are effects of 2 issues:</p> <ul class="alternate" type="square"> <li>ovs currently does not support groups - so by polling group stats device will always respond with errorMessage</li> <li>by processing of error messages (multiple of the same type) controller sometimes hit interrupted exception deep in classLoader.</li> </ul> <p>Regarding your testing scenario:<br/> DecNwTtl action is supported for OF-1.3 only. That is why you are getting the exception: <br/> Serializer for key: msgVersion: 1 msgType: org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.action.rev130731.actions.grouping.Action msgType2: org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.action.rev130731.DecNwTtl was not found</p> <p>In order not to get this exception you should use some of actions supported by OF-1.0. Otherwise there is no way for OFJava/OFPlugin to recover from the state.</p> <p>Sorry Michal for creating inconvenience and for the wrong body - Actually I was bit confused with the body (The link: <a href="https://wiki.opendaylight.org/view/CrossProject:Integration_Group:CSIT_Test_Plan_Base_of13" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/CrossProject:Integration_Group:CSIT_Test_Plan_Base_of13</a> is updated with the correct response body now to avoid this type of silly mistakes in the future)</p> <p>Anyways, using of10 mininet simulation, when I try to push a flow with an action &lt;output-node-connector&gt;openflow:1:1&lt;/output-node-connector&gt;, I could not see the change reflected in operational datastore.</p> <p>Steps to reproduce: </p> <p>1. Start the mininet OF10 simulation<br/> 2. Push a flow : PUT <a href="http://10.125.136.52:8080/restconf/config/opendaylight-inventory:nodes/node/openflow:1/table/2/flow/152" class="external-link" target="_blank" rel="nofollow noopener">http://10.125.136.52:8080/restconf/config/opendaylight-inventory:nodes/node/openflow:1/table/2/flow/152</a> and body: <a href="https://wiki.opendaylight.org/view/Flow_body" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/Flow_body</a> &#8211; look for of10 simulation<br/> 3. Verify the flows at operational: <a href="http://10.125.136.52:8080/restconf/operational/opendaylight-inventory:nodes/node/openflow:1/table/2" class="external-link" target="_blank" rel="nofollow noopener">http://10.125.136.52:8080/restconf/operational/opendaylight-inventory:nodes/node/openflow:1/table/2</a> &#8211; I could not see the flow gets updated.</p> <p>So I did some experimenting and:</p> <ul class="alternate" type="square"> <li>OF-10 supports only one table (table_id = 0) so pushing flow in table 0 works better - it appears in 20 secs in operational and after deleting from config it disappears from operational immediately.</li> </ul> <ul class="alternate" type="square"> <li>pushing flow into table 2 works too, but it will appear in operational under table 0 (as OF-10 uses no table_id in add flow message)</li> <li>and removing such a flow from config wont affect operational immediately. Statistics update will flush operational in 40-100 secs. But operational will get damaged and no more flows will appear there until switch is reconnected.</li> </ul> <p>Could you please try with table_id set to 0 (in xml), so that controller will be less confused?</p> <p>Anyway the behavior after flow removal resulting into cleaned operational part is not expected.</p> <p>Hi Michal, Madhusudhan left the OpenDaylight project for a while to finish his college. I do not think this is a bug so you can close it.</p> <p>BR/Luis</p> <p>ok</p> Development External issue ID 782 External issue URL Rank 0|i02z6f: