Re: [ovs-discuss] High CPU usage due to L3/4 flows

2012-12-07 Thread Brad Hedlund
Hi Bernhard, Out of curiosity, have you tried using the *ovs-controller*? http://openvswitch.org/cgi-bin/ovsman.cgi?page=utilities%2Fovs-controller.8 Cheers, Brad On Wed, Dec 5, 2012 at 5:22 PM, Bernhard Schmidt wrote: > Hi, > > I think this is a FAQ, but I seem to be blind enough to miss an

Re: [ovs-discuss] Controller reference as name

2012-12-07 Thread Ben Pfaff
The manpage for ovs-vsctl says: set-controller bridge target... Sets the configured controller target or targets. Each target may use any of the following forms: The manpage for cp says: cp [OPTION]... SOURCE... DIRECTORY If you know how to use cp, t

Re: [ovs-discuss] Controller reference as name

2012-12-07 Thread Wanderson Paim
Hi Ben and Justin, Thanks for the reply. Yes I have a set of controllers IPs, which would take control in case of primary controller failure. Maybe setting more than one would fit. How could I do it, I tried separating with comma like "ovs-vsctl set-controller br0 tcp:xxx.xxx.xxx.xxx:6633,tcp:yyy.

Re: [ovs-discuss] Controller reference as name

2012-12-07 Thread Justin Pettit
We don't currently allow setting the controller based on name mostly due to in-band control rules. We effectively would need to whitelist all DNS traffic when a switch is connected in-band, which means controller writers wouldn't be able to write DNS flows (at least to the configured DNS server

Re: [ovs-discuss] Controller reference as name

2012-12-07 Thread Ben Pfaff
On Fri, Dec 07, 2012 at 03:06:52PM -0200, Wanderson Paim wrote: > I'm trying a loadbalancer implementation with DNS and I need to set the > controller of the vswitch as a domain name instead of its IP address. > > Example: > ovs-vsctl set-controller br0 tcp:controllerx:6633 > > Such "controllerx"

[ovs-discuss] Controller reference as name

2012-12-07 Thread Wanderson Paim
Hi, I'm trying a loadbalancer implementation with DNS and I need to set the controller of the vswitch as a domain name instead of its IP address. Example: ovs-vsctl set-controller br0 tcp:controllerx:6633 Such "controllerx" has the appropriate IP reference of the controller at the DNS Server. I

Re: [ovs-discuss] OVS ip address specification and flow size

2012-12-07 Thread Ben Pfaff
On Sat, Dec 08, 2012 at 12:52:45AM +0800, Hong Wayne wrote: > Thanks for your useful suggestions. > > ''the total number of bytes in the packets that the flow has processed.'' > > So, It means one of the packet size(Unit for Bytes) during the flow > processed or all of the packets size? The sum

Re: [ovs-discuss] OVS ip address specification and flow size

2012-12-07 Thread Ben Pfaff
On Fri, Dec 07, 2012 at 10:35:10PM +0800, Hong Wayne wrote: > In OVS, the flow entry's field ''n_bytes'', it means the flow size per sec? n_bytes is the total number of bytes in the packets that the flow has processed. > And when the packet destination value is ''broadcast''. What's the field > v

[ovs-discuss] OVS ip address specification and flow size

2012-12-07 Thread Hong Wayne
Dear all: In OVS, the flow entry's field ''n_bytes'', it means the flow size per sec? And when the packet destination value is ''broadcast''. What's the field value for OVS be specified? Can anyone resolve my problems? Thanks. Wayne. ___ discuss mai

[ovs-discuss] Simples doubts

2012-12-07 Thread Rafael Gomes
Good morning, I have a simples questions about openflow, because i'm a little confuse... When we have a network with OpenFlow protocol worked with openvswitch and floodlight controller. My question is about, what happens when arrive a packets a switch. The switch look for your flow table and