diff options
| author | Donald Sharp <sharpd@cumulusnetworks.com> | 2018-04-24 20:08:06 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-04-24 20:08:06 -0400 |
| commit | 97722e560ecaf87125aff5a56e247b7952ef8105 (patch) | |
| tree | 7df81db10dcf62dd04772ffb4a8ee35acb9ee8b5 /doc/manpages | |
| parent | b5b9eedbb2fc0e205335a4c86f13073185fef4a7 (diff) | |
| parent | 71e55fb257a1849523d8de382f5c7ab4c429afd9 (diff) | |
Merge pull request #2110 from msablic/pim_mtrace_group
pimd: adding querying of state to mtrace
Diffstat (limited to 'doc/manpages')
| -rw-r--r-- | doc/manpages/mtracebis.rst | 19 |
1 files changed, 12 insertions, 7 deletions
diff --git a/doc/manpages/mtracebis.rst b/doc/manpages/mtracebis.rst index b4d57c1b97..d3ba8036d8 100644 --- a/doc/manpages/mtracebis.rst +++ b/doc/manpages/mtracebis.rst @@ -9,17 +9,22 @@ SYNOPSIS ======== |PROGRAM| |synopsis-options-hv| -|PROGRAM| <multicast source> +|PROGRAM| <multicast source> [<multicast group>] DESCRIPTION =========== -|PROGRAM| is a program to initiate multicast traceroute, or "mtrace", queries. +|PROGRAM| is a program for initiating multicast traceroute, or "mtrace", queries. -The initial version of the program requires multicast source IP address and -initiates a weak traceroute across the network. This tests whether the -interfaces towards the source are multicast enabled. The first query sent is a -full query, capable of crossing the network all the way to the source. If this -fails, hop-by-hop queries are initiated. +It can initiate two types of mtrace queries: weak and group. + +Weak tests whether the interfaces towards the source are multicast enabled and is +initiated by supplying only the multicast source address. + +Group tests whether there is multicast routing protocol state for particular +multicast group and is initiated by supplying mutlicast source and group. + +The first query sent is a full query, capable of crossing the network all the way +to the source. If this fails, hop-by-hop queries are initiated. Hop-by-hop queries start by requesting only a response from the nearest router. Following that, next query is extended to the next two routers, and so on... |