Hey everyone,
I have a simple question about the time OVS takes to detect link failure if i don't explicitly enable BFD on interfaces? It seems that port down message is immediately generated, while link failure detection is taking some additional time. What is the exact time after which the link
> On Jul 25, 2016, at 9:52 AM, Chiappero, Marco
> wrote:
>
> Hello everyone,
>
> I’m currently carrying out RFC2544 based tests on a server running hundreds
> of applications which forward back a matching number of traffic flows
> generated by a HW traffic generator. These applications are
Hello Mauricio,
On Sun, Jul 24, 2016 at 12:17 PM, Mauricio Vasquez
wrote:
> Hi Sothy,
>
>
> On 07/21/2016 11:55 AM, sothy shan wrote:
>>
>> On Thu, Jul 21, 2016 at 11:43 AM, Mauricio Vasquez
>> wrote:
>>>
>>>
>>> On 07/21/2016 10:51 AM, sothy shan wrote:
On Thu, Jul 21, 2016 at 10:41 A
I've just checked the logs and i didn't see nothing weird.
I thing that maybe I've not added queues in the qos.
When I check with ovs-vsctl list queue appears this:
mininet@mininet-vm:~$ sudo ovs-vsctl list queue
_uuid : 5dcd4bc4-4706-4e30-86b1-dc2c2a13f499
dscp:
That looks OK to me. You might check your OVS logs for related
warnings.
On Mon, Jul 25, 2016 at 07:06:42PM +, álvaro wrote:
>
> Yes I did, with this command:
>
> ovs-vsctl -- set Port s1-eth1 qos=@newqos --
>
> --id=@newqos create QoS type=linux-htb other-config:max-rate=10
> que
Thanks Cascardo,
I am on 2.4.0.
I delved into the source code, and it seems that it is because the querier
sets its IPv4 source address to 0.0.0.0. I understand that this is in
accordance with the RFC 4541 (Section 2.1.1.1 - 1(b)), so I guess this is
indeed the correct behavior.
Would you know w
Yes I did, with this command:
ovs-vsctl -- set Port s1-eth1 qos=@newqos --
--id=@newqos create QoS type=linux-htb other-config:max-rate=10
queues=0=@q0 --
--id=@q0 create Queue other-config:min-rate=400
other-config:max-rate=400
and when I check with:
sudo ovs-vsctl list qu
On Mon, Jul 25, 2016 at 10:17:19AM +, álvaro wrote:
> Hi, I'm trying to get the queue stats of the network, I make a request to the
> controller and use the QueueStatsReceived with a handler, but when I print
> the stats nothing appears(even saturating switch ports), with the FlowStats
> and
Hi all, from the FAQ section i read that OVS from the version 2.0 supports
OpenFlow meters but it hasn’t an implementation. What does it exactly means?
Maybe i can use meters but they have no effect on the QoS?
Thank you,
Roberto
___
discuss mailing l
Hmm, there's no change in this area since 2.4. Can you give an example
of an OpenFlow message that provokes the error? A hexdump or pcap of
the message would be ideal.
On Mon, Jul 25, 2016 at 12:19:43PM +0530, Aswin S wrote:
> Hi Ben
>
> The below extension were used.
>
> #define NXM_OF_TCP_SR
Hello everyone,
I'm currently carrying out RFC2544 based tests on a server running hundreds
of applications which forward back a matching number of traffic flows
generated by a HW traffic generator. These applications are running in Linux
containers, bridged altogether by a single OvS bridge in
Hi, I'm trying to get the queue stats of the network, I make a request to the
controller and use the QueueStatsReceived with a handler, but when I print the
stats nothing appears(even saturating switch ports), with the FlowStats and
PortStats works normally.
Anyone knows why always appear "[]"
12 matches
Mail list logo