Thanks Ben,
here is my ovs-dpctl -s show
you can see that port 4 (eth1) is the culprit. The dropped packets are there...
root@arm:~# ovs-dpctl -s show
system@ovs-system:
lookups: hit:637519 missed:1110 lost:0
flows: 10
port 0: ovs-system (internal)
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 aborted:0 carrier:0
collisions:0
RX bytes:0 TX bytes:0
port 1: br0 (internal)
RX packets:269207 errors:0 dropped:0 overruns:0 frame:0
TX packets:185580 errors:0 dropped:0 aborted:0 carrier:0
collisions:0
RX bytes:158410366 (151.1 MiB) TX bytes:17196078 (16.4 MiB)
port 2: eth0
RX packets:368290 errors:0 dropped:0 overruns:0 frame:0
TX packets:269281 errors:0 dropped:0 aborted:0 carrier:0
collisions:0
RX bytes:202222289 (192.9 MiB) TX bytes:158421663 (151.1 MiB)
port 3: bra (internal)
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:106 errors:0 dropped:0 aborted:0 carrier:0
collisions:0
RX bytes:468 TX bytes:19399 (18.9 KiB)
port 4: eth1
RX packets:1160 errors:0 dropped:12 overruns:0 frame:0
TX packets:62956 errors:0 dropped:34299 aborted:0 carrier:0
collisions:0
RX bytes:220953 (215.8 KiB) TX bytes:2651472 (2.5 MiB)
sam
> Date: Fri, 19 Sep 2014 08:33:27 -0700
> From: b...@nicira.com
> To: sam.anda...@hotmail.com
> CC: discuss@openvswitch.org; d...@openvswitch.org
> Subject: Re: [ovs-dev] debugging OVS
>
> Can you show us the "ovs-dpctl show" output?
>
> Thanks,
>
> Ben.
>
> On Fri, Sep 19, 2014 at 11:30:05AM -0400, samantha Andares wrote:
> > hi ben,
> >
> > thanks for your feedback.
> >
> > I am getting 100% packets drop.. If problem was with the amount of
> > messages... I presume some would have been going through... as stated in my
> > latest email.... this is specific to when going out on a USB to Ethernet
> > adaptor on a specific hardware (beagle bone board). I am using OVS 2.0 and
> > Ubuntu 14.04. How can we analyse the messages in userspace and why would
> > the message go to userspace... shouldn't it stay in kernel space if it
> > matches a flow and just be forwarded to the outgoing physical port as per
> > the rule is saying? My traffic is simple iperf udp messages.. tried flow of
> > 10MB and 100KB... problem is the same...
> >
> > thanks,
> >
> > sam
> >
> > > Date: Fri, 19 Sep 2014 08:20:24 -0700
> > > From: b...@nicira.com
> > > To: sam.anda...@hotmail.com
> > > CC: discuss@openvswitch.org; d...@openvswitch.org
> > > Subject: Re: [ovs-dev] debugging OVS
> > >
> > > [dropping mininet-discuss because it is a closed mailing list and I am
> > > not a subscriber]
> > >
> > > On Thu, Sep 18, 2014 at 05:37:43PM -0400, samantha Andares wrote:
> > > > I am getting packets dropped when going out of an OVS bridge. The TX
> > > > dropped is increased in ovs-dpctl but not at the physical interface
> > > > level (ifconfig).
> > > >
> > > > Can anyone tell me how to enable some OVS debugging so I can find the
> > > > reason to fix that problem?
> > >
> > > Do you mean that ovs-dpctl shows the datapath's "drop" count is going
> > > up? If so, the problem is that packets that need attention from
> > > userspace are arriving faster than userspace can process them. The best
> > > way to reduce drops is to upgrade to the latest version of Open vSwitch,
> > > which is 2.3, because we've spent a lot of time the last few years
> > > coming up with ways to reduce the number of packets that have to be sent
> > > to userspace. If you are already using 2.3, then I am surprised that
> > > you are seeing lots of drops. Is there anything unusual about your
> > > environment or the traffic that you are using?
> >
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
