Details
-
Improvement
-
Status: Resolved
-
Resolution: Done
-
None
-
None
-
None
-
Operating System: Mac OS
Platform: PC
Description
When running:
sudo mn --topo tree,2 --controller 'remote,ip=10.0.2.2:6633' --switch ovsk,protocols=OpenFlow10
Against the new openflowplugin, and then running in mininet
h1 ping h2
(which fails, different bug)
In stats I see:
http://localhost:8080/restconf/operational/opendaylight-inventory:nodes/node/openflow:1/table/0
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<table
xmlns="urn:opendaylight:flow:inventory">
<aggregate-flow-statistics
xmlns="urn:opendaylight:flow:statistics">
<byte-count>0</byte-count>
<packet-count>0</packet-count>
<flow-count>0</flow-count>
</aggregate-flow-statistics>
<id>0</id>
<flow-table-statistics
xmlns="urn:opendaylight:flow:table:statistics">
<packets-looked-up>36852</packets-looked-up>
<packets-matched>36595</packets-matched>
<active-flows>9</active-flows>
</flow-table-statistics>
<flow>
<id>1011</id>
<flow-statistics
xmlns="urn:opendaylight:flow:statistics">
<match>
<ipv4-source>0.0.0.0/0</ipv4-source>
<ipv4-destination>0.0.0.0/0</ipv4-destination>
<ip-match>
<ip-protocol>0</ip-protocol>
</ip-match>
<in-port>openflow:1:0</in-port>
<ethernet-match>
<ethernet-source>
<address>00:00:00:00:00:00</address>
</ethernet-source>
<ethernet-type>
<type>2048</type>
</ethernet-type>
<ethernet-destination>
<address>00:00:00:00:00:00</address>
</ethernet-destination>
</ethernet-match>
<vlan-match>
<vlan-pcp>0</vlan-pcp>
<vlan-id>
<vlan-id>0</vlan-id>
</vlan-id>
</vlan-match>
</match>
<table_id>0</table_id>
<duration>
<nanosecond>369000000</nanosecond>
<second>78</second>
</duration>
<cookie>0</cookie>
<packet-count>0</packet-count>
<priority>1</priority>
<byte-count>0</byte-count>
<hard-timeout>0</hard-timeout>
<idle-timeout>0</idle-timeout>
</flow-statistics>
</flow>
</table>
On the switch I see:
vagrant@vagrant-ubuntu-trusty-64:~$ sudo ovs-ofctl -O OpenFlow10 dump-flows s1
NXST_FLOW reply (xid=0x4):
cookie=0x0, duration=5.357s, table=0, n_packets=0, n_bytes=0, idle_age=5, priority=1,ip actions=output:1
And in the config I see:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<table
xmlns="urn:opendaylight:flow:inventory">
<flow>
<instructions>
<instruction>
<order>0</order>
<apply-actions>
<action>
<output-action>
<output-node-connector>openflow:1:1</output-node-connector>
</output-action>
</action>
</apply-actions>
</instruction>
</instructions>
<table_id>0</table_id>
<id>b80f35b0-ebe9-476a-a36a-3bcb459cee86</id>
<match>
<ipv4-destination>10.0.0.1</ipv4-destination>
<ethernet-match>
<ethernet-type>
<type>2048</type>
</ethernet-type>
</ethernet-match>
</match>
<hard-timeout>0</hard-timeout>
<cookie>0</cookie>
<idle-timeout>0</idle-timeout>
<priority>1</priority>
</flow>
</table>
We are getting spurious eth src/dst matches reported in stats which we shouldn't.