[ovs-discuss] Lookup and Match count behavior

[love you]

Please find the output below

ovs-ofctl add-flow br0 "dl_src=11:22:33:44:55:66,arp action=normal"

[root at shally ovs]#ovs-ofctl dump-flows br0
NXST_FLOW reply (xid=0x4):
 cookie=0x0, duration=27.888s, table=0, n_packets=0, n_bytes=0,
idle_age=27, arp,dl_src=11:22:33:44:55:66 actions=NORMAL

ovs-ofctl dump-tables br0 | less

OFPST_TABLE reply (xid=0x1): 255 tables

  0: main    : wild=0x3fffff, max=1000000, active=1

               lookup=33941, matched=1900



Result for tcpdump-

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

listening on br0, link-type EN10MB (Ethernet), capture size 65535 bytes

15:04:15.799164 IP 0.0.0.0 > 0.0.0.0:  ip-proto-255 0

15:04:15.975006 IP 0.0.0.0 > 0.0.0.0:  ip-proto-255 0

^C

2 packets captured

2 packets received by filter

0 packets dropped by kernel




ovs-ofctl dump-tables br0 | less

OFPST_TABLE reply (xid=0x1): 255 tables

  0: main    : wild=0x3fffff, max=1000000, active=1

               lookup=33943, matched=1903



Result for tcpdump-

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

listening on br0, link-type EN10MB (Ethernet), capture size 65535 bytes

15:05:28.590683 IP 0.0.0.0 > 0.0.0.0:  ip-proto-255 0

15:05:28.766497 IP 0.0.0.0 > 0.0.0.0:  ip-proto-255 0

15:05:28.961985 IP 0.0.0.0 > 0.0.0.0:  ip-proto-255 0

^C

3 packets captured

3 packets received by filter

0 packets dropped by kernel

ovs-ofctl dump-tables br0 | less

OFPST_TABLE reply (xid=0x1): 255 tables

  0: main    : wild=0x3fffff, max=1000000, active=1

               lookup=33946, matched=1908


The think above output will explain the issue clearly.


Regards

Anish










On Thu, May 23, 2013 at 8:51 PM, Jesse Gross <jesse at nicira.com> wrote:

> Please still check the actual packets that are being sent using
> tcpdump. If that shows what you expect, then post that output plus the
> exact messages that you are seeing.
>
> On Wed, May 22, 2013 at 9:25 AM, love you <thunder.love07 at gmail.com>
> wrote:
> > I am sending the non matching packet from the ostinato and my physical
> > interface is down, I also didn't have any virtual machine on my setup.
> >
> > One more thing here is that the lookup count is incremented by 2 only.
> >
> >
> > On Wednesday, May 22, 2013, Jesse Gross <jesse at nicira.com> wrote:
> >> On Wed, May 22, 2013 at 6:31 AM, love you <thunder.love07 at gmail.com>
> >> wrote:
> >>> sorry the behavior was observed for non-matching packets, let me
> explain
> >>> again
> >>>
> >>>
> >>> I have following observations regarding the dump-table stats, I think
> the
> >>> actual behavior is incorrect, please confirm.
> >>>
> >>> Table stats should increment the lookup and matched count by one for
> >>> every
> >>> non-matching packet. When we are sending two non-maching packet for a
> >>> flow
> >>> entry, the match count is incremented by three.
> >>>
> >>> For even count of packets, odd number of matched counts are
> incremented.
> >>>
> >>> However as per my understanding the match count for non matching packet
> >>> are
> >>> incremented because of hidden flows of the switch.
> >>>
> >>>
> >>> Steps:-
> >>> 1) Add flow entry with valid ether-type 0x0800 with action forward
> >>> 2) show table statistics
> >>> 3) send two matching packets with ether type as 0x0800 for flow entries
> >>> and
> >>> check statistics
> >>>
> >>> Expected Result:-
> >>> step 2 will show zero packet lookups and zero packet matches
> >>> after step 3, packet lookups will be 2 and packet matches will be 2
> >>>
> >>> Actual Result
> >>> after step 3, packet lookups will be 2 and packet matches will be 3
> >>
> >> ARP?
> >>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20130524/769b2ea5/attachment.html>