Re: [ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest
Hi I am trying to decode the core dump, however, I am not familiar with the command to run the debug, can you please provide the steps? the linux version is CentOS7 (3.10.0-514.el7.x86_64), and we currently try to run the OVS+DPDK as a VMware guest. the expected topology would be connect another two nodes with this OVS+DPDK vm. On Wed, Sep 27, 2017 at 5:13 AM, Darrell Ball <db...@vmware.com> wrote: > > > On 9/25/17, 11:18 PM, "Sun Paul" <paul...@gmail.com> wrote: > > hi > > I am trying to use the vmxnet3 (:03:00.0) as the dpdk0 interface. > > # ./dpdk-devbind.py --status > > Network devices using DPDK-compatible driver > > :03:00.0 'VMXNET3 Ethernet Controller 07b0' drv=igb_uio unused= > > Network devices using kernel driver > === > :02:01.0 '82545EM Gigabit Ethernet Controller (Copper) 100f' > if=ens33 drv=e1000 unused=igb_uio *Active* > > Other Network devices > = > :0b:00.0 'VMXNET3 Ethernet Controller 07b0' unused=igb_uio > > > so, when I try to execute "ovs-vsctl add-port g1 dpdk0 -- set > Interface dpdk0 type=dpdk options:dpdk-devargs=:03:00.0" > > I got core dump as below. > > [Darrell] > Pls decode your core dump (btw: probably you will get this request on some of > the other threads you created) > What version of rhel is this ? > Can you describe your environment and your setup steps? > > > Sep 27 11:28:50 dlocalhost ovs-vsctl: ovs|1|vsctl|INFO|Called as > ovs-vsctl del-port g1 dpdk0 > Sep 27 11:28:50 dlocalhost ovs-vsctl: ovs|2|db_ctl_base|ERR|no > port named dpdk0 > Sep 27 11:28:51 dlocalhost ovs-vswitchd[2858]: > ovs|00071|memory|INFO|20076 kB peak resident set size after 10.3 > seconds > Sep 27 11:28:51 dlocalhost ovs-vswitchd: > 2017-09-27T03:28:51Z|00071|memory|INFO|20076 kB peak resident set size > after 10.3 seconds > Sep 27 11:28:51 dlocalhost ovs-vswitchd: > 2017-09-27T03:28:51Z|00072|memory|INFO|handlers:2 ports:1 > revalidators:2 rules:5 > Sep 27 11:28:51 dlocalhost ovs-vswitchd[2858]: > ovs|00072|memory|INFO|handlers:2 ports:1 revalidators:2 rules:5 > Sep 27 11:29:10 dlocalhost ovs-vsctl: ovs|1|vsctl|INFO|Called as > ovs-vsctl add-port g1 dpdk0 -- set Interface dpdk0 type=dpdk > options:dpdk-devargs=:03:00.0 > Sep 27 11:29:10 dlocalhost ovs-vswitchd[2858]: > ovs|00073|dpif_netdev|INFO|PMD thread on numa_id: 0, core id: 0 > created. > Sep 27 11:29:10 dlocalhost ovs-vswitchd: > 2017-09-27T03:29:10Z|00073|dpif_netdev|INFO|PMD thread on numa_id: 0, > core id: 0 created. > Sep 27 11:29:10 dlocalhost ovs-vswitchd: > 2017-09-27T03:29:10Z|00074|dpif_netdev|INFO|There are 1 pmd threads on > numa node 0 > Sep 27 11:29:10 dlocalhost ovs-vswitchd[2858]: > ovs|00074|dpif_netdev|INFO|There are 1 pmd threads on numa node 0 > Sep 27 11:29:10 dlocalhost ovs-vswitchd[2858]: > ovs|00075|netdev_dpdk|WARN|Rx checksum offload is not supported on > port 0 > Sep 27 11:29:10 dlocalhost ovs-vswitchd: > 2017-09-27T03:29:10Z|00075|netdev_dpdk|WARN|Rx checksum offload is not > supported on port 0 > Sep 27 11:29:10 dlocalhost ovs-vswitchd: > 2017-09-27T03:29:10Z|00076|netdev_dpdk|ERR|Interface dpdk0 MTU (1500) > setup error: Operation not supported > Sep 27 11:29:10 dlocalhost ovs-vswitchd: > 2017-09-27T03:29:10Z|00077|netdev_dpdk|ERR|Interface dpdk0(rxq:1 > txq:2) configure error: Operation not supported > Sep 27 11:29:10 dlocalhost ovs-vswitchd[2858]: > ovs|00076|netdev_dpdk|ERR|Interface dpdk0 MTU (1500) setup error: > Operation not supported > Sep 27 11:29:10 dlocalhost ovs-vswitchd[2858]: > ovs|00077|netdev_dpdk|ERR|Interface dpdk0(rxq:1 txq:2) configure > error: Operation not supported > Sep 27 11:29:10 dlocalhost kernel: pmd12[2885]: segfault at 64 ip > 0067fa98 sp 7f588d7f9680 error 4 in > ovs-vswitchd[40+566000] > Sep 27 11:29:10 dlocalhost abrt-hook-ccpp: Process 2858 (ovs-vswitchd) > of user 0 killed by SIGSEGV - dumping core > Sep 27 11:29:10 dlocalhost abrt-hook-ccpp: Failed to create > core_backtrace: waitpid failed: No child processes > Sep 27 11:29:10 dlocalhost systemd: ovs-vswitchd.service: main process > exited, code=killed, status=11/SEGV > Sep 27 11:29:10 dlocalhost systemd: Unit ovs-vswitchd.service entered > failed state. > Sep 27 11:29:10 dlocalhost systemd: ovs-vswitchd.service failed. > Sep 27 11:29:11 dlocalhost abrt-se
Re: [ovs-discuss] How to create mirror packet over GRE on OVS+DPDK
Hi
I tried to create one more bridge on the host, and it seems GRE packet
can be propagated, but I am not able to capture the packet on the g1
bridge. I believed I gave issue on the command to create the tunnel,
any idea?
# ovs-vsctl show
9fe3ef4d-7f29-4a21-80ea-62a705f5d934
Bridge "mirror0"
Port "eth1"
Interface "eth1"
Port "mirror0"
Interface "mirror0"
type: internal
Bridge "g1"
Port "g1"
Interface "g1"
type: internal
Port "dpdk0"
Interface "dpdk0"
type: dpdk
options: {dpdk-devargs=":00:09.0"}
# ovs-vsctl add-port mirror0 gre0 -- set interface gre0 type=gre
options:remote_ip=192.1.2.243 -- --id=@p get port dpdk0 -- --id=@m
create mirror name=m0 select-all=true output-port=@p -- set bridge
mirror0 mirrors=@m
On Mon, Sep 25, 2017 at 3:43 PM, Guoshuai Li <l...@dtdream.com> wrote:
> I have not tested the GRE tunnel, I used geneve Tunnel, I think they are
> similar.
>
> I mean that the tunnel encap ip uses the ovs bridge.
>
> What is your tunnel source ip? Your source IP should be configured on an
> ovs bridge, the physical out of this bridge uses dpdk
>
> You can refer to
> http://docs.openvswitch.org/en/latest/howto/userspace-tunneling/?highlight=tunnel
>
> On host1, add a port for the VXLAN tunnel:
>
> $ ovs-vsctl add-port br-int vxlan0 \
> -- set interface vxlan0 type=vxlan options:remote_ip=172.168.1.2
>
> Note
>
> 172.168.1.2 is the remote tunnel end point address. On the remote host this
> will be 172.168.1.1
>
> Create a br-phy bridge:
>
> $ ovs-vsctl --may-exist add-br br-phy \
> -- set Bridge br-phy datapath_type=netdev \
> -- br-set-external-id br-phy bridge-id br-phy \
> -- set bridge br-phy fail-mode=standalone \
> other_config:hwaddr=
>
>
> I am not sure whether the source ip using physical network with kernel will
> be a problem.
>
>
> sorry to overlook.
>
> from your configuration, you have two bridges, one is with dpdk, and
> the other is not which is on management subnet, right?
>
> can you share the GRE tunnel command for reference?
>
> On Mon, Sep 25, 2017 at 3:22 PM, Sun Paul <paul...@gmail.com> wrote:
>
> do you mean I need to bridge the management interface to bridge as well?
>
> On Mon, Sep 25, 2017 at 2:14 PM, Guoshuai Li <l...@dtdream.com> wrote:
>
> You can catch packets on your management interface.
>
>
> I guess your package sent to the userspace from vm by dpdk , and then
> through the tunnel to return to the kernel.
>
> I do not know if this will be a problem.
>
>
> I suggest you can try your management interface using OVS bridge with dpdk,
> such as "g1".
>
>
> This is my configuration:
>
> 7: br-agg: <BROADCAST,PROMISC,UP,LOWER_UP> mtu 1600 qdisc pfifo_fast state
> UP qlen 1000
> link/ether 6c:92:bf:04:f9:18 brd ff:ff:ff:ff:ff:ff
> inet 10.157.145.213/24 brd 10.157.145.255 scope global br-agg
>valid_lft forever preferred_lft forever
> inet6 fe80::6e92:bfff:fe04:f918/64 scope link
>valid_lft forever preferred_lft forever
>
> [root@gateway1 ~]# ovs-vsctl show
> b99b043b-951b-4bc7-9fd7-329d60d443a5
> Bridge br-agg
> Port bond-agg
> Interface "agg-dpdk-2"
> type: dpdk
> options: {dpdk-devargs=":02:00.1"}
> Interface "agg-dpdk-1"
> type: dpdk
> options: {dpdk-devargs=":02:00.0"}
> Bridge br-int
> Port "ovn-d172cc-0"
> Interface "ovn-d172cc-0"
> type: geneve
> options: {csum="true", key=flow, remote_ip="10.157.145.212"}
> Port br-int
> Interface br-int
> type: internal
> Port "ovn-d131e4-0"
> Interface "ovn-d131e4-0"
> type: geneve
> options: {csum="true", key=flow, remote_ip="10.157.145.214"}
> Port "ovn-844fcd-0"
> Interface "ovn-844fcd-0"
> type: geneve
> options: {csum="true", key=flow, remote_ip="10.157.145.211"}
>
>
>
>
>
> Hi
>
> thank for your reply.
>
> the 192.1.2.159 is actually on the same subnet of the management
> interface, it is not part of the OVS bridge.
>
>
>
> On Mon, Sep 25, 2017 at 1:37 PM, Guoshuai Li <l...@dtdream.com&
Re: [ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest
hi I am trying to use the vmxnet3 (:03:00.0) as the dpdk0 interface. # ./dpdk-devbind.py --status Network devices using DPDK-compatible driver :03:00.0 'VMXNET3 Ethernet Controller 07b0' drv=igb_uio unused= Network devices using kernel driver === :02:01.0 '82545EM Gigabit Ethernet Controller (Copper) 100f' if=ens33 drv=e1000 unused=igb_uio *Active* Other Network devices = :0b:00.0 'VMXNET3 Ethernet Controller 07b0' unused=igb_uio so, when I try to execute "ovs-vsctl add-port g1 dpdk0 -- set Interface dpdk0 type=dpdk options:dpdk-devargs=:03:00.0" I got core dump as below. Sep 27 11:28:50 dlocalhost ovs-vsctl: ovs|1|vsctl|INFO|Called as ovs-vsctl del-port g1 dpdk0 Sep 27 11:28:50 dlocalhost ovs-vsctl: ovs|2|db_ctl_base|ERR|no port named dpdk0 Sep 27 11:28:51 dlocalhost ovs-vswitchd[2858]: ovs|00071|memory|INFO|20076 kB peak resident set size after 10.3 seconds Sep 27 11:28:51 dlocalhost ovs-vswitchd: 2017-09-27T03:28:51Z|00071|memory|INFO|20076 kB peak resident set size after 10.3 seconds Sep 27 11:28:51 dlocalhost ovs-vswitchd: 2017-09-27T03:28:51Z|00072|memory|INFO|handlers:2 ports:1 revalidators:2 rules:5 Sep 27 11:28:51 dlocalhost ovs-vswitchd[2858]: ovs|00072|memory|INFO|handlers:2 ports:1 revalidators:2 rules:5 Sep 27 11:29:10 dlocalhost ovs-vsctl: ovs|1|vsctl|INFO|Called as ovs-vsctl add-port g1 dpdk0 -- set Interface dpdk0 type=dpdk options:dpdk-devargs=:03:00.0 Sep 27 11:29:10 dlocalhost ovs-vswitchd[2858]: ovs|00073|dpif_netdev|INFO|PMD thread on numa_id: 0, core id: 0 created. Sep 27 11:29:10 dlocalhost ovs-vswitchd: 2017-09-27T03:29:10Z|00073|dpif_netdev|INFO|PMD thread on numa_id: 0, core id: 0 created. Sep 27 11:29:10 dlocalhost ovs-vswitchd: 2017-09-27T03:29:10Z|00074|dpif_netdev|INFO|There are 1 pmd threads on numa node 0 Sep 27 11:29:10 dlocalhost ovs-vswitchd[2858]: ovs|00074|dpif_netdev|INFO|There are 1 pmd threads on numa node 0 Sep 27 11:29:10 dlocalhost ovs-vswitchd[2858]: ovs|00075|netdev_dpdk|WARN|Rx checksum offload is not supported on port 0 Sep 27 11:29:10 dlocalhost ovs-vswitchd: 2017-09-27T03:29:10Z|00075|netdev_dpdk|WARN|Rx checksum offload is not supported on port 0 Sep 27 11:29:10 dlocalhost ovs-vswitchd: 2017-09-27T03:29:10Z|00076|netdev_dpdk|ERR|Interface dpdk0 MTU (1500) setup error: Operation not supported Sep 27 11:29:10 dlocalhost ovs-vswitchd: 2017-09-27T03:29:10Z|00077|netdev_dpdk|ERR|Interface dpdk0(rxq:1 txq:2) configure error: Operation not supported Sep 27 11:29:10 dlocalhost ovs-vswitchd[2858]: ovs|00076|netdev_dpdk|ERR|Interface dpdk0 MTU (1500) setup error: Operation not supported Sep 27 11:29:10 dlocalhost ovs-vswitchd[2858]: ovs|00077|netdev_dpdk|ERR|Interface dpdk0(rxq:1 txq:2) configure error: Operation not supported Sep 27 11:29:10 dlocalhost kernel: pmd12[2885]: segfault at 64 ip 0067fa98 sp 7f588d7f9680 error 4 in ovs-vswitchd[40+566000] Sep 27 11:29:10 dlocalhost abrt-hook-ccpp: Process 2858 (ovs-vswitchd) of user 0 killed by SIGSEGV - dumping core Sep 27 11:29:10 dlocalhost abrt-hook-ccpp: Failed to create core_backtrace: waitpid failed: No child processes Sep 27 11:29:10 dlocalhost systemd: ovs-vswitchd.service: main process exited, code=killed, status=11/SEGV Sep 27 11:29:10 dlocalhost systemd: Unit ovs-vswitchd.service entered failed state. Sep 27 11:29:10 dlocalhost systemd: ovs-vswitchd.service failed. Sep 27 11:29:11 dlocalhost abrt-server: Executable '/usr/local/sbin/ovs-vswitchd' doesn't belong to any package and ProcessUnpackaged is set to 'no' Sep 27 11:29:11 dlocalhost abrt-server: 'post-create' on '/var/spool/abrt/ccpp-2017-09-27-11:29:10-2858' exited with 1 Sep 27 11:29:11 dlocalhost abrt-server: Deleting problem directory '/var/spool/abrt/ccpp-2017-09-27-11:29:10-2858' On Tue, Sep 26, 2017 at 1:09 PM, Darrell Ball <db...@vmware.com> wrote: > > > On 9/25/17, 9:26 PM, "Sun Paul" <paul...@gmail.com> wrote: > > we are evauluating the DPDK on VMXNET3 , is sit supported in the VMware > guest? > > I see what you are doing now; I think it should be supported. > What driver are you using to bind the “vmxnet3 nic” ? > Probably you should provide all the steps you are using and your environment. > > > > On Tue, Sep 26, 2017 at 12:09 PM, Darrell Ball <db...@vmware.com> wrote: > > Do you have a hard requirement to use vmxnet3 ? > > What are you requirements otherwise ? > > > > > > On 9/25/17, 9:06 PM, "ovs-discuss-boun...@openvswitch.org on behalf of > Darrell Ball" <ovs-discuss-boun...@openvswitch.org on behalf of > db...@vmware.com> wrote: > > > > > > > > On 9/25/17, 8:31 PM, "Sun Paul" <paul...@gmail.com> wrote: > > > > Hi >
Re: [ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest
it looks like something we need to do http://dpdk.org/doc/vmxnet3-usermap On Tue, Sep 26, 2017 at 12:26 PM, Sun Paul <paul...@gmail.com> wrote: > we are evauluating the DPDK on VMXNET3 , is sit supported in the VMware guest? > > On Tue, Sep 26, 2017 at 12:09 PM, Darrell Ball <db...@vmware.com> wrote: >> Do you have a hard requirement to use vmxnet3 ? >> What are you requirements otherwise ? >> >> >> On 9/25/17, 9:06 PM, "ovs-discuss-boun...@openvswitch.org on behalf of >> Darrell Ball" <ovs-discuss-boun...@openvswitch.org on behalf of >> db...@vmware.com> wrote: >> >> >> >> On 9/25/17, 8:31 PM, "Sun Paul" <paul...@gmail.com> wrote: >> >> Hi >> >> thank for the reply. but can you explain what I should do? >> >> >> Do you have a hard requirement to use ESXi and vmxnet3 ? >> What are you requirements otherwise ? >> >> >> >> On Tue, Sep 26, 2017 at 3:18 AM, Darrell Ball <db...@vmware.com> >> wrote: >> > >> > >> > On 9/25/17, 2:53 AM, "ovs-discuss-boun...@openvswitch.org on >> behalf of Sun Paul" <ovs-discuss-boun...@openvswitch.org on behalf of >> paul...@gmail.com> wrote: >> > >> > Hi >> > >> > I am trying to have a OVS+DPDK setup on a VM guest in Vmware >> > environment. the network adapter type for the dpdk is vmxnet3. >> > >> > The present support for guest connectivity for OVS-DPDK is here: >> > >> https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.openvswitch.org_en_latest_topics_dpdk_vhost-2Duser_=DwIFaQ=uilaK90D4TOVoH58JNXRgQ=BVhFA09CGX7JQ5Ih-uZnsw=U9YEU77bZamqSg208ehS8-3M4sgEVZoZE9yILybkOuU=6iVy8pqpuoo_1QAliEi37GLAiW2wEkUl5UGZMf7l5WA= >> > >> > >> > when I am trying to add-port on it, it failed. any idea? >> > >> > Sep 26 17:51:57 plocalhost ovs-vswitchd: >> > 2017-09-26T09:51:57Z|00058|netdev_dpdk|ERR|Interface dpdk0 MTU >> (1500) >> > setup error: Operation not supported >> > Sep 26 17:51:57 plocalhost ovs-vswitchd: >> > 2017-09-26T09:51:57Z|00059|netdev_dpdk|ERR|Interface >> dpdk0(rxq:1 >> > txq:2) configure error: Operation not supported >> > >> > >> > >> > the full log is shown below. >> > >> > Sep 26 17:51:26 plocalhost ovs-vswitchd: >> > 2017-09-26T09:51:26Z|00051|ofproto_dpif|INFO|netdev@ovs-netdev: >> > Datapath supports ct_orig_tuple6 >> > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: >> > ovs|00039|ofproto_dpif|INFO|netdev@ovs-netdev: MPLS label >> stack length >> > probed as 3 >> > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: >> > ovs|00040|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath >> supports >> > truncate action >> > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: >> > ovs|00041|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath >> supports >> > unique flow ids >> > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: >> > ovs|00042|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath >> supports clone >> > action >> > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: >> > ovs|00043|ofproto_dpif|INFO|netdev@ovs-netdev: Max sample >> nesting >> > level probed as 10 >> > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: >> > ovs|00044|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath >> supports >> > eventmask in conntrack action >> > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: >> > ovs|00045|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath >> supports >> > ct_state >> > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: >> > ovs|00046|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath >> supports >> > ct_zone >> > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: >> > ovs|00047|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath >> supports >> > ct_mark >>
Re: [ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest
we are evauluating the DPDK on VMXNET3 , is sit supported in the VMware guest? On Tue, Sep 26, 2017 at 12:09 PM, Darrell Ball <db...@vmware.com> wrote: > Do you have a hard requirement to use vmxnet3 ? > What are you requirements otherwise ? > > > On 9/25/17, 9:06 PM, "ovs-discuss-boun...@openvswitch.org on behalf of > Darrell Ball" <ovs-discuss-boun...@openvswitch.org on behalf of > db...@vmware.com> wrote: > > > > On 9/25/17, 8:31 PM, "Sun Paul" <paul...@gmail.com> wrote: > > Hi > > thank for the reply. but can you explain what I should do? > > > Do you have a hard requirement to use ESXi and vmxnet3 ? > What are you requirements otherwise ? > > > > On Tue, Sep 26, 2017 at 3:18 AM, Darrell Ball <db...@vmware.com> > wrote: > > > > > > On 9/25/17, 2:53 AM, "ovs-discuss-boun...@openvswitch.org on behalf > of Sun Paul" <ovs-discuss-boun...@openvswitch.org on behalf of > paul...@gmail.com> wrote: > > > > Hi > > > > I am trying to have a OVS+DPDK setup on a VM guest in Vmware > > environment. the network adapter type for the dpdk is vmxnet3. > > > > The present support for guest connectivity for OVS-DPDK is here: > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.openvswitch.org_en_latest_topics_dpdk_vhost-2Duser_=DwIFaQ=uilaK90D4TOVoH58JNXRgQ=BVhFA09CGX7JQ5Ih-uZnsw=U9YEU77bZamqSg208ehS8-3M4sgEVZoZE9yILybkOuU=6iVy8pqpuoo_1QAliEi37GLAiW2wEkUl5UGZMf7l5WA= > > > > > > when I am trying to add-port on it, it failed. any idea? > > > > Sep 26 17:51:57 plocalhost ovs-vswitchd: > > 2017-09-26T09:51:57Z|00058|netdev_dpdk|ERR|Interface dpdk0 MTU > (1500) > > setup error: Operation not supported > > Sep 26 17:51:57 plocalhost ovs-vswitchd: > > 2017-09-26T09:51:57Z|00059|netdev_dpdk|ERR|Interface dpdk0(rxq:1 > > txq:2) configure error: Operation not supported > > > > > > > > the full log is shown below. > > > > Sep 26 17:51:26 plocalhost ovs-vswitchd: > > 2017-09-26T09:51:26Z|00051|ofproto_dpif|INFO|netdev@ovs-netdev: > > Datapath supports ct_orig_tuple6 > > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > > ovs|00039|ofproto_dpif|INFO|netdev@ovs-netdev: MPLS label stack > length > > probed as 3 > > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > > ovs|00040|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > > truncate action > > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > > ovs|00041|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > > unique flow ids > > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > > ovs|00042|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath > supports clone > > action > > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > > ovs|00043|ofproto_dpif|INFO|netdev@ovs-netdev: Max sample > nesting > > level probed as 10 > > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > > ovs|00044|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > > eventmask in conntrack action > > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > > ovs|00045|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > > ct_state > > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > > ovs|00046|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > > ct_zone > > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > > ovs|00047|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > > ct_mark > > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > > ovs|00048|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > > ct_label > > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > > ovs|00049|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > > ct_state_nat > > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > > ovs|00050|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > > ct_orig_tuple > > S
Re: [ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest
Hi thank for the reply. but can you explain what I should do? On Tue, Sep 26, 2017 at 3:18 AM, Darrell Ball <db...@vmware.com> wrote: > > > On 9/25/17, 2:53 AM, "ovs-discuss-boun...@openvswitch.org on behalf of Sun > Paul" <ovs-discuss-boun...@openvswitch.org on behalf of paul...@gmail.com> > wrote: > > Hi > > I am trying to have a OVS+DPDK setup on a VM guest in Vmware > environment. the network adapter type for the dpdk is vmxnet3. > > The present support for guest connectivity for OVS-DPDK is here: > http://docs.openvswitch.org/en/latest/topics/dpdk/vhost-user/ > > > when I am trying to add-port on it, it failed. any idea? > > Sep 26 17:51:57 plocalhost ovs-vswitchd: > 2017-09-26T09:51:57Z|00058|netdev_dpdk|ERR|Interface dpdk0 MTU (1500) > setup error: Operation not supported > Sep 26 17:51:57 plocalhost ovs-vswitchd: > 2017-09-26T09:51:57Z|00059|netdev_dpdk|ERR|Interface dpdk0(rxq:1 > txq:2) configure error: Operation not supported > > > > the full log is shown below. > > Sep 26 17:51:26 plocalhost ovs-vswitchd: > 2017-09-26T09:51:26Z|00051|ofproto_dpif|INFO|netdev@ovs-netdev: > Datapath supports ct_orig_tuple6 > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > ovs|00039|ofproto_dpif|INFO|netdev@ovs-netdev: MPLS label stack length > probed as 3 > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > ovs|00040|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > truncate action > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > ovs|00041|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > unique flow ids > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > ovs|00042|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports clone > action > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > ovs|00043|ofproto_dpif|INFO|netdev@ovs-netdev: Max sample nesting > level probed as 10 > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > ovs|00044|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > eventmask in conntrack action > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > ovs|00045|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > ct_state > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > ovs|00046|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > ct_zone > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > ovs|00047|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > ct_mark > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > ovs|00048|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > ct_label > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > ovs|00049|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > ct_state_nat > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > ovs|00050|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > ct_orig_tuple > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > ovs|00051|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports > ct_orig_tuple6 > Sep 26 17:51:26 plocalhost ovs-vswitchd: > 2017-09-26T09:51:26Z|00052|bridge|INFO|bridge c1: added interface c1 > on port 65534 > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > ovs|00052|bridge|INFO|bridge c1: added interface c1 on port 65534 > Sep 26 17:51:26 plocalhost kernel: device c1 entered promiscuous mode > Sep 26 17:51:26 plocalhost ovs-vswitchd: > 2017-09-26T09:51:26Z|00053|bridge|INFO|bridge c1: using datapath ID > 76ff8ff75d4e > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > ovs|00053|bridge|INFO|bridge c1: using datapath ID 76ff8ff75d4e > Sep 26 17:51:26 plocalhost ovs-vswitchd: > 2017-09-26T09:51:26Z|00054|connmgr|INFO|c1: added service controller > "punix:/usr/local/var/run/openvswitch/c1.mgmt" > Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: > ovs|00054|connmgr|INFO|c1: added service controller > "punix:/usr/local/var/run/openvswitch/c1.mgmt" > Sep 26 17:51:57 plocalhost ovs-vsctl: ovs|1|vsctl|INFO|Called as > ovs-vsctl add-port c1 dpdk0 -- set Interface dpdk0 type=dpdk > options:dpdk-devargs=:03:00.0 > Sep 26 17:51:57 plocalhost ovs-vswitchd: > 2017-09-26T09:51:57Z|00055|dpif_netdev|INFO|PMD thread on numa_id: 0, > core id: 0 created. > Sep 26 17:51:57 plocalhost ovs-vswitchd[2624]: > ovs|00055|dpif_netdev|INFO|PMD thread on numa_id: 0, core id: 0 > created. > Sep 26 17:51:57 plocalhost ovs-vswitchd: > 2017-09-26T09:51:57Z|00056|dpif_netdev|INFO|There are 1 pmd threads on > numa node 0 > Sep 26 17:51
[ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest
Hi I am trying to have a OVS+DPDK setup on a VM guest in Vmware environment. the network adapter type for the dpdk is vmxnet3. when I am trying to add-port on it, it failed. any idea? Sep 26 17:51:57 plocalhost ovs-vswitchd: 2017-09-26T09:51:57Z|00058|netdev_dpdk|ERR|Interface dpdk0 MTU (1500) setup error: Operation not supported Sep 26 17:51:57 plocalhost ovs-vswitchd: 2017-09-26T09:51:57Z|00059|netdev_dpdk|ERR|Interface dpdk0(rxq:1 txq:2) configure error: Operation not supported the full log is shown below. Sep 26 17:51:26 plocalhost ovs-vswitchd: 2017-09-26T09:51:26Z|00051|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_orig_tuple6 Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: ovs|00039|ofproto_dpif|INFO|netdev@ovs-netdev: MPLS label stack length probed as 3 Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: ovs|00040|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports truncate action Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: ovs|00041|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports unique flow ids Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: ovs|00042|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports clone action Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: ovs|00043|ofproto_dpif|INFO|netdev@ovs-netdev: Max sample nesting level probed as 10 Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: ovs|00044|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports eventmask in conntrack action Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: ovs|00045|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_state Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: ovs|00046|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_zone Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: ovs|00047|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_mark Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: ovs|00048|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_label Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: ovs|00049|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_state_nat Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: ovs|00050|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_orig_tuple Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: ovs|00051|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_orig_tuple6 Sep 26 17:51:26 plocalhost ovs-vswitchd: 2017-09-26T09:51:26Z|00052|bridge|INFO|bridge c1: added interface c1 on port 65534 Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: ovs|00052|bridge|INFO|bridge c1: added interface c1 on port 65534 Sep 26 17:51:26 plocalhost kernel: device c1 entered promiscuous mode Sep 26 17:51:26 plocalhost ovs-vswitchd: 2017-09-26T09:51:26Z|00053|bridge|INFO|bridge c1: using datapath ID 76ff8ff75d4e Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: ovs|00053|bridge|INFO|bridge c1: using datapath ID 76ff8ff75d4e Sep 26 17:51:26 plocalhost ovs-vswitchd: 2017-09-26T09:51:26Z|00054|connmgr|INFO|c1: added service controller "punix:/usr/local/var/run/openvswitch/c1.mgmt" Sep 26 17:51:26 plocalhost ovs-vswitchd[2624]: ovs|00054|connmgr|INFO|c1: added service controller "punix:/usr/local/var/run/openvswitch/c1.mgmt" Sep 26 17:51:57 plocalhost ovs-vsctl: ovs|1|vsctl|INFO|Called as ovs-vsctl add-port c1 dpdk0 -- set Interface dpdk0 type=dpdk options:dpdk-devargs=:03:00.0 Sep 26 17:51:57 plocalhost ovs-vswitchd: 2017-09-26T09:51:57Z|00055|dpif_netdev|INFO|PMD thread on numa_id: 0, core id: 0 created. Sep 26 17:51:57 plocalhost ovs-vswitchd[2624]: ovs|00055|dpif_netdev|INFO|PMD thread on numa_id: 0, core id: 0 created. Sep 26 17:51:57 plocalhost ovs-vswitchd: 2017-09-26T09:51:57Z|00056|dpif_netdev|INFO|There are 1 pmd threads on numa node 0 Sep 26 17:51:57 plocalhost ovs-vswitchd[2624]: ovs|00056|dpif_netdev|INFO|There are 1 pmd threads on numa node 0 Sep 26 17:51:57 plocalhost ovs-vswitchd[2624]: ovs|00057|netdev_dpdk|WARN|Rx checksum offload is not supported on port 0 Sep 26 17:51:57 plocalhost ovs-vswitchd: 2017-09-26T09:51:57Z|00057|netdev_dpdk|WARN|Rx checksum offload is not supported on port 0 Sep 26 17:51:57 plocalhost ovs-vswitchd: 2017-09-26T09:51:57Z|00058|netdev_dpdk|ERR|Interface dpdk0 MTU (1500) setup error: Operation not supported Sep 26 17:51:57 plocalhost ovs-vswitchd: 2017-09-26T09:51:57Z|00059|netdev_dpdk|ERR|Interface dpdk0(rxq:1 txq:2) configure error: Operation not supported Sep 26 17:51:57 plocalhost ovs-vswitchd: 2017-09-26T09:51:57Z|00060|bridge|INFO|bridge c1: added interface dpdk0 on port 1 Sep 26 17:51:57 plocalhost kernel: pmd12[2671]: segfault at 64 ip 0067fa98 sp 7f68faffc680 error 4 in ovs-vswitchd[40+566000] Sep 26 17:51:57 plocalhost ovs-vswitchd[2624]: ovs|00058|netdev_dpdk|ERR|Interface dpdk0 MTU (1500) setup error: Operation not supported Sep 26 17:51:57 plocalhost ovs-vswitchd[2624]: ovs|00059|netdev_dpdk|ERR|Interface dpdk0(rxq:1 txq:2) configure error: Operation not supported Sep 26 17:51:57 plocalhost ovs-vswitchd[2624]: ovs|00060|bridge|INFO|bridge c1: added
Re: [ovs-discuss] How to create mirror packet over GRE on OVS+DPDK
sorry to overlook.
from your configuration, you have two bridges, one is with dpdk, and
the other is not which is on management subnet, right?
can you share the GRE tunnel command for reference?
On Mon, Sep 25, 2017 at 3:22 PM, Sun Paul <paul...@gmail.com> wrote:
> do you mean I need to bridge the management interface to bridge as well?
>
> On Mon, Sep 25, 2017 at 2:14 PM, Guoshuai Li <l...@dtdream.com> wrote:
>> You can catch packets on your management interface.
>>
>>
>> I guess your package sent to the userspace from vm by dpdk , and then
>> through the tunnel to return to the kernel.
>>
>> I do not know if this will be a problem.
>>
>>
>> I suggest you can try your management interface using OVS bridge with dpdk,
>> such as "g1".
>>
>>
>> This is my configuration:
>>
>> 7: br-agg: <BROADCAST,PROMISC,UP,LOWER_UP> mtu 1600 qdisc pfifo_fast state
>> UP qlen 1000
>> link/ether 6c:92:bf:04:f9:18 brd ff:ff:ff:ff:ff:ff
>> inet 10.157.145.213/24 brd 10.157.145.255 scope global br-agg
>>valid_lft forever preferred_lft forever
>> inet6 fe80::6e92:bfff:fe04:f918/64 scope link
>>valid_lft forever preferred_lft forever
>>
>> [root@gateway1 ~]# ovs-vsctl show
>> b99b043b-951b-4bc7-9fd7-329d60d443a5
>> Bridge br-agg
>> Port bond-agg
>> Interface "agg-dpdk-2"
>> type: dpdk
>> options: {dpdk-devargs=":02:00.1"}
>> Interface "agg-dpdk-1"
>> type: dpdk
>> options: {dpdk-devargs=":02:00.0"}
>> Bridge br-int
>> Port "ovn-d172cc-0"
>> Interface "ovn-d172cc-0"
>> type: geneve
>> options: {csum="true", key=flow, remote_ip="10.157.145.212"}
>> Port br-int
>> Interface br-int
>> type: internal
>> Port "ovn-d131e4-0"
>> Interface "ovn-d131e4-0"
>> type: geneve
>> options: {csum="true", key=flow, remote_ip="10.157.145.214"}
>> Port "ovn-844fcd-0"
>> Interface "ovn-844fcd-0"
>> type: geneve
>> options: {csum="true", key=flow, remote_ip="10.157.145.211"}
>>
>>
>>
>>
>>
>>> Hi
>>>
>>> thank for your reply.
>>>
>>> the 192.1.2.159 is actually on the same subnet of the management
>>> interface, it is not part of the OVS bridge.
>>>
>>>
>>>
>>> On Mon, Sep 25, 2017 at 1:37 PM, Guoshuai Li <l...@dtdream.com> wrote:
>>>>
>>>> I think you may have caught the tunnel inner package.
>>>>
>>>> Is the tunnel outbound from interface dpdk0? how about caught dpdk0 with
>>>> mirror?
>>>>
>>>> Or use dpdk-pdump?
>>>>
>>>>> Hi
>>>>>
>>>>> How do I configure mirroring of all traffic to a GRE tunnel on OVS+DPDK?
>>>>>
>>>>> I have a OVS+DPDK setip as below.
>>>>>
>>>>> # ovs-vsctl show
>>>>> 9fe3ef4d-7f29-4a21-80ea-62a705f5d934
>>>>> Bridge "g1"
>>>>> Port "g1"
>>>>> Interface "g1"
>>>>> type: internal
>>>>> Port "dpdk0"
>>>>> Interface "dpdk0"
>>>>> type: dpdk
>>>>> options: {dpdk-devargs=":00:09.0"}
>>>>>
>>>>> I tried to create gre tunnel for packet mirroring
>>>>>
>>>>> #ovs-vsctl add-port g1 gre0 -- set interface gre0 type=gre
>>>>> options:remote_ip=192.1.2.159 -- --id=@p get port gre0 -- --id=@m
>>>>> create mirror name=m0 select-all=true output-port=@p -- set bridge g1
>>>>> mirrors=@m
>>>>>
>>>>> I cannot find any packet arrive on 192.1.2.159, any idea?
>>>>>
>>>>> I have tried to use the same command in an OVS setup without DPDK
>>>>> enabled, it works.
>>>>>
>>>>> please help
>>>>>
>>>>> - RBK
>>>>>
>>>>>
>>>>> On Mon, Sep 25, 2017 at 1:26 PM, Sun Paul <paul...@gmail.com> wrote:
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>> How do I configure mirroring of all traffic to a GRE tunnel on
>>>>>> OVS+DPDK?
>>>>>>
>>>>>>
>>>>>> I have a OVS+DPDK setip as below.
>>>>>>
>>>>>> # ovs-vsctl show
>>>>>> 9fe3ef4d-7f29-4a21-80ea-62a705f5d934
>>>>>> Bridge "g1"
>>>>>> Port "g1"
>>>>>> Interface "g1"
>>>>>> type: internal
>>>>>> Port "dpdk0"
>>>>>> Interface "dpdk0"
>>>>>> type: dpdk
>>>>>> options: {dpdk-devargs=":00:09.0"}
>>>>>>
>>>>>> I tried to create gre tunnel for packet mirroring
>>>>>
>>>>> ___
>>>>> discuss mailing list
>>>>> disc...@openvswitch.org
>>>>> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>>>>
>>>>
>>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] How to create mirror packet over GRE on OVS+DPDK
do you mean I need to bridge the management interface to bridge as well?
On Mon, Sep 25, 2017 at 2:14 PM, Guoshuai Li <l...@dtdream.com> wrote:
> You can catch packets on your management interface.
>
>
> I guess your package sent to the userspace from vm by dpdk , and then
> through the tunnel to return to the kernel.
>
> I do not know if this will be a problem.
>
>
> I suggest you can try your management interface using OVS bridge with dpdk,
> such as "g1".
>
>
> This is my configuration:
>
> 7: br-agg: <BROADCAST,PROMISC,UP,LOWER_UP> mtu 1600 qdisc pfifo_fast state
> UP qlen 1000
> link/ether 6c:92:bf:04:f9:18 brd ff:ff:ff:ff:ff:ff
> inet 10.157.145.213/24 brd 10.157.145.255 scope global br-agg
>valid_lft forever preferred_lft forever
> inet6 fe80::6e92:bfff:fe04:f918/64 scope link
>valid_lft forever preferred_lft forever
>
> [root@gateway1 ~]# ovs-vsctl show
> b99b043b-951b-4bc7-9fd7-329d60d443a5
> Bridge br-agg
> Port bond-agg
> Interface "agg-dpdk-2"
> type: dpdk
> options: {dpdk-devargs=":02:00.1"}
> Interface "agg-dpdk-1"
> type: dpdk
> options: {dpdk-devargs=":02:00.0"}
> Bridge br-int
> Port "ovn-d172cc-0"
> Interface "ovn-d172cc-0"
> type: geneve
> options: {csum="true", key=flow, remote_ip="10.157.145.212"}
> Port br-int
> Interface br-int
> type: internal
> Port "ovn-d131e4-0"
> Interface "ovn-d131e4-0"
> type: geneve
> options: {csum="true", key=flow, remote_ip="10.157.145.214"}
> Port "ovn-844fcd-0"
> Interface "ovn-844fcd-0"
> type: geneve
> options: {csum="true", key=flow, remote_ip="10.157.145.211"}
>
>
>
>
>
>> Hi
>>
>> thank for your reply.
>>
>> the 192.1.2.159 is actually on the same subnet of the management
>> interface, it is not part of the OVS bridge.
>>
>>
>>
>> On Mon, Sep 25, 2017 at 1:37 PM, Guoshuai Li <l...@dtdream.com> wrote:
>>>
>>> I think you may have caught the tunnel inner package.
>>>
>>> Is the tunnel outbound from interface dpdk0? how about caught dpdk0 with
>>> mirror?
>>>
>>> Or use dpdk-pdump?
>>>
>>>> Hi
>>>>
>>>> How do I configure mirroring of all traffic to a GRE tunnel on OVS+DPDK?
>>>>
>>>> I have a OVS+DPDK setip as below.
>>>>
>>>> # ovs-vsctl show
>>>> 9fe3ef4d-7f29-4a21-80ea-62a705f5d934
>>>> Bridge "g1"
>>>> Port "g1"
>>>> Interface "g1"
>>>> type: internal
>>>> Port "dpdk0"
>>>> Interface "dpdk0"
>>>> type: dpdk
>>>> options: {dpdk-devargs=":00:09.0"}
>>>>
>>>> I tried to create gre tunnel for packet mirroring
>>>>
>>>> #ovs-vsctl add-port g1 gre0 -- set interface gre0 type=gre
>>>> options:remote_ip=192.1.2.159 -- --id=@p get port gre0 -- --id=@m
>>>> create mirror name=m0 select-all=true output-port=@p -- set bridge g1
>>>> mirrors=@m
>>>>
>>>> I cannot find any packet arrive on 192.1.2.159, any idea?
>>>>
>>>> I have tried to use the same command in an OVS setup without DPDK
>>>> enabled, it works.
>>>>
>>>> please help
>>>>
>>>> - RBK
>>>>
>>>>
>>>> On Mon, Sep 25, 2017 at 1:26 PM, Sun Paul <paul...@gmail.com> wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> How do I configure mirroring of all traffic to a GRE tunnel on
>>>>> OVS+DPDK?
>>>>>
>>>>>
>>>>> I have a OVS+DPDK setip as below.
>>>>>
>>>>> # ovs-vsctl show
>>>>> 9fe3ef4d-7f29-4a21-80ea-62a705f5d934
>>>>> Bridge "g1"
>>>>> Port "g1"
>>>>> Interface "g1"
>>>>> type: internal
>>>>> Port "dpdk0"
>>>>> Interface "dpdk0"
>>>>> type: dpdk
>>>>> options: {dpdk-devargs=":00:09.0"}
>>>>>
>>>>> I tried to create gre tunnel for packet mirroring
>>>>
>>>> ___
>>>> discuss mailing list
>>>> disc...@openvswitch.org
>>>> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>>>
>>>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] How to create mirror packet over GRE on OVS+DPDK
Hi
thank for your reply.
the 192.1.2.159 is actually on the same subnet of the management
interface, it is not part of the OVS bridge.
On Mon, Sep 25, 2017 at 1:37 PM, Guoshuai Li <l...@dtdream.com> wrote:
> I think you may have caught the tunnel inner package.
>
> Is the tunnel outbound from interface dpdk0? how about caught dpdk0 with
> mirror?
>
> Or use dpdk-pdump?
>
>> Hi
>>
>> How do I configure mirroring of all traffic to a GRE tunnel on OVS+DPDK?
>>
>> I have a OVS+DPDK setip as below.
>>
>> # ovs-vsctl show
>> 9fe3ef4d-7f29-4a21-80ea-62a705f5d934
>> Bridge "g1"
>> Port "g1"
>> Interface "g1"
>> type: internal
>> Port "dpdk0"
>> Interface "dpdk0"
>> type: dpdk
>> options: {dpdk-devargs=":00:09.0"}
>>
>> I tried to create gre tunnel for packet mirroring
>>
>> #ovs-vsctl add-port g1 gre0 -- set interface gre0 type=gre
>> options:remote_ip=192.1.2.159 -- --id=@p get port gre0 -- --id=@m
>> create mirror name=m0 select-all=true output-port=@p -- set bridge g1
>> mirrors=@m
>>
>> I cannot find any packet arrive on 192.1.2.159, any idea?
>>
>> I have tried to use the same command in an OVS setup without DPDK
>> enabled, it works.
>>
>> please help
>>
>> - RBK
>>
>>
>> On Mon, Sep 25, 2017 at 1:26 PM, Sun Paul <paul...@gmail.com> wrote:
>>>
>>> Hi
>>>
>>> How do I configure mirroring of all traffic to a GRE tunnel on OVS+DPDK?
>>>
>>>
>>> I have a OVS+DPDK setip as below.
>>>
>>> # ovs-vsctl show
>>> 9fe3ef4d-7f29-4a21-80ea-62a705f5d934
>>> Bridge "g1"
>>> Port "g1"
>>> Interface "g1"
>>> type: internal
>>> Port "dpdk0"
>>> Interface "dpdk0"
>>> type: dpdk
>>> options: {dpdk-devargs=":00:09.0"}
>>>
>>> I tried to create gre tunnel for packet mirroring
>>
>> ___
>> discuss mailing list
>> disc...@openvswitch.org
>> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] How to create mirror packet over GRE on OVS+DPDK
Hi
How do I configure mirroring of all traffic to a GRE tunnel on OVS+DPDK?
I have a OVS+DPDK setip as below.
# ovs-vsctl show
9fe3ef4d-7f29-4a21-80ea-62a705f5d934
Bridge "g1"
Port "g1"
Interface "g1"
type: internal
Port "dpdk0"
Interface "dpdk0"
type: dpdk
options: {dpdk-devargs=":00:09.0"}
I tried to create gre tunnel for packet mirroring
#ovs-vsctl add-port g1 gre0 -- set interface gre0 type=gre
options:remote_ip=192.1.2.159 -- --id=@p get port gre0 -- --id=@m
create mirror name=m0 select-all=true output-port=@p -- set bridge g1
mirrors=@m
I cannot find any packet arrive on 192.1.2.159, any idea?
I have tried to use the same command in an OVS setup without DPDK
enabled, it works.
please help
- RBK
On Mon, Sep 25, 2017 at 1:26 PM, Sun Paul <paul...@gmail.com> wrote:
> Hi
>
> How do I configure mirroring of all traffic to a GRE tunnel on OVS+DPDK?
>
>
> I have a OVS+DPDK setip as below.
>
> # ovs-vsctl show
> 9fe3ef4d-7f29-4a21-80ea-62a705f5d934
> Bridge "g1"
> Port "g1"
> Interface "g1"
> type: internal
> Port "dpdk0"
> Interface "dpdk0"
> type: dpdk
> options: {dpdk-devargs=":00:09.0"}
>
> I tried to create gre tunnel for packet mirroring
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] How to create mirror packet over GRE on OVS+DPDK
Hi
How do I configure mirroring of all traffic to a GRE tunnel on OVS+DPDK?
I have a OVS+DPDK setip as below.
# ovs-vsctl show
9fe3ef4d-7f29-4a21-80ea-62a705f5d934
Bridge "g1"
Port "g1"
Interface "g1"
type: internal
Port "dpdk0"
Interface "dpdk0"
type: dpdk
options: {dpdk-devargs=":00:09.0"}
I tried to create gre tunnel for packet mirroring
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] Cannot dump packet capture using dpdk-pdump
Hi I am trying to configured dpdk-pdump to dump the packet in the OVS bridge, however, I am failed. no packet is capture on ingress or egress, any idea? the command I used is ./dpdk-pdump -- --pdump port=1,queue=*,rx-dev=/tmp/pkts_rx.pcap,tx-dev=/tmp/pkts_tx.pcap --server-socket-path=/usr/local/var/run/openvswitch the output on the screen is shown below. EAL: Detected 24 lcore(s) EAL: Probing VFIO support... EAL: WARNING: Address Space Layout Randomization (ASLR) is enabled in the kernel. EAL:This may cause issues with mapping memory into secondary processes EAL: PCI device :04:00.0 on NUMA socket 0 EAL: probe driver: 8086:150e net_e1000_igb EAL: PCI device :04:00.1 on NUMA socket 0 EAL: probe driver: 8086:150e net_e1000_igb EAL: PCI device :04:00.2 on NUMA socket 0 EAL: probe driver: 8086:150e net_e1000_igb EAL: PCI device :04:00.3 on NUMA socket 0 EAL: probe driver: 8086:150e net_e1000_igb EAL: PCI device :07:00.0 on NUMA socket 0 EAL: probe driver: 8086:1521 net_e1000_igb EAL: PCI device :07:00.1 on NUMA socket 0 EAL: probe driver: 8086:1521 net_e1000_igb EAL: PCI device :07:00.2 on NUMA socket 0 EAL: probe driver: 8086:1521 net_e1000_igb EAL: PCI device :07:00.3 on NUMA socket 0 EAL: probe driver: 8086:1521 net_e1000_igb PMD: Initializing pmd_pcap for net_pcap_rx_0 PMD: Creating pcap-backed ethdev on numa socket 4294967295 Port 2 MAC: 00 00 00 01 02 03 PMD: Initializing pmd_pcap for net_pcap_tx_0 PMD: Creating pcap-backed ethdev on numa socket 4294967295 Port 3 MAC: 00 00 00 01 02 03 the port assignment is # ovs-ofctl show xtp1 OFPT_FEATURES_REPLY (xid=0x2): dpid:001b21a7f596 n_tables:254, n_buffers:0 capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan mod_dl_src mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src mod_tp_dst 1(dpdk1): addr:00:1b:21:a7:f5:97 config: 0 state: LINK_DOWN current:AUTO_NEG speed: 0 Mbps now, 0 Mbps max 2(dpdk0): addr:00:1b:21:a7:f5:96 config: 0 state: LINK_DOWN current:AUTO_NEG speed: 0 Mbps now, 0 Mbps max LOCAL(gtp1): addr:00:1b:21:a7:f5:96 config: 0 state: 0 current:10MB-FD COPPER speed: 10 Mbps now, 0 Mbps max OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0 ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] how many CPU cannot allocate for PMD thread?
hi
we have tried on that. e.g. if we set to 0x22, we still only able to
see 2 cpu is in 100%, why?
# ovs-vsctl get Open_vSwitch . other_config
{dpdk-init="true", n-dpdk-rxqs="2", pmd-cpu-mask="0x22"}
Sep 22 22:54:29 host1 ovs-vswitchd[3504]:
ovs|00196|netdev_dpdk|WARN|Failed to enable flow control on device 0
Sep 22 22:54:29 host1 ovs-vswitchd[3504]:
ovs|00197|dpif_netdev|INFO|PMD thread on numa_id: 0, core id: 2
destroyed.
Sep 22 22:54:29 host1 ovs-vswitchd[3504]:
ovs|00198|dpif_netdev|INFO|PMD thread on numa_id: 0, core id: 5
created.
Sep 22 22:54:29 host1 ovs-vswitchd[3504]:
ovs|00199|dpif_netdev|INFO|There are 2 pmd threads on numa node 0
On Wed, Sep 20, 2017 at 8:59 PM, Flavio Leitner <f...@sysclose.org> wrote:
> On Wed, 20 Sep 2017 09:13:55 +0800
> Sun Paul <paul...@gmail.com> wrote:
>
>> sorry about that
>>
>> # ovs-vsctl get Open_vSwitch . other_config
>> {dpdk-init="true", n-dpdk-rxqs="2", pmd-cpu-mask="0x6"}
>
> Have you tried to change pmd-cpu-mask? Because that is mask of bits
> representing the CPUs you allow PMDs to be created. In this case,
> you are saying '0x6' (binary mask: 0110), so only two CPUs.
>
> Also check ovs-vswitchd.conf.db(5) man-page:
>
>other_config : pmd-cpu-mask: optional string
> Specifies CPU mask for setting the cpu affinity of PMD (Poll
> Mode
> Driver) threads. Value should be in the form of hex string,
> similar
> to the dpdk EAL ’-c COREMASK’ option input or the ’taskset’
> mask
> input.
>
> The lowest order bit corresponds to the first CPU core. A set
> bit
> means the corresponding core is available and a pmd thread
> will be
> created and pinned to it. If the input does not cover all
> cores,
> those uncovered cores are considered not set.
>
> If not specified, one pmd thread will be created for each numa
> node
> and pinned to any available core on the numa node by default.
>
> fbl
>
>>
>> On Tue, Sep 19, 2017 at 8:02 PM, Flavio Leitner <f...@sysclose.org> wrote:
>> > On Tue, 19 Sep 2017 13:43:25 +0800
>> > Sun Paul <paul...@gmail.com> wrote:
>> >
>> >> Hi
>> >>
>> >> below is the output. currently, I am only able to set to use two CPU for
>> >> PMD.
>> >
>> >
>> > I was referring to the output of
>> > ovs-vsctl get Open_vSwitch . other_config
>> >
>> > fbl
>> >
>> >>
>> >> # ovs-vsctl show
>> >> ea7f2b40-b7b3-4f11-a81f-cf25a56f8172
>> >> Bridge "gtp1"
>> >> Port "dpdk0"
>> >> Interface "dpdk0"
>> >> type: dpdk
>> >> options: {dpdk-devargs=":04:00.2", n_rxq="4"}
>> >> Port "gtp1"
>> >> Interface "gtp1"
>> >> type: internal
>> >> Port "dpdk1"
>> >> Interface "dpdk1"
>> >> type: dpdk
>> >> options: {dpdk-devargs=":04:00.3", n_rxq="4"}
>> >>
>> >>
>> >>
>> >> On Tue, Sep 19, 2017 at 4:09 AM, Flavio Leitner <f...@sysclose.org> wrote:
>> >> > On Mon, 18 Sep 2017 16:51:33 +0800
>> >> > Sun Paul <paul...@gmail.com> wrote:
>> >> >
>> >> >> Hi
>> >> >>
>> >> >> I have two interfaces mapped to DPDK, and run the OVS on top of it. I
>> >> >> tried to set the cpu mask, but I cannot only allocate more than 2 CPU
>> >> >> for pmd thread. any idea?
>> >> >>
>> >> >> # /usr/local/bin/ovs-appctl dpif-netdev/pmd-rxq-show
>> >> >> pmd thread numa_id 0 core_id 1:
>> >> >> isolated : false
>> >> >> port: dpdk0 queue-id: 0
>> >> >> pmd thread numa_id 0 core_id 2:
>> >> >> isolated : false
>> >> >> port: dpdk1 queue-id: 0
>> >> >
>> >> > Could you post the DPDK configuration and what do you want?
>> >> >
>> >> > Thanks,
>> >> > --
>> >> > Flavio
>> >> >
>> >
>> >
>> >
>> > --
>> > Flavio
>> >
>
>
>
> --
> Flavio
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] how many CPU cannot allocate for PMD thread?
sorry about that
# ovs-vsctl get Open_vSwitch . other_config
{dpdk-init="true", n-dpdk-rxqs="2", pmd-cpu-mask="0x6"}
On Tue, Sep 19, 2017 at 8:02 PM, Flavio Leitner <f...@sysclose.org> wrote:
> On Tue, 19 Sep 2017 13:43:25 +0800
> Sun Paul <paul...@gmail.com> wrote:
>
>> Hi
>>
>> below is the output. currently, I am only able to set to use two CPU for PMD.
>
>
> I was referring to the output of
> ovs-vsctl get Open_vSwitch . other_config
>
> fbl
>
>>
>> # ovs-vsctl show
>> ea7f2b40-b7b3-4f11-a81f-cf25a56f8172
>> Bridge "gtp1"
>> Port "dpdk0"
>> Interface "dpdk0"
>> type: dpdk
>> options: {dpdk-devargs=":04:00.2", n_rxq="4"}
>> Port "gtp1"
>> Interface "gtp1"
>> type: internal
>> Port "dpdk1"
>> Interface "dpdk1"
>> type: dpdk
>> options: {dpdk-devargs=":04:00.3", n_rxq="4"}
>>
>>
>>
>> On Tue, Sep 19, 2017 at 4:09 AM, Flavio Leitner <f...@sysclose.org> wrote:
>> > On Mon, 18 Sep 2017 16:51:33 +0800
>> > Sun Paul <paul...@gmail.com> wrote:
>> >
>> >> Hi
>> >>
>> >> I have two interfaces mapped to DPDK, and run the OVS on top of it. I
>> >> tried to set the cpu mask, but I cannot only allocate more than 2 CPU
>> >> for pmd thread. any idea?
>> >>
>> >> # /usr/local/bin/ovs-appctl dpif-netdev/pmd-rxq-show
>> >> pmd thread numa_id 0 core_id 1:
>> >> isolated : false
>> >> port: dpdk0 queue-id: 0
>> >> pmd thread numa_id 0 core_id 2:
>> >> isolated : false
>> >> port: dpdk1 queue-id: 0
>> >
>> > Could you post the DPDK configuration and what do you want?
>> >
>> > Thanks,
>> > --
>> > Flavio
>> >
>
>
>
> --
> Flavio
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] how many CPU cannot allocate for PMD thread?
Hi
below is the output. currently, I am only able to set to use two CPU for PMD.
# ovs-vsctl show
ea7f2b40-b7b3-4f11-a81f-cf25a56f8172
Bridge "gtp1"
Port "dpdk0"
Interface "dpdk0"
type: dpdk
options: {dpdk-devargs=":04:00.2", n_rxq="4"}
Port "gtp1"
Interface "gtp1"
type: internal
Port "dpdk1"
Interface "dpdk1"
type: dpdk
options: {dpdk-devargs=":04:00.3", n_rxq="4"}
On Tue, Sep 19, 2017 at 4:09 AM, Flavio Leitner <f...@sysclose.org> wrote:
> On Mon, 18 Sep 2017 16:51:33 +0800
> Sun Paul <paul...@gmail.com> wrote:
>
>> Hi
>>
>> I have two interfaces mapped to DPDK, and run the OVS on top of it. I
>> tried to set the cpu mask, but I cannot only allocate more than 2 CPU
>> for pmd thread. any idea?
>>
>> # /usr/local/bin/ovs-appctl dpif-netdev/pmd-rxq-show
>> pmd thread numa_id 0 core_id 1:
>> isolated : false
>> port: dpdk0 queue-id: 0
>> pmd thread numa_id 0 core_id 2:
>> isolated : false
>> port: dpdk1 queue-id: 0
>
> Could you post the DPDK configuration and what do you want?
>
> Thanks,
> --
> Flavio
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] how many CPU cannot allocate for PMD thread?
Hi I have two interfaces mapped to DPDK, and run the OVS on top of it. I tried to set the cpu mask, but I cannot only allocate more than 2 CPU for pmd thread. any idea? # /usr/local/bin/ovs-appctl dpif-netdev/pmd-rxq-show pmd thread numa_id 0 core_id 1: isolated : false port: dpdk0 queue-id: 0 pmd thread numa_id 0 core_id 2: isolated : false port: dpdk1 queue-id: 0 ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] OVS Errors
is there any reason why those info come out? On Sat, Apr 8, 2017 at 6:08 AM, Ben Pfaff <b...@ovn.org> wrote: > None of those are errors. > > On Fri, Apr 07, 2017 at 09:26:22AM +0800, Sun Paul wrote: >> Hi >> >> we used OVS to create bridge interface and passing SCTP traffics on >> it, after running a period of time, we found below error, any idea? >> >> >> Apr 6 01:30:04 app011 ovs-vswitchd[11300]: >> 2017-04-06T01:30:03Z|00392|coverage(revalidator10)|INFO|netlink_recv_jumbo >> 0.8/sec 0.800/sec0.7911/sec total: 196782 >> Apr 6 01:30:04 app011 ovs-vswitchd[11300]: >> 2017-04-06T01:30:03Z|00393|coverage(revalidator10)|INFO|netlink_sent >> 8.2/sec 7.600/sec8.7511/sec total: 1832605 >> Apr 6 01:30:04 app011 ovs-vswitchd[11300]: >> 2017-04-06T01:30:03Z|00394|coverage(revalidator10)|INFO|nln_changed >> 0.0/sec 0.000/sec0.0006/sec total: 58 >> Apr 6 01:30:04 app011 ovs-vswitchd[11300]: >> 2017-04-06T01:30:03Z|00395|coverage(revalidator10)|INFO|56 events >> never hit >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00351|coverage(revalidator10)|INFO|ofproto_flush >> 0.0/sec 0.000/sec0./sec total: 4 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00352|coverage(revalidator10)|INFO|ofproto_update_port >> 0.0/sec 0.000/sec0.0006/sec total: 44 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00353|coverage(revalidator10)|INFO|rev_reconfigure >> 0.0/sec 0.000/sec0.0006/sec total: 17 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00354|coverage(revalidator10)|INFO|rev_port_toggled >> 0.0/sec 0.000/sec0./sec total: 5 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00355|coverage(revalidator10)|INFO|rev_flow_table >> 0.0/sec 0.000/sec0./sec total: 1 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00356|coverage(revalidator10)|INFO|rev_mac_learning >> 0.0/sec 0.017/sec0.0008/sec total: 311 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00357|coverage(revalidator10)|INFO|dumped_new_flow >> 0.0/sec 0.317/sec0.7211/sec total: 80247 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00358|coverage(revalidator10)|INFO|handler_duplicate_upcall >> 0.0/sec 0.000/sec0.0008/sec total: 3330 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00358|coverage(revalidator10)|INFO|handler_duplicate_upcall >> 0.0/sec 0.000/sec0.0008/sec total: 3330 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00359|coverage(revalidator10)|INFO|upcall_ukey_replace >> 0.0/sec 0.000/sec0./sec total: 13 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00360|coverage(revalidator10)|INFO|xlate_actions >> 1.2/sec 0.650/sec1.0614/sec total: 114587 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00361|coverage(revalidator10)|INFO|cmap_expand >> 0.0/sec 0.000/sec0.0039/sec total: 456 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00362|coverage(revalidator10)|INFO|cmap_shrink >> 0.0/sec 0.000/sec0.0039/sec total: 420 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00363|coverage(revalidator10)|INFO|dpif_port_add >> 0.0/sec 0.000/sec0./sec total: 8 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00364|coverage(revalidator10)|INFO|dpif_flow_flush >> 0.0/sec 0.000/sec0./sec total: 5 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00365|coverage(revalidator10)|INFO|dpif_flow_get >> 0.0/sec 0.000/sec0./sec total: 8 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00366|coverage(revalidator10)|INFO|dpif_flow_put >> 0.8/sec 0.350/sec0.7631/sec total: 81900 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00367|coverage(revalidator10)|INFO|dpif_flow_del >> 0.0/sec 0.433/sec0.7233/sec total: 80282 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00368|coverage(revalidator10)|INFO|dpif_execute >> 0.8/sec 0.350/sec0.7639/sec total: 85224 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00369|coverage(revalidator10)|INFO|flow_extract >> 0.8/sec 0.350/sec0.7639/sec total: 85224 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00370|coverage(revalidator10)|INFO|miniflow_malloc >> 0.0/sec 0.000/sec0.0106/sec total: 393 >> Apr 6 01:30:04 app011 ovs-vswitchd: >> ovs|00371|coverage(revalidator10)|INFO|hmap_pathological >> 0.0/sec 0.000/sec0./sec total: 1 >> Apr 6 01:30:04 app011 ovs
