Reset Search



How to configure “Static” MVR regardless of IGMP join

« Go Back


TitleHow to configure “Static” MVR regardless of IGMP join
By default, Multicast traffic can’t pass through different VLANs without Multicast routing protocols such as PIM.
But EXOS provides MVR (Multicast VLAN Registration) feature which supports distributing multicast streams for IPTV to subscribers over a Layer 2 networks.

EXOS supports two types of MVR, Static MVR and Dynamic MVR.
Dynamic MVR operates based on IGMP join (or report) received from host, please refer How To Configure MVR for configuring dynamic MVR.

Otherwise, "Static MVR" operates regardless of IGMP join (or report). When static MVR is enabled, if multicast traffics are incoming from a VLAN, it floods the multicast traffic to other VLAN by statically.
Static MVR can be used in Layer 2 Core network for high demand channels to copy them quickly as soon as the switch receives IGMP join for the channel.
  • All EXOS
  • Summit
  • BlackDiamond
User-added image

Configure static MVR on SW#2:
configure mvr add vlan v100
configure igmp snooping vlan v200 port 2 add static router
configure mvr vlan v200 add receiver port 2
enable mvr

Multicast groups to be flooded can be configured with “mvr-address”:
configure mvr vlan v100 mvr-address <mvr_address_range>

Example policy of “mvr_address_range” :

entry mvr_adress_range {
 if match any{
    nlri ;
 } then {

Additional notes
Static MVR works only when there are incoming multicast traffic into the switch. In other words, the upstream switch/router must flood multicast streams to the switch forced by using IGMP static join or making the downstream switch as IGMP querier, etc.
Because static MVR floods the received multicast traffic to other configured VLANs regardless of IGMP join, if there is no incoming multicast stream, Static MVR doesn't work as expected.



Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255