Multicast VLAN Registration Overview

Multicast VLAN Registration (MVR) is a Layer 2 feature that enables efficient distribution of Internet Protocol Television (IPTV) multicast streams across a network. MVR addresses the inefficiencies of Internet Group Management Protocol (IGMP), which in traditional VLAN-based multicast delivery confines multicast streams to individual VLANs, leading to bandwidth waste due to duplication when multiple VLANs request the same stream.

Feature Overview

MVR introduces a dedicated multicast VLAN (MVLAN) that acts as the source VLAN for multicast traffic. Receiver VLANs remain isolated for security and bandwidth control but dynamically associate with the MVLAN based on multicast group addresses. This allows multicast traffic to flow through a single MVLAN while maintaining VLAN separation.

MVR supports two port types:

  • MVR Source Port (SP): Located in the MVLAN, forwards multicast traffic.
  • MVR Receiver Port (RP): Located in receiver VLANs, receives multicast traffic but cannot send traffic to the MVLAN.

MVR-enabled devices forward IPTV multicast traffic from MVLAN source ports to host interfaces in other VLANs designated as MVR receiver ports. Receiver ports remain in their own VLANs for bandwidth and security reasons. MVR assumes that subscriber ports subscribe and unsubscribe (join and leave) multicast streams by sending IGMP join and leave messages.

Requirements

This feature has no special hardware or software requirements for feature enablement or usage.

Considerations

Consider the following when configuring and using this feature:

  • MVR modifies multicast forwarding behavior by allowing traffic to cross VLAN boundaries selectively, based on IGMP messages.
  • Beginning with FastIron release 10.0.10h_cd1, a Layer 3 Premium license is no longer needed to enable MVR.
  • On ICX 8100 devices, if multicast receivers use IGMPv3, you must enter the ip igmp version 3 command in global configuration mode. Without this configuration, the device does not process IGMPv3 join messages received on MVR receiver VLANs. IGMPv2 join messages are not affected.
  • MVR reduces bandwidth consumption by eliminating duplicate multicast streams across VLANs.
  • Source ports must be manually configured as router ports to forward multicast data if they are not already router ports.
  • IGMP message handling is a critical aspect of MVR operation, as it determines how join and leave messages are processed across VLANs. For detailed IGMP message handling behavior, refer to IGMP Message Handling.
  • Support is added for ICX 8100 devices in FastIron 10.0.10h_cd1.

Limitations

Note the following limitations regarding this feature:

  • MVR is not supported on Private VLANs (PVLANs).
  • The maximum number of MVLANs supported is 10, with up to 100 group configurations per MVLAN.
  • The number of MVR interfaces you can configure on an ICX switch is limited by the maximum number of virtual Ethernet (VE) interfaces that the switch hardware supports.
  • MVR does not support Protocol Independent Multicast (PIM), and the two features cannot coexist.
  • The maximum number of flows and outgoing interfaces (OIFs) supported is similar to the PIM module scale numbers for the ICX switch platform.

Best Practices

To optimize MVR performance and reliability RUCKUS suggests the following:

  • Ensure that multicast group-to-MVLAN mappings are correctly configured. When modifying these mappings, manually clear the multicast cache to avoid inconsistencies between the snooping and MVR modules. Refer to the Configuring Multicast VLAN Registration section for detailed steps.
  • Use tagged interfaces for receiver VLANs to maintain VLAN separation and ensure proper traffic delivery. Refer to the RUCKUS FastIron Layer 2 Switching Configuration Guide for more information regarding VLANs and tagged Ethernet ports.
  • Monitor IGMP join/leave activity to validate dynamic group associations and troubleshoot multicast delivery issues. Refer to Displaying MVR Information for more information.
  • Periodically verify MVLAN mappings using the show ip multicast mvr mvlan group-map command.
  • Regularly check CPU and memory utilization after enabling MVR to help ensure network stability. Refer to the RUCKUS FastIron Command Reference for guidance on using the show cpu commands.

Prerequisites

This feature has no prerequisites to feature enablement or usage.

Parent topic: Multicast VLAN Registration