348
NOTE:
This configuration takes effect for dynamically joined IPv6 multicast groups but not the statically
configured multicast groups.
Adjusting MLD performance
For the configuration tasks in this section:
• In MLD view, the configuration is effective globally. In interface view, the configuration is effective
only on the current interface.
• If the same function or parameter is configured in both MLD view and interface view, the
configuration performed in interface view is given priority, regardless of the configuration order.
Configuration prerequisites
Before adjusting MLD performance, complete the following tasks:
• Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the
domain can be interoperable at the network layer.
• Configure basic MLD functions.
• Determine the startup query interval.
• Determine the startup query count.
• Determine the MLD query interval.
• Determine the MLD querier's robustness variable.
• Determine the maximum response delay of MLD general query messages.
• Determine the MLD last listener query interval.
• Determine the MLD other querier present interval.
• Determine the DSCP value for MLD messages.
Configuring Router-Alert option handling methods
MLD queries include multicast-address-specific queries and multicast-address-and-source-specific queries,
and IPv6 multicast groups change dynamically, so a device cannot maintain the information for all IPv6
multicast sources and groups. Therefore, a router might receive IPv6 multicast packets addressed to IPv6
multicast groups that have no members on the local subnet. In this case, the Router-Alert option carried
in the IPv6 multicast packets is useful for the router to determine whether to deliver the IPv6 multicast
packets to the upper-layer protocol for processing. For more information about the Router-Alert option,
see RFC 2113 .
An MLD message is processed differently depending on whether it carries the Router-Alert option in the
IPv6 header, as follows:
To Next Page
Loading...
