[ovs-discuss] Connecting 2 separated OvS

[Scott Lowe]

Please see my responses inline, prefixed with [SL].

On 06/01/2018 06:35 AM, Jose Carlos Ferreira de Melo Junior wrote:
> Yes,  the final idea is connect them to a openflow controller and then
> generate some isolated trafic among them.
> 
> But I dont know how it would be logically. For example: to connect one
> OvS bridge to another OvS bridge I heard about patch port but I think
> it's not working.


[SL] It is my understanding that patch ports are only for connecting OVS
bridges on the same system, not between systems.


> how can I be sure the connection really works? I don't know if Im
> missing something


[SL] From a control plane (switch to controller) perspective, OVS will
provide some feedback about whether a connection to the controller was
successful (I believe some feedback is provided via `ovs-vsctl`, other
commands may provide even more information).

From a data plane perspective, I guess you'll just need to set up the
environment and then use the appropriate tools (tcpdump, etc.) to verify
that the traffic is flowing as expected. OVS has some additional tools
that will help here as well, like `ovs-dpctl`. The man pages for OVS
will be very helpful in determining the best ways to verify if traffic
is behaving as you expect/intend.


> 2018-06-01 8:55 GMT-03:00 Scott Lowe <scott.lowe at scottlowe.org
> <mailto:scott.lowe at scottlowe.org>>:
> 
>     On 06/01/2018 05:41 AM, Jose Carlos Ferreira de Melo Junior wrote:
>> 
>> Hello everyone,
>> 
>> I'm new in the house so I have some doubts.
>> 
>> How can I connect 2 or more separated OvS bridges? 
>> 
>> When I say separated I really mean in OvS on different VM
> 
> 
>     From a data plane perspective, you can connect them in the same way you
>     would go about connecting multiple physical switches together. For
>     example, you could use an interface from your VM (say, eth1) and connect
>     that to the OVS bridge running in the VM. That interface is then
>     connected to your hypervisor's switching functionality, which in turn
>     connects it to the physical network. All three OVS bridges are now part
>     of the same L2 broadcast domain.
> 
>     From a control plane perspective, you'd (typically) need to use an
>     OpenFlow controller if you wanted them to act as a single (logical)
>     switch consisting of multiple (virtual) switches.
> 
>     I hope this helps.


-- 
Scott

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20180601/04de5923/attachment.sig>