Hi Lenny, Are you trying to use these apis to control in-band packet tracing documented here - https://docs.fd.io/vpp/17.01/ioam_plugin_doc.html? If yes: It is part of the plugin package - dpkg-deb -c vpp-plugins_17.01*.deb : ./usr/share/vpp/api/trace.api.json trace_profile_apply is no longer used: instead you can use ioam_enable api and set the flow for trace using classifier apis with hit-next index set to ip6-add-hop-by-hop node.
Thanks, Shwetha From: <vpp-dev-boun...@lists.fd.io> on behalf of Lenny Lyytinen <len...@checkpoint.com> Date: Sunday, February 19, 2017 at 3:32 PM To: Lenny Lyytinen <len...@checkpoint.com>, "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] Trace methods removed from vpp_papi? Any help with this matter would be appreciated. Thanks, Lenny From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Lenny Lyytinen Sent: 14 February 2017 15:17 To: vpp-dev@lists.fd.io Subject: [vpp-dev] Trace methods removed from vpp_papi? Hey, Before VPP 17.01, I remember vpp_papi offered methods to control the packet tracer: def trace_profile_add(id, trace_type, trace_num_elt, trace_ppc, trace_tsp, trace_app_data, pow_enable, node_id, async = False) def trace_profile_apply(id, dest_ipv6, prefix_length, vrf_id, trace_op, enable, async = False) def trace_profile_del(id, async = False) In 17.01 they’re no longer recognized, and they’re not listed in any /usr/share/vpp/api/*.api.json file, however in the source I can find plugins/ioam/lib-trace/trace.api which mentions these methods. Is there a reason that they’re excluded from the installation, or am I missing something and I can still control the packet tracer somehow with vpp_papi? Thanks, Lenny
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
