Re: [ovs-discuss] OVN /OVS openvswitch: ovs-system: deferred action limit reached, drop recirc action

[Krzysztof Klimonda]

Hi,

Not sure if it's related, but I've seen this bug in ovn 20.12 release, where 
routing loop was related to flows created to handle SNAT, I've sent an RFC 
patch few months back but didn't really have time to follow up on it since then 
to get some feedback: 
https://www.mail-archive.com/ovs-dev@openvswitch.org/msg53195.html
I was planning on re-testing it with 21.06 release and follow up on the patch.

On Mon, Aug 2, 2021, at 21:31, Han Zhou wrote:
> 
> 
> On Mon, Aug 2, 2021 at 5:07 AM Ammad Syed  wrote:
> >
> > Hello, 
> >
> > I am using openstack with OVN 20.12 and OVS 2.15.0 on ubuntu 20.04. I am 
> > using geneve tenant network and vlan provider network. 
> >
> > I am continuously getting below messages in my dmesg logs continuously on 
> > compute node 1 only the other two compute nodes have no such messages. 
> >
> > [275612.826698] openvswitch: ovs-system: deferred action limit reached, 
> > drop recirc action
> > [275683.750343] openvswitch: ovs-system: deferred action limit reached, 
> > drop recirc action
> > [276102.200772] openvswitch: ovs-system: deferred action limit reached, 
> > drop recirc action
> > [276161.575494] openvswitch: ovs-system: deferred action limit reached, 
> > drop recirc action
> > [276210.262524] openvswitch: ovs-system: deferred action limit reached, 
> > drop recirc action
> >
> > I have tried by reinstalling (OS everything) compute node 1 but still 
> > having same errors.
> >
> > Need your advise.
> >
> > --
> > Regards,
> >
> >
> > Syed Ammad Ali
> > ___
> > discuss mailing list
> > disc...@openvswitch.org
> > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
> 
> Hi Syed,
> 
> Could you check if you have routing loops (i.e. a packet being routed 
> back and forth between logical routers infinitely) in your logical 
> topology?
> 
> Thanks,
> Han
> ___
> discuss mailing list
> disc...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
> 


-- 
  Krzysztof Klimonda
  kklimo...@syntaxhighlighted.com
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OVN /OVS openvswitch: ovs-system: deferred action limit reached, drop recirc action

[Han Zhou]

On Mon, Aug 2, 2021 at 5:07 AM Ammad Syed  wrote:
>
> Hello,
>
> I am using openstack with OVN 20.12 and OVS 2.15.0 on ubuntu 20.04. I am
using geneve tenant network and vlan provider network.
>
> I am continuously getting below messages in my dmesg logs continuously on
compute node 1 only the other two compute nodes have no such messages.
>
> [275612.826698] openvswitch: ovs-system: deferred action limit reached,
drop recirc action
> [275683.750343] openvswitch: ovs-system: deferred action limit reached,
drop recirc action
> [276102.200772] openvswitch: ovs-system: deferred action limit reached,
drop recirc action
> [276161.575494] openvswitch: ovs-system: deferred action limit reached,
drop recirc action
> [276210.262524] openvswitch: ovs-system: deferred action limit reached,
drop recirc action
>
> I have tried by reinstalling (OS everything) compute node 1 but still
having same errors.
>
> Need your advise.
>
> --
> Regards,
>
>
> Syed Ammad Ali
> ___
> discuss mailing list
> disc...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Hi Syed,

Could you check if you have routing loops (i.e. a packet being routed back
and forth between logical routers infinitely) in your logical topology?

Thanks,
Han
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OVSDB key, indexes

[Ben Pfaff]

On Mon, Aug 02, 2021 at 02:04:59PM +, Rutuja Umesh Madhure wrote:
> I had a question about key, indexes in ovsdb. Referring to
> RFC7047, the 'type'
> of a column can be a 'key'. What does that exactly mean.

OVSDB supports various kinds of types, including maps from keys to
values.  When a type isn't a map, OVSDB considers it to just contain
keys instead of key-value pairs.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] Query

[Kuntal Gaur]

Hi,

I am a research scholar. I want to know if I can implement VPLS
architecture with SDN in OVS. If yes, please suggest the method in brief.
Kindly help.

Regards
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] OVSDB key, indexes

[Rutuja Umesh Madhure]

Hi,

I had a question about key, indexes in ovsdb. Referring to 
RFC7047, the 'type' of a 
column can be a 'key'. What does that exactly mean. Since, there is 'indexes' 
where the 'column-set' uniquely identifies a row.

It will help if you could explain a bit about the context in which 'key', 
'indexes' are used.


Thanking you,

Regards,
Rutuja Madhure
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] [ovs-dev] meter stats cleared when modify meter bands

[Ilya Maximets]

> I know  that in latest ovs versions, both kernel datapath and dpdk userspace 
> datapath supports meter action.
> what I want to know is why we need to clear stats when modify meter bands? 
> are there any considerations?
> I think it is easily to keep meter stats when only modify meter bands.

Hi.  I looked at the OFPMC_MODIFY definition in the OpenFlow specification
and I see the following for the OpenFlow 1.3 and 1.4:

"For modify requests (OFPMC_MODIFY), if a meter entry with the specified
meter identifier already exists, then that entry, including its bands, must
be removed, and the new meter entry added."

I think, this matches with the current implementation.  So, the meter is
completely removed and the new one added, hence no statistics is preserved.

What you're looking for seems to be defined in the OpenFlow 1.5:

"For modify requests (OFPMC_MODIFY), if a meter entry with the specified
meter identifier already exists, then the configuration of that meter entry,
including its flags and bands, must be removed (cleared), and the meter entry
must use the new configuration included in the request. For that entry, meter
top-level statistics are preserved (continued), meter band statistics are
reset (cleared)."

So, for OpenFlow 1.5 the top-level statistics should be preserved.
However, I don't think that OVS currently implements that.  It looks like
OVS always implements meters as OF13 meters, which is a bug(?).  In order to
support OF15 behavior we'll need to correctly implement it on all levels
starting form the distinguishing the OF version of the particular OFPMC_MODIFY
message and instruct the datapath to behave differently based on that.
The behavior for OF 1.3 and 1.4 should stay as it is now.

Maybe Ben or Jean can correct me if my understanding is not correct here.

Best regards, Ilya Maximets.

> 
> 
> At 2021-07-28 13:46:21, "Tonghao Zhang"  wrote:
>>On Wed, Jul 28, 2021 at 10:57 AM ychen  wrote:
>>>
>>> Hi, all:
>>> I have a question why meter stats need  cleared when just modify meter 
>>> bands?
>>> when call function handle_modify_meter(), it finally call function 
>>> dpif_netdev_meter_set(), in this function new dp_meter will be allocated 
>>> and attched, hence stats will be cleared.
>>>if we just update dp_meter bands configuration, so the stats will be 
>>> keeped when meter modify.
>>>Is there any consideration about this meter modify action?
>>The commit 80738e5f93a70 supports the meter for kernel datapath.
>>and even though kernel modules support to set stats, but userspace
>>doesn't set them.
>>https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=96fbc13d7e770b542d2d1fcf700d0baadc6e8063
>>
>>If needed, we can support this.
>>
>>> ___
>>> dev mailing list
>>> dev at openvswitch.org
>>> https://mail.openvswitch.org/mailman/listinfo/ovs-dev
>>
>>
>>
>>-- 
>>Best regards, Tonghao

___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] OVN /OVS openvswitch: ovs-system: deferred action limit reached, drop recirc action

[Ammad Syed]

Hello,

I am using openstack with OVN 20.12 and OVS 2.15.0 on ubuntu 20.04. I am
using geneve tenant network and vlan provider network.

I am continuously getting below messages in my dmesg logs continuously on
compute node 1 only the other two compute nodes have no such messages.

[275612.826698] openvswitch: ovs-system: deferred action limit reached,
drop recirc action
[275683.750343] openvswitch: ovs-system: deferred action limit reached,
drop recirc action
[276102.200772] openvswitch: ovs-system: deferred action limit reached,
drop recirc action
[276161.575494] openvswitch: ovs-system: deferred action limit reached,
drop recirc action
[276210.262524] openvswitch: ovs-system: deferred action limit reached,
drop recirc action

I have tried by reinstalling (OS everything) compute node 1 but still
having same errors.

Need your advise.

-- 
Regards,


Syed Ammad Ali
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss