Hi Nash,
I'm interested in your case, but I need some information below to
understand your case. We can set up collaboration if needed to solve this.
I'm using OVN mostly for OpenStack.
1. May I know your physical and logical topology?
2. What have you seen with packet capture regarding your hear
Hi,
It seem that you can attach SR-IOV VF of NIC to the VM. You mau use
suitable PMD of NIV for that purpose.
Best regards.
Date: Fri, 18 Nov 2022 08:51:51 +
> From: Rohan Bose
> To: "ovs-discuss@openvswitch.org"
> Subject: [ovs-discuss] OVS-DPDK in Virtual Machine (KVM)
> Message-ID: <810
Hi,
I have problem on using bonded bnxt VF PMDs with OVS-DPDK for OVN. I have
successfully attached both VF PMD to br-int. I have created br-int.vlanid
internal port and give it IP address for GENEVE tunnel address since the
tunnel should use that VLAN ID. Both respective PFs are LACP bonded on
ke
Hi,
I'm deploying OVN with OVS-DPDK. When I'm trying to offload flows by using
rte_flow, I find the following logs appear every second. How to get rid
those offload incompatible flows warning/error logs? How can I safely
select which offload incompatible flow should not be offloaded?
2023-02-06T1
HI David,
Don't you think that offload of reserved Ethernet address should be
disabled by default?
Best regards.
On Mon, Feb 6, 2023 at 10:36 PM David Marchand
wrote:
> Hello,
>
> On Mon, Feb 6, 2023 at 4:16 PM Lazuardi Nasution via discuss
> wrote:
> >
> > Hi,
&
.
On Mon, Feb 6, 2023 at 11:34 PM Ajit Khaparde
wrote:
> On Mon, Feb 6, 2023 at 7:36 AM David Marchand
> wrote:
> >
> > Hello,
> >
> > On Mon, Feb 6, 2023 at 4:16 PM Lazuardi Nasution via discuss
> > wrote:
> > >
> > > Hi,
> > >
&g
Hi David,
I think I can understand your opinion. So your target is to prevent frames
with those ethernet addresses from reaching CP, right? FYI, I'm using
bonded VFs of bonded PFs as OVS-DPDK interfaces, so offcourse LACP should
be handled by bonded PFs only.
Best regards,
On Mon, Feb 6, 2023 at
Hi Ajit,
I'm using the following versions.
dpdk_version: "DPDK 21.11.2"
ovs_version : "3.0.1"
Best regards.
On Tue, Feb 7, 2023 at 12:12 AM Ajit Khaparde
wrote:
> On Mon, Feb 6, 2023 at 9:02 AM Lazuardi Nasution
> wrote:
> >
> > Hi David,
> >
> > I think I can understand your
Hi Ajit,
Have you find the way to overcome this problem? Would you mind to explain
why this reserved Ethernet addresses throw error on offloading the flows
and not just make related flows non-offloaded?
Another think, but not so important is bnxt PMD logs warning about cannot
do flow control on V
Hi Ajit,
I'm using firmware version 219.0.144.0.of
I'm not sure that the problem is about the capability of the firmware. By
digging the source code of bnxt PMD, it seems that this problem is related
to bnxt_validate_and_parse_flow_type() function which throws an error if
the destination Ethernet
Hi Ajit,
Is there any update on this? If it is firmware matter, what is suggested
firmware for enabling flow offload with OVN?
Best regards.
On Thu, Feb 9, 2023, 12:17 PM Lazuardi Nasution
wrote:
> Hi Ajit,
>
> I'm using firmware version 219.0.144.0.of
>
> I'm not sure that the problem is abou
Hi Ajit,
It seem that the flows which are related with broadcast DMAC are appear on
bridges which are connected to PF/VF like below.
admin@controller01:~$ sudo ovs-appctl dpif/dump-flows type=all br-provider
recirc_id(0),in_port(7),packet_type(ns=0,id=0),eth(src=84:16:0c:f0:47:2b,dst=01:80:c2:00:
Any progress about this case?
By the way, is it possible to filter reserved broadcast addresses from
being seen by such VF? I'm thinking about something like the following
rule, but I know that rule will never work.
ethtool -N ens4f0np0 flow-type ether dst 01:80:c2:00:00:00 m
ff:ff:ff:ff:ff:00 vf
Hi Michael,
Have you found the solution for this case? I find the same weird problem
without any information about which conntrack entries are causing
this issue.
I'm using OVS 3.0.1 with DPDK 21.11.2 on Ubuntu 22.04. By the way, this
problem is disappear after I remove some Kubernutes cluster V
Hi,
Is this related to following glibc bug? I'm not so sure about this because
when I check the glibc source of installed version (2.35), the proposed
patch has been applied.
https://sourceware.org/bugzilla/show_bug.cgi?id=12889
I can confirm that this problem only happen if I use statefull ACL
Hi,
Any update with this issue? This issue happens with OVS 3.0.1 and DPDK
21.11.3 too.
Best regards,
> Date: Mon, 23 Jan 2023 15:45:37 +0800 (CST)
> From: ?? <13813836...@163.com>
> To: b...@openvswitch.org
> Subject: [ovs-discuss] ovs-dpdk crash
> Message-ID: <6cb12966.2f9.185dd96f9a5.coremai
Hi Michael,
Is your patch working on the same subnet unreachable traffic too. In my
case, crashes happen when too many unreachable replies even from the same
subnet. For example, when one of the etcd instances is down, there will be
huge reconnection attempts and then unreachable replies from the
Hi Michael,
I assume that your k8s cluster is on the same subnet, right? Would you mind
testing it by shutting down one of etcd instances and see if this bug still
exists?
Best regards.
On Tue, Apr 4, 2023 at 2:50 PM Plato, Michael
wrote:
> Hi,
>
> from my perspective the patch works for all c
Hi Paolo,
Would you mind to explain this to me? Currently, I'm still looking for
compiling options of installed OVS-DPDK from Ubuntu repo. After that, I'll
try your patch and compile it with same options.
Best regards.
On Wed, Apr 5, 2023, 2:51 AM Paolo Valerio wrote:
> Hello,
>
> thanks for r
Hi Michael,
Great, know that. I will try on my cluster too. Btw, do you know how to
find compiling options of OVS-DPDK package from Ubuntu repo?
Best regards.
On Wed, Apr 5, 2023, 1:56 PM Plato, Michael
wrote:
> Hi,
>
>
>
> yes our k8s cluster is on the same subnet. I stopped one of the etcd n
Hi Paolo,
I'm interested in your statement of "expired connections (but not yet
reclaimed)". Do you think that shortening conntrack timeout policy will
help? Or, should we make it larger so there will be fewer conntrack table
update and flush attempts?
Best regards.
On Wed, Apr 5, 2023 at 2:51 A
Hi Paolo,
Should we combine this patch too?
https://patchwork.ozlabs.org/project/openvswitch/patch/168192964823.4031872.3228556334798413886.st...@fed.void/
Best regards.
On Wed, Apr 5, 2023 at 2:51 AM Paolo Valerio wrote:
> Hello,
>
> thanks for reporting this.
> I had a look at it, and, alth
Hi Paolo, Hi Michael,
I want to confirm that following patch is working on openvswitch 3.0.3 and
the OVS crash is not happen after patching.
https://patchwork.ozlabs.org/project/openvswitch/patch/168192964823.4031872.3228556334798413886.st...@fed.void/
But currently, I find some logs like follow
Hi,
Continuing my posting on "ovs-vswitchd crashes several times a day", it
seems that I find some racing conditions on the conntrack update. Without
enabling debugging logs, I find logs like the following frequently.
2023-05-25T12:48:07.270Z|02757|conntrack(pmd-c47/id:101)|WARN|Unable to NAT
due
Hi,
I have followed ASAP2 Direct documentation for Kernel OVS. I can confirm
that VXLAN encapsulation offload is working properly. But, decapsulation is
not with following flow offloading error. The servers are using
MCX654105A-HCAT with latest firmware and OFED version. I need to know why
those f
25 matches
Mail list logo
