https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/ODLTOOLS-25 odltools <p>Hi,</p> <p>Currently, we are using following ofproto/trace command to trace to flow pipeline for the southbound device (openvswitch). The trace output doesn't carry any granular information about the flow table.</p> <p>ovs-appctl ofproto/trace $br_name "in_port=$in_port,$proto,dl_src=$dl_src,dl_dst=$dl_dst,nw_src=$nw_src,nw_dst=$nw_dst</p> <p>Since Netvirt carries neutron-north-bound information, would it possible to add the odltool feature to trace flow from source to destination similar like ofproto/trace command and includes granular information about the flow table details and flows.</p> <p>In this way, odltools helps to troubleshoot the flowpipeline w.r.t southbound devices. I appreciate if anyone has other alternative solution on it.</p> <p>Regards,<br/> Pradipta</p> ODLTOOLS-25

Use odltools to collect Netvirt flow trace from source to destination [L2 & L3]

Epic Medium To Do Unresolved Tim Rozet Pradipta Sahoo Wed, 12 Dec 2018 02:34:35 +0000 Wed, 12 Dec 2018 12:02:40 +0000 0 1 <p>Hi,</p> <p>For ovs flow trace, I made following small script which helps to trace flow pipeline and flow table information w.r.t specific source and destination. But we need a similar feature from odltools which helps to diagnose the Netvirt flow pipeline.</p> <p><a href="https://github.com/pradiptapks/nfv-sdn-troubleshooting/blob/master/ovs-trace.sh" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/pradiptapks/nfv-sdn-troubleshooting/blob/master/ovs-trace.sh</a></p> <p>Regards,<br/> Pradipta</p> Development Rank 0|i03lfj: