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-146 OpenFlowPlugin <p>Hello,</p> <p>Topology fails with controller(of13) using both OF13 &amp; OF10 mininet simulation</p> <p>Steps can be reproduced easily:</p> <p>Download the latest controller form integration repo.</p> <p>1. Start the controller : ./run.sh -of13 -Xmx1G -start<br/> 2. Start the mininet(of10): sudo mn --controller 'remote,ip=127.0.0.1,port=6633' --topo tree,2<br/> 3. GET <a href="http://localhost:8080/controller/nb/v2/topology/default" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8080/controller/nb/v2/topology/default</a></p> <p>and the response is<br/> &lt;?xml version="1.0" encoding="UTF-8" standalone="yes"?&gt;<br/> &lt;topology/&gt;</p> <p>4. Start the mininet(of13): sudo mn --topo tree,2 --controller 'remote,ip=127.0.0.1,port=6633' --switch ovsk,protocols=OpenFlow13</p> <p>5. GET <a href="http://localhost:8080/controller/nb/v2/topology/default" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8080/controller/nb/v2/topology/default</a></p> <p>and the response is<br/> &lt;?xml version="1.0" encoding="UTF-8" standalone="yes"?&gt;<br/> &lt;topology/&gt;</p> <p>Because of this topology behavior, the other testcases are getting failed.</p> <p>Thanks,<br/> Madhusudhan</p> <p>Operating System: Windows<br/> Platform: PC</p> OPNFLWPLUG-146

Topology not cleared using mininet of13/of10 simulation

Bug Resolved Done Madhusudhan Ananderi Madhusudhan Ananderi Thu, 1 May 2014 00:29:56 +0000 Mon, 27 Sep 2021 09:01:10 +0000 Fri, 30 May 2014 08:28:49 +0000 General 0 6 <p>This bug should be fixed at current master, please verify if the topology is working.</p> <p>Yes, this has been fixed and working fine now. I am able to see the links. </p> <p>However, I still having issues with the errors shown in OSGi logs after starting the mininet (of13/of10) simulation. This is reported in <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> and waiting for the fix status to be merged.</p> <p>Thanks,<br/> Madhusudhan</p> <p>Tony,</p> <p>Topology is not cleared on the GUI now after disconnecting mininet (both of13/of10).</p> <p>However, when I check at the inventory, it is cleared and working as expected.</p> <p>GET <a href="http://127.0.0.1:8080/controller/nb/v2/connectionmanager/nodes" class="external-link" target="_blank" rel="nofollow noopener">http://127.0.0.1:8080/controller/nb/v2/connectionmanager/nodes</a></p> <p>Thanks,<br/> Tony</p> <p>Bugfix in <a href="https://git.opendaylight.org/gerrit/#/c/6785/1" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/6785/1</a> . Incorrect edge update was sent to topology manager on link removed.</p> <p>Hi Tony,</p> <p>Thanks for the fix. Topology is cleared on the GUI after disconnecting mininet (both of13/of10)</p> <p>I got the following in the topology:</p> <p>1. When using mininet (of10) simulation: sudo mn --topo tree,2 --controller 'remote,ip=10.125.136.52,port=6633' --switch ovsk,protocols=OpenFlow13</p> <p>The below stats is correct.</p> <p>Node ID Ports<br/> MD_SAL|openflow:1 3<br/> MD_SAL|openflow:3 4<br/> MD_SAL|openflow:2 4</p> <p>2. When using mininet (of13) simulation: sudo mn --topo tree,2 --controller 'remote,ip=10.125.136.52,port=6633' --switch ovsk,protocols=OpenFlow13</p> <p>Node ID Ports<br/> MD_SAL|openflow:1 2<br/> MD_SAL|openflow:3 3<br/> MD_SAL|openflow:2 3</p> <p>Shouldn't be the same stats as shown using mininet (of10)?</p> <p>Sorry for the typo error. </p> <p>Please assume the below point</p> <p>1. When using mininet (of10) simulation: sudo mn --topo tree,2 --controller 'remote,ip=10.125.136.52,port=6633' --switch ovsk,protocols=OpenFlow13</p> <p>as this one.</p> <p>1. When using mininet (of10) simulation: sudo mn --topo tree,2 --controller 'remote,ip=10.125.136.52,port=6633'</p> <p>This is working for me now, what about you Madhusudhan?</p> <p>Luis, Were you able to see the correct ports on the GUI?</p> <p>Everything works fine except the above thing!</p> <p>Hi Madhu, I see the same as you but this is totally unrelated issue so please open a new bug for it. For this new bug I already saw it could be because of the internal switch connector type in the AD-SAL switch manager. For the same topology:</p> <p>Using OF13 simulation, the internal switch connector is type SW and does not show in GUI: </p> <p>GET <a href="http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflow:1" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflow:1</a></p> <p> {<br/> "properties": {<br/> "name": </p> { "value": "s1" } <p>,<br/> "state": </p> { "value": 1 } <p>,<br/> "config": </p> { "value": 1 } <p> },<br/> "nodeconnector": {<br/> "node": </p> { "id": "openflow:1", "type": "MD_SAL" } <p>,<br/> "id": "0",<br/> "type": "SW"<br/> }<br/> },</p> <p>Using OF10 simulation, the internal switch connector is type MD_SAL and shows in GUI: </p> <p>"properties": {<br/> "name": </p> { "value": "s1" } <p>,<br/> "state": </p> { "value": 1 } <p>,<br/> "config": </p> { "value": 1 } <p> },<br/> "nodeconnector": {<br/> "node": </p> { "id": "openflow:1", "type": "MD_SAL" } <p>,<br/> "id": "openflow:1:65534",<br/> "type": "MD_SAL"<br/> }<br/> },</p> <p>Thanks Luis. I agree with your logic. The new issue is not related to the title of this bug. </p> <p>Hence this bug stands resolved!</p> <p>Madhusudhan - if its resolved - can you mark it fixed?</p> <p>Hi Abhijit,</p> <p>This issue is fixed and verified. Moved the status to FIXED.</p> <p>BR/Madhu</p> <p>I opened <a href="https://jira.opendaylight.org/browse/OPNFLWPLUG-178" title="Different connector count in GUI depending if mininet OF10 or OF13" class="issue-link" data-issue-key="OPNFLWPLUG-178"><del>OPNFLWPLUG-178</del></a> for the issue that is nothing to do with this bug.</p> Duplicate CONTROLLER-452 Development External issue ID 933 External issue URL Rank 0|i02zcn: