Arista has an open RFE (#184550) for this internally. You can use that to "me too" to your AM/SE
On Mon, Jan 7, 2019 at 3:51 PM Sander Steffann <[email protected]> wrote: > Hi, > > > 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. > > I like it! > Sander > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
