Sunteți pe pagina 1din 20

Configuring Multicast VLAN Registration

2008 Extreme Networks, Inc. All rights reserved. ExtremeXOS Implementing Multicast Routing (EIMR), Version 12.1. Part # DOC-01616.

Student Objectives
Upon successful completion of this module, you will be able to: Define Multicast VLAN Registration (MVR). Describe the most common application for MVR. Describe the forwarding behavior of MVR. Describe the difference between static and dynamic MVR. Configure a dynamic MVR-enabled VLAN. Configure subscriber VLANs.

Verify the configuration and operation of MVR.

Slide 2

Multicast VLAN Registration


Allows a stream received over a layer-2 VLAN to be forwarded to another VLAN, without the need for a layer-3 routing protocol. (PIM/OSPF) Helps prevent IPTV customers from trying to become senders on the
subscriber VLAN.

Supports distributing multicast streams for IPTV to subscribers over a layer-2 network. Enable MVR on the ingress VLAN. Other VLANs with interested receivers (IGMP join) receive the stream. With IGMP snooping enabled. Only hosts that register receive the stream on VLAN 2.

Slide 3

Simple MVR Example

Without MVR

With MVR

*
Slide 4

Typical MVR Example

EAPS Ring

MVR Enabled

IGMP and IGMP Snooping Enabled

Slide 5

Static and Dynamic MVR


By default, all MVR streams are static. Streams are always available on the MVR-enabled multicast VLAN. When a subscriber requests one of the channels, it is quickly forwarded from
the multicast VLAN to the subscriber VLAN.

The layer-2 switch does not send any proxy IGMP join messages towards
the IGMP querier.

Using dynamic MVR, streams are not forwarded on the MVRenabled multicast VLAN until a IGMP join is received for that stream. The switch send proxy IGMP join messages on behalf of all the subscriber
VLANs.

IGMP join and leave messages appear to come from a port in the multicast
VLAN rather than the VLAN to which the subscriber host port is assigned.

Provides on-demand service


Slide 6

MVR Forwarding Rules


Multicast traffic is forwarded to member ports and router ports on the ingress MVR-enabled VLAN. MVR traffic is not forwarded to a non-MVR VLAN unless an IGMP join message is received from a host on that VLAN.

Packets are not forwarded to host ports belonging to another MVRenabled VLAN.
Traffic from one MVR-enabled VLAN is forwarded into the router ports of another MVR-enabled VLAN.

Streams belonging to static MVR groups are always forwarded on the ingress MVR-enabled VLAN.
Streams belonging to dynamic MVR groups are forwarded on the ingress MVR-enabled VLAN only if a host is interested in them.

Slide 7

MVR Forwarding Example


IGMP with MVR restricts multicast traffic to only the designated multicast VLAN.

Slide 8

Inter-Multicast VLAN Forwarding


Used when streams need to be forwarded onto another multicast VLAN. Normally packets are not forwarded to ports belonging to other MVR VLANs.

Traffic from one MVR VLAN is forwarded to the router ports of another MVR-enabled VLAN.

Slide 9

Inter-Multicast VLAN Forwarding


Enable MVR on the CustVlan on one of the switches. To avoid a loop, do not enable MVR on both SW1 and SW2.
MSP_VLAN
SW2 SW1 Forwards the multicast traffic. Receives but, does not forward multicast traffic.

Slide 10

Enabling MVR
To configure a VLAN as an MVR VLAN. configure mvr add vlan <vlan-name> The VLAN must be added to MVR before MVR is enabled. To enable MVR on the switch. enable mvr

Slide 11

Configuring the MVR Address Range


To configure the MVR address range. configure mvr vlan <vlan-name> mvr-address {<policyname> | none} Any multicast address within the address range is forwarded according to the MVR forwarding rules. Excluding the multicast control range. Any multicast address outside the MVR address range receives default switching behavior.

If no policy file is specified (the none option), the entire multicast address range is forwarded according to the MVR forwarding rules. Excluding the multicast control range.

Slide 12

Configuring a Static MVR Group


By default, all the MVR group addresses work in static mode. To configure the static MVR address range.
configure mvr vlan <vlan-name> static group {<policy-name> | none}

Any multicast address within the static address range is forwarded according to the static MVR forwarding rules
Any multicast address outside the static address range and within MVR address range is treated as a dynamic group address.

If no policy file is specified (the none option), the entire MVR address range is static. Excluding the multicast control range.

Slide 13

Additional MVR Configuration


To override the normal MVR forwarding rules and add a group of ports for multicast forwarding through MVR. configure mvr vlan <vlan-name> add receiver port <port-list>

To delete a VLAN from MVR. configure mvr delete vlan <vlan-name>


To remove a group of virtual ports for multicast forwarding through MVR. configure mvr vlan <vlan-name> delete receiver port <port-list>

Slide 14

show mvr show mvr vlan mcast

Verifying the MVR Configuration

Slide 15

show mvr cache

Verifying the MVR Operation

Slide 16

Summary
You should now be able to: Define Multicast VLAN Registration (MVR). Describe the most common application for MVR. Describe the forwarding behavior of MVR. Describe the difference between static and dynamic MVR. Configure a dynamic MVR-enabled VLAN. Configure subscriber VLANs.

Verify the configuration and operation of MVR.

Slide 17

Lab
Turn to the Multicast VLAN Registration Configuration Lab in the ExtremeXOS Implementing Multicast Routing - Lab Guide, Rev. 12.1 and complete the hands-on portion of this module.

Slide 18

This presentation contains forward-looking statements that involve risks and uncertainties, including statements regarding our expectations as to products, trends and our performance. There can be no assurances that any forward-looking statements will be achieved, and actual results could differ materially from forecasts and estimates. For factors that may affect our business and financial results please refer to our filings with the Securities and Exchange Commission, including, without limitation, under the captions: Managements Discussion and Analysis of Financial Condition and Results of Operations, and Risk Factors, which is on file with the Securities and Exchange Commission (http://www.sec.gov). We undertake no obligation to update the forward-looking information in this release.

2008 Extreme Networks, Inc. All rights reserved. ExtremeXOS Implementing Multicast Routing (EIMR), Version 12.1. Part # DOC-01616.

The End

2008 Extreme Networks, Inc. All rights reserved. ExtremeXOS Implementing Multicast Routing (EIMR), Version 12.1. Part # DOC-01616.

S-ar putea să vă placă și