Re: [ovs-discuss] ovs-dpdk crash when use vhost-user in docker

Hi, This issue was resolved. The cause is i miss a parameter --file-prefix when run l2fwd Thanks Billy and Ciara 张广明 于2018年8月21日周二 下午4:59写道： > Hi, Ciara and Billy > > Thanks for your reply > > The default huge page size that i used is 1GB . > root@localhost openvswitch]# cat

Re: [ovs-discuss] [ovs-dev] fix the mod_vlan_vid actions with OpenFlow13.

Hi Eric and all, Thanks for Eric's advice very much. But in my opinion, this issue reported from wangyunjian is something about feature's compatibility. Using the rule: ovs-ofctl -O OpenFlow13 add-flow ovsbr0 " table=0,priority=2,in_port=1 actions=mod_vlan_vid:3,NORMAL", the action

Re: [ovs-discuss] OVS Faucet tutorial broken

Hi Ben, On 21 August 2018 at 04:41, Ben Pfaff wrote: > > Since the tutorial recommends ovs-sandbox, ports will always be down due > to > > the use of the netdev-dummy datapath which skips the linux network stack. > > This is fine though as we can use "ovs-appctl > netdev-dummy/set-admin-state >

Re: [ovs-discuss] [ovs-dev] RX Mirroing issue with Decap in vxlan case

Ah. In that case, probably I'm not the right person to handle this. Simon, does this make sense to you? On Tue, Aug 21, 2018 at 08:17:23PM +, Limaye, Namrata wrote: > I haven’t tested it with openvswitch kernel and code that is issue is in tc.c > so I am guessing it is only hw offload. >

Re: [ovs-discuss] [ovs-dev] RX Mirroing issue with Decap in vxlan case

I haven’t tested it with openvswitch kernel and code that is issue is in tc.c so I am guessing it is only hw offload. Thanks Namrata > On Aug 21, 2018, at 12:37 PM, Ben Pfaff wrote: > > Is this problem only for hardware offload? > >> On Tue, Aug 21, 2018 at 06:26:03PM +, Limaye, Namrata

Re: [ovs-discuss] [ovs-dev] RX Mirroing issue with Decap in vxlan case

Is this problem only for hardware offload? On Tue, Aug 21, 2018 at 06:26:03PM +, Limaye, Namrata wrote: > Sorry missed the release part - > > Release action is added first in this function before any other action is > processed which is used in decap case in our solution. > >

Re: [ovs-discuss] OVS 2.10 geneve errors

It does not seem to be because of duplicate IPs. With duplicate IP, we get EEXIST. Port "ovn-55491a-0" Interface "ovn-55491a-0" type: geneve options: {csum="true", key=flow, remote_ip="10.100.0.42"} error: "could not add network

Re: [ovs-discuss] OVS 2.10 geneve errors

On 8/21/2018 11:27 AM, Ben Pfaff wrote: On Tue, Aug 21, 2018 at 11:15:31AM -0700, Gregory Rose wrote: On 8/21/2018 7:38 AM, William Tu wrote: On Mon, Aug 20, 2018 at 9:30 PM Manoj Sharma wrote: It may be because of duplicate chassis IPs (same IP address used for more than one chassis). Is

Re: [ovs-discuss] OVS 2.10 geneve errors

On Tue, Aug 21, 2018 at 11:15:31AM -0700, Gregory Rose wrote: > On 8/21/2018 7:38 AM, William Tu wrote: > >On Mon, Aug 20, 2018 at 9:30 PM Manoj Sharma > >wrote: > >>It may be because of duplicate chassis IPs (same IP address used for more > >>than one chassis). > >> > >Is this the case? I saw

Re: [ovs-discuss] [ovs-dev] RX Mirroing issue with Decap in vxlan case

Sorry missed the release part - Release action is added first in this function before any other action is processed which is used in decap case in our solution. 'nl_msg_put_flower_acts' if (flower->tunnel.tunnel) { act_offset = nl_msg_start_nested(request, act_index++);

Re: [ovs-discuss] [ovs-dev] RX Mirroing issue with Decap in vxlan case

Hi Ben, This is the configuration - ovs-vsctl -- --id=@p get port vxlan0 -- --id=@eth0.128 get Port eth0.128 -- --id=@eth0.129 get Port eth0.129 -- --id=@m create Mirror name=mirror1 select-src-port=@eth0.128,@p output-port=@eth0.129 -- set Bridge br0 mirrors=@m Thanks Namrata -Original

Re: [ovs-discuss] OVS 2.10 geneve errors

On 8/21/2018 7:38 AM, William Tu wrote: On Mon, Aug 20, 2018 at 9:30 PM Manoj Sharma wrote: It may be because of duplicate chassis IPs (same IP address used for more than one chassis). Is this the case? I saw Guru is using different remote_ip --William I'm looking into it today. Thanks,

Re: [ovs-discuss] [ovs-dev] RX Mirroing issue with Decap in vxlan case

On Fri, Aug 17, 2018 at 06:55:39PM +, Limaye, Namrata wrote: > > Hi, > > I am facing an issue with Decap in RX Mirroring case (select_src_port) for > Vxlan. With the following config – > > ovs-vsctl -- --id=@p get port vxlan0 -- --id=@eth0.128 > get Port eth0.128 --

Re: [ovs-discuss] Tunnel packets from unknown VTEPs

On Tue, Aug 21, 2018 at 03:45:34PM +, Paul Greenberg wrote: > Currently, when a VXLAN packet comes to a host, but the source ip > (chassis) of the packet is not in OVN SB database, packets are being > dropped prior to getting to openvswitch. > > How to make the packets reach the switch? It

[ovs-discuss] Tunnel packets from unknown VTEPs

All, Currently, when a VXLAN packet comes to a host, but the source ip (chassis) of the packet is not in OVN SB database, packets are being dropped prior to getting to openvswitch. How to make the packets reach the switch? Best Regards, Paul Greenberg

Re: [ovs-discuss] OVS 2.10 geneve errors

On Mon, Aug 20, 2018 at 9:30 PM Manoj Sharma wrote: > > It may be because of duplicate chassis IPs (same IP address used for more > than one chassis). > Is this the case? I saw Guru is using different remote_ip --William > > > Thanks. > > > > From: on behalf of Guru Shetty > > Date:

Re: [ovs-discuss] [ovs-dev] fix the mod_vlan_vid actions with OpenFlow13.

On Tue, Aug 21, 2018 at 02:23:33AM +, wangyunjian wrote: > > > > -Original Message- > > From: Eric Garver [mailto:e...@erig.me] > > Sent: Monday, August 20, 2018 9:15 PM > > To: wangyunjian > > Cc: d...@openvswitch.org; ovs-discuss@openvswitch.org; Zhoulei (stone, > > Cloud

Re: [ovs-discuss] ovs-dpdk crash when use vhost-user in docker

Hi, Ciara and Billy Thanks for your reply The default huge page size that i used is 1GB . root@localhost openvswitch]# cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.10.0-514.el7.x86_64 root=/dev/mapper/centos-root ro crashkernel=auto iommu=pt intel_iommu=on default_hugepagesz=1G hugepagesz=1G

Re: [ovs-discuss] ovs-dpdk crash when use vhost-user in docker

Hi, One thing to look out for with DPDK < 18.05 is that you need to used 1GB huge pages (and no more than eight of them) to use virtio. I’m not sure if that is the issue you have as I think it I don’t remember it causing a seg fault. But is certainly worth checking. If that does not work