Control Path Trace
==================

Commands
========
   netq trace <mac> [vlan <1-4096>] from <hostname> [vrf <vrf>] [around <text-time>] [json]
   netq trace <ip> from (<hostname>|<ip-src>) [vrf <vrf>] [around <text-time>] [json]

Usage
=====
netq trace provides control path tracing (no real packets are sent) from
a specified source to a specified destination. The trace covers complete
end-to-end path tracing including bridged, routed and Vxlan overlay paths.
ECMP is supported as well as checking for forwarding loops, MTU consistency
across all paths, and VLAN consistency across all paths. The trace also
covers that the path from dest to src also exists on each hop.

cumulus@torc-12:~$ netq trace 27.0.0.22 from 27.0.0.21
torc-12 -- torc-12:swp3 -- spine-1:swp5 -- torc-21:lo
        -- torc-12:swp4 -- spine-2:swp5 -- torc-21:lo

When tracing data, only the egress information is shown as this information
is gathered by looking at the routing table. In this case, there are two paths
(one through spine01 and one through spine02) because the environment is
leveraging equal cost routing.

You can trace by MAC as well:
cumulus@leaf1:~$ netq trace 00:02:00:00:00:02 vlan 1009 from leaf1
leaf1 -- leaf1:sw_clag200 -- spine1:sw_clag300 -- edge2
                          -- spine1:sw_clag300 -- edge1:VlA-1
      -- leaf1:sw_clag200 -- spine2:sw_clag300 -- edge1:VlA-1
                          -- spine2:sw_clag300 -- edge2
cumulus@leaf1:~$

Legend
======
Any errors are shown in red. Bridged paths are always in WHITE, routed paths
in GREEN, the VTEPs are shown in BLUE. A node in error is shown in RED.
