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-44 OpenFlowPlugin <p>I am seeing some missing nodeconnectors when I use<br/> "/controller/nb/v2/switchmanager/default/node/type/nodeid" using -of13 .I am using mininet with OF 1.0 for topology building. To test use "sudo mn –controller=remote,ip=127.0.0.01 –topo=tree,depth=3" and the </p> <p>I have attached a txt file with each call (from the mininet command above), the json output and what nodeconnectors are missing (at the bottom, output from my app)</p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-44

Missing nodeconnectors with new OF plugin using the SwitchNorthbound API

Bug Resolved Cannot Reproduce Lakshman K Mukkamalla Stace Hipperson Thu, 23 Jan 2014 18:00:21 +0000 Mon, 27 Sep 2021 09:01:02 +0000 Thu, 17 Apr 2014 18:36:56 +0000 General Mon, 31 Mar 2014 00:00:00 +0000 0 6 <p>Attachment missing-nodeconnectors-22-Jan-14.txt has been added with description: json output</p> <p>I am seeing "Ignore edge that contains invalid node connector" log messages that seem to correspond to the missing nodeconnectors (see output below)</p> <p>2014-01-24 10:23:47.949 GMT <span class="error">&#91;md-sal-binding-commit-7&#93;</span> WARN o.o.c.t.internal.TopologyManagerImpl - Ignore edge that contains invalid node connector: (MD_SAL|openflow:5:1@MD_SAL|openflow:5-&gt;MD_SAL|openflow:6:3@MD_SAL|openflow:6)<br/> 2014-01-24 10:23:52.946 GMT <span class="error">&#91;md-sal-binding-commit-4&#93;</span> WARN o.o.c.t.internal.TopologyManagerImpl - Ignore edge that contains invalid node connector: (MD_SAL|openflow:1:1@MD_SAL|openflow:1-&gt;MD_SAL|openflow:2:3@MD_SAL|openflow:2)<br/> 2014-01-24 10:23:52.947 GMT <span class="error">&#91;md-sal-binding-commit-7&#93;</span> WARN o.o.c.t.internal.TopologyManagerImpl - Ignore edge that contains invalid node connector: (MD_SAL|openflow:5:1@MD_SAL|openflow:5-&gt;MD_SAL|openflow:6:3@MD_SAL|openflow:6)</p> <p>This seems to be an adaptor issue:</p> <p>Output from: "sudo mn --topo=tree,3 --controller=remote,127.0.0.1"</p> <p>ovsdb-client dump<br/> <a href="http://pastebin.com/download.php?i=5yrbq8hn" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/download.php?i=5yrbq8hn</a> </p> <p>Warning messages from ODP and switchmanager/default/node/"+nodetype + "/" + nodeid<br/> <a href="http://pastebin.com/download.php?i=nDkFsSZ9" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/download.php?i=nDkFsSZ9</a></p> <p>output from <a href="http://localhost:8080/restconf/datastore/opendaylight-inventory:nodes/node/openflow:5" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8080/restconf/datastore/opendaylight-inventory:nodes/node/openflow:5</a></p> <p><a href="http://pastebin.com/download.php?i=J4v8gz61" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/download.php?i=J4v8gz61</a></p> <p>(In reply to Stace Hipperson from comment #1)<br/> &gt; I am seeing "Ignore edge that contains invalid node connector" log messages<br/> &gt; that seem to correspond to the missing nodeconnectors (see output below)<br/> &gt; <br/> &gt; 2014-01-24 10:23:47.949 GMT <span class="error">&#91;md-sal-binding-commit-7&#93;</span> WARN <br/> &gt; o.o.c.t.internal.TopologyManagerImpl - Ignore edge that contains invalid<br/> &gt; node connector:<br/> &gt; (MD_SAL|openflow:5:1@MD_SAL|openflow:5-&gt;MD_SAL|openflow:6:3@MD_SAL|openflow:<br/> &gt; 6)<br/> &gt; 2014-01-24 10:23:52.946 GMT <span class="error">&#91;md-sal-binding-commit-4&#93;</span> WARN <br/> &gt; o.o.c.t.internal.TopologyManagerImpl - Ignore edge that contains invalid<br/> &gt; node connector:<br/> &gt; (MD_SAL|openflow:1:1@MD_SAL|openflow:1-&gt;MD_SAL|openflow:2:3@MD_SAL|openflow:<br/> &gt; 2)<br/> &gt; 2014-01-24 10:23:52.947 GMT <span class="error">&#91;md-sal-binding-commit-7&#93;</span> WARN <br/> &gt; o.o.c.t.internal.TopologyManagerImpl - Ignore edge that contains invalid<br/> &gt; node connector:<br/> &gt; (MD_SAL|openflow:5:1@MD_SAL|openflow:5-&gt;MD_SAL|openflow:6:3@MD_SAL|openflow:<br/> &gt; 6)</p> <p>I'm using the release artifact for the base edition which I got the following page.</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>And, I see the same result with the release artifact.</p> <p>Any thoughts?</p> <p>(In reply to Abhijit Kumbhare from comment #4)<br/> &gt; Any thoughts?</p> <p>It may be already fixed by some patches.<br/> I'll test this with the latest code this weekend.</p> <p>Thanks Hideyuki! Please let us know what you find - especially Ed.</p> <p>OVS client dump output</p> <p>Attachment ovsdb-client dump.txt has been added with description: OVSDB_Client Dump</p> <p>Tried to reproduce the issue on OF project with following setup:<br/> Mininet version - 2.1.0<br/> OVS version-<br/> ovs-ofctl (Open vSwitch) 2.0.0<br/> Compiled Nov28 2013 01:14:20<br/> OpenFlow versions 0x1:0x4</p> <p>sudo mn --controller=remote,ip=192.168.56.1 --topo=tree,3 --switch ovsk,protocols=OpenFlow13</p> <p>Topology view - response from /operational/network-topology:network-topology/topology/flow:1<br/> <a href="http://pastebin.com/download.php?i=8K62VurP" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/download.php?i=8K62VurP</a></p> <p>Operational Nodes - response from operational/opendaylight-inventory:nodes<br/> <a href="http://pastebin.com/download.php?i=bTZJxN5q" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/download.php?i=bTZJxN5q</a></p> <p>Switch Manager Nodes - response from /controller/nb/v2/switchmanager/default/nodes<br/> <a href="http://pastebin.com/download.php?i=TWtZUnWS" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/download.php?i=TWtZUnWS</a></p> <p>Also attached the ovsclient dump</p> <p>Lakshman - so you are not able to reproduce this issue?</p> <p>I don't see this issues with the latest code.</p> <p>I pulled the latest code of the Integration Git repository, and built the base edition.<br/> On the base edition, I did the same operation by which I saw the issue on 2014-01-29 (See Comment 3 on the bug report).<br/> But I did not see the issue, and confirmed that I can get all nodeconnectors using the SwitchNorthbound API.<br/> I think this issue has been fixed by a patch which has been merged after Hydrogen release.</p> <p><span class="error">&#91;Operation for mininet&#93;</span><br/> mininet@mininet-vm:~$ mn --version<br/> 2.0.0<br/> mininet@mininet-vm:~$ sudo mn --controller=remote,ip=192.168.60.180 --topo tree,3</p> <p><span class="error">&#91;Operation for OpenDaylight Controller&#93;</span></p> <p>$ git log -1<br/> commit e4ecb6d69d0d7b6b7566fa184386866fb05ae3e1<br/> Author: Robert Varga &lt;rovarga@cisco.com&gt;<br/> Date: Fri Apr 11 17:20:51 2014 +0200</p> <p> Do not bundle META-INF in configuration</p> <p> This fixes a packaging issue, where the META-INF directory of<br/> downstream configuration jars would be included in final distribution's<br/> configuration directory &#8211; e.g. we had a useless configuration/META-INF<br/> directory.</p> <p> Should be included in stable branch, too.</p> <p> Change-Id: I96ad12589876d2585dab5cd3ddee4e271fbb3231<br/> Signed-off-by: Robert Varga &lt;rovarga@cisco.com&gt;</p> <p>$ ./run.sh -of13</p> <p><span class="error">&#91;Operation for SwitchNorthbound API&#93;</span><br/> I sent GET requests to the following URI.</p> <p><a href="http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflo" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflo</a><br/> w:1<br/> <a href="http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflow:2" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflow:2</a><br/> <a href="http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflow:3" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflow:3</a><br/> <a href="http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflow:4" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflow:4</a><br/> <a href="http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflow:5" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflow:5</a><br/> <a href="http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflow:6" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflow:6</a></p> <p>Abhijit, This is not reproducible. Shall move it to R with resolution worksforme.</p> Development External issue ID 354 External issue URL Rank 0|i02ypz: