Thank you for support!
Yes, really the kernel module was still 1.9.2 version. After upgrade of it
the problem eliminated itself.
On 3 February 2014 19:48, Jesse Gross wrote:
> On Mon, Feb 3, 2014 at 5:36 AM, Anton Matsiuk
> wrote:
> > Dear all,
> >
> > I install La
and? (I couldn't find IT
neither in man page nor in examples)
--
Best regards,
Anton Matsiuk
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
Thank you for response!
The problem was with MTU on Lo iface, after increasing it the TCP window
increased up to the limit specified by socket on controller's side and
packet drops stopped.
On 4 December 2013 19:16, Ben Pfaff wrote:
> On Wed, Nov 27, 2013 at 04:59:02PM +0100, Anton
generate Packet_In messages not to all of them without logging
it?
On 25 November 2013 19:08, Ben Pfaff wrote:
> On Mon, Nov 25, 2013 at 03:15:07PM +0100, Anton Matsiuk wrote:
> > as Open vSwitch stores only 256 Packet_Ins in buffer
> (OFPT_FEATURES_REPLY:
> > n_buffers = 256)
o set buffer_id = -1 for all packets) using OpenFlow 1.0? (In
OpenFlow 1.2+ it should be possible by setting OFPCML_NO_BUFFER as I
understood).
Is it possible to vary the size of buffer for Packet_In in Open vSwitch?
--
Best regards,
Anton Matsiuk
On 22 November 2013 18:52, Ben Pfaff wrote:
> On
3 16:44, Ben Pfaff wrote:
> Does the controller get any error replies from Open vSwitch?
> What's in the ovs-vswitchd log? (Not in debug mode, that's too big.)
>
> On Fri, Nov 22, 2013 at 04:15:20PM +0100, Anton Matsiuk wrote:
> > Dear Ben,
> >
> > I
Is there possibility to track drops in internal buffers of OVS or somehow
to debug it?
Or, probably, does OVS drop packets after expired timeout for Packet_In
residing in buffer? And what is the default value for such timeout if any?
--
Best regards,
Anton Matsiuk
On 21 November 2013 17:56, B
UPD:
Sorry, I forget to add dump from user space that shows that part of packets
are missed:
sudo ovs-ofctl dump-aggregate br0
NXST_AGGREGATE reply (xid=0x4): packet_count=380 byte_count=20736
flow_count=500
On 18 November 2013 15:52, Anton Matsiuk wrote:
> Hello all,
>
> I test
t I experienced the same drops. It seems like OVS starts dropping
packets after some threshold (or buffer overload).
Is there any possibility to debug these drops and maybe to manipulate
ingress buffer sizes (or queue priorities) in order to avoid such drops?
--
Best regards,
Anton Mats
UPD: Cancel current request, the request will be rewritten
On 19 November 2013 11:08, Anton Matsiuk wrote:
> UPD:
>
> Sorry, I forget to add dump from user space that shows that part of
> packets are missed:
> sudo ovs-ofctl dump-aggregate br0
> NXST_AGGREGATE reply (xid=
ere drops are occurred? is there possibility to debug internal
queues or buffers?
And how could I fix such drops? Should I implement some advances QoS
policies in OVS in this case?
--
Best regards,
Anton Matsiuk
___
discuss mailing list
disc
11 matches
Mail list logo
