On 07/01/2019 17:00, Saku Ytti wrote:
Hey,
I somewhat recently discovered https://tools.ietf.org/html/rfc5837
Exec summary: your traceroute will show the ingress ifindex where
packet came in, allowing you to discriminate LAG/bundle/ae interfaces
and determine actual path in network with ease.
It seems like massively useful feature for modern networks where LAG
is rule, not exception, much more useful than widely supported MPLS
labels.
If you do agree, and have some leverage, please ping your account team
and make enhancement request.
Thanks!
Are there traceroute implementation had patch for it? last time I
checked (5 years or so), there isn't any. Though we did complained to
our vendor about it.
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
