You can use CLI mtrace commands to trace information about multicast paths. This section covers the following mtrace commands:
For more information about the mtrace commands, see the JUNOS Protocols, Class of Service, and System Basics Command Reference.
To display information about a multicast path from a source to a receiver, enter the mtrace from-source command with the following syntax. Table 72 describes the mtrace from-source command options.
user@host> mtrace from-source source host <<extra-hops number> | <group address>
| <interval seconds>
| <max-hops number>
| <max-queries number>
| <response host>
| <ttl number> | <wait-time seconds>> <loop> <multicast-response | unicast-response>
<no-resolve> <no-router-alert>
<brief | detail>
Table 72: CLI mtrace from-source Command Options
Following is sample output from the mtrace from-source command:
user@host> mtrace from-source source 192.1.4.1
group 224.1.1.1
Mtrace from 192.1.4.1 to 192.1.30.2 via group 224.1.1.1
Querying full reverse path... * *
0 ? (192.1.30.2)
-1 ? (192.1.30.1) PIM thresh^ 1
-2 routerC.mycompany.net (192.1.40.2) PIM thresh^ 1
-3 hostA.mycompany.net (192.1.4.1)
Round trip time 22 ms; total ttl of 2 required.
Waiting to accumulate statistics...Results after 10 seconds:
Source Response Dest Overall Packet Statistics For Traffic From
192.1.4.1 192.1.30.2 Packet 192.1.4.1 To 224.1.1.1
v __/ rtt 16 ms Rate Lost/Sent = Pct Rate
192.168.195.37
192.1.40.2 routerC.mycompany.net
v ^ ttl 2 0/0 = -- 0 pps
192.1.40.1
192.1.30.1 ?
v \__ ttl 3 ?/0 0 pps
192.1.30.2 192.1.30.2
Receiver Query Source
Each line of the trace display is usually in the following format (depending on the options selected and the responses from the routers along the path):
hop-number host (ip-address) protocolttl
Table 73 summarizes the output fields of the display.
![]() |
The packet statistics gathered from Juniper Networks routers and routing nodes are always displayed as 0. |
Table 73: CLI mtrace from-source Command Display Summary
To monitor and display multicast trace operations, enter the mtrace monitor command:
user@host> mtrace monitor
Mtrace query at Apr 21 16:00:54 by 192.1.30.2, resp to 224.0.1.32, qid 2a83aa packet from 192.1.30.2 to 224.0.0.2 from 192.1.30.2 to 192.1.4.1 via group 224.1.1.1 (mxhop=60) Mtrace query at Apr 21 16:00:57 by 192.1.30.2, resp to 224.0.1.32, qid 25dc17 packet from 192.1.30.2 to 224.0.0.2 from 192.1.30.2 to 192.1.4.1 via group 224.1.1.1 (mxhop=60) Mtrace query at Apr 21 16:01:00 by 192.1.30.2, resp to same, qid 20e046 packet from 192.1.30.2 to 224.0.0.2 from 192.1.30.2 to 192.1.4.1 via group 224.1.1.1 (mxhop=60) Mtrace query at Apr 21 16:01:10 by 192.1.30.2, resp to same, qid 1d25ad packet from 192.1.30.2 to 224.0.0.2 from 192.1.30.2 to 192.1.4.1 via group 224.1.1.1 (mxhop=60)
This example displays only mtrace queries. When the Services Router captures an mtrace response, the display is similar, but the complete mtrace response is also displayed—exactly as it is displayed in mtrace from-source command output.
Table 74 summarizes the output fields of the display.
Table 74: CLI mtrace monitor Command Display Summary