[ovs-discuss] OVS supported hardware switches
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
How to do the IP connectivity part using OVS internal ports? Thanks. Shravan On 16 January 2017 at 04:40, Scott Lowe wrote: > On 01/13/2017 03:20 AM, Shravan S K wrote: > > My motive is to simulate VXLAN functionality on a bigger topology using > > mininet. > > My plan - As Mininet uses OVS bridges to simulate vswitch functionality, > > we can use ovs-vsctl to configure VXLAN functionality on the bridges. I > > thought let me try for a simple topology without using Mininet and just > > using OVS on a single host and 2 VMs. If it works, then I can make a > > similar configuration for a bigger topology using mininet. > > > > OVS on a single host and 2 VMs : vm1-br1---br2-vm2 > > I am confused on how to perform the vxlan config for the above setup. > > > > If the above one works, I could try on the mininet topologies. > > For the mininet topology ( --topo=linear,2 ) > > h1 - s1 -- s2 h2 (h1,h2 are hosts, s1,s2 are switches - > > actually ovs bridges) > > > Setting aside the mininet question for the moment, the way to get VXLAN > working between two OVS bridges is to establish an IP endpoint (also > known as a VXLAN Tunnel Endpoint, or VTEP) for each bridge. So, in your > example configuration, br1 and br2 each need an interface (of some sort) > with an IP address. You'd then configure a VXLAN port on br1 that points > to the IP endpoint for br2, and configure a VXLAN port on br2 that > points to the IP endpoint for br1. Since you're trying to do this within > a single host, you might consider using OVS internal ports as the IP > endpoints for each bridge. As long as each IP endpoint can reach the > other, then in theory it should work. > > -- > Scott > > ___ > 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] VXLAN support in OVS 2.5.0
My motive is to simulate VXLAN functionality on a bigger topology using mininet. My plan - As Mininet uses OVS bridges to simulate vswitch functionality, we can use ovs-vsctl to configure VXLAN functionality on the bridges. I thought let me try for a simple topology without using Mininet and just using OVS on a single host and 2 VMs. If it works, then I can make a similar configuration for a bigger topology using mininet. OVS on a single host and 2 VMs : vm1-br1---br2-vm2 I am confused on how to perform the vxlan config for the above setup. If the above one works, I could try on the mininet topologies. For the mininet topology ( --topo=linear,2 ) h1 - s1 -- s2 h2 (h1,h2 are hosts, s1,s2 are switches - actually ovs bridges) *$ ovs-vsctl show * ad172f01-511d-46fe-9022-d23de31e06e2 Bridge "s2" Controller "ptcp:6635" fail_mode: standalone Port "s2-eth2" Interface "s2-eth2" Port "s2" Interface "s2" type: internal Port "s2-eth1" Interface "s2-eth1" Bridge "s1" Controller "ptcp:6634" fail_mode: standalone Port "s1-eth2" Interface "s1-eth2" Port "s1" Interface "s1" type: internal Port "s1-eth1" Interface "s1-eth1" ovs_version: "2.5.0" In the mininet console, *mininet>net* h1 h1-eth0:s1-eth1 h2 h2-eth0:s2-eth1 s1 lo: s1-eth1:h1-eth0 s1-eth2:s2-eth2 s2 lo: s2-eth1:h2-eth0 s2-eth2:s1-eth2 As the vxlan configuration part is related to OVS, I am asking in this forum, rather than the mininet forum. Thanks. Shravan On 13 January 2017 at 11:08, Scott Lowe wrote: > I would still echo Raymond's suggestion: use VirtualBox to create two > "hosts" running OVS and connect them via a VXLAN tunnel over standard VBox > networking. You can use network namespaces (as Justin suggested) on the VMs > running OVS to simulate connecting to OVS since VBox doesn't support nested > virtualization. > > You can take a look at <https://github.com/lowescott/learning-tools> to > see if there is a Vagrant environment I've already created that might help > you in this situation. > > -- > Scott > > Sent from my mobile device > > On Jan 12, 2017, at 9:46 PM, Shravan S K wrote: > > 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 > 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-boun...@openvswitch.org] *On Behalf Of *Shravan S K >> *Sent:* Thursday, January 12, 2017 22:34 >> *To:* Scott Lowe >> *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" 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 > > <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]
Re: [ovs-discuss] VXLAN support in OVS 2.5.0
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 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 > *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" 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 > <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 <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 <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 possible to create a VXLAN setup using just bridges created > > >>> by OVS? (using
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" 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 > <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 <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 <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 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
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 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 > <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
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 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
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 wrote: > Thanks, Scott. > > Beautiful explanation in the post! > > Shravan > > On 28 December 2016 at 21:29, Scott Lowe wrote: > >> Please see my responses inline, prefixed by [SL]. >> >> >> On Dec 28, 2016, at 4:15 AM, Shravan S K 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
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 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] ovsdb-client transact not working
Hello,
I executed the following ovsdb-client transact command, please check.
--
root@shravan-desktop:/home/shravan# ovsdb-client transact tcp:
192.168.3.20:6640 '["Open_vSwitch",{"op":"insert", "table":"Bridge",
"row":{"name":"br2"}}]'
[{"uuid":["uuid","336f112b-0fbc-4594-aed9-eb86a6d9c35c"]}]
root@shravan-desktop:/home/shravan# ovsdb-client dump 192.168.3.20:6640
Open_vSwitch Bridge
Bridge table
_uuidauto_attach
controller datapath_iddatapath_type
datapath_version external_ids fail_mode flood_vlans flow_tables ipfix
mcast_snooping_enable mirrors name netflow other_config
ports
protocols rstp_enable rstp_status sflow status stp_enable
---
-- -- -
- --- --- -
- --- - ---
--
- --- --- - -- --
7e995cf0-097c-42e3-ba0c-a5c51295a26e []
[21160d2d-144e-4e35-a275-dd21f74e904b] "f25c997ee342" ""
"" {} [][] {} []
false [] "br0" [] {}
[26e7da53-237b-47f0-9e81-545cd302f028,
68eb5030-4e92-4419-a1e4-3b1635981887, f908152e-421e-48bd-b31e-f5794d4c6e8f]
[]false {} []{} false
---
Why is the uuid (336f112b-0fbc-4594-aed9-eb86a6d9c35c) of br2 not showing
in the dump ?
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] ovs-vsctl using ovsdb-client
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
Thanks, Flavio. Shravan On 30 December 2016 at 21:15, Flavio Leitner wrote: > On Fri, 30 Dec 2016 14:59:27 +0530 > Shravan S K 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
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
Thanks, Scott. Beautiful explanation in the post! Shravan On 28 December 2016 at 21:29, Scott Lowe wrote: > Please see my responses inline, prefixed by [SL]. > > > On Dec 28, 2016, at 4:15 AM, Shravan S K 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
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 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 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
I found info in this http://openvswitch.org/releases/NEWS-2.6.0 Shravan On 28 December 2016 at 11:07, Shravan S K 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
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
I apologise for your frustration, Ben. I had gone through the OVN architecture and a few videos posted on OVS YouTube channel. I just was not able to put it all together. Great effort in the documentation. I shall go through the architecture doc again and come back with specific questions. Shravan On 15 December 2016 at 22:27, Ben Pfaff wrote: > On Thu, Dec 15, 2016 at 02:59:28PM +0530, Shravan S K wrote: > > 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? > > I've written thousands of words about OVN, and given many talks about > it, and it's very frustrating to get general questions that show that > the person asking hasn't bothered to read or view any of it. > > Ask a specific question. > ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] OVN vs Distributed vSwitches
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
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" 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
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" wrote: Please see my response below. > On Dec 13, 2016, at 4:08 AM, Shravan S K 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
[ovs-discuss] OVN vs Distributed vSwitches
How is OVN related to distributed virtual switches like the VMware vNetwork distributed switch or the Cisco Nexus 1000V ? -- Shravan ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
