When configuring a multicast static route, you cannot specify an RPF neighbor by providing the type
and number (interface-type interface-number) of the interface connecting the RPF neighbor if the
interface type of the RPF neighbor is Ethernet, Layer 3 aggregate, Loopback, RPR, or VLAN-interface;
instead, you can specify such an RPF neighbor only by its address (rpf-nbr-address).
Configuring a Multicast Routing Policy
You can configure the router to determine the RPF route based on the longest match principle. For
details about RPF route selection, refer to
By configuring per-source or per-source-and-group load splitting, you can optimize the traffic delivery
when multiple data flows are handled.
Configuring a multicast routing policy in the public instance
Follow these steps to configure a multicast routing policy in the public instance:
To do...
Enter system view
Configure the device to select
the RPF route based on the
longest match
Configure multicast load
splitting
Configuring a multicast routing policy in a VPN instance
Follow these steps to configure a multicast routing policy in a VPN instance:
To do...
Enter system view
Enter VPN instance view
Configure the device to select
the RPF route based on the
longest match
Configure multicast load
splitting
RPF check
process.
Use the command...
system-view
multicast longest-match
multicast load-splitting
{ source | source-group }
Use the command...
system-view
ip vpn-instance
vpn-instance-name
multicast longest-match
multicast load-splitting
{ source | source-group }
1-9
Remarks
—
Required
The route with the highest
priority is selected as the RPF
route by default
Optional
Disabled by default
Remarks
—
—
Required
The route with the highest
priority is selected as the RPF
route by default
Optional
Disabled by default