White Papers

Table Of Contents
Table 62. Mtrace Scenarios (continued)
Scenario Output
-1 5.5.5.4 PIM Wrong Last-Hop
6.6.6.0/24
-2 20.20.20.2 PIM 6.6.6.0/24
-3 10.10.10.1 PIM 6.6.6.0/24
-4 6.6.6.6 --> Source
---------------------------------------------------------
---------
If a router in the network does not
process mtrace and drops the packet
resulting in no response, the system
performs an expanding-hop search to
trace the path to the router that has
dropped mtrace. The output of the
command displays a * indicating that
no response is received for an mtrace
request. The following message appears
when the system performs a hop-by-hop
search: switching to hop-by-hop:
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 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
-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 buffer size of
the packet, then NO SPACE error is
displayed in the output. You can initiate
a new mtrace query by specifying the
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 (?)
Multicast Features 559