Configuring Ipv6 Multicast Load Splitting; Configuring An Ipv6 Multicast Forwarding Boundary - HP MSR2003 Configuration Manual

Step
3. Configure the device to select
the RPF route based on the
longest prefix match.

Configuring IPv6 multicast load splitting

By configuring per-source or per-source-and-group load splitting, you can optimize the traffic delivery
when multiple IPv6 multicast data streams are handled.
You do not need to enable IPv6 multicast routing before this configuration.
To configure IPv6 multicast load splitting:
Step
1. Enter system view.
2. Enter IPv6 MRIB view.
3. Configure IPv6 multicast load
splitting.

Configuring an IPv6 multicast forwarding boundary

IPv6 multicast packets do not travel infinitely in a network. The IPv6 multicast data of each IPv6 multicast
group must be transmitted within a definite scope. A multicast forwarding boundary sets the boundary
condition for the IPv6 multicast groups in the specified range or scope. If the destination address of an
IPv6 multicast packet matches the set boundary condition, the packet is not forwarded. Once an IPv6
multicast boundary is configured on an interface, this interface can no longer forward IPv6 multicast
packets (including those sent from the local device) or receive IPv6 multicast packets.
TIP:
You do not need to enable IPv6 multicast routing before this configuration.
To configure an IPv6 multicast forwarding boundary:
Step
1. Enter system view.
2. Enter interface view.
3. Configure an IPv6 multicast
forwarding boundary.
Command
longest-match
Command
system-view
ipv6 multicast routing
[ vpn-instance vpn-instance-name ]
load-splitting {source |
source-group }
Command
system-view
interface interface-type
interface-number
ipv6 multicast boundary
{ ipv6-group-address prefix-length
| scope { scope-id | admin-local |
global | organization-local |
site-local } }
249
Remarks
By default, the route with the
highest priority is selected as the
RPF route.
Remarks
N/A
N/A
By default, IPv6 multicast load
splitting is disabled.
Remarks
N/A
N/A
By default, no forwarding
boundary is configured.