No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

CLI-based Configuration Guide - IP Multicast

AR500, AR510, AR531, AR550, AR1500, and AR2500 V200R010

This document describes the concepts and configuration procedures of IP Service features on the device, and provides the configuration examples.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Using Tracert to Check Multicast Service Performance

Using Tracert to Check Multicast Service Performance

Context

During multicast service troubleshooting and routine maintenance, run the mtrace command to collect traffic information, which helps you locate the failure points and reduce configuration errors. You can also perform tracert tests multiple times to figure out rates of multicast flows.

Before running the mtrace command, run the mtrace query-policy command to filter the unicast Internet Group Management Protocol (IGMP) Tracert Query packets.

Procedure

  • Run the mtrace [ -l [ stat-times ] [ -st stat-int ] | -m max-ttl | [ -mr | -ur resp-dest ] | -q nqueries | -tr ttl | -ts ttl | -v | -vpn-instance vpn-instance-name | -w timeout ] * source source-address command to trace the reverse path forwarding (RPF) path from a multicast source to the querier.
  • Run the mtrace -g group [ -l [ stat-times ] [ -st stat-int ] | -m max-ttl | [ -mr | -ur resp-dest ] | -q nqueries | -tr ttl | -ts ttl | -v | -vpn-instance vpn-instance-name | -w timeout ] * source source-address command to trace the multicast path from a multicast source to the querier.

  • Run the mtrace { -gw last-hop-router | -d } -r receiver [ -a source-ip-address | -l [ stat-times ] [ -st stat-int ] | -m max-ttl | [ -mr | -ur resp-dest ] | -q nqueries | -tr ttl | -ts ttl | -v | -vpn-instance vpn-instance-name | -w timeout ] * source source-address command to trace the RPF path from a multicast source to a destination host.
  • Run the mtrace { -gw last-hop-router | -b | -d } -r receiver -g group [ -a source-ip-address | -l [ stat-times ] [ -st stat-int ] | -m max-ttl | [ -mr | -ur resp-dest ] | -q nqueries | -tr ttl | -ts ttl | -v | -vpn-instance vpn-instance-name | -w timeout ] * source source-address command to trace the multicast path from a multicast source to a destination host.

Follow-up Procedure

Run the display mtrace statistics command to display statistics about an mtrace test instance. After multiple MTrace tests are performed, the accumulated statistics make the analysis result inaccurate. In this case, run the reset mtrace statistics command to reset MTrace statistics.

Translation
Download
Updated: 2019-08-09

Document ID: EDOC1100034230

Views: 121292

Downloads: 37

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next