$ sudo ovs-appctl -t ovn-controller version
ovn-controller (Open vSwitch) 2.5.90
$ sudo ovs-appctl -t ovn-controller ct−zone−list
"ct−zone−list" is not a valid command
ovs-appctl: ovn-controller: server returned an error
-- flaviof
___
discuss mailing
On Sun, Jul 17, 2016 at 10:00 PM, Flaviof wrote:
> Hi folks,
>
> This could be that I'm configuring something wrong, but I consistently get
> my test VM setup
> spinning at 100% CPU utilization after doing the following config:
>
>3 VM: db, compute1, compute2
>2 ls, each with 1 lsp, 1 lr
I am trying to implement fast failover with OVS:
my configuration :
> sh ovs-ofctl -O OpenFlow13 add-group s1
group_id=4,type=ff,bucket=watch_port:1,output:1,bucket=watch_port:2,output:2,bucket=watch_port:3,output:3
>sh ovs-ofctl -O OpenFlow13 add-flow s1 in_port=4,actions=group:4
Then i tried
Thank you very much for the explanation !!
That’s exactly the answer I was looking for :-)
> On Jul 17, 2016, at 11:34 PM, Ben Pfaff wrote:
>
> On Sun, Jul 17, 2016 at 11:07:17PM +0100, D3c3 Balus wrote:
>> I’d like to understand the difference between these 2 actions:
>> actions=set_field:1.1
On Sun, Jul 17, 2016 at 11:07:17PM +0100, D3c3 Balus wrote:
> I’d like to understand the difference between these 2 actions:
> actions=set_field:1.1.1.1->nw_dstvs. actions=mod_nw_dst:1.1.1.1 ?
> In my understanding, the end result is the same, but what would be different ?
>
> Yes, I have
Hello,
I’d like to understand the difference between these 2 actions:
actions=set_field:1.1.1.1->nw_dstvs. actions=mod_nw_dst:1.1.1.1 ?
In my understanding, the end result is the same, but what would be different ?
Yes, I have read about the differences between set_field:value and load:va
