On Mon, Apr 15, 2013 at 04:31:39PM +0530, love you wrote:
> It has been observed that the flow limit in multiple tables is not getting
> set in multiple tables at the same time.
>
>
>
> *Command used to set the flow limit*:
>
> ovs-vsctl -- --id=@t0 create Flow_Table name=main flow-limit=10 --
> --id=@t1 create Flow_Table flow-limit=5 overflow-policy=refuse -- set
> bridge br0 flow_tables={1=@t1,0=@t0}
Did you read the documentation? Here is an important excerpt:
Curly braces may optionally enclose non-empty maps as well (but
use quotes to prevent the shell from expanding
other-config={0=x,1=y} into other-config=0=x other-config=1=y,
which may not have the desired effect).
> It has been observed that the When flow limit is set on one table, it
> resets the flow limit of the other table to its default value.
>
>
>
> *Command used to set the flow limit on table 1: *
>
> ovs-vsctl -- --id=@t1 create Flow_Table flow-limit=10
> overflow-policy=refuse -- set bridge br0 flow_tables={1=@t1}
You set flow_tables to one value...
>
>
> *Command used to set the flow limit on table 2: *
>
> ovs-vsctl -- --id=@t2 create Flow_Table flow-limit=10
> overflow-policy=refuse -- set bridge br0 flow_tables={2=@t2}
...and then you set it to a different value, so of course this
overwrote the first one.
> It has been observed that the when flow entries exceed the flow limit it
> gives the error OFPFMFC_ALL_TABLES_FULL without the overflow_policy option.
>
> Even when the overflow_policy option is set as refuse or evict, it gives
> the same error.
> Is it a bug or the functionality is yet not implemented .
>
> Can you please explain the difference between the overflow_policy options *
> refuse* and *evict*
It's well-documented. Did you read the documentation?
Do your flows have timeouts? Flows without timeouts are not evicted.
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
