When a point-to-multipoint (P2MP) traffic engineering (TE) tunnel is used to carry multicast services, you must direct multicast traffic out of the P2MP TE tunnel on the tunnel egress so that the multicast traffic can be correctly forwarded after leaving the tunnel.
When a P2MP TE tunnel is used to carry multicast services, you do not need to deploy the Protocol Independent Multicast (PIM) on the transit nodes of the tunnel. If an egress performs the Reverse Path Forwarding (RPF) check on a received multicast data packet, the RPF check fails. As a result, the multicast data packet cannot be forwarded to the next-hop device. To resolve this problem, disable each egress from performing the RPF check on received packets.
The system view is displayed.
An advanced ACL is created, and the advanced ACL view is displayed.
Rules are configured for the advanced ACL.
Run the rule command, set the source parameter to a multicast source address, and set the destination parameter to a multicast group address.
Return to the system view.
The PIM view is displayed.
The RPF check on multicast entries is disabled.
The multicast traffic from the specified P2MP TE tunnel is directed to the VPN.
The configuration is committed.