[ovs-dev] [PATCH] FAQ: Add troubleshooting procedure and example.

Justin Pettit jpettit at nicira.com
Thu Feb 14 00:31:42 UTC 2013


On Feb 13, 2013, at 9:36 AM, Ben Pfaff <blp at nicira.com> wrote:

> +       - "ovs-appctl ofproto/trace" to observe the logic behind how
> +         ovs-vswitchd treats packets.  See ovs-vswitchd(8) for
> +         documentation.  The ofproto/trace input format makes it easy
> +         to cut and paste flows output by "ovs-dpctl dump-flows", to
> +         find out more details about a given flow.

I don't know if that final comma is necessary.

> +       4. Use "ovs-appctl ofproto/trace", cutting and pasting the ARP
> +          flow from "ovs-dpctl dump-flows" output, to observe details
> +          of how ovs-vswitchd determined the actions in the "ovs-dpctl
> +          dump-flows" output

Most people won't need to do this step unless it's being directed to the wrong place.  Maybe preface this paragraph with "If the datapath flows are not what you expect, use…"

The last sentence should end with a period.

> +       8. Use "ovs-appctl ofproto/trace", cutting and pasting the ARP
> +          flow from "ovs-dpctl dump-flows" output, to observe details
> +          of how ovs-vswitchd determined the actions in the "ovs-dpctl
> +          dump-flows" output

Same comments as step 4.

Thanks for writing this up!

--Justin





More information about the dev mailing list