You can use the ovs-appctl command to configure logging. There's a man page for it that you'd probably want to look at.
--Justin On Sep 17, 2012, at 4:02 PM, kashyap TA <kashyap...@gmail.com> wrote: > Thanks Ben for the reply. Can you please let me know how can I enable the > logging module? Is there a CLI to enable it or do we need to make some > changes in the code? Would this give a packet to packet log as to whats > happening? Please do let me know. > > Thanks and Regards > Kashyap > > On Mon, Sep 17, 2012 at 1:32 PM, Ben Pfaff <b...@nicira.com> wrote: > On Mon, Sep 17, 2012 at 11:09:53AM -0700, kashyap TA wrote: > > I am not sure if this is the right forum to put this question across, If > > its not, I apologize. I have an issue where I have an Encaped packet coming > > on a interface on Fedora 17. I can see the packet when I do tcpdump . That > > packet is supposed to go to OVS and then get directed towards the slow path > > as this is the first packet, and should show up in my controller. The > > packet never shows up in the controller. Can some one help me debug this? > > I enabled some logs using ovs-appctl and I dont see any log for this > > packet. Is there a log to print every packet that goes through ovs? One > > thing to note is that the packet snap type is 136. Would that cause OVS to > > drop it or something? Please let me know. Any kind of help will help.. :-) > > I'd look for the packet in the "dpif" log module and for a > corresponding flow in "ovs-dpctl dump-flows" output. > > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
