[ovs-discuss] About the Hardware VTEP emulator

[Mark Maglana]

I set up another instance of this emulated VTEP and tried to connect it to
a controller. When I looked at the manager UI, the "physical ports" are
listed as follows:

[image: Inline image 1]

I'm confused by that second table. Why are the two "physical ports" listed
under Port Number 0?

Regards,

Mark



On Fri, Aug 8, 2014 at 6:15 PM, Mark Maglana <mmaglana at gmail.com> wrote:

> Thank you for clarifying!
>
>
> On Friday, August 8, 2014, Gurucharan Shetty <shettyg at nicira.com> wrote:
>
>> On Thu, Aug 7, 2014 at 9:35 PM, Mark Maglana <mmaglana at gmail.com> wrote:
>> > Hi,
>> >
>> > I'm currently trying out the hardware VTEP emulator that came with OVS
>> > v2.1.2 and wanted to check if I correctly understand how it works:
>> >
>> > 1. I use OVS to create and manage a bridge which will serve as the fake
>> VTEP
>> Yes. And then this bridge is added as a record in the physical_switch
>> table of VTEP schema.
>> Information at
>>
>> >
>> > 2. the python script ovs-vtep synchronizes that fake VTEP with whatever
>> gets
>> > written to the hardware_vtep database (since OVS has no idea of the
>> latter)
>> Yes.
>> More information of setup here: vtep/README.ovs-vtep
>> >
>> > Below is a link to a diagram I created after reading the documentation.
>> Is
>> > this correct?
>> >
>> > https://dl.dropboxusercontent.com/u/1355795/vtepemulator.JPG
>>
>> If "eth2" is how you connect your VTEP to other nodes like
>> Hypervisors, then you should not add it to "br0".
>> Keep an IP address at eth2.
>>
>> This will be the IP address you add with
>> vtep-ctl set Physical_Switch br0 tunnel_ips=192.168.0.3
>> As mentioned in the README.
>>
>> I see a block called "VM" in your diagram. I suppose that is meant to
>> be the "physical_port" of the VTEP. If so, that is correct. You add
>> that interface name as a port using ovs-vsctl to the VTEP bridge and
>> also add it using "vtep_ctl" to VTEP's "physical_port" table.
>>
>> >
>> > NOTE: I'm instantiating the host via Vagrant + VirtualBox which uses
>> eth0 by
>> > default for SSH access. I wanted to leave that alone which is why I have
>> > eth1 for management (host-only networking) and eth2 for data (internal
>> > networking). No controller listening on the management network (yet).
>> >
>> > Regards,
>> >
>> > Mark
>> >
>> > _______________________________________________
>> > discuss mailing list
>> > discuss at openvswitch.org
>> > http://openvswitch.org/mailman/listinfo/discuss
>> >
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20140811/2d7949b9/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2014-08-11 at 4.03.14 PM.png
Type: image/png
Size: 118460 bytes
Desc: not available
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20140811/2d7949b9/attachment-0002.png>