So this is what I am doing.

I am enabling the global netvirt option to use OF tunnels. This makes netvirt make the TZs VTEPs with that option. Let's say I have 2 nodes so 2 VTEPs.

I see the corresponding logical tunnel interfaces in IETF config interfaces.

> {
> "interfaces": {
> "interface": [
>

{ > "name": "tunca6ebf5c4f6", > "odl-interface:datapath-node-identifier": 17826645854953, > "type": "iana-if-type:tunnel", > "enabled": true, > "odl-interface:tunnel-interface-type": "odl-interface:tunnel- > type-vxlan", > "odl-interface:tunnel-source": "172.19.0.3", > "odl-interface:monitor-enabled": true, > "odl-interface:monitor-interval": 1000, > "odl-interface:tunnel-destination": "172.19.0.2", > "odl-interface:tunnel-remote-ip-flow": true, > "odl-interface:monitor-protocol": "odl-interface:tunnel- > monitoring-type-bfd", > "odl-interface:tunnel-gateway": "0.0.0.0", > "odl-interface:internal": true, > "description": "VXLAN Trunk Interface" > }

,
>

{ > "name": "tun3141ddab506", > "odl-interface:datapath-node-identifier": 22984997280292, > "type": "iana-if-type:tunnel", > "enabled": true, > "odl-interface:tunnel-interface-type": "odl-interface:tunnel- > type-vxlan", > "odl-interface:tunnel-source": "172.19.0.2", > "odl-interface:monitor-enabled": true, > "odl-interface:monitor-interval": 1000, > "odl-interface:tunnel-destination": "172.19.0.3", > "odl-interface:tunnel-remote-ip-flow": true, > "odl-interface:monitor-protocol": "odl-interface:tunnel- > monitoring-type-bfd", > "odl-interface:tunnel-gateway": "0.0.0.0", > "odl-interface:internal": true, > "description": "VXLAN Trunk Interface" > }

,
>

{ > "name": "71e6cfd9-cb83-4827-a244-2adbda5857c9", > "type": "iana-if-type:l2vlan", > "odl-interface:l2vlan-mode": "trunk", > "enabled": true, > "odl-interface:parent-interface": "tap71e6cfd9-cb" > }

,
>

{ > "name": "d4bbeeba-c062-45d7-9bdd-89114b978705", > "type": "iana-if-type:l2vlan", > "odl-interface:l2vlan-mode": "trunk", > "enabled": true, > "odl-interface:parent-interface": "tapd4bbeeba-c0" > }

> ]
> }
> }

I see none in the IETF operational interfaces.

> {
> "interfaces-state": {
> "interface": [
>

{ > "name": "tap71e6cfd9-cb", > "phys-address": "0a:d5:5e:b4:3e:9b", > "admin-status": "up", > "oper-status": "up", > "lower-layer-if": [ > "openflow:22984997280292:1" > ] > }

,
>

{ > "name": "71e6cfd9-cb83-4827-a244-2adbda5857c9", > "type": "iana-if-type:l2vlan", > "admin-status": "up", > "phys-address": "0a:d5:5e:b4:3e:9b", > "if-index": 1, > "oper-status": "up", > "lower-layer-if": [ > "openflow:22984997280292:1" > ] > }

,
>

{ > "name": "d4bbeeba-c062-45d7-9bdd-89114b978705", > "type": "iana-if-type:l2vlan", > "admin-status": "up", > "phys-address": "a2:28:e2:58:35:18", > "if-index": 2, > "oper-status": "up", > "lower-layer-if": [ > "openflow:17826645854953:1" > ] > }

,
>

{ > "name": "tapd4bbeeba-c0", > "phys-address": "a2:28:e2:58:35:18", > "admin-status": "up", > "oper-status": "up", > "lower-layer-if": [ > "openflow:17826645854953:1" > ] > }

> ]
> }
> }

In Genius child interface info, I see both VTEPS as child of other two tunnel interfaces:

> {
> "interface-child-info": {
> "interface-parent-entry": [
> {
> "parent-interface": "tun1403f28cf31",
> "interface-child-entry": [
>

{ > "child-interface": "tunca6ebf5c4f6" > }

> ]
> },
> {
> "parent-interface": "tapd4bbeeba-c0",
> "interface-child-entry": [
>

{ > "child-interface": "d4bbeeba-c062-45d7-9bdd-89114b978705" > }

> ]
> },
> {
> "parent-interface": "tun0eae2df36ea",
> "interface-child-entry": [
>

{ > "child-interface": "tun3141ddab506" > }

> ]
> },
> {
> "parent-interface": "tap71e6cfd9-cb",
> "interface-child-entry": [
>

{ > "child-interface": "71e6cfd9-cb83-4827-a244-2adbda5857c9" > }

> ]
> }
> ]
> }
> }

Looking at one node, the flow based tunnel is there:

> 41883803-1d4e-4a5c-8c87-a1403f97f966
> Manager "tcp:172.28.128.1:6640"
> is_connected: true
> Bridge br-int
> Controller "tcp:172.28.128.1:6653"
> is_connected: true
> fail_mode: secure
> Port br-int
> Interface br-int
> type: internal
> Port "tap71e6cfd9-cb"
> Interface "tap71e6cfd9-cb"
> Port "tun0eae2df36ea"
> Interface "tun0eae2df36ea"
> type: vxlan
> options:

{key=flow, local_ip="172.19.0.2", > remote_ip=flow}

> ovs_version: "2.6.1"

But no handling for it on Table 0:

> cookie=0x8000000, duration=15.065s, table=0, n_packets=6, n_bytes=480,
> priority=4,in_port=1
> actions=write_metadata:0x10000000000/0xffffff0000000001,goto_table:17
> cookie=0x8040000, duration=13.779s, table=17, n_packets=3,
> n_bytes=230, priority=9,metadata=0x10000000000/0xffffff0000000000
> actions=load:0x1-
> >NXM_NX_REG1[0..19],write_metadata:0xa000011389000000/0xffffffffff
> fffffe,goto_table:48
> cookie=0x8000000, duration=15.536s, table=17, n_packets=0, n_bytes=0,
> priority=0,metadata=0x8000000000000000/0xf000000000000000
> actions=write_metadata:0x9000000000000000/0xf000000000000000,goto_tab
> le:80