CloudEngine 6800&5800 V100R001C00 Configuration Guide - Multicast 04.pdf

8/12/2019 CloudEngine 6800&5800 V100R001C00 Configuration Guide - Multicast 04.pdf

1/281

CloudEngine 6800&5800 Series Switches

V100R001C00

Configuration Guide - IP Multicast

Issue 04

Date 2013-07-10

HUAWEI TECHNOLOGIES CO., LTD.


2/281

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written

consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and the

customer. All or part of the products, services and features described in this document may not be within the

purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representations

of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://enterprise.huawei.com

Issue 04 (2013-07-10) Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

i
http://enterprise.huawei.com/


3/281

About This Document

Intended Audience

This document describes the concepts and configuration procedures of IP multicast on the CE

series switches, and provides the configuration examples.

This document is intended for:

l Data configuration engineers

l Commissioning engineers

l Network monitoring engineers

l System maintenance engineers

Symbol Conventions

The symbols that may be found in this document are defined as follows.

Symbol Description

DANGER

Indicates a hazard with a high level or medium level of risk

which, if not avoided, could result in death or serious injury.

WARNINGIndicates a hazard with a low level of risk which, if notavoided, could result in minor or moderate injury.

CAUTION

Indicates a potentially hazardous situation that, if not

avoided, could result in equipment damage, data loss,

performance deterioration, or unanticipated results.

TIP Provides a tip that may help you solve a problem or save time.

NOTE Provides additional information to emphasize or supplement

important points in the main text.


Configuration Guide - IP Multicast About This Document



ii


4/281

Command Conventions

The command conventions that may be found in this document are defined as follows.

Convention Description

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of all

items can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. You can select one or several items, or select

no item.

& The parameter before the & sign can be repeated 1 to n times.

# A line starting with the # sign is comments.

Interface Numbering Conventions

Interface numbers used in this manual are examples. In device configuration, use the existing

interface numbers on devices.

Change History

Updates between document issues are cumulative. Therefore, the latest document issue containsall updates made in previous issues.

Changes in Issue 04 (2013-07-10)

This version has the following updates:

The following information is modified:

l 7.6.4 Configuring a Policy to Filter IGMP Report Messages







iii


5/281


l 3.6 Adjusting Multicast Source Control Parameters

l 7.6.7 Setting the Aging Time for Entries Triggered by Multicast Traffic




l 7.6.2 Filtering Multicast Data on an Interface

l 7.6.3 Discarding of Unknown Multicast Flows

l 7.6.4 Configuring a Policy to Filter IGMP Report Messages

The following information is added:

l 6.5 Disabling Soft Forwarding for Multicast Packets


Initial commercial release.





iv


6/281

Contents

About This Document.....................................................................................................................ii

1 Basics for IP Multicast Configuration.......................................................................................1

1.1 IP Multicast Overview....................................................................................................................................................2

1.2 Concepts of IPv4 Multicast............................................................................................................................................51.3 Multicast Deployment on an IPv4 Network...................................................................................................................9

2 IGMP Configuration...................................................................................................................16

2.1 IGMP Overview...........................................................................................................................................................18

2.2 IGMP Features Supported by the Switch.....................................................................................................................19

2.3 Default Configuration...................................................................................................................................................20

2.4 Configuring Basic IGMP Functions.............................................................................................................................20

2.4.1 Enabling IGMP..........................................................................................................................................................20

2.4.2 Configuring the IGMP Version.................................................................................................................................21

2.4.3 (Optional) Configuring a Static Multicast Group on an Interface.............................................................................222.4.4 (Optional) Configuring the Range of Multicast Groups That an Interface Can Join................................................23

2.4.5 Checking the Configuration.......................................................................................................................................23

2.5 Optimizing IGMP Performance....................................................................................................................................24

2.5.1 Configuring the Router-Alert Option........................................................................................................................24

2.5.2 Configuring IGMP Querier Parameters.....................................................................................................................26

2.5.3 Configuring IGMP Fast Leave..................................................................................................................................29

2.5.4 Configuring IGMP On-Demand................................................................................................................................30

2.5.5 FilteringIGMP Messages Based on Source IP Addresses........................................................................................31


2.6 Configuring IGMP SSM Mapping...............................................................................................................................32

2.7 Maintaining IGMP........................................................................................................................................................33

2.7.1 ClearingIGMP Group Memberships........................................................................................................................33

2.7.2 Monitoring IGMP Running Status............................................................................................................................34

2.8 Configuration Example.................................................................................................................................................34

2.8.1 Examplefor Configuring Basic IGMP Functions.....................................................................................................34

2.8.2 Example for Configuring a Static Multicast Group on an Interface..........................................................................39

2.8.3 Example for Configuring IGMP SSM Mapping.......................................................................................................43

2.9 Common Configuration Errors.....................................................................................................................................50

2.9.1 IGMP Entries Cannot Be Created.............................................................................................................................50


Configuration Guide - IP Multicast Contents



v


7/281

2.9.2 (S, G) Entries Are Not Generated After SSM Mapping Is Enabled..........................................................................50

3 PIM-SM (IPv4) Configuration..................................................................................................52

3.1 PIM-SM (IPv4) Overview............................................................................................................................................54

3.2 PIM-SM (IPv4) Features Supported by the Switch......................................................................................................563.3 Default Configuration...................................................................................................................................................58

3.4 Configuring PIM-SM in the ASM Model....................................................................................................................59

3.4.1 Enabling PIM-SM......................................................................................................................................................59

3.4.2 Configuring an RP.....................................................................................................................................................60

3.4.3 (Optional) Configuring a BSR Administrative Domain............................................................................................63

3.4.4 (Optional) Configuring SPT Switchover Conditions................................................................................................65

3.4.5 (Optional) Adjusting Control Parameters for Source Registering.............................................................................66

3.4.6 (Optional) Adjusting C-RP Control Parameters........................................................................................................68

3.4.7 (Optional) Adjusting C-BSR Control Parameters.....................................................................................................69


3.5 Configuring PIM-SM in the SSM Model.....................................................................................................................72

3.5.1 Enabling PIM-SM......................................................................................................................................................72

3.5.2 (Optional) Configuring an SSM Group Policy..........................................................................................................72


3.6 Adjusting Multicast Source Control Parameters..........................................................................................................74

3.7 Adjusting Control Parameters for Establishing Neighbor Relationships ....................................................................76

3.7.1 Adjusting Control Parameters for Hello Messages...................................................................................................76

3.7.2 Configuring PIM Neighbor Filtering ........................................................................................................................78


3.8 Adjusting Control Parameters for DR Election............................................................................................................79

3.8.1 Configuring the DR Priority......................................................................................................................................79

3.8.2 Configuring the DR Switchover Delay.....................................................................................................................80


3.9 Adjusting Control Parameters for Join/Prune Messages..............................................................................................81

3.9.1 Adjusting Time Related Parameters for Join/Prune Messages..................................................................................82

3.9.2 Disabling PIM Join/Prune Message Packaging.........................................................................................................83

3.9.3 Adjusting Control Parameters for Prune Delay.........................................................................................................84

3.9.4 Configuring a Join Information Filtering Policy.......................................................................................................863.9.5 Checking the Configuration.......................................................................................................................................86

3.10 Adjusting Assert Control Parameters.........................................................................................................................87

3.11 Configuring PIM Anycast RP.....................................................................................................................................89

3.11.1 Configuring Global Anycast RP..............................................................................................................................89

3.11.2 Configuring Local Addresses for Anycast RPs.......................................................................................................90

3.11.3 Configuring Anycast RP Peers................................................................................................................................91

3.11.4 Checking the Configuration.....................................................................................................................................91

3.12 Configuring PIM BFD................................................................................................................................................92

3.13 Configuring PIM Silent..............................................................................................................................................93

3.14 Maintaining PIM-SM.................................................................................................................................................95





vi


8/281

3.14.1 Clearing Statistics About PIM Control Packets......................................................................................................95

3.14.2 Clearing the PIM Status of the Specified Downstream Interfaces in PIM Entries..................................................95

3.14.3 Monitoring the Running Status of PIM-SM ...........................................................................................................96

3.15 Configuration Examples.............................................................................................................................................97

3.15.1 Example for Configuring PIM-SM in the ASM Model..........................................................................................97

3.15.2 Example for Configuring PIM-SM in the SSM Model.........................................................................................106

3.15.3 Example for Configuring PIM for Anycast RP.....................................................................................................115

3.16 CommonConfiguration Errors.................................................................................................................................121

3.16.1 RPT ona PIM-SM Network Fails to be Established.............................................................................................121

3.16.2 SPT ona PIM-SM Network Fails to be Established.............................................................................................124

3.16.3 Registration Interface Still Exists After the Source DR Registers with the RP....................................................126

4 MSDP Configuration................................................................................................................128

4.1 MSDP Overview.........................................................................................................................................................130

4.2 MSDP Features Supported by the Switch..................................................................................................................131

4.3 Default Configuration.................................................................................................................................................132

4.4 Configuring Basic MSDP Functions..........................................................................................................................132

4.4.1 Enabling MSDP.......................................................................................................................................................132

4.4.2 Configuring MSDP Peers........................................................................................................................................133

4.4.3 (Optional) Configuring Static RPF Peers................................................................................................................135

4.4.4 (Optional) Configuring the MSDP Mesh Group.....................................................................................................136


4.5 Controlling SA Messages and the SA Cache.............................................................................................................137

4.5.1 Configuring the SA Cache.......................................................................................................................................137

4.5.2 Setting Parameters of the SA Request Message......................................................................................................138

4.5.3 Configuring the Content of an SA Message............................................................................................................139

4.5.4 Configuring the Rule for Filtering SA Messages....................................................................................................140


4.6 Configuring MSDP Anycast RP.................................................................................................................................141

4.6.1 Configuring an RP...................................................................................................................................................142

4.6.2 Configuring MSDP Peer Connections.....................................................................................................................143

4.6.3 Configuring the Source RP Address of the SA Message........................................................................................143

4.6.4 Checking the Configuration.....................................................................................................................................1444.7 Maintaining MSDP.....................................................................................................................................................144

4.7.1 ClearingStatistics on MSDP Peers.........................................................................................................................144

4.7.2 Clearing(S, G) Information in the SA Cache.........................................................................................................145

4.7.3 Monitoring the Running Status of MSDP...............................................................................................................145


4.8.1 Examplefor Configuring PIM-SM Inter-domain Multicast Using MSDP.............................................................146

4.8.2 Examplefor Configuring Inter-AS Multicast Using Static RPF Peers...................................................................155

4.8.3 Examplefor Configuring Anycast RP in a PIM-SM Domain.................................................................................163

4.8.4 Examplefor Configuring SA Message Filtering.....................................................................................................170

4.9 Common Configuration Errors...................................................................................................................................177





vii


9/281

4.9.1 An MSDP Peer Is Always in Down State...............................................................................................................177

4.9.2 There Is No (S, G) Entry in the SA Cache..............................................................................................................178

4.9.3 RPs Fail to Exchange Registration Information with Each Other...........................................................................178

5 MBGP Configuration................................................................................................................1805.1 MBGP Overview........................................................................................................................................................181

5.2 MBGP Features Supported by the Switch..................................................................................................................181

5.3 MBGP Default Configuration....................................................................................................................................181

6 Multicast Route Management (IPv4) Configuration..........................................................182

6.1 Overview of Multicast Route Management (IPv4)....................................................................................................183


6.3 Configuring RPF Check Policies................................................................................................................................184

6.3.1 Configuring a Multicast Static Route......................................................................................................................184

6.3.2 Configuring the Longest Match Rule for Multicast Route Selection......................................................................1856.3.3 Configuring Multicast Load Splitting......................................................................................................................186


6.4 Configuring the Multicast Boundary..........................................................................................................................187

6.5 Disabling Soft Forwarding for Multicast Packets......................................................................................................188

6.6 Maintaining Multicast Routes....................................................................................................................................189

6.6.1 Resetting Multicast Forwarding Entries..................................................................................................................189

6.6.2 Monitoring Multicast Routing and Forwarding.......................................................................................................189


6.7.1 Examplefor Configuring a Multicast Static Route to Change the RPF Route.......................................................190

6.7.2 Examplefor Configuring Multicast Static Routes to Connect RPF Routes............................................................195

6.7.3 Examplefor Configuring Multicast Load Splitting.................................................................................................201

6.8 Common Configuration Errors...................................................................................................................................207

6.8.1 A Multicast Static Route Fails to Take Effect.........................................................................................................207

7 IGMP Snooping Configuration..............................................................................................208

7.1 IGMP Snooping Overview.........................................................................................................................................210

7.2 IGMP Snooping Features Supported by the Switch...................................................................................................211


7.4 Configuring Basic IGMP Snooping Functions...........................................................................................................2127.4.1 Enabling IGMP Snooping.......................................................................................................................................213

7.4.2 Configuring the IGMP Snooping Version...............................................................................................................214

7.4.3 (Optional) Configuring a Static Router Port............................................................................................................215

7.4.4 (Optional) Configuring a Static Member Port.........................................................................................................216

7.4.5 (Optional) Configuring an IGMP Snooping Querier...............................................................................................217

7.4.6 (Optional) Suppressing Report and Leave Messages..............................................................................................222

7.4.7 (Optional) Configuring the Router-Alert Option.....................................................................................................222

7.4.8 (Optional) Disabling Users from Dynamically Joining Multicast Groups..............................................................223


7.5 Configuring IGMP Snooping Proxy...........................................................................................................................224





viii


10/281

7.6 Configuring the IGMP Snooping Policy....................................................................................................................226

7.6.1 Configuring a Multicast Group Policy....................................................................................................................226

7.6.2 Filtering Multicast Data on an Interface..................................................................................................................227

7.6.3 Discarding of Unknown Multicast Flows................................................................................................................228

7.6.4 Configuring a Policy to Filter IGMP Report Messages..........................................................................................229

7.6.5 Configuring a Policy to Filter IGMP Query Messages...........................................................................................229

7.6.6 Configuring the Multicast Group Type for a VLAN...............................................................................................230

7.6.7 Setting the Aging Time for Entries Triggered by Multicast Traffic........................................................................231


7.7 Configuring Membership Fast-Update.......................................................................................................................232

7.7.1 Setting the Aging Time of Group Member Ports....................................................................................................233

7.7.2 Setting the Aging Time of Dynamic Router Ports..................................................................................................234

7.7.3 Configuring Fast Leave for Member Ports..............................................................................................................234

7.7.4 Sending IGMP Query Messages upon Topology Changes.....................................................................................2357.7.5 Checking the Configuration.....................................................................................................................................236

7.8 Configuring IGMP Snooping SSM Mapping.............................................................................................................236

7.8.1 (Optional) Configuring an SSM Group Policy........................................................................................................237

7.8.2 Configuring IGMP Snooping SSM Mapping..........................................................................................................237


7.9 Maintaining IGMP Snooping.....................................................................................................................................239

7.9.1 ClearingIGMP Snooping Entries............................................................................................................................239

7.9.2 ClearingIGMP Snooping Statistics.........................................................................................................................240

7.9.3 Displaying the IGMP Snooping Running Status.....................................................................................................240

7.10 Configuration Examples...........................................................................................................................................241

7.10.1 Example for Configuring IGMP Snooping...........................................................................................................241

7.10.2 Example for Configuring Layer 2 Multicast Through Static Interfaces................................................................244

7.10.3 Example for Configuring an IGMP Snooping Querier.........................................................................................247

7.10.4 Example for Configuring IGMP Snooping Proxy.................................................................................................251

7.10.5 Example for Configuring Multicast SSM Mapping..............................................................................................254

7.11 CommonConfiguration Errors.................................................................................................................................257

7.11.1 Layer 2Multicast Packets Cannot Be Forwarded.................................................................................................257

7.11.2 The Multicast Group Policy Does Not Take Effect...............................................................................................258

8 Static Multicast MAC Address Configuration.................................................................... 260

8.1 Multicast MAC Address.............................................................................................................................................261

8.2 Configuring a Static Multicast MAC Address...........................................................................................................262

8.3 Example for Configuring a Static Multicast MAC Address.......................................................................................263

9 Multicast Network Management............................................................................................266

9.1 Overview of Multicast Network Management...........................................................................................................267

9.2 MulticastNetwork Management Features Supported by the Switch.........................................................................267

9.3 Configuring Multicast Network Management............................................................................................................267

9.3.1 Enabling Multicast Network Management..............................................................................................................267

9.3.2 Enabling the Trap Function for a Specified Module...............................................................................................268





ix


11/281

9.3.3 Adjusting the Interval for PIM to Send Trap Messages..........................................................................................269






x


12/281

1Basics for IP Multicast ConfigurationAbout This Chapter

This chapter describes basic concepts, protocols, and features of IP multicast, and provides

multicast service deployment on IPv4 networks.

1.1 IP Multicast Overview

Multicast technology implements point-to-multipoint data transmission to save network

bandwidth and reduce network loads. It is widely used in IPTV, real-time data transmission, and

multimedia conference applications.

1.2 Conceptsof IPv4 Multicast

Before using IPv4 multicast services, familiarize yourself with basic concepts of multicast,

multicast models, as well as multicast addresses and multicast protocols used on IPv4 networks.

A good understanding of these concepts and features helps you complete multicast service

configurationefficiently.

1.3 MulticastDeployment on an IPv4 Network

This section describes typical multicast service scenarios on an IPv4 network and applications

of multicast protocols and features in these scenarios, helping you configure multicast services

efficiently. Typical multicast service scenarios include multicast within a PIM domain, multicast

between PIM-SM domains, and multicast between ASs.


Configuration Guide - IP Multicast 1 Basics for IP Multicast Configuration



1


13/281

1.1 IP Multicast Overview

Multicast technology implements point-to-multipoint data transmission to save network

bandwidth and reduce network loads. It is widely used in IPTV, real-time data transmission, and

multimedia conference applications.

NOTE

Multicast routers mentioned in this document refer to routers or Layer 3 switches. The CE series

switches support IP multicast routing and can be used as a multicast router.

Why Multicast Is Needed

Traditional IP communication supports two transmission modes: unicast and broadcast. In

unicast transmission, a source sends an independent data packet to each host that requiring its

data. In broadcast transmission, a source sends data to all the hosts on the local network segment,

regardless whether the hosts require its data.

To transmit data to multiple destination hosts but not all hosts, a source host uses the broadcast

mode or sends multiple copies of data in unicast mode to the destination hosts one by one, as

shown in Figure 1-1.





2


14/281

Figure 1-1Point-to-multipoint data transmission in unicast and broadcast modes

IP network

Packets for HostA

HostB

HostC

Source SwitchB

SwitchA SwitchD

SwitchC

SwitchE

HostA

SwitchF

Receiver

Receiver

Packets for HostC

Unicast transmission

A network segment

Packets for all hosts

HostB

HostC

Source SwitchB

SwitchA SwitchD

SwitchC

SwitchE

HostA

SwitchF

Receiver

Receiver

Broadcast transmission

l In unicast mode, the amount of data transmitted on the network is proportional to the number

of users that require the data. If a large number of users require the same data, the source

host must send many copies of data to these users, consuming high bandwidth on the source

host and network. Therefore, the unicast mode is not suitable for batch data transmission

and is applicable only to networks with a small number of users.

l In broadcast mode, data is sent to all hosts on a network segment regardless of whether

they need the data. This threatens information security and causes storms on the network

segment. Therefore, the broadcast mode is not suitable for data transmission from a source

to specified destinations and it also wastes network bandwidth.





3


15/281

In a summary, traditional unicast and broadcast modes cannot effectively implement point-to-

multipoint data transmission.

Multicast is a solution to point-to-multipoint data transmission. As shown in Figure 1-2, the

source sends only one copy of data, and all the hosts that require the data can receive the same

data copy. Other hosts on the network cannot receive the data.

Figure 1-2Point-to-multipoint data transmission in multicast mode

IP network

Packets for the multicast group

HostB

HostC

Source SwitchB

SwitchA SwitchD

SwitchC

SwitchE

HostA

SwitchF

Receiver

Receiver

Multicast transmission

Advantages of Multicast

Multicast has the following advantages over unicast and broadcast:

l Compared with the unicast mode, the multicast mode starts to copy data and distribute data

copies on the network node as far from the source as possible. Therefore, the amount of

data and network resource consumption will not increase greatly when the number of

receivers increases.

l Compared with the broadcast mode, the multicast mode transmits data only to receivers

that require the data. This saves network resources and enhances data transmission security.

Applications

IP multicast effectively addresses the problem of point-to-multipoint data transmission. This

technology efficiently transmits data from one point to multiple points over an IP network, saving

network bandwidth and reducing network loads. More importantly, multicast technology

facilitates deployment of new value-added services, including live broadcasting, IPTV, tele-

education, telemedicine, online radio, video conferencing, and other information services on the

Internet.

NOTE

Multicast technologies used on IPv4 and IPv6 networks are collectively called IP multicast. The CE seriesswitches support only IPv4 multicast.





4


16/281

1.2 Concepts of IPv4 MulticastBefore using IPv4 multicast services, familiarize yourself with basic concepts of multicast,

multicast models, as well as multicast addresses and multicast protocols used on IPv4 networks.

A good understanding of these concepts and features helps you complete multicast service

configuration efficiently.

Basic Concepts of Multicast

As shown in Figure 1-3, an information source sends data to interested users in multicast mode.

Figure 1-3Multicast transmission

IP network

Multicast packets

HostB

HostC

Source SwitchB

SwitchA SwitchD

SwitchC

SwitchE

HostA

SwitchF

Receiver

Receiver

l Multicast group: a group of receivers identified by an IP multicast address. After joining a

multicast group, hosts can receive multicast data sent to this multicast group.

l Multicast source: a sender of multicast data. Source in Figure 1-3is a multicast source. A

multicast source can simultaneously send data to multiple multicast groups. Multiple

multicast sources can simultaneously send data to a multicast group. A multicast source

does not need to join any multicast groups.l Multicast group member: a host that has joined a multicast group. HostA and HostC in

Figure 1-3are multicast group members. Memberships in a multicast group change

dynamically. Hosts can join or leave a multicast group any time. Members of a multicast

group are located anywhere on a network.

l Multicast router: a router or Layer 3 switch that supports Layer 3 multicast. The switches

in Figure 1-3are multicast routers. In addition to multicast routing functions, multicast

routers connected to user network segments provide multicast member management

functions.

Multicast Models

The following multicast models are used depending on the way receivers treat multicast sources:





5


17/281

l Any-Source Multicast (ASM) model: provides multicast distribution only based on

multicast group addresses. A multicast group address identifies a collection of network

services, and multicast packets sent from any source to this address obtain the same service.

Receiver hosts can receive data sent from any source to this group after joining the group.

l Source-Specific Multicast (SSM) model: provides service for the data flow from a specificsource to a specific group. Receiver hosts can specify the source from which they want to

receive data when they join a group. After joining the group, the hosts receive only the data

sent from the specified source.

The SSM and ASM models use different multicast address ranges so that receivers can easily

identify the two models.

IPv4 Multicast Addresses

On an IPv4 network, multicast sources and group members use IPv4 multicast addresses to

communicate. IPv4 multicast addresses are Class D IP addresses in the range of 224.0.0.0 to

239.255.255.255. Table 1-1describes the meaning of each segment in this range.

Table 1-1Range and description of IPv4 multicast addresses

Class D Address Range Description

224.0.0.0-224.0.0.255 Group addresses reserved for local links. These

addresses are reserved by the Internet Assigned Number

Authority (IANA) for routing protocols, and are called

permanent multicast addresses. The addresses identify

a group of network devices and are not used for multicast

forwarding.

224.0.1.0-231.255.255.255

233.0.0.0-238.255.255.255

ASM group addresses that are valid on the entire

network.

232.0.0.0-232.255.255.255 Default SSM group addresses that are valid on the entire

network.

239.0.0.0-239.255.255.255 Administrative multicast addresses. This is the default

group address range of BootStrap Router (BSR)

administrative domains. Addresses in this range are

private addresses and are valid only in a BSR

administrative domain. BSR administrative domains

can use the same multicast address.

IPv4 Multicast MAC Addresses

When unicast IP packets are transmitted on an Ethernet network, the packets use receiver MAC

addresses as destination MAC addresses. However, the destination of a multicast data packet is

a group with changeable members but not a specific receiver. Therefore, multicast data packets

must use IPv4 multicast MAC addresses on an Ethernet network. IPv4 multicast MAC addresses

are link-layer addresses mapped from IPv4 multicast addresses.

As defined by the IANA, leftmost 24 bits of an IPv4 multicast MAC address are 0x01005e, the25th bit is 0, and the rightmost 23 bits are the same as the rightmost 23 bits of a multicast IP





6


18/281

address, as shown in Figure 1-4. For example, if the IPv4 multicast address of a group is

224.0.1.1, the IPv4 multicast MAC address of this group is 01-00-5e-00-01-01.

Figure 1-4Mapping between an IPv4 multicast address and an IPv4 multicast MAC address

25 bits MAC address prefix

XXXX X

1110 XXXX X XXXXXXX XXXXXXXX XXXXXXXX

00000001 00000000 01011110 0 XXXXXXX XXXXXXXX XXXXXXXX

48-bit MAC address

5 bits information loss

23 bits

mapping

...... ......

32-bit IP address

The first 4 bits of an IPv4 multicast address are 1110 (multicast identifier), and only 23 bits of

the last 28 bits are mapped to a MAC address. That is, information about 5 bits of the IP address

is lost. As a result, 32 multicast IP addresses are mapped to the same MAC address, which may

cause address conflicts in MAC address-based multicast forwarding. When this occurs, change

the multicast forwarding mode to IP address-based forwarding. For example, IP multicast

addresses 224.0.1.1, 224.128.1.1, 225.0.1.1, and 239.128.1.1 are all mapped to multicast MACaddress 01-00-5e-00-01-01.

IPv4 Multicast Protocols

Table 1-2IPv4 multicast protocols

Protocol Function Remarks

Internet Group Management

Protocol (IGMP)

IGMP manages IPv4

multicast group members and

runs on the end of a multicastnetwork (network segments

where Layer 3 multicast

devices connect to user

hosts). Hosts use the IGMP

protocol to join or leave

multicast groups, and Layer 3

multicast devices use the

IGMP protocol to manage

and maintain group

memberships. IGMP can

interact with upper-layer

multicast routing protocols.

IGMP has three versions:

IGMPv1, IGMPv2, and

IGMPv3.

All the three versions support

the ASM model. IGMPv3

can be independently used in

the SSM model, whereas

IGMPv1 and IGMPv2 must

be used with SSM mapping.





7


19/281


Protocol Independent

Multicast (PIM)

PIM runs on an IPv4 network

and sends multicast data

flows to multicast devices

connected to multicast group

members interested in the

data flows. The PIM protocol

has two modes, the sparse

mode (PIM-SM) applicable

to large-scale networks with

sparsely distributed group

members, and the dense

mode (PIM-DM) applicable

to small-scale networks with

concentrated group

members.NOTE

The CE series switches support

only PIM-SM.

The PIM-DM model does not

need to differentiate the ASM

and SSM models.

The PIM-SM model

differentiates the ASM and

SSM models based on

multicast addresses in

multicast data and protocol

packets.

l If multicast addresses of

packets are in the range of

SSM group addresses,

PIM-SM uses the SSM

model to provide

multicast services. The

SSM model has a high

efficiency and simplifies

the multicast address

allocation process. It is

applicable to the scenario

where a group has only

one specific source.

l If multicast addresses of

packets are in the range of

ASM group addresses,

PIM-SM uses the ASMmodel to provide

multicast services.

Multicast Source Discovery

Protocol (MSDP)

MSDP is an inter-domain

multicast protocol that

implements multicast

forwarding between PIM-

SM domains. Multicast

devices in a PIM-SM domain

use MSDP to discover

multicast sources in other

PIM-SM domains, and sendinformation about active

sources in other PIM-SM

domains to receivers in the

local PIM domain.

MSDP is not required when

PIM-SM uses the SSM

model.

MultiProtocol Border

Gateway Protocol (MBGP)

MBGP is also called

multicast BGP. It enables

multicast data to be

transmitted between

multicast sources and

receivers in different

autonomous systems (ASs).

-





8


20/281


IGMP snooping and IGMP

snooping proxy

IGMP snooping enables a

switch to create and maintain

a Layer 2 multicast

forwarding table by listening

to IGMP packets exchanged

between the upstream Layer

3 device and user hosts. The

switch controls forwarding of

multicast data packets based

on the Layer 2 multicast

forwarding table to reduce

multicast data flooding on the

Layer 2 network.

IGMP snooping proxy

enables a switch to substitutefor an upstream device to

send IGMP Query messages

and receive IGMP Report/

Leave messages from

downstream devices. This

function saves bandwidth

between the upstream device

and the switch.

IGMP snooping is an

extension of IGMP on Layer

2 network devices. You can

specify the IGMP snooping

version on a switch to enable

the switch to process IGMP

packets of specific versions.

1.3 Multicast Deployment on an IPv4 Network

This section describes typical multicast service scenarios on an IPv4 network and applications

of multicast protocols and features in these scenarios, helping you configure multicast services

efficiently. Typical multicast service scenarios include multicast within a PIM domain, multicast

between PIM-SM domains, and multicast between ASs.

CAUTION

Configure multicast services based on the actual situations and service requirements on your

network. This section provides only deployment of basic multicast services.

NOTE

Before deploying IPv4 multicast services on a network, ensure that IPv4 unicast routes on the network are

reachable.

Multicast Within a PIM Domain

On a small-scale network, all network devices and hosts belong to the same PIM domain. Figure

1-5shows the multicast service deployment in this scenario.





9


21/281

Figure 1-5Multicast service deployment within a PIM domain

Source

SwitchC

SwitchA

SwitchB

IGMP

PIMPIM

IP network

IGMP Snooping /

IGMP Snooping

Proxy

HostA

Receiver

LAN

SwitchDHostBReceiver

IGMP

Table 1-3Multicast protocols used for multicast within a PIM domain

Protocol Application Position Purpose

PIM (mandatory) PIM must be configured on all

interfaces of multicast devices in

the PIM domain, including

SwitchA, SwitchB, and

SwitchC.

For the configuration procedure,

see 3 PIM-SM (IPv4)

Configuration.

PIM sends multicast data from

the multicast source to SwitchB

and SwitchC connected to

multicast receivers.

IGMP (mandatory) IGMP must be configured on

user-side interfaces of Layer 3

multicast devices SwitchB and

SwitchC.


see 2 IGMP Configuration.

IGMP allows receiver hosts to

join or leave multicast groups,

and allows SwitchB and

SwitchC to maintain and manage

multicast memberships.





10


22/281


IGMP snooping and

IGMP snooping

proxy (optional)

IGMP snooping and IGMP

snooping proxy must be

configured in VLANs on

SwitchD, a device between a

Layer 3 multicast device and

user hosts.


see 7 IGMP Snooping

Configuration.

IGMP snooping listens to IGMP

packets exchanged between

SwitchB and hosts to create and

maintain a Layer 2 multicast

forwarding table. In this manner,

SwitchD can control forwarding

of multicast data packets on the

Layer 2 network.

IGMP snooping proxy allows

SwitchD to substitute for

SwitchB to send IGMP Query

messages and substitute hosts to

send IGMP Report/Leave

messages.

Multicast Between PIM-SM Domains

A multicast domain can be divided into multiple isolated PIM-SM domains to facilitate

management of multicast resources, including multicast groups, multicast sources, and group

members. To enable the PIM-SM domains to exchange multicast data, MSDP needs to be

deployed between the PIM-SM domains, as shown in Figure 1-6.

NOTE

MSDP is not required when PIM-SM uses the SSM model.





11


23/281

Figure 1-6Multicast service deployment between PIM-SM domains

PIM-SM 2

Source1

SwitchB

SwitchA

RP

IP network

Source2

Host

SwitchC

SwitchD

LAN

PIM-SM 1

RP

SwitchF

IP network

(Receiver)

IGMP

PIM

PIMMSDP

IGMP Snooping /

SwitchEPIM

IGMP Snooping

Proxy

SwitchG

PIM

PIM

Table 1-4Multicast protocols used for multicast between PIM-SM domains


PIM-SM (mandatory) PIM-SM must be configured on

all interfaces of multicast

switches in the PIM-SM

domains, including Switches A

to G (except F).

For the configuration procedure,see 3 PIM-SM (IPv4)

Configuration.

PIM-SM sends multicast data

from multicast sources Source 1

and Source 2 to SwitchD

connected to multicast receivers.

Receiver hosts proactively join a

multicast group, and multicastdata is forwarded to the receiver

hosts thought rendezvous points

(RPs) in the PIM-SM domains.


user-side interfaces of SwitchD.





and allows SwitchD to maintain

and manage multicast

memberships.





12


24/281


MSDP (mandatory) MSDP must be configured on

the RP in each PIM-SM domain,

that is, SwitchA and SwitchC.


see 4 MSDP Configuration.

MSDP transmits multicast data

between PIM-SM1 and PIM-

SM2. Host in PIM-SM2 can

receive data from Source 1.

IGMP snooping and

IGMP snooping

proxy (optional)

IGMP snooping must be

configured in VLANs on

SwitchF, a between user hosts

and multicast devices.


see 7 IGMP Snooping

Configuration.

IGMP snooping listens to IGMP

messages exchanged between

SwitchD and hosts to create and

maintain a Layer 2 multicast

forwarding table. In this manner,

SwitchF can control forwarding

of multicast data packets on the

Layer 2 network.

IGMP snooping proxy allowsSwitchF to substitute for

SwitchD to send IGMP Query

messages and substitute hosts to

send IGMP Report/Leave

messages.

Inter-AS Multicast

PIM forwards multicast data based on a unicast routing table; therefore, multicast forwarding

paths are the same as unicast forwarding paths. When a multicast source and receivers are located

in different ASs, a multicast distribution tree needs to be set up between the ASs. In this scenario,

MBGP can be used to create a multicast routing table independent of the unicast routing table.

Then multicast data is transmitted based on the multicast routing table. Figure 1-7shows the

deployment of inter-AS multicast service deployment.

NOTE

Before configuring MBGP between ASs, configure BGP between the ASs.





13


25/281

Figure 1-7Inter-AS multicast service deployment

SwitchE

SwitchD

RPPIM-SM 2

Source2

PIM-SM3

HostB

SwitchF

AS200

RP

RP PIM-SM1

HostA

SwitchA

AS100

Source1

SwitchB

SwitchGSwitchC

SwitchH

(Receiver)

(Receiver)

PIM

PIM

PIM

PIM

PIM

MSDP

IGMP

IGMP

MSDP

MBGP

Table 1-5Multicast protocols used for inter-AS multicast


PIM-SM (mandatory) PIM-SM must be configured on

all interfaces of multicast

switches in the PIM-SMdomains, including Switches A

to H.


see 3 PIM-SM (IPv4)

Configuration.

PIM-SM sends multicast data


and Source 2 to SwitchB andSwitchH connected to multicast

receivers. Receiver hosts

proactively join a multicast

group, and multicast data is

forwarded to the receiver hosts

thought RPs in the PIM-SM

domains.





14


26/281



user-side interfaces of SwitchB

and SwitchH.





and allows SwitchB and

SwitchH to maintain and

manage multicast memberships.

MBGP (mandatory) MBGP must be configured on

SwitchA and SwitchF located at

the AS borders.


see 5 MBGP Configuration.

MBGP sends multicast data


and Source 2 to receivers in

another AS based on an

independent multicast routing

table.

MSDP (mandatory) MSDP must be configured on

the RP in each PIM-SM, that is,

SwitchA, SwitchD, and

SwitchF.


see 4 MSDP Configuration.

MSDP transmits multicast data

among PIM-SM1, PIM-SM2,

and PIM-SM3.





15


27/281

2IGMP ConfigurationAbout This Chapter

You can manage multicast group members by configuring IGMP on multicast device interfaces

connected to user networks.

2.1 IGMP Overview

The Internet Group Management Protocol (IGMP) is a protocol in the TCP/IP protocol suite

used by IPv4 hosts to report their group memberships to any immediately-neighboring multicast

routers.

2.2 IGMP Features Supported by the Switch

The IGMP features supported by the switch include basic IGMP settings, Router-Alert option,IGMP querier, SSM mapping.

2.3 Default Configuration

This sectionprovides the default IGMP configuration.

2.4 Configuring Basic IGMP Functions

After basic IGMP configurations are complete on interfaces connected to user networks, hosts

can connect to multicast networks and receive multicast packets.

2.5 Optimizing IGMP Performance

After being enabled, IGMP can work normally using the default configuration. You can also

adjust IGMP parameter settings to enhance network security and performance.

2.6 Configuring IGMP SSM Mapping

On a multicast network that provides the SSM service, interfaces of multicast devices run

IGMPv3, but some hosts can run only IGMPv1 or IGMPv2. To enable multicast devices to

provide the SSM service for hosts running IGMPv1 or IGMPv2, configure SSM mapping on

multicast devices.

2.7 Maintaining IGMP

You can clear IGMP group memberships and monitor IGMP running information.

2.8 Configuration Example

This section provides IGMP configuration examples to help you configure IGMP functions on

a multicast network.

2.9 Common Configuration Errors


Configuration Guide - IP Multicast 2 IGMP Configuration



16


28/281

This section describes common faults caused by incorrect IGMP configurations and provides

the troubleshooting procedure.





17


29/281

2.1 IGMP Overview

The Internet Group Management Protocol (IGMP) is a protocol in the TCP/IP protocol suite

used by IPv4 hosts to report their group memberships to any immediately-neighboring multicast

routers.

To receive multicast data, receivers must connect to an IP multicast network and joins

corresponding multicast groups. IGMP defines a signaling mechanism that IP hosts on user

networks use to communicate with multicast routers.

After IGMP is configured on receiver hosts and multicast routers on a shared network segment,

the receiver hosts can dynamically join multicast groups, and multicast routers can manage

multicast group members on the local network.

At present, IGMP has three versions: IGMPv1 (defined in RFC 1112), IGMPv2 (defined in RFC

2236), and IGMPv3 (defined in RFC 3376). All IGMP versions support the Any-SourceMulticast (ASM) model. IGMPv3 can be directly applied to the Source-Specific Multicast

(SSM) model, whereas IGMPv1 and IGMPv2 can be applied to the SSM model after SSM

mapping is configured.

Figure 2-1IGMP networking

HostA HostB HostC

Ethernet

SwitchA SwitchB

Multicast network

IGMP IGMP

As shown in Figure 2-1, IGMP is configured on the receiver hosts and switches on the shared

network segment.

l If a user network segment connects to multiple switches, one switch is elected as the querier

to periodically send Query messages to the network segment.

l The querier periodically sends Query messages to hosts and receives Report and Leave

messages from hosts. From these messages, the querier obtains information about receivers

(members) of multicast groups on network segments connected to its interfaces. If a

network segment has members of a multicast group, the switches forward multicast data

packets to this network segment. If a network segment has no multicast member, theswitches do not forward multicast data packets to this network segment.





18


30/281

l Hosts send Report messages to join multicast groups. If a host is running IGMPv2 or

IGMPv3, it can proactively leave a multicast group by sending a Leave message when it

does not need to receive multicast data of the multicast group.

2.2 IGMP Features Supported by the SwitchThe IGMP features supported by the switch include basic IGMP settings, Router-Alert option,

IGMP querier, SSM mapping.

NOTE

On the CE series switches, IGMP can be configured only on VLANIF and loopback interfaces. In this document,

IGMP is configured on VLANIF interfaces unless otherwise specified. Before configuring IGMP on a VLANIF

interface, add physical interfaces to the corresponding VLAN.

Basic IGMP Functions

The switch supports the following basic IGMP settings:

l IGMP versions, including IGMPv1, IGMPv2, and IGMPv3. These IGMP versions define

different IGMP messages. To ensure normal communication between the switch and

receiver hosts, configure compatible IGMP versions on the switch and hosts. (A later IGMP

version running on the switch is compatible with an earlier IGMP version running on hosts.)

l Static multicast groups. When an interface connects to long-term members of a multicast

group, you can statically bind the interface to the multicast group so that the group members

can receive multicast data quickly and steadily.

l Range of multicast groups that an interface can join. You can apply an ACL to an interface

to limit the range of the multicast groups that the interface serves. This configuration

improves security of IGMP applications.

IGMP Performance Optimization

You can configure the following items on the switch to improve IGMP security or network

performance:

l Router-Alert option: To improve device security, configure the switch to accept only IGMP

packets with the Router-Alert option.

l Querier: Proper querier parameter settings ensure that memberships can be updated quickly

and prevent network congestion caused by excessive IGMP packets.

l Fast leave: This function allows fast response to Leave messages sent by hosts and saves

network bandwidth.

l IGMP on-demand: This function maintains memberships based on service requirements of

multicast members, reducing packets transmitted on the network.

l IGMP message filtering: This function filters IGMP messages received on an interface

based on source IP addresses, improving security.

SSM Mapping

Source-Specific Multicast (SSM) allows multicast group members to receive multicast data from

the specified multicast sources. Only IGMPv3 supports the SSM model. If some hosts can run

only IGMPv1 or IGMPv2, you can configure SSM mapping on the switch so that the switch canprovide the SSM service for these hosts.





19


31/281

2.3 Default Configuration

This section provides the default IGMP configuration.

Table 2-1lists the default IGMP configuration.

Table 2-1Default IGMP configuration

Parameter Default Setting

IP multicast routing Disabled

IGMP Disabled

IGMP version IGMPv2

IGMP SSM mapping Disabled


After basic IGMP configurations are complete on interfaces connected to user networks, hosts

can connect to multicast networks and receive multicast packets.

Pre-configuration Tasks

Before configuring basic IGMP functions, complete the following task:

l Configuring a unicast routing protocol to ensure that IP routes between nodes are reachable

Configuration Process

IGMP needs to be configured on member hosts and switches connected to the hosts. This section

describes how to configure IGMP on a switch.

2.4.1 Enabling IGMPand 2.4.2 Configuring the IGMP Versionare mandatory and other tasks

are optional.

2.4.1 Enabling IGMP

Context

You must enable IP multicast routing before configuring IGMP. Other multicast functions can

be configured only after IP multicast routing is enabled. All the multicast configurations become

invalid when IP multicast routing is disabled.

IGMP is configured on interfaces connected to user hosts.

Procedure

Step 1 Run:





20


32/281

system-view

The system view is displayed.

Step 2 Run:multicast routing-enable

IP multicast routing is enabled.

Step 3 Run:interfaceinterface-typeinterface-number

The interface view is displayed.

Step 4 Run:pim sm

Protocol Independent Multicast-Sparse Mode (PIM-SM) is enabled on the interface.

Before enabling IGMP on an interface, enable PIM-SM on the interface to allow the interfaceto forward multicast data packets.

Step 5 Run:igmp enable

IGMP is enabled on the interface.

Step 6 Run:commit

The configuration is committed.

----End

2.4.2 Configuring the IGMP Version

Context

A switch running a later IGMP version can identify Membership Report messages of an earlier

IGMP version. However, a switch running an earlier IGMP version cannot identify Membership

Report messages of a later IGMP version. To ensure normal IGMP operation, ensure that the

switch runs the same IGMP version as member hosts or a later IGMP version.

If multiple switches exist on a shared network segment, configure the same IGMP version on

all switch interfaces. Otherwise, errors may occur in IGMP operation because interfaces runningdifferent IGMP versions send packets with different formats.

Procedure

Step 1 Run:system-view








21


33/281

Step 3 Run:igmp version{ 1| 2| 3}

The IGMP version is specified for the interface.

By default, an interface runs IGMPv2 after IGMP is enabled on the interface.

Step 4 Run:commit


----End

2.4.3 (Optional) Configuring a Static Multicast Group on anInterface

Context

You can configure static multicast groups on user-side interfaces of the switch in some scenarios,

for example:

l There are long-term group members on a shared network segment, and the switch needs to

forward multicast data to these group members quickly and steadily.

l A network segment has no group member or hosts on the network segment cannot send

Report messages, but multicast data needs to be sent to this network segment.

After a static multicast group is configured on an interface, the switch considers that the multicast

group always has members on the network segment of the interface. Therefore, the switch always

forwards multicast data of the multicast group.

Procedure





Step 3 Run:igmp static-groupgroup-address[ inc-step-mask{ group-mask| group-mask-length}

numbergroup-number] [ sourcesource-address]

The interface is statically bound to a multicast group or a source-group.

If the interface is a loopback interface, the switch forwards the received data only when a user

requests the data. This saves bandwidth. If the interface is a VLANIF interface, the switch

forwards the received data immediately.

By default, no static multicast group is configured on an interface.

Step 4 Run:commit





22


34/281


----End

2.4.4 (Optional) Configuring the Range of Multicast Groups Thatan Interface Can Join

Context

To enable hosts on the same network segment as an interface to receive packets of specified

multicast groups, use an ACL to filter Membership Report messages received on the interface.

This ACL allows the switch to maintain only memberships of the interface in these multicast

groups. For details on how to configure an ACL, see "ACL Configuration" in the CloudEngine

6800&5800 Series Switches Configuration Guide - Security.

Procedure





Step 3 Run:

igmp group-policy{ acl-number| acl-nameacl-name} [ 1| 2| 3]

An ACL is applied to specify the range of multicast groups that the interface can join.

By default, an interface can join any multicast group.

Step 4 Run:commit


----End

2.4.5 Checking the Configuration

Context

After completing basic IGMP configuration on an interface, you can run the following

commands in any view to check the IGMP configuration, IGMP running information, and

membership information on the interface.

Procedure

l Run the display igmp interface[ interface-typeinterface-number| up| down]

[ verbose] command to check the IGMP configuration and running information on aninterface.





23


35/281

l Run the display igmp group[group-address| interfaceinterface-typeinterface-

number]*static[ verbose] command to check information about members of a static

multicast group.

l Run the display igmp group[group-address| interfaceinterface-typeinterface-

number] *[ verbose] command to check information about the members that havedynamically joined a multicast group.

----End

2.5 Optimizing IGMP Performance

After being enabled, IGMP can work normally using the default configuration. You can also

adjust IGMP parameter settings to enhance network security and performance.

Pre-configuration Tasks


Configuration Process

You can perform the following configuration tasks in any sequence as required.

2.5.1 Configuring the Router-Alert Option

Context

Generally, a network device sends a packet to the corresponding protocol module for processingonly when the destination address of the packet is the address of a local interface. According to

this rule, IGMP packets cannot be sent to the IGMP module because their destination addresses

are multicast addresses but not a local interface address. As a result, the network device cannot

maintain group memberships. The Router-Alert option is introduced to solve this problem. If a

packet contains the Router-Alert option in the IP header, devices that receive the packet send

the packet to the corresponding protocol module without checking the destination IP address of

the packet.

By default, the switch sends received IGMP packets to the IGMP module for processing no

matter whether the packets have the Router-Alert option in their IP headers. This ensures

compatibility between the switch and other de

Date post:	03-Jun-2018
Category:	Documents
Upload:	menganofulano
View:	238 times
Download:	0 times

CloudEngine 6800&5800 V100R001C00 Configuration Guide - Multicast 04.pdf

Documents