<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<div><!-- This file has been automatically generated. See web/README.md -->
<div>
<div>
<div style="direction: ltr;">Hi Ben,</div>
<div><br>
</div>
<div style="direction: ltr;">The ovsdb transaction log indeed shows geneve and vxlan interfaces being specified with “type” field. Perhaps the “type” coming out empty is just a cosmetic issue of “ovs-vsctl list” command.</div>
</div>
<div><br>
</div>
<div class="ms-outlook-ios-signature">
<div style="direction: ltr;">Best Regards,</div>
<div style="direction: ltr;">Paul Greenberg</div>
</div>
</div>
<div> </div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="dir="ltr""><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Ben Pfaff <blp@ovn.org><br>
<b>Sent:</b> Saturday, November 10, 2018 3:27 PM<br>
<b>To:</b> Paul Greenberg<br>
<b>Cc:</b> ovs-discuss@openvswitch.org<br>
<b>Subject:</b> Re: Interface Type in Interface Table of OVS DB
<div> </div>
</font></div>
There's no way that ovs-vswitchd can know to create a geneve or vxlan <br>
interface unless the database tells it to do so. <br>
<br>
Can you provide a copy of your ovs-vswitchd.conf.db, and the output of <br>
ovs-appctl dpif/show? <br>
<br>
Thanks, <br>
<br>
Ben. <br>
<br>
On Sat, Nov 10, 2018 at 07:56:08PM +0000, Paul Greenberg wrote: <br>
> Ben, <br>
> <br>
> It is 100% like that. In my case ovn-controller creates these geneve and vxlan interfaces, but it looks like that information never gets to Interface table, because “type” is empty there.
<br>
> <br>
> Best Regards, <br>
> Paul Greenberg <br>
> <br>
> ________________________________ <br>
> From: Ben Pfaff <blp@ovn.org> <br>
> Sent: Saturday, November 10, 2018 2:29 PM <br>
> To: Paul Greenberg <br>
> Cc: ovs-discuss@openvswitch.org <br>
> Subject: Re: Interface Type in Interface Table of OVS DB <br>
> <br>
> On Sat, Nov 10, 2018 at 07:15:02PM +0000, Paul Greenberg wrote: <br>
> > Hi Ben, <br>
> > <br>
> > Noticed the following behavior. <br>
> > <br>
> > When I run "ovs-vsctl list Interface", I get: <br>
> > <br>
> > > type : internal <br>
> > <br>
> > only for the bridge interface. The rest of the interface types are empty: <br>
> > <br>
> > > type : "" <br>
> > <br>
> > When I run "ovs-appctl dpif/show", the types are showing up properly, i.e. system, geneve, vxlan.
<br>
> > <br>
> > ovs_version: "2.10.90" <br>
> > <br>
> > Do you think this is a cosmetic bug? <br>
> <br>
> I don't know any way you can have vxlan or geneve ports without setting <br>
> the interface type to vxlan or geneve. Please check again. <br>
</div>
</body>
</html>