Administrator Guide
Scenario Output
 -3 2.2.2.1 PIM - 
99.99.0.0/16 
 -4 * * * * 
--------------------------------------------------------------
----
If there is no response for mtrace even after 
switching to expanded hop search, the 
command displays an error message.
R1>mtrace 99.99.99.99 1.1.1.1
Type Ctrl-C to abort.
Querying reverse path for source 99.99.99.99 to destination 
1.1.1.1 via RPF
From source (?) to destination (?)
 * * * * switching to hop-by-hop:
--------------------------------------------------------------
---
|Hop| OIF IP |Proto| Forwarding Code |Source Network/
Mask|
--------------------------------------------------------------
---
 0 1.1.1.1 --> Destination
 -1 * * * * 
--------------------------------------------------------------
----
Timed out receiving responses
Perhaps no local router has a route for source, the receiver 
is not
a member of the multicast group or the multicast ttl is too 
low.
While traversing the path from source to 
destination, if the mtrace packet exhausts 
the maximum buer size of the packet, then 
NO SPACE error is displayed in the output. 
You can initiate a new mtrace query by 
specifying the destination as the last IP 
address from the output of the previous 
trace query.
R1>mtrace 99.99.99.99 1.1.1.1
Type Ctrl-C to abort.
Querying reverse path for source 99.99.99.99 to destination 
1.1.1.1 via RPF
From source (?) to destination (?)
--------------------------------------------------------------
---
|Hop| OIF IP |Proto| Forwarding Code |Source Network/
Mask|
--------------------------------------------------------------
---
 0 1.1.1.1 --> Destination
 -1 1.1.1.1 PIM - 
99.99.0.0/16 
 -2 101.101.101.102 PIM - 
99.99.0.0/16 
 -3 2.2.2.1 PIM - 
99.99.0.0/16 
 .
 .
 .
-146 17.17.17.17 PIM No space in packet 99.99.0.0/16
--------------------------------------------------------------
----
In a valid scenario, mtrace request packets 
are expected to be received on the OIF of the 
node. However, due to incorrect formation of 
the multicast tree, the packet may be 
received on a wrong interface. In such a 
R1>mtrace 6.6.6.6 4.4.4.5 
Type Ctrl-C to abort.
Querying reverse path for source 6.6.6.6 to destination 
4.4.4.5 via RPF
From source (?) to destination (?)
544 Multicast Features










