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

AR Router Troubleshooting Guide

This Product Documentation provides guidance for maintaining AR Enterprise Router, covering common information collection and fault diagnostic commands, typical fault troubleshooting guide, and troubleshooting.
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).
The RPT on a PIM-SM Network Fails to Forward Data

The RPT on a PIM-SM Network Fails to Forward Data

Common Causes

This fault is commonly caused by one of the following causes:

  • The unicast route from the multicast device to the RP is unavailable.

  • The RP addresses on multicast devices are inconsistent.

  • The downstream interface on the multicast device does not receive any (*, G) Join messages.

  • PIM-SM is not enabled on interfaces.

  • The RPF route to RP is incorrect, for example, the unicast route contains a loop.

  • Configurations are incorrect, for example, the configurations of the TTL, MTU, or multicast boundary are improper.

Troubleshooting Flowchart

After a PIM-SM network is configured, the RPT cannot forward data.

Figure 20-4 shows the troubleshooting flowchart.

Figure 20-4  Troubleshooting flowchart: the RPT on a PIM-SM network fails to forward data

Troubleshooting Procedure

NOTE:

Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel.

Procedure

  1. Check that the PIM routing table contains correct (*, G) entries.

    Run the display pim routing-table group-address command on the device to check whether the PIM routing table contains correct (*, G) entries. Focus on checking whether the downstream interface list contains downstream interfaces to forward data to all (*, G) group members.

    • If the (*, G) entries exist and are all correct in the PIM routing table, run the display multicast forwarding-table group-address command every 15 seconds to check whether the forwarding table contains (S, G) entries associated with the (*, G) entries and whether the value of the Matched field in the command output keeps increasing.

      • If the forwarding table contains associated (S, G) entries and the value of the Matched field keeps increasing, it indicates that the upstream device can normally forward multicast data to the current device but the current device fails to forward the data downstream, for example, a too small TTL value or a forwarding fault.

      • If the forwarding table does not contain associated (S, G) entries or the value of the Matched field remains unchanged, do as follows:
        • If the current device is not an RP, it indicates that the current device has not received any multicast data. The fault may be caused by the upstream device. Then check whether the PIM routing table on the upstream device contains correct (S, G) entries.

        • If the current device is already an RP, it indicates the RPT has been set up but the RP fails to receive the multicast data from the multicast source. The fault may be caused by a failure in source's DR registration. In such a case, go to Step 10.

    • If the PIM routing table does not contain correct (*, G) entries, go to Step 2.

  2. Check that the downstream interface has received Join messages.

    Run the display pim control-message counters interface interface-type interface-number message-type join-prune command to check whether the number of received Join/Prune messages on the downstream interface keeps increasing.

    • If the number of received Join/Prune messages on the downstream interface does not increase, run the display pim control-message counters interface interface-type interface-number message-type join-prune command on the downstream device to check whether the downstream device has sent Join/Prune messages upstream.
      • If the command output shows that the number of sent Join/Prune messages keeps increasing, it indicates that the downstream device has sent Join/Prune messages. The fault may be caused by a failure in PIM neighbor communication. In such a case, go to Step 10.

      • If the command output shows that the number of sent Join/Prune messages does not increase, it indicates the downstream device experiences a fault. Then locate the fault.

    • If the number of received Join/Prune messages on the downstream interface keeps increasing, go to Step 3.

  3. Check that PIM-SM is enabled on interfaces.

    The following interfaces are easy to be ignored in enabling PIM-SM:
    • RPF neighboring interface to the RP

    • RPF interface to the RP

    • Interface directly connected to shared network segment of user hosts, that is, downstream interface of the receiver's DR

    Run the display pim interface verbose command to check PIM configurations on the interface. Focus on checking whether PIM-SM is enabled on the preceding interfaces.

    • If the command output does not contain information about an interface of the device or the PIM mode of an interface is dense, you need to run thepim sm command on the interface.

      If the system prompts that "Warning: Please enable multicast routing first" when you configure PIM-SM on the interface, run the multicast routing-enable command in the system view to enable the multicast function first and enable PIM-SM on the interface.

    • If PIM-SM has been enabled on all the interfaces on the device, go to Step 4.

  4. Check that the RP information is correct.

    Run the display pim rp-info command on the device to check whether the device has learnt information about the RP serving a specific group and whether the RP information of the same group on all other devices is consistent.

    • If no RP information is displayed or RP information on the devices are inconsistent, do as follows:
      • If the static RP is used on the network, run the static-rp command on all the devices to make information about the RP serving a specific group consistent.

      • If the dynamic RP is used, go to Step 10.

    • If RP information of a specific group is consistent on all the devices, go to Step 5.

  5. Check that an RPF route to the RP is available.

    Run the display multicast rpf-info source-address command on the device to check whether there is an RPF route to the RP.

    • If the command output does not contain any RPF route to the RP, check the configurations of unicast routes. Run the ping command on the device and the RP to check whether they can ping each other successfully.

    • If the command output contains an RPF route to the RP, do as follows:
      • If the command output shows that the RPF route is a static multicast route, run the display current-configuration command to check whether the static multicast route is properly configured.

      • If the command output shows that the RPF route is a unicast route, run the display ip routing-table command to check whether the unicast route is consistent with the RPF route.

    • If the command output contains an RPF route to the RP and the route is properly configured, go to Step 6.

  6. Check that the interface that forwards multicast data is a receiver's DR.

    Run the display pim interface interface-type interface-number command on the device to check whether the interface that forwards multicast data is a receiver's DR.

    • If the DR information in the command output is not marked with local, troubleshoot the involved DR following the preceding steps.

    • If the DR information in the command output is marked with local, go to Step 7.

  7. Check whether a multicast boundary is configured on the interface.

    Run the display current-configuration interface interface-type interface-number command on the device to check whether a multicast boundary is configured on the interface.

    • If the configuration of the interface contains multicast boundary, it indicates that a multicast boundary is configured on the interface. Then you need to run the undo multicast boundary { group-address { mask | mask-length } | all command to delete the configuration of the multicast boundary or re-plan the network to ensure that no multicast boundary is configured on the RPF interface or the RPF neighboring interface.

    • If no multicast boundary is configured on the interface, go to Step 8.

  8. Check whether a source policy is configured.

    Run the display current-configuration configuration pim command to view the current configurations in the PIM view.

    • If the configuration contains source-policy acl-number, it indicates a source-based filtering rule is configured. If the received multicast data is denied by the ACL rule, the multicast data is discarded. Then you need to run the undo source-policy command to delete the configuration of the ACL rule or reconfigure an ACL rule to ensure that demanded multicast data can be normally forwarded.

    • If no source policy is configured, go to Step 9.

  9. Check whether the PIM routing table contains correct (*, G) entries.

    Run the display pim routing-table group-address command on the device to check whether the PIM routing table contains correct (*, G) entries. For details, see Step 1.

    If the fault persists after the preceding troubleshooting procedures are complete, go to Step 10.

  10. Collect the following information and contact technical support personnel.
    • Results of the preceding troubleshooting procedure

    • Configuration files, log files, and alarm files of the devices

Translation
Download
Updated: 2019-05-10

Document ID: EDOC1000079719

Views: 454655

Downloads: 4318

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