Configuring mld query and response parameters – H3C Technologies H3C SecPath F1000-E User Manual

Page 927

Advertising
background image

902

Configuring the Router-Alert option for MLD messages globally

Step

Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter MLD view.

mld

N/A

3.

Configure the interface to

discard any MLD message
without the Router-Alert

option.

require-router-alert

By default, the device does not
check MLD messages for the

Router-Alert option.

4.

Enable the insertion of the
Router-Alert option into MLD

messages.

send-router-alert

By default, MLD messages carry
the Router-Alert option.

Configuring the Router-Alert option on an interface

Step

Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter interface view.

interface interface-type
interface-number

N/A

3.

Configure the interface to
discard any MLD message

without the Router-Alert

option.

mld require-router-alert

By default, the device does not
check MLD messages for the

Router-Alert option.

4.

Enable the insertion of the
Router-Alert option into MLD

messages.

mld send-router-alert

By default, MLD messages carry
the Router-Alert option.

Configuring MLD query and response parameters

On startup, the MLD querier sends MLD general queries at the startup query interval, which is

one-quarter of the MLD query interval. The number of queries, or the startup query count, is user

configurable.
After startup, the MLD querier periodically sends MLD general queries at the MLD query interval to check

for IPv6 multicast group members on the network. You can modify the query interval based on the actual

condition of the network.
The MLDv1 querier sends MLD multicast-address-specific queries at the MLD last listener query interval
when it receives an MLD done message. The MLDv2 querier sends MLD

multicast-address-and-source-specific queries at the MLD last listener query interval when it receives a

multicast group and multicast source mapping change report. The number of queries, or the last listener

query count, equals the robustness variable—the maximum number of packet retransmissions.
A multicast listening host starts a timer for each IPv6 multicast group that it has joined when it receives an

MLD query (general query), multicast-address-specific query, or multicast-address-and-source-specific

query. The timer is initialized to a random value in the range of 0 to the maximum response delay

advertised in the MLD query message. When the timer decreases to 0, the host sends an MLD

membership report message to the IPv6 multicast group.

Advertising