[ovs-discuss] OVS-DPDK - packets received at dpdk interface but not forwarded to VXLAN port

Avi Cohen (A) avi.cohen at huawei.com
Wed Jun 7 10:27:12 UTC 2017


Sugesh
Dpctl dump-dps - show nothing - I think this make sense because we are in user-space only
Ofctl dump-flows - show 1 NORMAL entry for both bridges
Bset Regards
avi

-----Original Message-----
From: Chandran, Sugesh [mailto:sugesh.chandran at intel.com] 
Sent: Wednesday, 07 June, 2017 11:59 AM
To: Avi Cohen (A); ovs-discuss at openvswitch.org
Subject: RE: [ovs-discuss] OVS-DPDK - packets received at dpdk interface but not forwarded to VXLAN port



Regards
_Sugesh


> -----Original Message-----
> From: Avi Cohen (A) [mailto:avi.cohen at huawei.com]
> Sent: Wednesday, June 7, 2017 9:26 AM
> To: Chandran, Sugesh <sugesh.chandran at intel.com>; ovs- 
> discuss at openvswitch.org
> Subject: RE: [ovs-discuss] OVS-DPDK - packets received at dpdk 
> interface but not forwarded to VXLAN port
> 
> Thank you Sugesh
> The problem is not an  arp/route  issue.
> The problem is that Packets received in the peer dpdk  not forwarded 
> to the vxlan port for decap.
> When I tried to investigate it - I saw that in ovs-dpdk setup the 
> outer header received at the peer dpdk interface is - for some reason 
> including vlan  2047, (on the other hand in native ovs setup the outer 
> eth header is untagged) I think that the packet is dropped there - 
> although I don't see any drops in
> dpdk0 statistics.
[Sugesh] Bit strange to me, I haven't seen anything as such in my setup.
Just wondering what is your ofproto and datapath flows looks like?
> 
> Output of vsctl show:
> 
> utilities/ovs-vsctl show
> 8cdae740-9eb3-4b79-ad6f-bca0652c5d54
>     Bridge br-int
>         fail_mode: standalone
>         Port "vxlan0"
>             Interface "vxlan0"
>                 type: vxlan
>                 options: {remote_ip="172.31.100.80"}
>         Port "veth0"
>             Interface "veth0"
>         Port br-int
>             Interface br-int
>                 type: internal
>     Bridge br-phy
>         fail_mode: standalone
>         Port "dpdk0"
>             Interface "dpdk0"
>                 type: dpdk
>                 options: {dpdk-devargs="0000:00:03.0"}
>         Port br-phy
>             Interface br-phy
>                 type: internal
> 
> 
> 
> > -----Original Message-----
> > From: Chandran, Sugesh [mailto:sugesh.chandran at intel.com]
> > Sent: Wednesday, 07 June, 2017 11:06 AM
> > To: Avi Cohen (A); ovs-discuss at openvswitch.org
> > Subject: RE: [ovs-discuss] OVS-DPDK - packets received at dpdk 
> > interface but not forwarded to VXLAN port
> >
> >
> >
> > Regards
> > _Sugesh
> >
> >
> > > -----Original Message-----
> > > From: ovs-discuss-bounces at openvswitch.org [mailto:ovs-discuss- 
> > > bounces at openvswitch.org] On Behalf Of Avi Cohen (A)
> > > Sent: Wednesday, June 7, 2017 7:42 AM
> > > To: ovs-discuss at openvswitch.org
> > > Subject: [ovs-discuss] OVS-DPDK - packets received at dpdk 
> > > interface but not forwarded to VXLAN port
> > >
> > >
> > >
> > > When I  work with native OVS (no DPDK)  - the traffic is OK.
> > > I see that with native OVS - I have NO VLAN in the outer Ethernet 
> > > header
> .
> > [Sugesh] I didn't understand the issue exactly..Is your traffic not 
> > forwarding at all Or Is it have wrong vlan tag.?
> > If its issue with the traffic forwarding, it must be something to do 
> > with arp/route.
> > Can you please have a look at datapath rules , arp and route entries 
> > in
> ovs.??
> > You can refer the following document for debug commands
> >
> > http://docs.openvswitch.org/en/latest/howto/userspace-
> > tunneling/?highlight=tunneling
> >
> >
> >
> > > in OVS-DPDK - for some reason -   I do have VLAN 2047 - see below ###
> > >
> > > > -----Original Message-----
> > > > From: Avi Cohen (A)
> > > > Sent: Tuesday, 06 June, 2017 1:58 PM
> > > > To: 'dpdk-ovs at lists.01.org'; 'users at dpdk.org'
> > > > Subject: OVS-DPDK - packets received at dpdk interface but not 
> > > > forwarded to VXLAN port
> > > >
> > > > Hello All (I resend because the prev msg was sent as html)
> > > >
> > > > I have 2  OVS-DPDK installed  - with the following below 
> > > > symmetric
> > > > configuration: see ***
> > > >
> > > > When I send ping from a namespace (connected to the ovs-dpdk) - 
> > > > I see that the packet is received at the peer  via the dpdk 
> > > > interface
> > > > - BUT not sent to the vxlan port
> > > >
> > > > See  ###  the tcpdump of the packet (captured at the br-phy  in 
> > > > the
> > > > peer) - the packet  looks  OK but  not sent to vxlan port  for decap.
> > > >
> > > > [note that in the TX direction - the behavior is OK - packet 
> > > > sent from namespace to veth0 then to vxlan encap, then to dpdk 
> > > > interface
> > > > --> eventually the packet is received at the dpdk peer 
> > > > --> interface]
> > > >
> > > > Can someone see any problem with my configuration ?
> > > >
> > > > Best Regards
> > > > avi
> > > >
> > > > ***
> > > > utilities/ovs-vsctl show
> > > > 8cdae740-9eb3-4b79-ad6f-bca0652c5d54
> > > >     Bridge br-int
> > > >         fail_mode: standalone
> > > >         Port "vxlan0"
> > > >             Interface "vxlan0"
> > > >                 type: vxlan
> > > >                 options: {remote_ip="172.31.100.80"}                // the peer has
> > other
> > > > ip
> > > >         Port "veth0"
> > > >             Interface "veth0"
> > > >         Port br-int
> > > >             Interface br-int
> > > >                 type: internal
> > > >     Bridge br-phy
> > > >         fail_mode: standalone
> > > >         Port "dpdk0"
> > > >             Interface "dpdk0"
> > > >                 type: dpdk
> > > >                 options: {dpdk-devargs="0000:00:03.0"}
> > > >         Port br-phy
> > > >             Interface br-phy
> > > >                 type: internal
> > > >
> > > > ###
> > > > 10:27:15.201711 02:d7:d1:26:84:e5 (oui Unknown) > 
> > > > 02:fb:9e:ce:f2:0d (oui Unknown), ethertype 802.1Q (0x8100), 
> > > > length
> > > > 152: vlan 2047, p 0, ethertype IPv4,
> > > > ip-172-31-100-80.eu-central-1.compute.internal.58740 >
> > > > ip-172-31-100-
> > > > 44.eu-central-1.compute.internal.4789: VXLAN, flags [I] (0x08), 
> > > > vni
> > > > 0
> > > > 7a:fd:3c:4c:ee:d3 (oui Unknown) > d2:ea:96:e1:ef:d2 (oui 
> > > > Unknown), ethertype
> > > > IPv4 (0x0800), length 98: 1.1.1.20 > 1.1.1.10: ICMP echo 
> > > > request, id 2235, seq 1176, length 64
> > >
> > > _______________________________________________
> > > discuss mailing list
> > > discuss at openvswitch.org
> > > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss


More information about the discuss mailing list