Hi Mauricio,
The hop-by-hop collection and processing of buffer occupancy, queue depth,
transit delays is not implemented.
M-Anycast focused on end to end delay by using timestamp in IOAM.
You could implement these 3 elements into the existing IOAM implementation
without having to update IOAM
.
> ]
> Do you have develop plan to update the VPP to the IOAM latest
version,including
> IPV6 Hop-by-hop option?
>
> Thanks,
> Davi
>
>
>
>
>
> At 2019-06-06 07:58:22, "Shwetha bhandari via Lists.Fd.Io&q
Hi Mojtaba,
Following up on your earlier thread, did you get a chance to see if IOAM decap
is failing?
Perhaps we can get on a quick webex on Monday and resolve this?
Thanks,
Shwetha
From: on behalf of "mojtaba.eshghi"
Date: Friday, August 2, 2019 at 1:40 PM
To: "vpp-dev@lists.fd.io"
Hi Mojtaba,
I suspect that this is due to IOAM decap being broken in 18.01+. Removal of
IOAM metadata added at the IOAM decap node depends on the ACL match whose
result is checked during v6 hbh processing. If decap fails IOAM options are
leaked to host2 in the setup below. Linux kernel network
Hi Davi,
We have an reference implementation of In-situ OAM (IOAM) in VPP -
https://docs.fd.io/vpp/18.07/ioam_plugin_doc.html, that provides Inband network
telemetry being defined at IETF -
https://tools.ietf.org/html/draft-ietf-ippm-ioam-data-05.
IOAM and P4 INT both are defined to provide a
Neha,
I tried this [1] and it works with output like this [2] in the latest VPP
branch. You should follow the instructions in
https://wiki.fd.io/view/VPP/Python_API for setting up python VPP module and
running the script.
I will update the wiki with this.
Thanks,
Shwetha
1]
from vpp_papi
IOAM trace timestamp is 4 bytes. So it always returns the least significant 4
bytes of milli, micro or nanoseconds specified by trace-tsp.
We have not yet implemented the long format timestamps yet.
For performance, the IOAM trace timestamp is populated using cpu time stamp
counter and
Hi Neha,
You should provide the PID of the process that wants to receive the callbacks
for the want apis not the PID of the vpp.
Look at the API documentation /src/vpp /stats/stats.api. Something like
pid=os.getpid() instead of the VPP PID in the code snippet below will fix it.
Also the
Hi Hadi,
Good to know!
Classification is needed for encap and decap not for transit processing.
Transit processes the options if present. Transit nodes only need node-id and
application data if trace option includes it.
Thanks,
Shwetha
From: HADI SHAIKHZAKER
Date: Thursday, July 5, 2018 at 7:57
Hi Hadi,
> set ioam rewrite trace-type 0x1f trace-elts 4 trace-tsp 1 node-id 0x1
> app-data 0x1234
To setup the node id and app-data that is needed on transit and decap you need
a trace profile configs:
Example: set ioam-trace profile trace-type 0x9 trace-elts 3 trace-tsp 2 node-id
0x2
I see
10 matches
Mail list logo
