On Wed, Sep 6, 2017 at 8:51 AM Jakub Sitnicki <[email protected]> wrote:
> ovn-trace example refers to a non-existent output port. Correct it.
>
> Fixes: 46a2dc58781a ("Document OVN support in ovs-sandbox.")
> Signed-off-by: Jakub Sitnicki <[email protected]>
>
Acked-By: Mark Michelson <[email protected]>
> ---
> Documentation/tutorials/ovn-sandbox.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/tutorials/ovn-sandbox.rst
> b/Documentation/tutorials/ovn-sandbox.rst
> index d47fcf5..d1e749f 100644
> --- a/Documentation/tutorials/ovn-sandbox.rst
> +++ b/Documentation/tutorials/ovn-sandbox.rst
> @@ -136,7 +136,7 @@ Using ovn-trace
> Once you have configured resources in OVN, try using ``ovn-trace`` to see
> how OVN would process a sample packet through its logical pipeline.
>
> -For example, we can trace an IP packet from ``sw0-port1`` to
> ``sw0-port2``.
> +For example, we can trace an IP packet from ``sw0-port1`` to
> ``sw1-port1``.
> The ``--minimal`` output shows each visible action performed on the
> packet,
> which includes:
>
> --
> 2.9.5
>
> _______________________________________________
> dev mailing list
> [email protected]
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev
>
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
