•
Source Network/Mask — source mask
Example of the
mtrace
Command to View the Network Path
The following is an example of tracing a multicast route.
R1>mtrace 103.103.103.3 1.1.1.1 226.0.0.3
Type Ctrl-C to abort.
Querying reverse path for source 103.103.103.3 to destination 1.1.1.1 via group 226.0.0.3
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 Reached RP/Core 103.103.103.0/24
-2 101.101.101.102 PIM - 103.103.103.0/24
-3 2.2.2.1 PIM - 103.103.103.0/24
-4 103.103.103.3 --> Source
------------------------------------------------------------------
The following table explains the output of the mtrace command:
Table 46. mtrace Command Output — Explained
Command Output
Description
Querying reverse path for source
103.103.103.3 to destination 1.1.1.1 via
group 226.0.0.3
mtrace traverses the reverse path from the given destination to the given
source for the given group
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.
Multicast Features
521
Содержание S3048-ON
Страница 1: ...Dell Configuration Guide for the S3048 ON System 9 11 2 5 ...
Страница 137: ...0 Gi 1 1 Gi 1 2 rx Flow N A N A 0 0 No N A N A yes Access Control Lists ACLs 137 ...
Страница 142: ...Figure 10 BFD Three Way Handshake State Changes 142 Bidirectional Forwarding Detection BFD ...
Страница 241: ...Dell Control Plane Policing CoPP 241 ...
Страница 287: ... RPM Synchronization GARP VLAN Registration Protocol GVRP 287 ...
Страница 428: ...Figure 53 Inspecting the LAG Configuration 428 Link Aggregation Control Protocol LACP ...
Страница 429: ...Figure 54 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 429 ...
Страница 432: ...Figure 56 Inspecting a LAG Port on BRAVO Using the show interface Command 432 Link Aggregation Control Protocol LACP ...
Страница 433: ...Figure 57 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 433 ...
Страница 477: ...Figure 73 Configuring Interfaces for MSDP Multicast Source Discovery Protocol MSDP 477 ...
Страница 478: ...Figure 74 Configuring OSPF and BGP for MSDP 478 Multicast Source Discovery Protocol MSDP ...
Страница 479: ...Figure 75 Configuring PIM in Multiple Routing Domains Multicast Source Discovery Protocol MSDP 479 ...
Страница 483: ...Figure 77 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 483 ...
Страница 484: ...Figure 78 MSDP Default Peer Scenario 3 484 Multicast Source Discovery Protocol MSDP ...
Страница 634: ...protocol spanning tree pvst no disable vlan 300 bridge priority 4096 634 Per VLAN Spanning Tree Plus PVST ...
Страница 745: ...Figure 104 Single and Double Tag TPID Match Service Provider Bridging 745 ...
Страница 746: ...Figure 105 Single and Double Tag First byte TPID Match 746 Service Provider Bridging ...