PowerConnect B-Series FCX Configuration Guide 89953-1002266-01Configuring MLD snooping 27Every group on a physical port keeps its own tracking record. However, it can track groupmembership only; it cannot track by (source, group). For example, Client A and Client B belong togroup1 but each is receiving traffic from different sources. Client A receives a traffic stream from(source_1, group1) and Client B receives a traffic stream from (source_2, group1). The device waitsfor the configured leave-wait-time before it stops the traffic because the two clients are in the samegroup. If the clients are in different groups, the waiting period is ignored and traffic is stoppedimmediately.To enable tracking and fast leave for VLAN 20, enter the following commands.PowerConnect(config)#vlan 20PowerConnect(config-vlan-20)#mld-snooping trackingSyntax: [no] mld-snooping trackingThe membership tracking and fast leave features are supported for MLDv2 only. If a port or client isnot configured for MLDv2, the mld-snooping tracking command is ignored.Configuring fast leave for MLDv1When a device receives an MLDv1 leave message, it sends out multiple group-specific queries. Ifno other client replies within the waiting period, the device stops forwarding traffic to this port.Configuring fast-leave-v1 allows the device to stop forwarding traffic to a port immediately uponreceiving a leave message. The device does not send group-specific queries. It is important that nosnooping ports have multiple clients. When two devices connect, the querier device should not beconfigured for fast-leave-v1 because the port to the non-querier device could have multiple clients.The number of queries and the waiting period (in seconds) can be configured using the ipv6mld-snooping leave-wait-time command. The default is 2 seconds. To configure fast leave forMLDv1, use commands such as the following.PowerConnect(config)#vlan 20PowerConnect(config-vlan-20)#mld-snooping fast-leave-v1Syntax: [no] mld-snooping fast-leave-v1Enabling fast convergenceIn addition to periodically sending general queries, an active (querier) device sends out generalqueries when it detects a new port. However, since it does not recognize the other device port-upevent, the multicast traffic might still use the query-interval time to resume after a topologychange. Configuring fast-convergence allows the device to listen to topology change events in L2protocols, such as spanning tree, and send general queries to shorten the convergence time.If the L2 protocol is unable to detect a topology change, the fast-convergence feature may not work.For example, if the direct connection between two devices switches from one interface to another,the rapid spanning tree protocol (802.1w) considers this an optimization action, rather than atopology change. In this case, other devices will not receive topology change notifications and willbe unable to send queries to speed up the convergence. The original spanning tree protocol doesnot recognize optimization actions, and fast-convergence works in all cases.To enable fast-convergence, enter commands such as the following.PowerConnect(config)#vlan 70PowerConnect(config-vlan-70)#mld-snooping fast-convergenceSyntax: mld-snooping fast-convergence
