The rendezvous point tree (RPT) used to provide the Any-Source Multicast (ASM) service fails to be established. User hosts cannot receive multicast data.
This fault is commonly caused by one of the following:
Run the display pim routing-table group-address command on the device to check whether the PIM routing table contains (*, G) entries of multicast group G.
If the PIM routing table contains correct (*, G) entries, you can run the display multicast forwarding-table group-address command every 15 seconds to check whether the forwarding table contains (S, G) entries that correspond to (*, G) entries and whether the value of the Matched field in the command output keeps increasing.
If the forwarding table contains (S, G) entries and the value of the Matched field keeps increasing, data forwarding on the upstream devices is correct but data cannot be forwarded to downstream devices. In this case, check whether the TTL value is too small or a forwarding failure occurs.
If the local device is not an RP, it has not received any multicast data. Check whether the PIM routing table on the upstream device contains correct (S, G) entries.
If the local device is the RP, the RPT has been established successfully. In this case, check whether the source's designated router (DR) is registered successfully.
If the PIM routing table does not contain correct (*, G) entries, go to step 2.
Run the display pim control-message counters interface interface-type interface-number message-type join-prune command to check whether the number of Join/Prune messages received by downstream interfaces increases.
If the number of Join/Prune messages increases, the downstream devices send Join/Prune messages. In this case, check whether PIM neighbors can communicate with each other.
If the number does not increase, the downstream devices are not working properly. In this case, locate and rectify the faults.
If the number of Join/Prune messages received by downstream interfaces increases, go to step 3.
RPF neighboring interface to the RP
RPF interface to RP
Interface directly connected to network segment of user hosts (downstream interfaces of the receiver's DR)
Run the display pim interface verbose command on the device to check PIM information on interfaces. Check whether PIM-SM is enabled on the preceding interfaces.
If "Error: Please enable multicast in the system view first." is displayed when you enable PIM-SM on interfaces, run the multicast routing-enable command in the system view to enable the multicast function. Then, enable PIM-SM on the interface.
If PIM-SM is enabled on all interfaces, go to step 4.
Run the display pim rp-info command on the device to check whether the device learns the RP information that provides services for a multicast group and has the same RP information as other devices that provide services for the same group.
run the static-rp command to configure the address of the RP that provides services for a multicast group to be the same on all devices.
If the RP information that provides services for a multicast group is the same on all devices, go to step 5.
Run the display multicast rpf-info source-address command on the device to check whether the RPF route to the RP is available.
If the command output does not contain the RPF route to the RP, check the configuration of the unicast route. Run the ping command on the device and on the RP to check whether they can ping each other.
If the RPF route is a static multicast route, run the display current-configuration command to check whether the static route configuration is correct.
If the command output indicates 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 the RPF route to the RP and the configuration of the route is correct, go to step 6.
Run the display pim interface interface-type interface-number command to check whether the interface forwarding multicast data is the receiver's DR.
If there is no local flag in the command output, the device is not the receiver' DR. In such a case, you can locate the receiver's DR based on the DR address that is displayed in the command output and go to step 7.
If there is local flag in the command output, go to step 7.
Run the display current-configuration interface interface-type interface-number command to check whether the multicast boundary is configured on the interface.
If the command output contains multicast boundary, the multicast boundary is configured on the interface. In this case, you can run the undo multicast boundary { group-address { mask | mask-length } | all } command to delete the multicast boundary configuration or replan the networking to ensure that the multicast boundary is not configured on the RPF interface or the RPF neighbor interface.
If the multicast boundary is not configured on the interface, go to step 8.
Run the display current-configuration configuration pim command to check current configuration in the PIM view.
If the command output contains the "source-policy acl-number", source-based filtering rules are configured. If the received multicast data does not match ACL rules, the multicast data is discarded. In this case, you can run the undo source-policy command to delete the configuration or reconfigure the ACL rules to ensure that the multicast data can be forwarded normally.