PLANET WGSW-50040 - Manual (Page 171)

22-5
SwitchB(config)#ipv6 mld snooping vlan 100
SwitchB(config)#ipv6 mld snooping vlan 100 mrouter interface ethernet 1/1
Multicast configuration:
Same as scenario 1
MLD Snooping interception results:
Same as scenario 1
Scenario 3: To run in cooperation with layer 3 multicast protocols
WITCH which is used in Scenario 1 is replaced with ROUTER with specific configurations remains the same.
And multicast and IGMP snooping configurations are the same with what it is in Scenario 1. To configure
PIM-SM6 on ROUTER, and enable PIM-SM6 on vlan 100 (use the same PIM mode with the connected
multicast router), the configurations are listed as below:
switch#config
switch(config)#ipv6 pim multicast-routing
switch(config)#interface vlan 100
switch(config-if-vlan100)#ipv6 pim sparse-mode
MLD snooping does not distribute entries when layer 3 multicast protocol is enabled. It only does the following
tasks.
 To remove the layer 2 multicast entries.
 To provide query functions to the layer 3 with vlan, S, and G as the parameters.
 When layer 3 MLD is disabled, re-enable distributing layer 2 multicast entries.
By looking up the layer 3 IP6MC entries, it can be found that ports can be indicated by the layer 3 multicast
entries. This ensures the MLD Snooping can work in cooperation with the layer 3 multicast protocols.
22.1.4 MLD Snooping Troubleshooting
In configuring and using MLD Snooping, the MLD Snooping server may fail to run properly due to physical
connection failure, wrong configuration, etc. The user should ensure the following:
 Ensure the physical connection is correct
 Ensure the MLD Snooping is enabled under global mode (using ipv6 mld snooping)
 Ensure the MLD Snooping is configured on the vlan under global mode (using ipv6 mld snooping vlan
<vlan-id>）
 Ensure there is a vlan configured as a L2 general querier, or there is a static mrouter configured in a
segment,
 Use command to check if the MLD snooping information is correct