[ovs-discuss] Unexpected behavior of counters when installing new flow
Tmusic
Tmusic987 at gmail.com
Mon Apr 29 18:08:12 UTC 2013
Hi,
I'm experiencing some unexpected behavior from the flow counters when using
wildcarded flow entries (with OpenFlow).
Steps to reproduce:
- Start a udp flow ex. 10.1.4.1=>10.1.6.1
- Install wildcarded entry 10.1.4.0/30 => 10.1.6.0/30
==>After some time counters (ovs-ofctl dump-flows) indicate for example
n_packets=4775, n_bytes=5090150, idle_age=0
- Install second entry and set higher priority (ex 65100) : 10.1.4.0/31 =>
10.1.6.0/31)
==> Now the counters read ex. n_packets=0, n_bytes=0, idle_age=7
==> The old counter values are added to the new flow n_packets=18775,
n_bytes=20014150, idle_age=0
I suppose this is a consequence of the fact that non-wildcarded entries are
installed in the datapath and later combined to form the 'OpenFlow'
counters and since the new entry overlaps with the old entry...
So my question are: First of all, did anyone else experience this behavior?
And second, is this the intended behavior?
Thank you in advance,
Tim
Configuration details:
Open vSwitch 1.7.3
Ubuntu 11.04
Kernel 2.6.38-11-generic-pae
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20130429/208a1806/attachment-0001.html>
More information about the discuss
mailing list