46
Step Command Remarks
3. (Optional.) Delete static
multicast routes.
• Delete a specific static multicast
route:
undo ip rpf-route-static
[ vpn-instance vpn-instance-name ]
source-address { mask-length |
mask } { rpf-nbr-address |
interface-type interface-number }
• Delete all static multicast routes:
delete ip rpf-route-static
[ vpn-instance vpn-instance-name ]
N/A
Configuring the RPF route selection rule
You can configure the router to select the RPF route based on the longest prefix match principle. For more
information about RPF route selection, see "RPF check process."
To
configure a multicast routing policy:
Step Command Remarks
1. Enter system view.
system-view
N/A
2. Enter MRIB view.
multicast routing [ vpn-instance
vpn-instance-name ]
N/A
3. Configure the device to
select the RPF route based
on the longest prefix match.
longest-match
By default, the route with the
highest priority is selected as the
RPF route.
Configuring multicast load splitting
To optimize the traffic delivery for multiple data flows, you can configure load splitting on a per-source
basis or on a per-source-and-group basis.
To configure multicast load splitting:
Step Command Remarks
1. Enter system view.
system-view
N/A
2. Enter MRIB view.
multicast routing [ vpn-instance
vpn-instance-name ]
N/A
3. Configure multicast load
splitting.
load-splitting { source |
source-group }
By default, load splitting is
disabled.
Configuring a multicast forwarding boundary
A multicast forwarding boundary sets the boundary condition for the multicast groups in a specific range.
The multicast data for a multicast group travels within a definite boundary in a network. If the destination
address of a multicast packet matches the boundary condition, the packet is not forwarded. If an
interface is configured as a multicast boundary, it can no longer forward multicast packets (including
packets sent from the local device), nor receive multicast packets.