365
3.
Set the MLD querier's
robustness variable.
mld robust-count count
By default, the MLD querier's
robustness variable is 2.
4.
Set the MLD startup query
interval.
mld startup-query-interval
interval
By default, the MLD startup query
interval equals one quarter of the
MLD general query interval.
5.
Set the MLD startup query
count.
mld startup-query-count count
By default, the MLD startup query
count equals the MLD querier's
robustness variable.
6.
Set the MLD general query
interval.
mld query-interval interval
By default, the MLD general query
interval is 125 seconds.
7.
Set the MLD last listener
query interval.
mld last-listener-query-interval
interval
By default, the MLD last listener
query interval is 1 second.
8.
Set the MLD last listener
query count.
mld
last-listener-query-count count
By default, the MLD last listener
query count equals the MLD
querier's robustness variable.
9.
Set the maximum response
time for MLD general
queries.
mld max-response-time time
By default, the maximum
response time for MLD general
queries is 10 seconds.
10.
Set the MLD other querier
present timer.
mld
other-querier-present-timeout ti
me
By default, the MLD other querier
present timer is calculated by
using the following formula:
[ MLD general query interval ] ×
[ MLD robustness variable ] +
[ maximum response time for MLD
general queries ] / 2.
Enabling fast-leave processing
This feature enables an MLD querier to send leave notifications to the upstream without sending
multicast-address-specific or multicast-address-and-source-specific queries after receiving a done
message. Use this feature to reduce leave latency and to preserve the network bandwidth.
To enable fast-leave processing:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter interface view.
interface interface-type
interface-number
N/A
3.
Enable fast-leave
processing.
mld
fast-leave
[
group-policy
ipv6-a
cl-number
]
By default, fast-leave processing
is disabled.
Configuring MLD SSM mappings
This feature enables the device to provide SSM services for MLDv1 hosts.
This feature does not process MLDv2 messages. Enable MLDv2 on the receiver-side interface to
ensure that MLDv2 reports from MLDv2 receiver hosts can be processed.