On Thu, Jul 10, 2014 at 10:49:58AM +0530, Anand S Angadi wrote:
> I want to run openvswitch on my Intel dpdk. i followed
> all steps to compile openvswitch but at last while detaching
> ovs-vswitchd
> i am getting error as follow. please tell me any alternative option
> for detach.
>
>
dear all,
I want to run openvswitch on my Intel dpdk. i followed all
steps to compile openvswitch but at last while detaching ovs-vswitchd
i am getting error as follow. please tell me any alternative option for
detach.
[root@localhost openvswitch]#*ovs-vswitchd --detach *
ovs-vswit
On Thu, Jul 10, 2014 at 07:39:52AM +0530, abhishek jain wrote:
> How can we set the limit for the same.
You can use the Flow_Table table in the database. See
ovs-vswitchd.conf.db(5).
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.or
The userspace install docs describe how:
https://github.com/openvswitch/ovs/blob/master/INSTALL.userspace
On 10 July 2014 14:27, Rod N. Melton wrote:
>
>
> then how do i install OVS so that it runs in userspace and MPLS is
> available?
>
>
> From: Ben Pfaff <> To: "Rod N. Melton" <> C
All of these tests seem to be failing due to the same problem:
ovs-vswitchd: unrecognized option '--detach'
This seems very odd - as far as I can tell this option has always existed
in OVS.
___
discuss mailing list
discuss@openvswitch.org
http://openvsw
then how do i install OVS so that it runs in userspace and MPLS is
available?
FROM:
Ben Pfaff <>
TO:
"Rod N. Melton" <>
CC:
ovs
There is no option to build
Hi Ben
How can we set the limit for the same.
Thanks
Abhishek Jain
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
There is no option to build for userspace. It is always supported.
On Jul 9, 2014 6:57 PM, "Rod N. Melton" wrote:
>
>
> i am using ubuntu 14.04 in virtualbox.
>
> I am trying to build openvswitch for userspace (so that I can use MPLS).
>
> when i get ovs source from:
>
> 1.)git clone https://gith
Rod,
I think you need to install libtools.
sudo apt-get install libtool
--Tom
On 7/9/14, 9:56 PM, Rod N. Melton wrote:
i am using ubuntu 14.04 in virtualbox.
I am trying to build openvswitch for userspace (so that I can use MPLS).
when i get ovs source from:
1.)git clone https://github.c
i am using ubuntu 14.04 in virtualbox.
I am trying to build openvswitch for userspace (so that I can use MPLS).
when i get ovs source from:
1.)git clone https://github.com/openvswitch/ovs.git OR from
http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=snapshot;sf=tgz;h=HEAD
[1] ,
b
On Wed, Jul 09, 2014 at 05:00:55PM -0700, Chris Hydon wrote:
> On 2014-07-09 3:41 PM, Ben Pfaff wrote:
> >On Wed, Jul 09, 2014 at 02:04:00PM -0700, Chris Hydon wrote:
> >>I am part of a team developing a program that connects to a running
> >>OVSDB server via the jsonrpc interface and performs tran
On Wed, Jul 09, 2014 at 12:21:13PM +0530, Prabhuling Kalyani wrote:
> Hi,
>
> I simply ran "make check" after following the steps in:
>
> https://01.org/sites/default/files/downloads/packet-processing/329865inteldpdkvswitchgsg09.pdf
>
> This was the output I got.
> Seems like some went wrong bad
On Wed, Jul 09, 2014 at 02:04:00PM -0700, Chris Hydon wrote:
> I am part of a team developing a program that connects to a running
> OVSDB server via the jsonrpc interface and performs transactions. I
> noticed during testing that after sending a database REQUEST, if a
> table has a monitor active
Hi there,
I tried goggling for more information. It seems to be the only way to
couple openvswitch from different host is via vxlan tunnel or gre tunnel.
Tunnelling is good for small number of host. Is there any other way of
coupling than the 2 methods which is mentioned which far more simple?
Th
I am part of a team developing a program that connects to a running
OVSDB server via the jsonrpc interface and performs transactions. I
noticed during testing that after sending a database REQUEST, if a table
has a monitor active on the same socket it will receive the monitor
NOTIFY before the
Hi all,
Once paquets are received at an interface, they are queued prior to be sent on
a physical port may i know how does that work with OVS bridges and what
would be the impact of a link failure.
For example... if i have an OVS bridge with 3 ports. Packets are coming in on
port A
I think, this tricks with "pre-up /etc/init.d/openvswitch-switch start"
and "auto" order must be documented.
>>> Did you read my first email and try removing things from auto?
>>
>> I have checked this, but there are potential problem exist: if I remove
>> ovs-controlled interfaces fr
> On Jul 9, 2014, at 11:37 AM, Pavel V. Kaygorodov wrote:
>
> Hi!
>
>>> I think, this tricks with "pre-up /etc/init.d/openvswitch-switch start" and
>>> "auto" order must be documented.
>> Did you read my first email and try removing things from auto?
>
> I have checked this, but there are po
Hi!
>> I have installed openvswitch-2.3.90 on Debian wheezy, and changed
>> /etc/network/interfaces.
>
> I am having a hard time as well integrating my openvswitch
> configuration into the interface file.
>
> However I am still using version 1.4.2[1] on Debian wheezy, where did
> you get a offi
Hi!
>> I think, this tricks with "pre-up /etc/init.d/openvswitch-switch start" and
>> "auto" order must be documented.
> Did you read my first email and try removing things from auto?
I have checked this, but there are potential problem exist: if I remove
ovs-controlled interfaces from auto, th
I ran that command on my own development host rather than in the Xen
DDK. (I use i386 instead of x86-64 to put some diversity into
development, since most developers use x86-64.) Rest assured that we
do all of our XenServer builds in the Xen DDK that corresponds to the
target XenServer target (an
I don't understand the question.
Maybe you are just asking how these work together. I believe that, if
you enable CFM or BFD on a GRE interface, then CFM or BFD signaling
that the tunnel is down will cause a fast failover group to bypass
that interface.
On Wed, Jul 09, 2014 at 06:12:08PM +0100,
Thank you. In this context, do you how can a GRE interface being used with
group fast-failover?
On 9 July 2014 18:08, Ben Pfaff wrote:
> On Wed, Jul 09, 2014 at 04:57:01PM +0100, Ricardo Santos wrote:
> > So right now my question gets more specific. Is there any method for
> > getting fast fail
On Wed, Jul 09, 2014 at 04:57:01PM +0100, Ricardo Santos wrote:
> So right now my question gets more specific. Is there any method for
> getting fast failover to work when using GRE interfaces in OVS? How can a
> GRE interface state get flagged as down?
You should be able to use CFM or BFD.
__
On Wed, Jul 09, 2014 at 12:21:26PM +0530, abhishek jain wrote:
> I want to know that how many flows can be added in one ovs table?
There is no limit, by default, but you can set a limit if you like.
___
discuss mailing list
discuss@openvswitch.org
http:
Hi,
I've ended up solving this problem. The interface state was not being
changed because I was handling a GRE tunnel in OpenvSwitch and shutting
down the physical interface down (the state of the physical interface was
being set as down, but the GRE interface state was still up).
I've made some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Pavel,
On 08/07/14 11:08, Pavel V. Kaygorodov wrote:
> I have installed openvswitch-2.3.90 on Debian wheezy, and changed
> /etc/network/interfaces.
I am having a hard time as well integrating my openvswitch
configuration into the interface file.
Hi Ben,
From the objdump-sed (%esp) command I realised that you guys might be
using a XenServer DDK shipped with 6.2, which is 32bit. From Creedence
(next release) onwards dom0 is 64bit, and so are the tools.
http://xenserver.org/open-source-virtualization-download/24-product/creedence/143-xs-
> On Jul 9, 2014, at 1:13 AM, "Pavel V. Kaygorodov" wrote:
>
> Hi!
>
> Thank you for response, I have already found a eth0->eth1 mistake, but this
> was not enough.
> The complete solution, after a number of experiments is:
>
> # The order is important: eth1 must be after br0!
> auto br0 eth
Hi!
Thank you for response, I have already found a eth0->eth1 mistake, but this was
not enough.
The complete solution, after a number of experiments is:
# The order is important: eth1 must be after br0!
auto br0 eth1 br0:1
allow-ovs br0
iface br0 inet static
address 192.168.111.1
netmask 25
30 matches
Mail list logo
