L3 path traces can be done using traceroute so the value of NetBrain’s path trace is not in its ability to render L3 path traces visually but to show the underlying L2 path.
It would be useful to have a switch/button in NetBrain GUI and also API to render path traces in L2 right away.
Currently we can only start an L3 path trace via API and run some device/link checks on the path using a DVT but it’s not of much use given that L2 path is often different from L3 path.
With a switch as mentioned above, we could trigger a path trace directly in L2, so the DVT checks applied to L2 links would make much more sense and be more useful for troubleshooting.