[ovs-discuss] OVS supported hardware switches

[Shravan S K]

Hello,

We are looking to buy a few OpenFlow-enabled switches. What advantages can
be achieved by a hardware switch that also supports OVS?
And can a hardware openflow L2 switch perform L3,L4 based openflow
forwarding - can I inspect L3,L4 layers and take a decision based on them ?
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

[Shravan S K]

I know that. But I wanted to experiment with OVS bridges first, and then if
it worked I wanted to re-create the config for a larger topology using
Mininet(which uses OVS bridges(for switches) using OVS).

Thanks.

Shravan

On 13 January 2017 at 08:06, Raymond Burkholder <r...@oneunified.net> wrote:

> Try running VirtualBox, and build two guests with shared networking.
> That will get you an appropriate simulation of computer to computer vxlan
> mechanisms.
>
>
>
> *From:* ovs-discuss-boun...@openvswitch.org [mailto:ovs-discuss-bounces@
> openvswitch.org] *On Behalf Of *Shravan S K
> *Sent:* Thursday, January 12, 2017 22:34
> *To:* Scott Lowe <scott.l...@scottlowe.org>
> *Cc:* ovs-discuss@openvswitch.org
> *Subject:* Re: [ovs-discuss] VXLAN support in OVS 2.5.0
>
>
>
> Because of lack of hardware, I'm trying a vxlan setup on a single
> computer.
>
> On 13-Jan-2017 04:47, "Scott Lowe" <scott.l...@scottlowe.org> wrote:
>
> Please don't drop the list.
>
> Before we go down that path, can you help me understand what you're
> trying to achieve by building a VXLAN tunnel between two VMs on the same
> host?
>
>
>
> On 01/12/2017 10:15 AM, Shravan S K wrote:
> > I am not sure how to do the config for what you said.
> > Can you please explain how to configure the setup that you're suggesting
> ?
> >
> > Shravan
> >
> > On 12 January 2017 at 02:17, Scott Lowe <scott.l...@scottlowe.org
> > <mailto:scott.l...@scottlowe.org>> wrote:
> >
> > On 01/11/2017 03:54 AM, Shravan S K wrote:
> > > Like this?
> > > vm01---|
> > > |--vm03
> > >
> > > br1(vxlanport1)br-int1=br-int2--
> (vxlanport2)br2
> > > vm02---|
> > > |---vm04
> > >
> > > What is the need for the bridges br-int1 and br-int2? Why is it not
> > > possible without them(as the topology shown earlier in this
> thread)?
> >
> >
> > [SL] No, I don't think this is the configuration you'd want to use.
> The
> > "br-int" bridges aren't strictly required; you could use br1 and br2.
> > The trick here---as you're trying to create a VXLAN tunnel within a
> > host---would be that you'll need 2 IP endpoints (one for each end of
> the
> > tunnel), and you'd need each bridge with a VXLAN port to be
> associated
> > with one of those IP endpoints.
> >
> > As I said, though, I haven't tested a configuration like this.
> Further,
> > to be honest, I'm not really sure what you're trying to accomplish
> with
> > such a configuration.
> >
> >
> > > Shravan
> > >
> > > On 11 January 2017 at 11:59, Scott Lowe <scott.l...@scottlowe.org
> <mailto:scott.l...@scottlowe.org>
> > > <mailto:scott.l...@scottlowe.org <mailto:scott.l...@scottlowe.org>>>
> wrote:
> > >
> > > Please see my response inline, prefixed with [SL].
> > >
> > >
> > > On 01/10/2017 09:50 PM, Shravan S K wrote:
> > >> I am asking if that can be done on a single physical host having
> > >> OVS. Say, as mininet creates bridges which act as switches. Can
> > >> vxlan be setup using Mininet?
> > >
> > >
> > > [SL] I don't know if it's possible for Mininet to set up VXLAN;
> > > that's a question best asked on a Mininet-related forum.
> > >
> > > As for whether it can be done on a single host, I suppose if you
> were
> > > to use 2 separate bridges for physical connectivity along with 2
> > > separate bridges for the tunnels, it might work. I've never tried
> it,
> > > though, so this is just conjecture.
> > >
> > >
> > >> Shravan
> > >>
> > >> On 10 January 2017 at 23:33, Scott Lowe <scott.l...@scottlowe.org
> <mailto:scott.l...@scottlowe.org>
> > <mailto:scott.l...@scottlowe.org <mailto:scott.l...@scottlowe.org>>
> > >> <mailto:scott.l...@scottlowe.org
> > <mailto:scott.l...@scottlowe.org> <mailto:scott.l...@scottlowe.org
> > <mailto:scott.l...@scottlowe.org>>>> wrote:
> > >>
> > >> Please see my response below.
> > >>
> > >>
> > >> On 01/10/2017 02:26 AM, Shravan S K wrote:
> > >>> Is it

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

[Shravan S K]

Like this?
vm01---|
|--vm03

br1(vxlanport1)br-int1=br-int2--(vxlanport2)br2
vm02---|
|---vm04

What is the need for the bridges br-int1 and br-int2? Why is it not
possible without them(as the topology shown earlier in this thread)?




Shravan

On 11 January 2017 at 11:59, Scott Lowe <scott.l...@scottlowe.org> wrote:

> Please see my response inline, prefixed with [SL].
>
>
> On 01/10/2017 09:50 PM, Shravan S K wrote:
> > I am asking if that can be done on a single physical host having OVS.
> > Say, as mininet creates bridges which act as switches. Can vxlan be
> > setup using Mininet?
>
>
> [SL] I don't know if it's possible for Mininet to set up VXLAN; that's a
> question best asked on a Mininet-related forum.
>
> As for whether it can be done on a single host, I suppose if you were to
> use 2 separate bridges for physical connectivity along with 2 separate
> bridges for the tunnels, it might work. I've never tried it, though, so
> this is just conjecture.
>
>
> > Shravan
> >
> > On 10 January 2017 at 23:33, Scott Lowe <scott.l...@scottlowe.org
> > <mailto:scott.l...@scottlowe.org>> wrote:
> >
> > Please see my response below.
> >
> >
> > On 01/10/2017 02:26 AM, Shravan S K wrote:
> > > Is it possible to create a VXLAN setup using just bridges created
> by
> > > OVS? (using ovs-vsctl to create these bridges,ports and vxlan
> config)
> > >
> > > vm01---| |--vm03
> > >   br1---br2
> > > vm02---| |---vm04
> >
> >
> > Yes, this is possible. On each hypervisor where OVS is running and
> where
> > you have VMs you'd like to connect over VXLAN tunnels, create a
> bridge
> > ("br-tun", for example). Create and configure a VXLAN port
> appropriately
> > on br-tun on each hypervisor, and then connect your VMs. You should
> be
> > good to go. My website has an example of doing this with GRE; VXLAN
> > should be nearly identical.
> >
> > Hope this helps,
>
>
> --
> Scott
>
>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

[Shravan S K]

I am asking if that can be done on a single physical host having OVS.
Say, as mininet creates bridges which act as switches. Can vxlan be setup
using Mininet?

Shravan

On 10 January 2017 at 23:33, Scott Lowe <scott.l...@scottlowe.org> wrote:

> Please see my response below.
>
>
> On 01/10/2017 02:26 AM, Shravan S K wrote:
> > Is it possible to create a VXLAN setup using just bridges created by
> > OVS? (using ovs-vsctl to create these bridges,ports and vxlan config)
> >
> > vm01---| |--vm03
> >   br1---br2
> > vm02---| |---vm04
>
>
> Yes, this is possible. On each hypervisor where OVS is running and where
> you have VMs you'd like to connect over VXLAN tunnels, create a bridge
> ("br-tun", for example). Create and configure a VXLAN port appropriately
> on br-tun on each hypervisor, and then connect your VMs. You should be
> good to go. My website has an example of doing this with GRE; VXLAN
> should be nearly identical.
>
> Hope this helps,
>
> --
> Scott
>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

[Shravan S K]

Is it possible to create a VXLAN setup using just bridges created by OVS?
(using ovs-vsctl to create these bridges,ports and vxlan config)

vm01---| |--vm03
  br1---br2
vm02---| |---vm04



Shravan

On 29 December 2016 at 10:42, Shravan S K <sra9...@gmail.com> wrote:

> Thanks, Scott.
>
> Beautiful explanation in the post!
>
> Shravan
>
> On 28 December 2016 at 21:29, Scott Lowe <scott.l...@scottlowe.org> wrote:
>
>> Please see my responses inline, prefixed by [SL].
>>
>>
>> On Dec 28, 2016, at 4:15 AM, Shravan S K <sra9...@gmail.com> wrote:
>> >
>> > I am trying this - http://docs.openvswitch.org/en
>> /latest/howto/userspace-tunneling/
>> >
>> > 1) Which step connects vxlan interface,vxlan0, to the bridge,br-phy, as
>> shown in the diagram ?
>>
>>
>> [SL] I haven't worked with userspace tunneling yet, but I believe the
>> principles here are much the same as with a "traditional" kernel-mode
>> implementation. Traffic from the vxlan0 port on br-int is directed out the
>> physical interfaces attached to br-phy via the kernel's routing table
>> (which is why step #5 is necessary).
>>
>> This article may help you understand the various traffic patterns you may
>> encounter with OVS:
>>
>> <http://blog.scottlowe.org/2013/05/15/examining-open-vswitch
>> -traffic-patterns/>
>>
>>
>> > 2) What should I do if also want to access(from the VM) the network
>> that my host is in ?
>>
>>
>> [SL] You would need to either a) add an additional interface to the VM,
>> or b) create a VXLAN-to-VLAN gateway. In the case of a), this additional
>> interface would need to be connected to br-phy (or its equivalent). In the
>> case of b), this would be another system (guest or VM) that receives VXLAN
>> traffic and handles decapsulation of the traffic and placement onto a VLAN
>> outside the overlay.
>>
>> I hope this helps.
>>
>> --
>> Scott
>>
>>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] ovs-vsctl using ovsdb-client

[Shravan S K]

I checked with -vjsonrpc, it shows the series of RPC methods that were
called along with the parameters.

I feel it is difficult/cumbersome to configure OVS using ovsdb-client. Are
there any other methods/workarounds for this?

Just to clarify, we can configure OVS remotely using 2 ways:
1) Using ovs-vsctl by SSHing to the host with OVS
2) Using ovsdb-client over TCP port 6640.
Am I right ? Are there any other methods possible?

Thanks.

Shravan

On 4 January 2017 at 23:39, Ben Pfaff <b...@ovn.org> wrote:

> On Sat, Dec 31, 2016 at 06:41:17PM +0530, Shravan S K wrote:
> > How the functionality provided by ovs-vsctl can be achieved using
> > ovsdb-client commands ?
> >
> > For example, to create a bridge and add a port using ovs-vsctl, we can
> use
> > $ ovs-vsctl add bridge br0
> > $ ovs-vsctl add-port br0 port0
> > How to do these using ovsdb-client ?
> >
> > I went through the doc
> > http://openvswitch.org/support/dist-docs-2.5/ovsdb-client.1.pdf Should
> we
> > use the transact command ? (I know basic database stuff) If so, can you
> > please give an example of how to do it or suggest some useful
> > resources/tutorials available online ?
>
> You might want to run ovs-vsctl with -vjsonrpc to look at how ovs-vsctl
> implements its commands.
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] ovs-vsctl using ovsdb-client

[Shravan S K]

Hello,

How the functionality provided by ovs-vsctl can be achieved using
ovsdb-client commands ?

For example, to create a bridge and add a port using ovs-vsctl, we can use
$ ovs-vsctl add bridge br0
$ ovs-vsctl add-port br0 port0
How to do these using ovsdb-client ?

I went through the doc
http://openvswitch.org/support/dist-docs-2.5/ovsdb-client.1.pdf Should we
use the transact command ? (I know basic database stuff) If so, can you
please give an example of how to do it or suggest some useful
resources/tutorials available online ?

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

Re: [ovs-discuss] ovsdb-client connection refused

[Shravan S K]

Thanks, Flavio.

Shravan

On 30 December 2016 at 21:15, Flavio Leitner <f...@sysclose.org> wrote:

> On Fri, 30 Dec 2016 14:59:27 +0530
> Shravan S K <sra9...@gmail.com> wrote:
>
> > Hello,
> >
> > set up : 2 machines running OVS 2.5.0.
> >
> > m1 - 192.168.20.1
> > m2 - 192.168.20.2
> >
> > On m2 ->
> > $ sudo ovs-vsctl set-manager tcp:192.168.20.1:6640
> > $ sudo ovs-vsctl show
> > 38bc233b-7431-4aad-aefd-9155aff54ad4
> > Manager "tcp:192.168.20.1:6640"
> > ovs_version: "2.5.0"
> >
> > On m1 ->
> > $ sudo ovsdb-client -v list-dbs tcp:192.168.20.2:6640
> > 2016-12-30T09:23:13Z|1|poll_loop|DBG|wakeup due to 0-ms timeout
> > 2016-12-30T09:23:13Z|2|poll_loop|DBG|wakeup due to
> > [POLLOUT][POLLERR][POLLHUP] on fd 3 (192.168.20.2:36486<->) at
> > ../lib/stream-fd.c:151
> > ovsdb-client: failed to connect to "tcp:192.168.20.2:6640" (Connection
> > refused)
>
> In the first command you are telling to connect to the manager
> using tcp at 192.168.20.1 port 6640 where you actually want to
> to listen for a connection on that port, i.e.:
>
> # ovs-vsctl set-manager ptcp:6640
>
> --
> Flavio
>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] ovsdb-client connection refused

[Shravan S K]

Hello,

set up : 2 machines running OVS 2.5.0.

m1 - 192.168.20.1
m2 - 192.168.20.2

On m2 ->
$ sudo ovs-vsctl set-manager tcp:192.168.20.1:6640
$ sudo ovs-vsctl show
38bc233b-7431-4aad-aefd-9155aff54ad4
Manager "tcp:192.168.20.1:6640"
ovs_version: "2.5.0"

On m1 ->
$ sudo ovsdb-client -v list-dbs tcp:192.168.20.2:6640
2016-12-30T09:23:13Z|1|poll_loop|DBG|wakeup due to 0-ms timeout
2016-12-30T09:23:13Z|2|poll_loop|DBG|wakeup due to
[POLLOUT][POLLERR][POLLHUP] on fd 3 (192.168.20.2:36486<->) at
../lib/stream-fd.c:151
ovsdb-client: failed to connect to "tcp:192.168.20.2:6640" (Connection
refused)
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

[Shravan S K]

Thanks, Scott.

Beautiful explanation in the post!

Shravan

On 28 December 2016 at 21:29, Scott Lowe <scott.l...@scottlowe.org> wrote:

> Please see my responses inline, prefixed by [SL].
>
>
> On Dec 28, 2016, at 4:15 AM, Shravan S K <sra9...@gmail.com> wrote:
> >
> > I am trying this - http://docs.openvswitch.org/
> en/latest/howto/userspace-tunneling/
> >
> > 1) Which step connects vxlan interface,vxlan0, to the bridge,br-phy, as
> shown in the diagram ?
>
>
> [SL] I haven't worked with userspace tunneling yet, but I believe the
> principles here are much the same as with a "traditional" kernel-mode
> implementation. Traffic from the vxlan0 port on br-int is directed out the
> physical interfaces attached to br-phy via the kernel's routing table
> (which is why step #5 is necessary).
>
> This article may help you understand the various traffic patterns you may
> encounter with OVS:
>
> <http://blog.scottlowe.org/2013/05/15/examining-open-
> vswitch-traffic-patterns/>
>
>
> > 2) What should I do if also want to access(from the VM) the network that
> my host is in ?
>
>
> [SL] You would need to either a) add an additional interface to the VM, or
> b) create a VXLAN-to-VLAN gateway. In the case of a), this additional
> interface would need to be connected to br-phy (or its equivalent). In the
> case of b), this would be another system (guest or VM) that receives VXLAN
> traffic and handles decapsulation of the traffic and placement onto a VLAN
> outside the overlay.
>
> I hope this helps.
>
> --
> Scott
>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

[Shravan S K]

I am trying this -
http://docs.openvswitch.org/en/latest/howto/userspace-tunneling/

1) Which step connects vxlan interface,vxlan0, to the bridge,br-phy, as
shown in the diagram ?

2) What should I do if *also* want to access(from the VM) the network that
my host is in ?

Thanks.

Shravan

On 28 December 2016 at 11:13, Shravan S K <sra9...@gmail.com> wrote:

> I found info in this http://openvswitch.org/releases/NEWS-2.6.0
>
>
>
>
> Shravan
>
> On 28 December 2016 at 11:07, Shravan S K <sra9...@gmail.com> wrote:
>
>> Does OVS 2.5.0 support VXLANs ?
>>
>>
>>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

[Shravan S K]

I found info in this http://openvswitch.org/releases/NEWS-2.6.0




Shravan

On 28 December 2016 at 11:07, Shravan S K <sra9...@gmail.com> wrote:

> Does OVS 2.5.0 support VXLANs ?
>
>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] VXLAN support in OVS 2.5.0

[Shravan S K]

Does OVS 2.5.0 support VXLANs ?
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OVN vs Distributed vSwitches

[Shravan S K]

On 14 December 2016 at 00:47, Ben Pfaff  wrote:

> OVN is an SDN controller.
>
> > Most SDN controllers are platforms.  OVN is an application.
>

Could you clarify this, please?

And, is microsegmentation(for example VMWare NSX, Cisco ACI) possible using
OVN?

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

Re: [ovs-discuss] OVN vs Distributed vSwitches

[Shravan S K]

I didn't understand clearly. Could you please elaborate ?

What is the role of an SDN Controller(where does it come into the picture)
in an Open Virtual Network (OVN) ?

In the OVN architecture, does the CMS specify the kind of
functionality(like routing, load balancing, ACLs, QoS) that is needed from
the underlying network ?


On 13-Dec-2016 22:06, "Ben Pfaff" <b...@ovn.org> wrote:

On Tue, Dec 13, 2016 at 09:52:38PM +0530, Shravan S K wrote:
> And can you please compare the OVN Controller to an SDN controller(say
> Floodlight) ?

Most SDN controllers are platforms.  OVN is an application.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OVN vs Distributed vSwitches

[Shravan S K]

The example that you mentioned, isn't it the same as what VXLAN can do ?

And can you please compare the OVN Controller to an SDN controller(say
Floodlight) ?

On 13-Dec-2016 20:59, "Scott Lowe" <scott.l...@scottlowe.org> wrote:

Please see my response below.


> On Dec 13, 2016, at 4:08 AM, Shravan S K <sra9...@gmail.com> wrote:
>
> How is OVN related to distributed virtual switches like the VMware
vNetwork distributed switch or the Cisco Nexus 1000V ?


OVN is intended to add network virtualization functionality to OVS. With
network virtualization via OVN, you can build logical network topologies
that are independent of the underlying physical network topology. Thus, you
could create a logical switch (a logical L2 domain) that spans multiple L3
segments in the physical network (as an example). Distributed virtual
switches such as the vSphere Distributed Switch or the Cisco Nexus 1000V do
not have this functionality.

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