[OPNFLWPLUG-54] NSF Flow port stats do not show for mininet OF10 Created: 26/Jan/14  Updated: 27/Sep/21  Resolved: 05/Mar/14

Status: Resolved
Project: OpenFlowPlugin
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Luis Gomez Assignee: Luis Gomez
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: PC

External issue ID: 371

 Description   

These are the steps:

start mininet with: sudo mn --controller=remote,ip=127.0.0.1 --topo tree,2

Pull port stats:
http://127.0.0.1:8080/controller/nb/v2/statistics/default/port

No ports are shown on the response body:

<list>
<portStatistics>
<node>
<id>00:00:00:00:00:00:00:02</id>
<type>OF</type>
</node>
</portStatistics>
<portStatistics>
<node>
<id>00:00:00:00:00:00:00:03</id>
<type>OF</type>
</node>
</portStatistics>
<portStatistics>
<node>
<id>00:00:00:00:00:00:00:01</id>
<type>OF</type>
</node>
</portStatistics>
</list>

 Comments   
Comment by Ed Warnicke [ 26/Jan/14 ]

A few notes. This bug is for

https://git.opendaylight.org/gerrit/#/c/4737/

And the relatvent exception at the console is:

2014-01-25 22:30:46.119 PST [md-sal-binding-notification-2] ERROR o.o.c.sal.binding.impl.NotifyTask - Unhandled exception thrown by listener: org.opendaylight.controller.sal.compatibility.InventoryAndReadAdapter$$Broker$ListenerInvoker@623b51f3
java.lang.NumberFormatException: Value 65534 out of range from input 65534
at java.lang.Short.decode(Short.java:283) ~[na:1.7.0_25]
at org.opendaylight.controller.sal.compatibility.NodeMapping.toPortNumber(NodeMapping.java:200) ~[na:na]
at org.opendaylight.controller.sal.compatibility.NodeMapping.toADNodeConnectorId(NodeMapping.java:190) ~[na:na]
at org.opendaylight.controller.sal.compatibility.NodeMapping.toADNodeConnector(NodeMapping.java:138) ~[na:na]
at org.opendaylight.controller.sal.compatibility.NodeMapping.toADNodeConnector(NodeMapping.java:132) ~[na:na]
at org.opendaylight.controller.sal.compatibility.InventoryAndReadAdapter.toNodeConnectorStatistics(InventoryAndReadAdapter.java:768) ~[na:na]
at org.opendaylight.controller.sal.compatibility.InventoryAndReadAdapter.onNodeConnectorStatisticsUpdate(InventoryAndReadAdapter.java:923) ~[na:na]
at org.opendaylight.controller.sal.compatibility.InventoryAndReadAdapter$$Broker$ListenerInvoker.onNotification(InventoryAndReadAdapter$$Broker$ListenerInvoker.java) ~[na:na]
at org.opendaylight.controller.sal.binding.impl.NotifyTask.call(NotifyTask.java:59) ~[na:na]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) ~[na:1.7.0_25]
at java.util.concurrent.FutureTask.run(FutureTask.java:166) ~[na:1.7.0_25]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) ~[na:1.7.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) ~[na:1.7.0_25]
at java.lang.Thread.run(Thread.java:724) ~[na:1.7.0_25]

Comment by Ed Warnicke [ 26/Jan/14 ]

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.

Comment by Michal Rehak [ 04/Mar/14 ]

Luis, could you retest? I tried, but I failed to replicate.
Thank you.

Comment by Luis Gomez [ 05/Mar/14 ]

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.

BR/Luis

Generated at Wed Feb 07 20:31:27 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.