[ovs-dev] [PATCH v2 2/2] ovn-trace: New --ovs option to also print OpenFlow flows.
Han Zhou
zhouhan at gmail.com
Mon Dec 12 07:55:03 UTC 2016
Thanks Ben, this is very useful!
On Fri, Dec 9, 2016 at 10:56 PM, Ben Pfaff <blp at ovn.org> wrote:
> diff --git a/ovn/utilities/ovn-trace.8.xml b/ovn/utilities/ovn-trace.8.xml
> index 92dcb17..776f69a 100644
> --- a/ovn/utilities/ovn-trace.8.xml
> +++ b/ovn/utilities/ovn-trace.8.xml
> @@ -255,6 +255,65 @@
> <dd>
> Selects all three forms of output.
> </dd>
> +
> + <dt><code>--ovs</code>[<code>=</code><var>remote</var>]</dt>
> + <dd>
> + <p>
> + Makes <code>ovn-trace</code> attempt to obtain and display the
OpenFlow
> + flows that correspond to each OVN logical flow. To do so,
> + <code>ovn-trace</code> connects to <var>remote</var> (by default,
> + <code>unix:@RUNDIR@/br-int.mgmt</code>) over OpenFlow and
retrieves the
> + flows. If <var>remote</var> is specified, it must be an active
> + OpenFlow connection method described in
<code>ovs-ofctl</code>(8).
> + </p>
> +
> + <p>
> + Keep in mind a few important aspects of the difference between
logical
> + flows and OpenFlow:
> + </p>
> +
> + <ul>
> + <li>
> + Each logical flow maps to one or more OpenFlow flows. An
actual
> + packet ordinarily matches only one of these, although in some
cases
> + it can more than one of these flows (which is not a problem
because
typo: it can match ...
More information about the dev
mailing list