OpenDaylight JIRA

OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us

8.20.10

820010

22-06-2022

[OPNFLWPLUG-54] NSF Flow port stats do not show for mininet OF10 https://jira.opendaylight.org/browse/OPNFLWPLUG-54 OpenFlowPlugin <p>These are the steps:</p> <p>start mininet with: sudo mn --controller=remote,ip=127.0.0.1 --topo tree,2</p> <p>Pull port stats:<br/> <a href="http://127.0.0.1:8080/controller/nb/v2/statistics/default/port" class="external-link" target="_blank" rel="nofollow noopener">http://127.0.0.1:8080/controller/nb/v2/statistics/default/port</a></p> <p>No ports are shown on the response body:</p> <p><list><br/> <portStatistics><br/> <node><br/> <id>00:00:00:00:00:00:00:02</id><br/> <type>OF</type><br/> </node><br/> </portStatistics><br/> <portStatistics><br/> <node><br/> <id>00:00:00:00:00:00:00:03</id><br/> <type>OF</type><br/> </node><br/> </portStatistics><br/> <portStatistics><br/> <node><br/> <id>00:00:00:00:00:00:00:01</id><br/> <type>OF</type><br/> </node><br/> </portStatistics><br/> </list></p> <p>Operating System: Linux<br/> Platform: PC</p> OPNFLWPLUG-54

NSF Flow port stats do not show for mininet OF10

Bug Resolved Won't Do Luis Gomez Luis Gomez Sun, 26 Jan 2014 07:03:41 +0000 Mon, 27 Sep 2021 09:01:03 +0000 Wed, 5 Mar 2014 10:23:04 +0000 General 0 2 <p>A few notes. This bug is for </p> <p><a href="https://git.opendaylight.org/gerrit/#/c/4737/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/4737/</a></p> <p>And the relatvent exception at the console is:</p> <p>2014-01-25 22:30:46.119 PST <span class="error">[md-sal-binding-notification-2]</span> ERROR o.o.c.sal.binding.impl.NotifyTask - Unhandled exception thrown by listener: org.opendaylight.controller.sal.compatibility.InventoryAndReadAdapter$$Broker$ListenerInvoker@623b51f3<br/> java.lang.NumberFormatException: Value 65534 out of range from input 65534<br/> at java.lang.Short.decode(Short.java:283) ~<span class="error">[na:1.7.0_25]</span><br/> at org.opendaylight.controller.sal.compatibility.NodeMapping.toPortNumber(NodeMapping.java:200) ~<span class="error">[na:na]</span><br/> at org.opendaylight.controller.sal.compatibility.NodeMapping.toADNodeConnectorId(NodeMapping.java:190) ~<span class="error">[na:na]</span><br/> at org.opendaylight.controller.sal.compatibility.NodeMapping.toADNodeConnector(NodeMapping.java:138) ~<span class="error">[na:na]</span><br/> at org.opendaylight.controller.sal.compatibility.NodeMapping.toADNodeConnector(NodeMapping.java:132) ~<span class="error">[na:na]</span><br/> at org.opendaylight.controller.sal.compatibility.InventoryAndReadAdapter.toNodeConnectorStatistics(InventoryAndReadAdapter.java:768) ~<span class="error">[na:na]</span><br/> at org.opendaylight.controller.sal.compatibility.InventoryAndReadAdapter.onNodeConnectorStatisticsUpdate(InventoryAndReadAdapter.java:923) ~<span class="error">[na:na]</span><br/> at org.opendaylight.controller.sal.compatibility.InventoryAndReadAdapter$$Broker$ListenerInvoker.onNotification(InventoryAndReadAdapter$$Broker$ListenerInvoker.java) ~<span class="error">[na:na]</span><br/> at org.opendaylight.controller.sal.binding.impl.NotifyTask.call(NotifyTask.java:59) ~<span class="error">[na:na]</span><br/> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) ~<span class="error">[na:1.7.0_25]</span><br/> at java.util.concurrent.FutureTask.run(FutureTask.java:166) ~<span class="error">[na:1.7.0_25]</span><br/> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) ~<span class="error">[na:1.7.0_25]</span><br/> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) ~<span class="error">[na:1.7.0_25]</span><br/> at java.lang.Thread.run(Thread.java:724) ~<span class="error">[na:1.7.0_25]</span></p> <p>What this comes down to is for we need to handle the correct mapping back and forth of special ports for both OF10 and OF13. I would suggest we simply map both sets of ports.</p> <p>Luis, could you retest? I tried, but I failed to replicate.<br/> Thank you.</p> <p>This bug is related to a fix Ed prepared to change the switches name in the new OF13 plugin. Since this fix never saw the light, you can safely close this bug.</p> <p>BR/Luis</p> Development External issue ID 371 External issue URL Rank 0|i02ys7: