- Audience
- Getting Started with Cisco ME 2600X
- Ethernet Virtual Circuit
- Quality of Service
- Resilient Ethernet Protocol
- Link Aggregation Group and Link Aggregation Control Protocol
- MAC Learning
- Multicast VLAN Registration
- IGMP Snooping
- Remote Network Monitoring and Alarm Troubleshooting
- Authentication, Authorization, and Accounting (AAA)
- Cisco Discovery Protocol
- SNMP
- IP Source Guard for Service Instance
- DHCP Snooping
- Dynamic ARP Inspection
- MAC Address Security
- Layer 2 Access Control Lists on EVCs
- Layer 3 Access Control Lists on EVCs
- Storm Control over EVC
- Control Plane Policing
- ICMP Unreachable Rate Limiting User Feedback
- IP Version 6 Support for the Management Port
- SSH
- PPPoE Intermediate Agent
- CFM over EVC
- Index
Cisco ME 2600X Series Ethernet Access Switch Software Configuration Guide
- Updated:
- November 19, 2017
Chapter: Multicast VLAN Registration
Contents
- Multicast VLAN Registration
- Multicast VLAN Registration
- Prerequisites for MVR
- Restrictions for MVR
- Information About MVR
- Using MVR in a Multicast Television Application
- How to Configure MVR
- Enabling MVR in Global Configuration Mode
- Enabling or Disabling MVR Source and MVR Receiver on an Interface
- Configuring MVR Source and MVR Receiver on an Interface
- Verifying the MVR Configuration
- Configuration Examples for MVR
- Additional References for MVR
Multicast VLAN Registration
This chapter describes Multicast VLAN Registration and procedures to configure Multicast VLAN Registration.
- Multicast VLAN Registration
- Prerequisites for MVR
- Restrictions for MVR
- Information About MVR
- How to Configure MVR
- Verifying the MVR Configuration
- Configuration Examples for MVR
- Additional References for MVR
Multicast VLAN Registration
In multicast VLAN networks, subscribers to a multicast group can exist in more than one VLAN. If the VLAN boundary restrictions in a network consist of Layer 2 switches, it might be necessary to replicate the multicast stream to the same group in different subnets, even if they are on the same physical network. Multicast VLAN Registration (MVR) routes packets received in a multicast source VLAN to one or more receive VLANs. Clients are in the receive VLANs and the multicast server is in the source VLAN. Multicast routing has to be disabled when MVR is enabled.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Toolkit and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for MVR
- It is mandatory to untag the packets before they enter the bridge domain. For an MVR source and receiver, the packets are untagged using the rewrite pop configuration at the EFP level.
- Only one MVR VLAN can be present in a router, and the same VLAN must be configured as the MVR VLAN for all the routers in the same network.
- Source ports must be in the MVR VLAN.
- Receiver ports of the VLAN must either have a snooping querier or a layer 3 switch virtual interfaces (SVI) to generate an IGMP query on that VLAN.
- The MVR VLAN must not be a reverse path forwarding (RPF) interface for any multicast route.
- VLAN Trunk Protocol (VTP) pruning must be disabled if the MVR VLAN number is between 1 and 1000.
Restrictions for MVR
- Do not connect a multicast router to a receiver port.
- Receiver ports can only be access ports; they cannot be trunk ports.
- MVR is available only on native systems.
- MVR cannot coexist with storm control on ES-20 ports.
- When Layer 2 port-channel is configured as MVR receiver port, multicast data traffic from MVR group is not forwarded out of the member links.
- MVR data received on an MVR receiver port cannot be forwarded to MVR source ports.
- MVR with IGMP on REP segment results in a stale entry in the IGMP snooping table when REP state changes.
- When using private VLANs, you cannot configure a primary or secondary VLAN as the MVR VLAN.
- The maximum number of multicast entries (MVR group addresses) on a router (maximum number of television channels received) is 2000.
- Receiver ports on a router can be in different VLANs, but must not be in the MVR VLAN.
Information About MVR
In a typical Layer 2 multi-VLAN network, subscribers to a multicast group can be on multiple VLANs. To maintain data isolation between these VLANs, the multicast stream on the source VLAN must be passed to a router, which replicates the stream on all subscriber VLANs, thereby wasting upstream bandwidth.
Multicast VLAN Registration (MVR) allows a Layer 2 switch to forward the multicast data from a source on a common assigned VLAN to the subscriber VLANs, conserving upstream bandwidth by bypassing the router. The switch will forward multicast data for MVR IP multicast streams only to MVR ports on which hosts have joined, either by IGMP reports or by MVR static configuration. The switch will forward IGMP reports received from MVR hosts only to the source port. MVR supports IGMPv3 messages. For other traffic, VLAN isolation is preserved.
MVR requires at least one VLAN to be designated as the common VLAN to carry the multicast stream from the source. More than one such multicast VLAN (MVR VLAN) can be configured in the system, and a global default MVR VLAN as well as interface-specific default MVR VLANs can also be configured.
MVR allows a subscriber on a port to subscribe and unsubscribe to a multicast stream on the MVR VLAN by sending IGMP join and leave messages. IGMP leave messages from an MVR group are handled according to the IGMP configuration of the VLAN on which the leave message is received. If IGMP fast leave is enabled on the VLAN, the port is removed immediately; otherwise an IGMP query is sent to the group to determine whether other hosts are present on the port.
MVR can coexist with IGMP snooping on a router.
Using MVR in a Multicast Television Application
In a multicast television application, a Personal Computer (PC) or a television with a set-top box, can receive the multicast stream. Multiple set-top boxes or PCs can be connected to one subscriber port, which is an EFP configured as the MVR receiver. The figure below is an example configuration. The DHCP assigns an IP address to the set-top box or the PC. When a subscriber selects a channel, the set-top box or PC sends an IGMP report to the Cisco ME 2600X Series Ethernet Access Switch to join the appropriate multicast. If the IGMP report matches one of the configured IP multicast group addresses, the Cisco ME 2600X Series Ethernet Access Switch modifies the hardware address table to include this receiver EFP and bridge-domain as a forwarding destination of the specified multicast stream when it is received from the multicast bridge-domain.
When a subscriber changes channels or turns off the television, the set-top box sends an IGMP leave message for the multicast stream. The Cisco ME 2600X Series Ethernet Access Switch sends a MAC-based general query through the receiver EFP bridge-domain. If there is another set-top box in the bridge-domain still subscribing to this group, that set-top box must respond within the maximum response time specified in the query. If the Cisco ME 2600X Series Ethernet Access Switch does not receive a response, it eliminates the receiver EFP as a forwarding destination for this group.
- Without Immediate Leave, when the Cisco ME 2600X Series Ethernet Access Switch receives an IGMP leave message from a subscriber on a receiver EFP, it sends out an IGMP group specific query on that EFP and waits for the IGMP group membership reports. If no reports are received in the configured time period, the receiver EFP is removed from the multicast group membership.
- With Immediate Leave, an IGMP query is not sent from the receiver EFP where the IGMP leave was received. As soon as the leave message is received, the receiver EFP is removed from the multicast group membership, which speeds up leave latency.
MVR eliminates the need to duplicate television-channel multicast traffic for subscribers in each bridge-domain. Multicast traffic for all channels is only sent around the bridge domain source EFPs—only on the multicast bridge-domain. The IGMP leave and join messages are in the bridge-domain to which the subscriber port is assigned. These messages dynamically register for streams of multicast traffic in the multicast bridge-domain on the Layer 3 device. The Cisco ME 2600X Series Ethernet Access Switchmodifies the forwarding behavior to allow the traffic to be forwarded from the multicast bridge domain to the subscriber port in a different bridge-domain, thereby selectively allowing traffic to cross between the two bridge-domains.
IGMP reports are sent to the same IP multicast group address as the multicast data. The Cisco ME 2600X Series Ethernet Access Switch must capture all IGMP join and leave messages from the receiver EFPs and forward them to the multicast bridge domain of the source EFP.
How to Configure MVR
The following tasks describe how to configure MVR on the Cisco ME 2600X device:
- Enabling MVR in Global Configuration Mode
- Enabling or Disabling MVR Source and MVR Receiver on an Interface
- Configuring MVR Source and MVR Receiver on an Interface
Enabling MVR in Global Configuration Mode
1.
enable
2.
configure terminal
3.
bridge-domain bridge-domain id
4.
exit
5.
mvr
6.
mvr max-groups max-groups
7.
mvr group ip-address [count count | [mask mask]]
8.
mvr vlan vlan-id
9.
end
DETAILED STEPS
Enabling or Disabling MVR Source and MVR Receiver on an Interface
MVR source and MVR receiver are configured on the interface and are mapped to the efp id of the service instance created on that port.
The mvr type {source | receiver} efp_id {ethernet service instance} command is used to configure the MVR source or receiver on the interface.
 Note | The service instance number of the EFP created on the port where MVR receiver is configured must be same as the service instance number of the EFP created on the port where MVR source is configured. |
To configure MVR source and receiver on the interface level, see Configuring MVR Source and MVR Receiver on an Interface
Configuring MVR Source and MVR Receiver on an Interface
1.
enable
2.
configure terminal
3.
interface type slot/port
4.
service instance id ethernet
5.
encapsulation dot1q vlan-id
6.
rewrite ingress tag pop {1|2} symmetric
7.
bridge-domain bridge-domain id
8.
exit
9. mvr type {source | receiver}efp_id {ethernet service instance}
10.
end
DETAILED STEPS
Verifying the MVR Configuration
MVR Receiver Port
The following command displays the MVR receiver port configuration.:
Switch# show mvr receiver-ports
Joins: v1,v2,v3 counter shows total IGMP joins
v3 counter shows IGMP joins received with both MVR and non-MVR groups
Port VLAN Status Immediate Joins
Leave (v1,v2,v3) (v3)
--------- ---- ------------- ---------- ---------- ----------
Po10 100 ACTIVE /UP DISABLED 0 0
Gi0/2 100 ACTIVE /UP DISABLED 0 0
Po10 200 ACTIVE /UP DISABLED 0 0
Gi0/2 101 ACTIVE /UP DISABLED 0 0
MVR Source Port
The following command displays the MVR source port configuration:
Switch# show mvr source-ports
Joins: v1,v2,v3 counter shows total IGMP joins
v3 counter shows IGMP joins received with both MVR and non-MVR groups
Port VLAN Status Immediate Joins
Leave (v1,v2,v3) (v3)
--------- ---- ------------- ---------- ---------- ----------
Gi0/1 1 ACTIVE /UP DISABLED 0 0
Gi0/1 2 ACTIVE /UP DISABLED 0 0
MVR Group
The following command displays the MVR group details:
Switch# show mvr groups
MVR multicast VLAN: 1
MVR max Multicast Groups allowed: 2000
MVR current multicast groups: 60
MVR groups:
Group start Group end Type Count/Mask
--------------- --------------- ----- ---------------
224.1.1.1 224.1.1.20 count 20
225.1.1.1 225.1.1.20 count 20
229.1.1.1 229.1.1.10 count 10
230.1.1.1 230.1.1.10 count 10
MVR multicast VLAN: 2
MVR max Multicast Groups allowed: 2000
MVR current multicast groups: 60
MVR groups:
Group start Group end Type Count/Mask
--------------- --------------- ----- ---------------
224.1.1.1 224.1.1.20 count 20
225.1.1.1 225.1.1.20 count 20
229.1.1.1 229.1.1.10 count 10
230.1.1.1 230.1.1.10 count 10
Snooping
The following command displays the snooping details:
Switch# show ip igmp snooping groups
Flags: I -- IGMP snooping, S -- Static, P -- PIM snooping, A -- ASM mode Vlan Group/source Type Version Port List ----------------------------------------------------------------------- 1 229.1.1.1 I v3 Po10 Gi0/2 1 229.1.1.2 I v3 Po10 Gi0/2 1 229.1.1.3 I v3 Po10 Gi0/2 1 229.1.1.4 I v3 Po10 Gi0/2 1 229.1.1.5 I v3 Po10 Gi0/2 1 229.1.1.6 I v3 Po10 Gi0/2 1 229.1.1.7 I v3 Po10 Gi0/2 1 229.1.1.8 I v3 Po10 Gi0/2 1 229.1.1.9 I v3 Po10 Gi0/2 1 229.1.1.10 I v3 Po10 Gi0/2
Querier
The following command displays the querier details:
Switch# show ip igmp snooping querier
Vlan IP Address IGMP Version Port ------------------------------------------------------------- 1 12.12.12.12 v3 Gi0/1
Generic MVR
The following command displays the generic MVR details:
Switch# show mvr
MVR Running: TRUE MVR multicast VLAN: 2 MVR Max Multicast Groups: 2000 MVR Current multicast groups: 100 MVR Global query response time: 5 (tenths of sec)
Mrouter
The following command displays the mrouter details:
Switch# show ip igmp snooping mrouter
Vlan ports ---- ----- 1 Gi0/1(dynamic)
Configuration Examples for MVR
The following example shows how to enable MVR:
Switch> enable Switch# configure terminal Switch(config)# mvr Switch(config)# mvr groups 225.1.1.1 5 Switch(config)# bridge-domain 100 Switch(config-bdomain)# exit Switch(config)# mvr vlan 100 Switch(config)# exit
The following example shows how to configure MVR source on the interface:
Switch> enable Switch# configure terminal Switch(config)# interface g0/4 Switch(config-if)# service instance 1 ethernet Switch(config-if-srv)# encapsulation dot1q 100 Switch(config-if-srv)# rewrite ingress tag pop 1 symmetric Switch(config-if-srv)# bridge-domain 100 Switch(config-if-srv)# exit Switch(config-if)# mvr type source efp_id 1 Switch(config-if)# end
The following example shows how to configure MVR receiver on the interface:
Switch> enable Switch# configure terminal Switch(config)# interface g0/45 Switch(config-if)# service instance 1 ethernet Switch(config-if-srv)# encapsulation dot1q 100 Switch(config-if-srv)# rewrite ingress tag pop 1 symmetric Switch(config-if-srv)# bridge-domain 50 Switch(config-if-srv)# exit Switch(config-if)# mvr type receiver efp_id 1 Switch(config-if)# end
Additional References for MVR
The following sections provide references related to the MVR feature.
Related Documents
| Related Topic | Document Title |
|---|---|
Cisco IOS basic commands |
Cisco IOS Configuration Fundamentals Command Reference |
Standards
| Standard | Title |
|---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
— |
MIBs
| MIB | MIBs link |
|---|---|
None. |
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFCs
| RFC | Title |
|---|---|
No new or modified RFCs are supported, and support for existing RFCs has not been modified. |
— |
Technical Assistance
| Description | Link |
|---|---|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
http://www.cisco.com/cisco/web/support/index.html |