Hi Ben,
Thanks a lot for your advice, yes, it's fast if we add 1000 tunnels in
one transaction, however, our user create/delete tunnels reactivelly
according to the traffic between the two VTEPS.
I also want to precreate 1000 tunnels and let user modify the tunnels as
they needed, since the
On Mon, Sep 22, 2014 at 01:25:24PM -0700, Pravin Shelar wrote:
> On Thu, Sep 18, 2014 at 10:30 PM, Dietmar Maurer wrote:
> > Is there a patch to compile OVS 2.3.0 with latest RHEL7 kernel?
> >
> I do not think there is patch to fix it.
>
> Flavio,
> Is anyone from Redhat working on this?
No, not
On September 24, 2014 at 3:26:40 PM, MCGRATH, GIL (gm2...@att.com) wrote:
> Can I try it - is it stable enough ? Does the does say enough to set it up?
It's definitely stable enough to try out, but I wouldn't run it in production
yet. We know that there are a couple of issues related to multi-th
Can I try it - is it stable enough ? Does the does say enough to set it up?
Sent from my iPhone
> On Sep 24, 2014, at 5:49 PM, Justin Pettit wrote:
>
>> On September 19, 2014 at 9:39:09 AM, MCGRATH, GIL (gm2...@att.com) wrote:
>> I am looking into the use of DPDK with OVS.
>>
>> I am a bit con
On September 19, 2014 at 9:39:09 AM, MCGRATH, GIL (gm2...@att.com) wrote:
> I am looking into the use of DPDK with OVS.
>
> I am a bit confused on the following:
>
> * What is the status of DPDK support in OVS?
It's still a work in progress, but it is functional in our "master" branch, and
we
So I’m now using option:key=1 and 2 instead of key=flow. I’m attempting to
tag 1 -> 2 with VNID 2, and 2 -> 1 with VNID 1.
*** Setting VXLAN 1 -> 2
ovs-vsctl set bridge s1 protocols=OpenFlow13
ovs-vsctl add-port s1 vx1 -- set interface vx1 type=vxlan
option:remote_ip=localhost option:key=1 ofport_
Sorry, I should have clarified, 172.16.4.1 is a dummy UDP server reflecting
packets back to the sender (since localhost wasn’t working). Indeed VXLAN
packets are arriving on the dummy server, though they’re not being accepted
back by OVS. I was hoping to specify the VNID in flows as it much more
dy
#switch 1
sh ovs-vsctl add-port s1 vx1 -- set interface vx1 type=vxlan
option:remote_ip=172.16.4.1 option:key=flow ofport_request=11
sh ovs-ofctl add-flow s1 'in_port=11,tun_id=2,actions=output:1'
sh ovs-ofctl add-flow s1 'in_port=1,actions=set_field:1->tun_id,output:11'
#switch 2
sh ovs-vsctl add
On Mon, Sep 22, 2014 at 06:14:36PM -0600, Vivien X.W. Liu wrote:
> I am currently working on a project that needs to use Open vSwitch, and
> modify the body of every OpenFlow message that is sent back and forward
> between the SDN controller and the Open vSwitch (body here means the rest
> of the b
On Mon, Sep 22, 2014 at 08:06:50PM +0800, ychen wrote:
>I found that internal port and netdev port can not ping each other, can
> you tell me why?
> The topology is like this:
> p0: type=internal, tag=100, vlan_mode=access, ip=192.168.1.100/24, br0,
> namespace ns0
> eth0: type=netndev, t
On Wed, Sep 24, 2014 at 03:59:03PM +0800, ?? wrote:
> We have used ovsdb-server/openvswitch for a long time on our switch
> which use an freescale SoC p1010 with cpu core frequency set to 533Mhz,
> recently we want to add 1000 GRE tunnel ports support to our switch,
> however, we have observed
Hello,
I'm using OpenStack icehouse and OpenvSwitch 2.1.3
The problem is that packets from VM's can go out, but never return to VM's.
#
# Cluster setup is as follows:
#
Compute node 2:
Vxlan: 192.168.100.2
Compute node 4:
Vxlan: 192.168.100.4
Network node:
Vxlan: 192.
Hi all,
We have used ovsdb-server/openvswitch for a long time on our switch
which use an freescale SoC p1010 with cpu core frequency set to 533Mhz,
recently we want to add 1000 GRE tunnel ports support to our switch,
however, we have observed significant slow down when we trying to
configure more
Resending the message since commands were scrambeled.
I didn't ask for any mode in purpose I used the commands below to initialize
OVS.
Nevertheless, I do like the fact that flows are getting deleted, I just think
that meters should be deleted as well.
ovsdb-server --remote=punix:/var/run/openv
I didn't ask for any mode in purpose I used the commands below to initialize
OVS.
Nevertheless, I do like the fact that flows are getting deleted, I just think
that meters should be deleted as well.
ovsdb-server --remote=punix:/var/run/openvswitch/db.sock --pidfile --detach
ovs-vsctl --no-wait -
15 matches
Mail list logo
