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-61 OpenFlowPlugin <p>I used the the base edition of the release artifact for Hydrogen.</p> <p><a href="http://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/distributions-base/0.1.0/distributions-base-0.1.0-osgipackage.zip" class="external-link" target="_blank" rel="nofollow noopener">http://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/distributions-base/0.1.0/distributions-base-0.1.0-osgipackage.zip</a></p> <p>I run a controller with -of13 option, and run a Mininet OF 1.0.</p> <p>mininet@mininet-vm:~$ sudo mn --controller=remote,ip=192.168.60.180 --topo tree,2</p> <p>I executed ping command from h1 to h3, but all packets does not reach to h3.</p> <p>mininet&gt; h1 ping h3<br/> ^CPING 10.0.0.3 (10.0.0.3) 56(84) bytes of data.</p> <p>&#8212; 10.0.0.3 ping statistics &#8212;<br/> 3008 packets transmitted, 0 received, 100% packet loss, time 3031057ms</p> <p>At the time, I saw an ERROR message on the OSGi console.</p> <p>2014-01-28 20:55:35.835 EST <span class="error">&#91;pool-26-thread-4&#93;</span> ERROR o.o.o.o.m.c.t.PortStatusMessageToNodeConnectorUpdatedTranslator - PortStatusMessage: version 1 dataPathId 2 portNo 1<br/> 2014-01-28 20:55:40.127 EST <span class="error">&#91;md-sal-binding-commit-14&#93;</span> WARN o.o.c.t.internal.TopologyManagerImpl - Ignore edge that contains invalid node connector: (MD_SAL|openflow:1:2@MD_SAL|openflow:1-&gt;MD_SAL|openflow:3:3@MD_SAL|openflow:3)<br/> 2014-01-28 20:55:45.121 EST <span class="error">&#91;md-sal-binding-commit-5&#93;</span> WARN o.o.c.t.internal.TopologyManagerImpl - Ignore edge that contains invalid node connector: (MD_SAL|openflow:1:2@MD_SAL|openflow:1-&gt;MD_SAL|openflow:3:3@MD_SAL|openflow:3)</p> <p>On the other hand ping between h1 and h2 worked well.</p> <p>mininet&gt; h1 ping h2<br/> PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.<br/> 64 bytes from 10.0.0.2: icmp_req=2 ttl=64 time=0.156 ms<br/> 64 bytes from 10.0.0.2: icmp_req=3 ttl=64 time=0.037 ms</p> <p>I think this issues is related to the following issue.</p> <p><a href="https://bugs.opendaylight.org/show_bug.cgi?id=354" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=354</a></p> <p>Operating System: Linux<br/> Platform: PC</p> OPNFLWPLUG-61

ping between hosts not working with mininet OF 1.0

Bug Resolved Duplicate Unassigned Hideyuki Tai Wed, 29 Jan 2014 02:55:30 +0000 Mon, 27 Sep 2021 09:01:04 +0000 Tue, 25 Mar 2014 17:14:19 +0000 General 0 6 <p>Hi Hideyuki Tai ,</p> <p>Following are my observation while trying to reproduce this bug :</p> <p>1)Start Mininet,then start Controller .Ping between h1 to h3 unreliable.Rest all pings work fine.</p> <p>2)Start Controller, start mininet within 1 minute of starting controller,ping works.</p> <p>3)Start Controller,once the controller is up and running then start Mininet. Ping only works between the hosts connected to same switch. </p> <p>For 1,3 Observations,I found out that getAllHosts method in hostTracker.java class returns only source host whereas in (2) it returns source and destination host.</p> <p>I am looking further into this.</p> <p>This should be working - can we check?</p> <p>It is working, but during the first round usually not all pings succeed. Reason is probably in strategy - how the controller pushes flows to switches. The second round is then always 100% success. Question is if this is expected behavior. </p> <p>I believe that as soon as the topology is explored, the controller must be able to manage all ping packets to be delivered.</p> <p>This ping is working fine after the first attempt.</p> <p>Downloaded the latest controller and started the mininet OF10</p> <p>mininet&gt; pingall</p> <ul> <li> <ul> <li> <ul> <li>Ping: testing ping reachability<br/> h1 -&gt; X h3 h4 <br/> h2 -&gt; h1 h3 h4 <br/> h3 -&gt; h1 h2 X <br/> h4 -&gt; h1 h2 h3 </li> <li>Results: 16% dropped (10/12 received)<br/> mininet&gt; pingall</li> <li>Ping: testing ping reachability<br/> h1 -&gt; h2 h3 h4 <br/> h2 -&gt; h1 h3 h4 <br/> h3 -&gt; h1 h2 h4 <br/> h4 -&gt; h1 h2 h3 </li> <li>Results: 0% dropped (12/12 received)</li> </ul> </li> </ul> </li> </ul> <p>I think the issue is fixed!</p> <p>We need to fix this for the first ping attempt. However this may not be critical for immediate service release (end of March).</p> <p>(In reply to Abhijit Kumbhare from comment #5)<br/> &gt; We need to fix this for the first ping attempt. However this may not be<br/> &gt; critical for immediate service release (end of March).</p> <p>agreed.</p> <p>In the bug report #384, I originally reported that ping failed with the following errors.</p> <p>2014-01-28 20:55:35.835 EST <span class="error">&#91;pool-26-thread-4&#93;</span> ERROR o.o.o.o.m.c.t.PortStatusMessageToNodeConnectorUpdatedTranslator - PortStatusMessage: version 1 dataPathId 2 portNo 1<br/> 2014-01-28 20:55:40.127 EST <span class="error">&#91;md-sal-binding-commit-14&#93;</span> WARN o.o.c.t.internal.TopologyManagerImpl - Ignore edge that contains invalid node connector: (MD_SAL|openflow:1:2@MD_SAL|openflow:1-&gt;MD_SAL|openflow:3:3@MD_SAL|openflow:3)<br/> 2014-01-28 20:55:45.121 EST <span class="error">&#91;md-sal-binding-commit-5&#93;</span> WARN o.o.c.t.internal.TopologyManagerImpl - Ignore edge that contains invalid node connector: (MD_SAL|openflow:1:2@MD_SAL|openflow:1-&gt;MD_SAL|openflow:3:3@MD_SAL|openflow:3)</p> <p>Therefore, I think it is ok to close this bug report if ping not failed with the above errors.</p> <p>I think the problem in the first ping attempt is caused by delay for topology discovery.<br/> Through some tests on OpenDaylight Controller, we figure out that the performance of the controller for topology discovery is very low.</p> <p>(In reply to Hideyuki Tai from comment #6)<br/> &gt; (In reply to Abhijit Kumbhare from comment #5)<br/> &gt; &gt; We need to fix this for the first ping attempt. However this may not be<br/> &gt; &gt; critical for immediate service release (end of March).<br/> &gt; <br/> &gt; agreed.<br/> &gt;<br/> (snip) <br/> &gt; <br/> &gt; Therefore, I think it is ok to close this bug report if ping not failed with<br/> &gt; the above errors.<br/> &gt; </p> <p>I'll test it with the latest code this weekend.</p> <p>I created <a href="https://jira.opendaylight.org/browse/CONTROLLER-232" title="Packet loss on first time ping test" class="issue-link" data-issue-key="CONTROLLER-232"><del>CONTROLLER-232</del></a> to collect this issue.</p> Blocks OPNFLWPLUG-67 Duplicate CONTROLLER-232 Development External issue ID 384 External issue URL Rank 0|i02ytr: