diff options
| author |   Filip Tehlar <ftehlar@cisco.com> | 2021-07-23 08:51:10 +0000 |
|---|---|---|
| committer | Filip Tehlar <ftehlar@cisco.com> | 2021-09-28 16:06:19 +0000 |
| commit | 36217e3ca8a1ca2e7a341b6b44ffc25e6497191c (patch) | |
| tree | ba45e2b144e0d66a69c0502a7823c28239d0bc66 /docs/gettingstarted/developers | |
| parent | 3459ece6da90627b161e2128b5926f1e58e7db65 (diff) | |
api: API trace improvements
Type: improvement
* add support for JSON format in API trace
* add ability to replay JSON API trace in both VPP and VAT2
* use CRC for backward compatibility check during JSON API replay
* fix API trace CLI (and remove duplicits)
* remove custom dump
* remove vppapitrace.py
* update docs accordingly
Change-Id: I5294f68bebe6cbe738630f457f3a87720e06486b
Signed-off-by: Filip Tehlar <ftehlar@cisco.com>
Signed-off-by: Ole Troan <ot@cisco.com>
Diffstat (limited to 'docs/gettingstarted/developers')
| -rw-r--r-- | docs/gettingstarted/developers/binary_api_support.rst | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/docs/gettingstarted/developers/binary_api_support.rst b/docs/gettingstarted/developers/binary_api_support.rst index 732ce978daa..f93bbc296fc 100644 --- a/docs/gettingstarted/developers/binary_api_support.rst +++ b/docs/gettingstarted/developers/binary_api_support.rst @@ -206,11 +206,10 @@ out the set of plugins: .. code-block:: console - DBGvpp# api trace custom-dump /tmp/api_trace - vl_api_trace_plugin_msg_ids: abf_54307ba2 first 846 last 855 - vl_api_trace_plugin_msg_ids: acl_0d7265b0 first 856 last 893 - vl_api_trace_plugin_msg_ids: cdp_8f707b96 first 894 last 895 - vl_api_trace_plugin_msg_ids: flowprobe_f2f0286c first 898 last 901 + DBGvpp# api trace dump /tmp/api_trace + vl_api_trace_plugin_msg_ids: arp_cfdf7292 first 49 last 56 + vl_api_trace_plugin_msg_ids: ip6_nd_ac628462 first 57 last 69 + vl_api_trace_plugin_msg_ids: rd_cp_8a996e86 first 70 last 71 <etc> Here, we see the "abf," "acl," "cdp," and "flowprobe" plugins. Use the @@ -239,7 +238,7 @@ __________________________ Along the same lines, it may be necessary to manufacture [simulated] physical interfaces so that an API trace will replay correctly. "show interface" on the trace origin system can help. An API trace -"custom-dump" as shown above may make it obvious how many loopback +dump as shown above may make it obvious how many loopback interfaces to create. If you see vhost interfaces being created and then configured, the first such configuration message in the trace will tell you how many physical interfaces were involved. |