Before configuring IPv6 multicast load splitting, complete the following tasks:
By default, if there are multiple equal-cost routes to a multicast source, the device selects the route with the largest next-hop address as the RPF route. After multicast load splitting is configured, the device uses the specified load splitting policy to distribute multicast data among multiple paths. This function improves quality of multicast forwarding.
It is recommended that you use a fixed load splitting policy based on the actual situation on your network. The stable-preferred or balance-preferred load splitting policy is recommended.
The load splitting timer and load splitting weights can be configured when the stable-preferred or balance-preferred load splitting policy is used.
If IPv6 PIM-DM is enabled on the current switch, the stable-preferred or balance-preferred policy cannot be used.
The system view is displayed.
Multicast load splitting is configured.
The keywords in the command specify different multicast load splitting policies:
balance-preferred: load splitting that ensures even load distribution among forwarding paths. This policy applies to scenarios where users frequently join and leave multicast groups. It enables traffic distribution to be automatically adjusted to adapt to frequent changes of group memberships.
If this load splitting policy is used, the switch automatically adjusts traffic on equal-cost routes when equal-cost routes are added or deleted, multicast routing entries are deleted, or load splitting weights on interfaces are changed.
group: load splitting based on group addresses. This policy applies to the scenarios where one multicast source sends data to multiple groups.
source: load splitting based on source addresses. This policy applies to the scenarios where one group receives data from multiple sources.
source-group: load splitting based on source addresses and group addresses. This policy applies to the scenarios with multiple sources and multiple groups.
stable-preferred: load splitting that ensures stable multicast forwarding. This policy applies to networks with stable multicast services.
If the stable-preferred load splitting policy is used, the switch automatically adjusts traffic on equal-cost routes when equal-cost routes are added or deleted. When multicast routing entries are deleted or load splitting weights on interfaces are changed, the switch does not automatically adjust the traffic on the equal-cost routes.
The multicast load splitting timer is set.
By default, the value of a load splitting timer is 1800 seconds.
After IPv6 multicast load splitting is configured, run the following command to check whether the loading splitting policy is configured successfully.
Run the display multicast ipv6 routing-table [ ipv6-source-address [ ipv6-source-mask-length ] | ipv6-group-address [ ipv6-group-mask-length ] | incoming-interface { interface-type interface-number | register } | outgoing-interface { exclude | include | match } { interface-type interface-number | register | none } ] * [ outgoing-interface-number [ number ] ] command to view the IPv6 multicast routing table.