Users Guide

Table 71. mtrace Command Output Explained (continued)
Command Output Description
From source (?) to destination (?)
In case the provided source or destination IP can be resolved to a
hostname the corresponding name will be displayed. In cases where
the IP cannot be resolved, it is displayed as (?)
0 1.1.1.1 --> Destination
The first row in the table corresponds to the destination provided by
the user.
-1 1.1.1.1 PIM Reached RP/Core
103.103.103.0/24
The information in each of the response blocks is displayed as follows:
o (-1) Hop count is always a negative number to indicate reverse
path
o (1.1.1.1) Outgoing interface address at that node for the source
and group
o (PIM) Multicast protocol used at the node to retrieve the
information
o (Reached RP/Core) Forwarding code in mtrace to denote that
RP node is reached
o (103.103.103.0/24) Source network and mask. In case (*G) tree
is used, this field will have the value as (shared tree). In case no
value is noted in the record or in case of error like No Route or
Wrong Last Hop the value (default) will be displayed
-4 103.103.103.3 --> Source The last line in the table corresponds to the source address provided
by the user.
Supported Error Codes
Error codes denote problems in the network that has caused the mtrace query to fail.
These codes not only provide error information but also provide general information such as RP node reachability information.
The response data block filled in by the last-hop router contains a Forwarding code field. Forwarding code can be added at any
node and is not restricted to the last hop router. This field is used to record error codes before forwarding the response to the
next neighbor in the path towards the source. In a response data packet, the following error codes are supported:
Table 72. Supported Error Codes
Error Code Error Name Description
0x00 NO_ERROR No error
0x01 WRONG_IF Traceroute request arrived on the wrong
interface. The router does not use this
interface to forward packets to the
source, group, and destination.
0x05 NO_ROUTE The router has no route for the source
or group and cannot determine a
potential route.
0x06 WRONG_LAST_HOP The router is not the proper last-hop
router.
0x08 REACHED_RP Reached Rendezvous Point or Core.
0x09 RPF_IF Traceroute request arrived on the
expected RPF interface for this source
and group.
0x0A NO_MULTICAST Traceroute request arrived on an
interface which is not enabled for
multicast.
Multicast Features 573