<dt><code>external_ids:ovn-encap-type</code></dt>
<dd>
- The encapsulation type that a chassis should use to connect to this
- node. Supported tunnel types for connecting hypervisors are
- <code>geneve</code> and <code>stt</code>. Gateways may use
- <code>geneve</code>, <code>vxlan</code>, or <code>stt</code>.
+ <p>
+ The encapsulation type that a chassis should use to connect to
+ this node. Multiple encapsulation types may be specified with
+ a comma-separated list. Each listed encapsulation type will
+ be paired with <code>ovn-encap-ip</code>.
+ </p>
+
+ <p>
+ Supported tunnel types for connecting hypervisors
+ are <code>geneve</code> and <code>stt</code>. Gateways may
+ use <code>geneve</code>, <code>vxlan</code>, or
+ <code>stt</code>.
+ </p>
+
+ <p>
+ Due to the limited amount of metadata in <code>vxlan</code>,
+ the capabilities and performance of connected gateways will be
+ reduced versus other tunnel formats.
+ </p>
</dd>
<dt><code>external_ids:ovn-encap-ip</code></dt>
<dd>
- The IP address that a chassis should use to connect to this node using
- encapsulation type specified by <code>external_ids:ovn-encap-ip</code>.
+ The IP address that a chassis should use to connect to this node
+ using encapsulation types specified by
+ <code>external_ids:ovn-encap-type</code>.
</dd>
<dt><code>external_ids:ovn-bridge-mappings</code></dt>
</dd>
<dt>
- <code>external-ids:ovn-patch-port</code> in the <code>Port</code> table
+ <code>external-ids:ovn-localnet-port</code> in the <code>Port</code>
+ table
</dt>
<dd>
<p>
<p>
Each <code>localnet</code> logical port is implemented as a pair of
patch ports, one in the integration bridge, one in a different
- bridge, with the same <code>external-ids:ovn-patch-port</code> value.
+ bridge, with the same <code>external-ids:ovn-localnet-port</code>
+ value.
</p>
</dd>
</dl>
<dd>
Causes <code>ovn-controller</code> to gracefully terminate.
</dd>
+
+ <dt><code>ct-zone-list</code></dt>
+ <dd>
+ Lists each local logical port and its connection tracking zone.
+ </dd>
</dl>
</p>