[ovs-discuss] connecting switches
bhhics at rit.edu
Wed Jun 21 16:36:18 UTC 2017
Thanks for the reply - I am giving GRE a whirl with ESXi (GRE seems to be the choice for most). I haven't had much luck so far but it does seem counter-intuitive especially when dealing with traffic that does not have an IP header. It seems like L2TP might be a better option for connecting layer 2 spaces together.
Professor, IST Dept., RIT
bhhics at rit.edu
CONFIDENTIALITY NOTE: The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information.
From: Justin Pettit <jpettit at ovn.org>
Sent: Saturday, June 17, 2017 5:29 PM
To: Bruce Hartpence
Cc: ovs-discuss at openvswitch.org
Subject: Re: [ovs-discuss] connecting switches
> On Jun 16, 2017, at 6:19 PM, Bruce Hartpence <bhhics at rit.edu> wrote:
> Hello all - I am working on a use case for ovs with multiple hypervisors. I am using ODL Carbon for the controller and can get all OVS instances to appear in DLUX but I am missing the boat on interconnecting the switches themselves. So, VMs on the different hypervisors cannot communicate. The documentation suggests that patch interfaces can be used to handle this but it appears to be for bridge instances on the same OVS VM.
Yes, patch ports are just used to connect bridge instances on the same hypervisor. You'll want to use tunnels to connect between hypervisors. You should be able to find plenty of tutorials online.
More information about the discuss