mhorner Fri, 09/17/2010 - 10:21


To trace the path from a source to a destination branch for a multicast distribution tree, use the mtrace user EXEC command.

mtrace source [destination] [group]

Syntax Description


DNS name or the IP address of the multicast-capable source. This is a unicast address of the beginning of the path to be traced.


(Optional) DNS name or address of the unicast destination. If omitted,  the mtrace starts from the system at which the command is typed.


(Optional) DNS name or multicast address of the group to be traced.  Default address is (the group used for MBONE Audio). When  address is used, the software invokes a weak mtrace. A weak mtrace is one that follows the RPF path to the source, regardless of whether  any router along the path has multicast routing table state.

Command Mode


Usage Guidelines

This command first appeared in Cisco IOS Release 11.0.

The trace request generated by the mtrace command  is multicast to the multicast group to find the last hop router to the  specified destination. The trace then follows the multicast path from  destination to source by passing the mtrace request packet via unicast  to each hop. Responses are unicast to the querying router by the first  hop router to the source. This command allows you to isolate multicast  routing failures.

If no arguments are entered, the router will interactively prompt you for them.

This command is identical in function to the UNIX version of mtrace.

Sample Display

The following is sample output from the mtrace command:

Router# mtrace

Type escape sequence to abort.

Mtrace from to via group

From source (?) to destination (?)

Querying full reverse path... 


-1 PIM  thresh^ 0  0 ms  

-2 PIM  thresh^ 0  2 ms  

-3 PIM  thresh^ 0  894 ms  

-4 PIM  thresh^ 0  893 ms  

-5 PIM  thresh^ 0  894 ms  

-6 PIM  thresh^ 0  893 ms 

describes the fields shown in the display.

Table 71     Mtrace Field Descriptions


Mtrace from to via group

Name and address of source, destination, and group for which routes are being traced.


Hops away from destination (-3) and address of intermediate router.

PIM thresh^ 0

Multicast protocol in use on this hop, and ttl threshold.

893 ms

Time taken for trace to be forwarded between hops.

Mani Ganesan Tue, 09/21/2010 - 03:15

Do you want to know the purpose of mtrace or how it works internally ?

When I dug up a littile bit on how it works , I got this :

Mtrace use special IGMP packet type (Queries and Response) IGMP 1F and 
1E. Requestor send packet to ther last-hop router. This router add some
usefull parameters such as IF, OF, input packet count, out packet count,
query time and many other. Then router send traceroute Request to the
next-hop (out to Input Interface for SPT or shared tree) and each hop add
same data to the packet. This packet extend as unicasts. At the end first-hop
router send IGMP Response to the requestor.



This Discussion