Hello all,
Just a heads-up that the plugin 'tracepath' has been recently introduced [1].
This plugin aims to facilitate troubleshooting with packet traces by adding
post-processing CLI commands "show trace paths / show trace path <idx>", which
respectively display VPP graph paths present in the current trace, and enables
filtering trace output to only show entries matching a specific VPP graph path.
vpp# trace add pg-input 100
vpp# show trace paths
Found 2 unique paths across all threads (showing top 2):
[0] Count: 7 ID: 0x00000007c61bef93 Length: 7 Threads: [0]
Path: pg-input -> ethernet-input -> ip4-input -> ip4-lookup -> ip4-drop
-> error-drop -> drop
[1] Count: 5 ID: 0x0000000707c1f778 Length: 7 Threads: [0]
Path: pg-input -> ethernet-input -> ip4-input -> ip4-lookup ->
ip4-rewrite -> pg1-output -> pg1-tx
vpp# show trace path 0
# Display all trace entries matching path [0] above..
More usage example can be found in the docs [2]. Thanks to folks for their
review/discussions around this plugin (Benoit Ganne, Guillaume Solignac, Yoann
Desmouceaux, Paul Ponchon)
[1] https://gerrit.fd.io/r/c/vpp/+/44754
[2] https://s3-docs.fd.io/vpp/26.06/developer/plugins/tracepath.html
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#27023): https://lists.fd.io/g/vpp-dev/message/27023
Mute This Topic: https://lists.fd.io/mt/119526717/21656
Group Owner: [email protected]
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/14379924/21656/631435203/xyzzy
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
