[ODLTOOLS-25] Use odltools to collect Netvirt flow trace from source to destination [L2 & L3] Created: 12/Dec/18 Updated: 12/Dec/18 |
|
| Status: | To Do |
| Project: | odltools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Epic | Priority: | Medium |
| Reporter: | Pradipta Sahoo | Assignee: | Tim Rozet |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Hi, 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. 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 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. In this way, odltools helps to troubleshoot the flowpipeline w.r.t southbound devices. I appreciate if anyone has other alternative solution on it. Regards, |
| Comments |
| Comment by Pradipta Sahoo [ 12/Dec/18 ] |
|
Hi, 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. https://github.com/pradiptapks/nfv-sdn-troubleshooting/blob/master/ovs-trace.sh Regards, |