Configuration Notes and Feature Limitations
- RUCKUS recommends that IGMPv2 configuration should be used for v2 hosts and IGMPv3 for v3 hosts for optimal performance. Using IGMPv3 with tracking with a v2 host does not give the desired result.
- With IGMPv3 tracking, only non-SSM groups using exclude mode for join is supported.
- If a set of group addresses that are flooded have identical MAC addresses with some other multicast streams, these Multicast streams are also flooded.
- When reports and leave messages are flooded in a VLAN for all non-edge ports, the Vlan learns the IGMP membership information for all the respective ports.
- Multicast streams received in a VLAN are not forwarded to mrouter ports.
- The configuring of a set of Multicast addresses to flood or drop in a VLAN is only supported for snooping-enabled VLANs.
- SDVoE cannot be enabled if the
ip multicast flood-unregisteredcommand is configured. - Source-specific tracking is not supported.
- If you want packets for some multicast groups to be flooded in the hardware, you can add mcaches statically for those groups, either to flood or drop those packets.
- When SDVoE is enabled for a VLAN, a default profile is added automatically and static mcaches are created for the groups in the default profile.
- When SDVoE is not enabled for a VLAN, you can manually add a static mcache profile for that VLAN.