date:20170925

Re: [ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest

2017-09-25 Thread Darrell Ball



On 9/25/17, 9:26 PM, "Sun Paul"  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  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"  wrote:
>
>
>
> On 9/25/17, 8:31 PM, "Sun Paul"  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  
wrote:
> >
> >
> > On 9/25/17, 2:53 AM, "ovs-discuss-boun...@openvswitch.org on 
behalf of Sun Paul"  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
>

Re: [ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest

2017-09-25 Thread Sun Paul

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  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  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" > db...@vmware.com> wrote:
>>
>>
>>
>> On 9/25/17, 8:31 PM, "Sun Paul"  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  
>> wrote:
>> >
>> >
>> > On 9/25/17, 2:53 AM, "ovs-discuss-boun...@openvswitch.org on 
>> behalf of Sun Paul" > 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
>> > 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:
>> >

Re: [ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest

2017-09-25 Thread Sun Paul

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  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"  db...@vmware.com> wrote:
>
>
>
> On 9/25/17, 8:31 PM, "Sun Paul"  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  
> wrote:
> >
> >
> > On 9/25/17, 2:53 AM, "ovs-discuss-boun...@openvswitch.org on behalf 
> of Sun Paul"  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
> > 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 
>

Re: [ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest

2017-09-25 Thread Darrell Ball



On 9/25/17, 8:31 PM, "Sun Paul"  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  wrote:
>
>
> On 9/25/17, 2:53 AM, "ovs-discuss-boun...@openvswitch.org on behalf of 
Sun Paul"  
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
> 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:
>

[ovs-discuss] VPP vs OVS-DPDK

2017-09-25 Thread Avi Cohen (A)

 Hi,
 The VPP [Avi Cohen shows   a  significant performance improvements compared to 
OVS.
 e.g. see https://www.youtube.com/watch?v=Z5M0Zl0uvj0  .
 in the bottom line:   significant  improvements  are seen  with multiple flows 
.
 can someone tell  'typical' number of flows in  VMs, hosts, TORs etc.
 
 Best Regards
 avi
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest

2017-09-25 Thread Sun Paul

Hi

thank for the reply. but can you explain what I should do?

On Tue, Sep 26, 2017 at 3:18 AM, Darrell Ball  wrote:
>
>
> On 9/25/17, 2:53 AM, "ovs-discuss-boun...@openvswitch.org on behalf of Sun 
> Paul"  
> 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: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:
>

Re: [ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest

2017-09-25 Thread Darrell Ball



On 9/25/17, 2:53 AM, "ovs-discuss-boun...@openvswitch.org on behalf of Sun 
Paul"  
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: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:

Re: [ovs-discuss] [ovn] Chassis Table or MAC_Binding Table in ovn-sb have aging?

2017-09-25 Thread Russell Bryant

On Mon, Sep 25, 2017 at 10:10 AM, Guoshuai Li  wrote:
> Hi All
>
>
> When the chassis node power off, the south of the database to the Chassis
> table also exists.
>
> For example, the gateway node power off, but the chassis information still
> exists, the traffic continues to forward the package to the chassis.

If you turn on gateway HA, the traffic should move to another host.

> When an external IP address is destroyed, MAC_Binding also has this IP.
>
> For example, the MAC address of the device of the external gateway changes
> (changed one). If there is no external ARP packet, MAC_Binding will not be
> updated.

There is no expiration of MAC_Binding entries.  This needs to be improved.

>
>
> Is there a good way to solve this problem?
>
> please help
>
> Thanks
>
> ___
> discuss mailing list
> disc...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss



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

[ovs-discuss] [ovn] Chassis Table or MAC_Binding Table in ovn-sb have aging?

2017-09-25 Thread Guoshuai Li


Hi All


When the chassis node power off, the south of the database to the 
Chassis table also exists.


For example, the gateway node power off, but the chassis information 
still exists, the traffic continues to forward the package to the chassis.



When an external IP address is destroyed, MAC_Binding also has this IP.

For example, the MAC address of the device of the external gateway 
changes (changed one). If there is no external ARP packet, MAC_Binding 
will not be updated.



Is there a good way to solve this problem?

please help

Thanks

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

[ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest

2017-09-25 Thread Sun Paul

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] Cannot dump packet capture using dpdk-pdump

2017-09-25 Thread Loftus, Ciara

> 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?

Hi,

You are capturing on port 1 but the link state is "down". Make sure your link 
is up and that you can see packets being rx/tx in the statistics first eg. via 
'ovs-ofctl dump-ports '
The following might be useful as well:
https://software.intel.com/en-us/articles/dpdk-pdump-in-open-vswitch-with-dpdk

Thanks,
Ciara

> 
> 
> 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
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] How instance get metadata with OVN

2017-09-25 Thread Daniel Alvarez Sanchez

Hi Vikran

On Sat, Sep 23, 2017 at 8:22 AM, Vikrant Aggarwal 
wrote:

> Hi Folks,
>
> I am trying to understand how instance get metadata when OVN is used as
> mechanism driver. I read the theory on [1] but not able to understand the
> practical implementation of same.
>
> Created two private networks (internal1 and internal2), one private
> network (internal1) is created to router and other one (internal2) is
> isolated.
>
> I tried to spin the cirros instances using both networks. Both instances
> are able to get the metadata from networks.
>
> List of metadata related processes running on devstack node.
>
> ~~~
> stack@testuser-KVM:~/devstack$ ps -ef | grep -i metadata
> stack 1067 1  0 Sep22 ?00:00:39 /usr/bin/python
> /usr/local/bin/networking-ovn-metadata-agent --config-file
> /etc/neutron/networking_ovn_metadata_agent.ini
> stack 1414  1067  0 Sep22 ?00:00:17 /usr/bin/python
> /usr/local/bin/networking-ovn-metadata-agent --config-file
> /etc/neutron/networking_ovn_metadata_agent.ini
> stack 1415  1067  0 Sep22 ?00:00:17 /usr/bin/python
> /usr/local/bin/networking-ovn-metadata-agent --config-file
> /etc/neutron/networking_ovn_metadata_agent.ini
> stack25192 1  0 10:43 ?00:00:00 haproxy -f
> /opt/stack/data/neutron/ovn-metadata-proxy/54f264d5-c2f5-
> 409c-9bd2-dbcec52edffd.conf
> stack27424 1  0 11:24 ?00:00:00 haproxy -f
> /opt/stack/data/neutron/ovn-metadata-proxy/86eefb22-1417-
> 407a-b56f-a1f3f147ee4e.conf
> ~~~
>
> Default content of neutron ovn metadata file.
>
> ~~~
> stack@testuser-KVM:~/devstack$ egrep -v "^(#|$)"
> /etc/neutron/networking_ovn_metadata_agent.ini
> [DEFAULT]
> state_path = /opt/stack/data/neutron
> metadata_workers = 2
> nova_metadata_ip = 192.168.122.98
> debug = True
> [ovs]
> ovsdb_connection = unix:/usr/local/var/run/openvswitch/db.sock
> [agent]
> root_helper_daemon = sudo /usr/local/bin/neutron-rootwrap-daemon
> /etc/neutron/rootwrap.conf
> [ovn]
> ovn_sb_connection = tcp:192.168.122.98:6642
> ~~~
>
> I don't see any NAT rule inside the network namespace which can route the
> request coming for "169.254.169.254" to nova metadata IP which is mentioned
> in ovn metadata configuration file.
>
> ~~~
> stack@testuser-KVM:~/devstack$ sudo ip netns list
> ovnmeta-86eefb22-1417-407a-b56f-a1f3f147ee4e (id: 1)
> ovnmeta-54f264d5-c2f5-409c-9bd2-dbcec52edffd (id: 0)
> stack@testuser-KVM:~/devstack$ sudo ip netns exec
> ovnmeta-86eefb22-1417-407a-b56f-a1f3f147ee4e iptables -t nat -L
> Chain PREROUTING (policy ACCEPT)
> target prot opt source   destination
>
> Chain INPUT (policy ACCEPT)
> target prot opt source   destination
>
> Chain OUTPUT (policy ACCEPT)
> target prot opt source   destination
>
> Chain POSTROUTING (policy ACCEPT)
> target prot opt source   destination
> ~~~
>
> Content of the haproxy configuration file.
>
> ~~~
> root@testuser-KVM:~/devstack# cat /opt/stack/data/neutron/ovn-
> metadata-proxy/86eefb22-1417-407a-b56f-a1f3f147ee4e.conf
>
> global
> log /dev/log local0 debug
> userstack
> group   stack
> maxconn 1024
> pidfile /opt/stack/data/neutron/external/pids/86eefb22-1417-
> 407a-b56f-a1f3f147ee4e.pid
> daemon
>
> defaults
> log global
> mode http
> option httplog
> option dontlognull
> option http-server-close
> option forwardfor
> retries 3
> timeout http-request30s
> timeout connect 30s
> timeout client  32s
> timeout server  32s
> timeout http-keep-alive 30s
>
> listen listener
> bind 0.0.0.0:80
> server metadata /opt/stack/data/neutron/metadata_proxy
> http-request add-header X-OVN-Network-ID 86eefb22-1417-407a-b56f-
> a1f3f147ee4e
> ~~~
>
> It seems like that isolate metadata option is enabled by default in my
> setup, but in neutron ovn configuration files I don't see such setting, I
> am suspecting it's enabled because when network is not connected to router
> even in that case instance spawned using isolated network able to get the
> metadata.
>

The way we implemented metadata in OVN is as ML2/OVS implements it for the
isolated networks case.
No matter if the network is connected to a router or not, metadata will be
served in OVN locally in each controller.
A metadata agent is running on each controller and one instance of haproxy
will be running for each network for
which that chassis is hosting a port in.



> How the instance is able to get metadata in both cases isolate network and
> network connected to router?
>

The way instances reach the metadata namespace is through a static route
(see the contents of the DHCP_Options table
and route command output from the instance itself) which is pushed via DHCP
so that when traffic is directed to 169.254.169.254,
instead of hitting the default route it will be directed to the IP address
of the

Re: [ovs-discuss] How to create mirror packet over GRE on OVS+DPDK

2017-09-25 Thread Guoshuai Li

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

4.

   Onhost1, add a port for the VXLANtunnel:

   $ 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 remotetunnelend point address. On the remote
   host this will be|172.168.1.1|

5.

   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  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  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:  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  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  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

Re: [ovs-discuss] How to create mirror packet over GRE on OVS+DPDK

2017-09-25 Thread Sun Paul

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  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  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:  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  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  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

2017-09-25 Thread Sun Paul

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  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:  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  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  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

2017-09-25 Thread Guoshuai Li


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:  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  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  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

2017-09-25 Thread Sun Paul

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  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  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] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest

Re: [ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest

Re: [ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest

Re: [ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest

[ovs-discuss] VPP vs OVS-DPDK

Re: [ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest

Re: [ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest

Re: [ovs-discuss] [ovn] Chassis Table or MAC_Binding Table in ovn-sb have aging?

[ovs-discuss] [ovn] Chassis Table or MAC_Binding Table in ovn-sb have aging?

[ovs-discuss] Problem on creating bridge interface on OVS_DPDK in a VMware VM guest

Re: [ovs-discuss] Cannot dump packet capture using dpdk-pdump

Re: [ovs-discuss] How instance get metadata with OVN

Re: [ovs-discuss] How to create mirror packet over GRE on OVS+DPDK

Re: [ovs-discuss] How to create mirror packet over GRE on OVS+DPDK

Re: [ovs-discuss] How to create mirror packet over GRE on OVS+DPDK

Re: [ovs-discuss] How to create mirror packet over GRE on OVS+DPDK

Re: [ovs-discuss] How to create mirror packet over GRE on OVS+DPDK

17 matches

Site Navigation

Mail list logo

Footer information