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

NE40E V800R010C10SPC500 Feature Description - System Monitor 01

This is NE40E V800R010C10SPC500 Feature Description - System Monitor
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).
MTrace

MTrace

A multicast trace route (MTrace) test instance monitors a multicast forwarding path from a multicast source to the current router or a destination host and collects statistics about routers along the multicast forwarding path.

MTrace is based on a multicast-enabled network, such as a Layer 3 multicast network that has Protocol Independent Multicast (PIM) configured, Rosen MVPN, or NG MVPN.

MTrace probes a multicast forwarding path by sending query messages. Query messages fall into IGMP tracert query messages, IGMP tracert request messages, and IGMP tracert response messages.
  • A device sends an IGMP tracert query message to query the last-hop device on a multicast forwarding path.

  • An IGMP tracert request message completely inherits an IGMP tracert query message, with a response data block being added to the end of the message.

  • An IGMP tracert response message completely inherits an IGMP tracert request message, with only the message type field changed.

Figure 5-18 MTrace usage scenarios

MTrace applies to the following scenarios.

  • An MTrace test instance detects a reverse path forwarding (RPF) path from a multicast source to the current router (when the current router is the last-hop multicast device to a destination host).

    1. The current router queries the previous-hop device on the RPF path and sends an IGMP tracert request message to it.

    2. After receiving the IGMP tracert request message, the previous-hop router adds a response data block containing information about the interface receiving this IGMP tracert request message and sends the message to its previous-hop router. The router of each hop adds a response data block to the IGMP tracert request message and sends the message upstream.

    3. When the first-hop router connected with the multicast source receives the IGMP tracert request message, it also adds a response data block and sends an IGMP tracert response message to the current router.

    4. After receiving the IGMP tracert response message, the current router parses it and obtains information about the RPF path from the multicast source to the destination host. This can clearly reflect the RPF path status.

    5. If the IGMP tracert request message cannot reach the first-hop router because of some errors, an IGMP tracert response message is directly sent to the current router. The current router then parses the data block information to locate the faulty node. In this way, faulty node monitoring is implemented.

  • An MTrace test instance detects a multicast path from a multicast source to the current router (when the current router is the last-hop multicast device to a destination host).

    1. The current router queries the previous-hop device on the multicast path and sends an IGMP tracert request message to it.

    2. After receiving the IGMP tracert request message, the previous-hop router adds a response data block containing information about the interface receiving this IGMP tracert request message and sends the message to its previous-hop router. The router of each hop adds a response data block to the IGMP tracert request message and sends the message upstream.

    3. When the first-hop router connected with the multicast source receives the IGMP tracert request message, it also adds a response data block and sends an IGMP tracert response message to the current router.

    4. After receiving the IGMP tracert response message, the current parses it and obtains information about the multicast path from the multicast source to the destination host. This can clearly reflect the multicast path status.

    5. If the IGMP tracert request message cannot reach the first-hop router because of some errors, an IGMP tracert response message is directly sent to the current router. The current router then parses the data block information to locate the faulty node. In this way, faulty node monitoring is implemented.

  • An MTrace test instance detects an RPF path from a multicast source to a destination host (when the current router is not the last-hop multicast device to a destination host).

    1. The current router sends an IGMP tracert query message to query the last-hop router connected with the destination host.

    2. After receiving the IGMP tracert query message, the last-hop router adds a response data block containing its device information, constructs an IGMP tracert request message, and sends the message to its previous-hop router. The router of each hop adds a response data block to the IGMP tracert request message and sends the message upstream.

    3. When the first-hop router connected with the multicast source receives the IGMP tracert request message, it also adds a response data block and sends an IGMP tracert response message to the current router.

    4. After receiving the IGMP tracert response message, the current router parses it and obtains information about the RPF path from the multicast source to the destination host and each router on the path. This can clearly reflect the RPF path status and statistics of each router on the path.

    5. If the IGMP tracert request message cannot reach the first-hop router because of some errors, an IGMP tracert response message is directly sent to the current router. The current router then parses the data block information to locate the faulty node. In this way, faulty node monitoring is implemented.

  • An MTrace test instance detects a multicast path from a multicast source to a destination host (when the current router is not the last-hop multicast device to a destination host).

    1. The current router sends an IGMP tracert query message to query the last-hop router connected with the destination host.

    2. After receiving the IGMP tracert query message, the last-hop router adds a response data block containing its device information, constructs an IGMP tracert request message, and sends the message to its previous-hop router. The router of each hop adds a response data block to the IGMP tracert request message and sends the message upstream.

    3. When the first-hop router connected with the multicast source receives the IGMP tracert request message, it also adds a response data block and sends an IGMP tracert response message to the current router.

    4. After receiving the IGMP tracert response message, the current router parses it and obtains information about the multicast path from the multicast source to the destination host and each router on the path. This can clearly reflect the multicast path status and statistics of each router on the path.

    5. If the IGMP tracert request message cannot reach the first-hop router because of some errors, an IGMP tracert response message is directly sent to the current router. The current router then parses the data block information to locate the faulty node. In this way, faulty node monitoring is implemented.

If the current router is not the last-hop multicast device to a destination host, an IGMP tracert query message sent to the last hop supports the following encapsulation modes.
  • The unicast address of the last-hop router is known: The IP address of the last-hop router is set as the destination address of the message. The current router encapsulates a unicast IGMP tracert query message.
  • The addresses of the last-hop router and destination host are unknown, but the current router directly connects to the destination host: 224.0.0.2 is set as the destination address of the message, and the TTL value is set to 1. The current router encapsulates an IGMP tracert query message and sends it to all routers on the same network segment to find the last-hop router.
  • The address of the last-hop router is unknown but the unicast address of the destination host is known: The IP address of the destination host is set as the destination address of the message. The current router encapsulates an IGMP tracert query message. The message must contain the IP option Router Alert.
  • The address of the last-hop router is unknown but the unicast address of the destination host is known, and the current router is in the multicast forwarding tree: The multicast group address is set as the destination address, and the multicast source address is set as the source address. The current router encapsulates an IGMP tracert query message. The message is forwarded along the multicast or RPF path and finally arrives at the last-hop router.
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055050

Views: 5642

Downloads: 29

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