# On Router B, enable IPv6 multicast routing globally, enable MLD proxying on GigabitEthernet
3/1/1, and enable MLD on GigabitEthernet 3/1/2.
<RouterB> system-view
[RouterB] multicast ipv6 routing-enable
[RouterB] interface GigabitEthernet 3/1/1
[RouterB-GigabitEthernet3/1/1] mld proxying enable
[RouterB-GigabitEthernet3/1/1] quit
[RouterB] interface GigabitEthernet 3/1/2
[RouterB-GigabitEthernet3/1/2] mld enable
[RouterB-GigabitEthernet3/1/2] quit
Verify the configuration
# Display MLD information on GigabitEthernet 3/1/1 of Router B.
[RouterB] display mld interface GigabitEthernet 3/1/1 verbose
GigabitEthernet3/1/1(2001::2):
MLD proxy is enabled
Current MLD version is 1
Multicast routing on this interface: enabled
Require-router-alert: disabled
# Display MLD group information on Router A.
[RouterA] display mld group
Total 1 MLD Group(s).
Interface group report information
GigabitEthernet3/1/1(2001::1):
Total 1 MLD Groups reported
Group Address
ff3e::101
The output shows that the MLD reports sent from the hosts are forwarded to Router A through the proxy
interface, GigabitEthernet 3/1/1 of Router B.
Troubleshooting MLD
No member information exists on the receiver-side router
Symptom
When a host sends a message to announce its joining IPv6 multicast group G, no member information
of multicast group G exists on the intermediate router.
Analysis
The correctness of networking and interface connections and whether the protocol layer of the
•
interface is up directly affect the generation of IPv6 group member information.
IPv6 multicast routing must be enabled on the router and MLD must be enabled on the interface
•
connecting to the host.
If the MLD version on the router interface is lower than that on the host, the router will not be able
•
to recognize the MLD report from the host.
Last Reporter
Uptime
2001::2
00:02:04
371
Expires
00:01:15